000035360 - RSA Identity Governance and Lifecycle fails to start after patching with error "Patching has failed" and "Closed Connection"

Document created by RSA Customer Support Employee on Jul 14, 2017
Version 1Show Document
  • View in full screen mode

Article Content

Article Number000035360
Applies ToRSA Product Set:  RSA Identity Governance and Lifecycle
RSA Version/Condition: 7.0.2 P01, 7.0.2 P01 HF01
IssueRSA Identity Governance and Lifecycle fails to startup after patching to 7.0.1 P01 or 7.0.2 P01 HF01.   The /home/oracle/wildfly-8.2.0.Final/standalone/log/aveksaServer.log shows the server startup failing during the CheckDatabase step with the following error:
07/03/2017 11:37:43.615 ERROR (MSC service thread 1-32) [com.aveksa.migration.jdbctool.CheckDatabase] Closed Connection
07/03/2017 11:37:43.615 ERROR (MSC service thread 1-32) [com.aveksa.migration.jdbctool.CheckDatabase]
Patching has failed
Closed Connection

07/03/2017 11:37:43.713 INFO  (MSC service thread 1-32) [com.aveksa.server.runtime.AveksaSystem] ******************** Aveksa System Initialization End ********************
07/03/2017 11:37:43.713 FATAL (MSC service thread 1-32) [com.aveksa.server.runtime.AveksaSystem]
Initialization has failed!
Closed Connection


The Oracle alert.log file shows that Oracle is deployed in compatible mode. 
Please note: The file location for the Oracle alert.log varies depending on the location where Oracle is installed, and the type of Oracle instance.  The filename is in the format alert<hostname>.log and typical locations are similar to /u01/app/12.1.0/grid/log/host01/alerthost01.log.
System parameters with non-default values:
  processes                = 1200
  sessions                 = 2000
  event                    = ""
  sga_max_size             = 80G
  pga_aggregate_limit      = 52G
  sga_target               = 80G
  control_files            = "/control_2/avektst/control02.ctl"
  control_files            = "/control_1/avektst/control01.ctl"
  db_block_size            = 8192
  compatible               = ""

CauseThis issue may occur on remote database instances supplied by the customer if Oracle is deployed in compatible mode.   During the acm startup sequence, the checkdatabase routine will attempt to determine if the supported version of Oracle is installed.  If compatible mode is set to an earlier version, the checkdatabase routine will fail and will incorrectly assume that the patch was not installed correctly. 
ResolutionEnsure that Oracle compatible mode is not enabled.  For more information on configuring Oracle compatible mode, see the following article from the Oracle Help Center entitled What Is Oracle Database Compatibility?
NotesThe patch application is actually installed correctly.   The error message that Patching has failed is misleading.