000038550 - The Oracle 12C January 2020 Appliance Updater fails and prevents the database from starting up in RSA Identity Governance & Lifecycle

Document created by RSA Customer Support Employee on Mar 11, 2020•Last modified by RSA Customer Support Employee on Mar 12, 2020
Version 2Show Document
  • Comment • 0
  • View in full screen mode

Article Content

Article Number000038550
Applies ToRSA Product Set: RSA Identity Governance & Lifecycle
RSA Product/Service Type: Appliance
RSA Version/Condition: 7.1.1, 7.2.x
Product Name: Appliance Updater
 
IssueThe RSA Identity Governance & Lifecycle Oracle 12C January 2020 Appliance Updater fails and after the failure, the database cannot be started.

The rsaimg_updater_Oracle_12C.log file (/var/log/rsaimg_updater_Oracle_12C.log) contains the following messages:

Cannot connect to the database.   The watchdog will start the server when it can connect to the database.



Starting CRS service on home /u01/app/12.1.0/grid Postpatch operation log file location: 
/u01/app/12.1.0/grid/cfgtoollogs/crsconfig/hapatch_2020-03-09_11-51-18AM.log
Failed to start CRS service on home /u01/app/12.1.0/grid
Execution of [xxxxStartupAction] patch action failed, check log for more details. Failures:
Patch Target : server->/u01/app/12.1.0/grid Type[xxxx]
Details: [
---------------------------Patching Failed---------------------------------
Command execution failed during patching in home: /u01/app/12.1.0/grid, host: server.
Command failed:  /u01/app/12.1.0/grid/perl/bin/perl -I/u01/app/12.1.0/grid/perl/lib 
-I/u01/app/12.1.0/grid/opatchautocfg/db/dbtmp/bootstrap_server/patchwork/crs/install 
/u01/app/12.1.0/grid/opatchautocfg/db/dbtmp/bootstrap_server/patchwork/crs/install/roothas.pl -postpatch
Command failure output: 
Using configuration parameter file: 
/u01/app/12.1.0/grid/opatchautocfg/db/dbtmp/bootstrap_server/patchwork/crs/install/crsconfig_params
2020/02/09 11:49:43 CLSRSC-329: Replacing Clusterware entries in file '/etc/inittab'
2020/02/09 11:49:50 CLSRSC-196: ACFS driver install actions failed



OPatch Session completed with warnings.
Log file location: /u01/app/oracle/product/12.1.0/db_1/cfgtoollogs/opatch/opatch2020-02-09_11-54-35AM_1.log

OPatch completed with warnings.
Patch 19509982 Exit Code:
CRS-4622: Oracle High Availability Services autostart is enabled.
CRS-6706: Oracle Clusterware Release patch level ('569727162') 
does not match Software patch level ('3790513828'). Oracle Clusterware cannot be started.
CRS-4000: Command Start failed, or completed with errors.
CRS-4639: Could not contact Oracle High Availability Services
PRCD-1027 : Failed to retrieve database AVDB
PRCR-1070 : Failed to check if resource ora.avdb.db is registered
CRS-0184 : Cannot communicate with the CRS daemon.
Finished installing additional Oracle patch : 19509982 12102180417 for 12.1.0.2.5
PRCR-1070 : Failed to check if resource ora.asm is registered
CRS-0184 : Cannot communicate with the CRS daemon.
PRCR-1070 : Failed to check if resource ora.asm is registered
CRS-0184 : Cannot communicate with the CRS daemon.

 
CauseThis is a known issue reported in engineering tickets ACM-104176 and ACM-103814.
 
ResolutionThis issue is being investigated by the Engineering team in order to provide a permanent resolution in a future release.
 
WorkaroundLogin as the oracle user and execute the following commands:

cd /u01/app/12.1.0/grid/bin/
./clscfg -localpatch
acm startoracle

Attachments

    Outcomes