Problem:
One of our guys was trying to configure the integration between Oracle GRC Application Access Controls Governor 8.5 to GRC Intelligence 3.0.
This is done by the following:
Investigation:
The Tomcat catalina log (in /u01/app/tomcat/apache-tomcat-5.5.28/logs/catalina.out) showed:
The grcc.log showed the following, and the error was blatantly obvious:
Solution:
1. Fixing the username (which happened to be “gri” and password was all that was needed).
Applicable Versions:
One of our guys was trying to configure the integration between Oracle GRC Application Access Controls Governor 8.5 to GRC Intelligence 3.0.
This is done by the following:
- Log in to AACG (http://host:port/grcc)
- Click on Administration
- Click on Application Configuration
- Click on the Analytics Integration tab
- Enter your connect information, test, and save
Data analytics database connection test failed.
Investigation:
The Tomcat catalina log (in /u01/app/tomcat/apache-tomcat-5.5.28/logs/catalina.out) showed:
GrccConfig: log location will be: /u01/app/tomcat/apache-tomcat-5.5.28/webapps/grcc/log/grcc.log
GrccConfig: log location will be: /u01/app/tomcat/apache-tomcat-5.5.28/webapps/grcc/log/grcc.log
GrccConfig: log location will be: /u01/app/tomcat/apache-tomcat-5.5.28/webapps/grcc/log/grcc.log
GrccConfig: log location will be: /u01/app/tomcat/apache-tomcat-5.5.28/webapps/grcc/log/grcc.log
GrccConfig: log location will be: /u01/app/tomcat/apache-tomcat-5.5.28/webapps/grcc/log/grcc.log
GrccConfig: log location will be: /u01/app/tomcat/apache-tomcat-5.5.28/webapps/grcc/log/grcc.log
GrccConfig: log location will be: /u01/app/tomcat/apache-tomcat-5.5.28/webapps/grcc/log/grcc.log
The grcc.log showed the following, and the error was blatantly obvious:
2010-04-15 11:46:45,397 ERROR [http-8080-Processor13] DBConfig:1304 SQL Exception Occured
java.sql.SQLException: ORA-01017: invalid username/password; logon denied
java.sql.SQLException: ORA-01017: invalid username/password; logon denied
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:331)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:283)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:278)
at oracle.jdbc.driver.T4CTTIoauthenticate.receiveOauth(T4CTTIoauthenticate.java:791)
at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:362)
at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:439)
at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:165)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:331)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:283)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:278)
at oracle.jdbc.driver.T4CTTIoauthenticate.receiveOauth(T4CTTIoauthenticate.java:791)
at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:362)
at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:439)
at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:165)
Solution:
1. Fixing the username (which happened to be “gri” and password was all that was needed).
Applicable Versions:
- Oracle GRC Application Access Controls Governor 8.5
- Oracle GRC Intelligence 3.0
No comments:
Post a Comment