|Applies To||RSA Adaptive Authentication (On Premise) |
The database server and connect descriptor must be configured in Websphere according to the Installation Guide for your AA version/service pack. This manual will contain the instructions for configuring Websphere for Oracle.
In v188.8.131.52, that is in the System Installation Guide, chapter 5, "Installing on IBM WebSphere", section "Setting Up an IBM WebSphere Application Server", subsection "Setting Up WebSphere with Oracle".
In v184.108.40.206 SP2, that is in the RSA Adaptive Authentication (On-Premise) 220.127.116.11 SP2 Installation Guide, Appendix B "Setting Up the Application Servers", section "Setting Up WebSphere with Oracle". For v18.104.22.168 SP1 the equivalent is in Chapter 11.
In v7.0, that is in the RSA? Adaptive Authentication (On-Premise) 7.0 Installation and Upgrade Guide , Appendix A "Setting Up the Application Servers", section "Setting Up Websphere with Oracle".
|Issue||Oracle Listener refusing the connection request from Websphere|
Websphere log shows Oracle ORA-12514 errors and IBM DSRA0010E errors such as:
WARN [server.startup : 1]   [org.hibernate.util.JDBCExceptionReporter] - <SQL Error: 12514, SQLState: 66000>
ORA-12514 is an Oracle database error code. See Oracle? Database Error Messages manual for your Oracle version and release, for a description of ORA-12514. You can also use the Oracle oraerr command to obtain this information.
DSRA0010E is an IBM Websphere message code. See the IBM Websphere Application Server Messages manual for your Websphere version, for a description of DSRA0010E.
The connect descriptor configured in Websphere for AA does not match any of the database services configured for the Oracle listener process on the specified database server.
One possible cause is an incorrectly applied Oracle bug fix for CVE-2012-1675 (at http://www.oracle.com/technetwork/topics/security/alert-cve-2012-1675-1608180.html) .
Suggested diagnostic steps:
|Legacy Article ID||a66532|