000036810 - RSA Identity Governance & Lifecycle fails to start with "Connection is not associated with a managed connection" message

Document created by RSA Customer Support Employee on Oct 9, 2018
Version 1Show Document
  • Comment • 0
  • View in full screen mode

Article Content

Article Number000036810
Applies ToRSA Product Set: Identity Governance & Lifecycle
RSA Product/Service Type: Hosted
RSA Version/Condition: 7.0.2, 7.1.0
Product Name: Oracle
Issue
  • RSA Identity Governance & Lifecycle fails to start with the following error displayed in the console.

Initialization operations completed with errors. Please resolve the problem(s) before the application server can accept requests. Connection is not associated with a managed connection.org.jboss.jca.adapters.jdbc.jdk7.WrappedConnectionJDK7@738e9520  
 


User-added image


  • The aveksaServer.log file (/home/oracle/wildfly-8.2.0.Final/standalone/log/aveksaServer.log) shows the following errors on startup:


10/03/2018 14:57:28.830 ERROR (MSC service thread 1-12) [com.aveksa.migration.jdbctool.CheckDatabase] Connection is not associated with a managed connection.org.jboss.jca.adapters.jdbc.jdk7.WrappedConnectionJDK7@738e9520
10/03/2018 14:57:28.830 ERROR (MSC service thread 1-12) [com.aveksa.migration.jdbctool.CheckDatabase] 

****************************************

Patching has failed

Connection is not associated with a managed connection.org.jboss.jca.adapters.jdbc.jdk7.WrappedConnectionJDK7@738e9520

****************************************


10/03/2018 14:57:28.900 INFO  (MSC service thread 1-12) [com.aveksa.server.runtime.AveksaSystem] ******************** Aveksa System Initialization End ********************
10/03/2018 14:57:28.901 FATAL (MSC service thread 1-12) [com.aveksa.server.runtime.AveksaSystem] 

****************************************

Initialization has failed!

Connection is not associated with a managed connection.org.jboss.jca.adapters.jdbc.jdk7.WrappedConnectionJDK7@738e9520


****************************************

 

  • The Oracle trace log (/u01/app/oracle/diag/rdbms/avdb/AVDB/trace/AVDB{nnnnn}.trc) shows an ORA-00600 error with the specific argument qkaffsindex3


ORA-00600: internal error code, arguments: [qkaffsindex3], [], [], [], [], [], [], [], [], [], [], []
CauseThis issue is caused by Oracle bug 24530463 - FA: GATHER STATS ON DOO_HEADERS_ALL FAILS W/ ORA-600 [QKAFFSINDEX3], which prevents the database statistics from completing correctly.  See Oracle knowledge article 2395827.1 - Exadata Database is Reporting ORA-00600:[qkaffsindex3] for more information.

 



Resolution
  • For RSA hardware appliances, apply the latest Appliance Updater package which contains all current Oracle patches.
  • For RSA software appliances with external databases, apply the latest Oracle patches.  Specifically this issue is resolved in Oracle patch: 24530463 : Description FA: GATHER STATS ON DOO_HEADERS_ALL FAILS W/ ORA-600 [QKAFFSINDEX3]
NotesThe issue occurs during the running of database statistics.   Database statistics may be run during patching or upgrading, or after certain events such as data collection.  If this issue occurs during patching it may cause the patching to fail. 

Attachments

    Outcomes