My Oracle Support Banner

18.10.0.0.200414 Windows Bundle Patch May Fail in Postpatch Phase at mgmtca with Error CLSRSC-180 (Doc ID 2697152.1)

Last updated on AUGUST 16, 2020

Applies to:

Oracle Database - Enterprise Edition - Version 18.9.0.0.0 to 18.10.0.0.0 [Release 18]
Microsoft Windows x64 (64-bit)

Symptoms

 When applying 18.10.0.0.200414 on Windows RAC environment,following error
will occur.

>rootcrs.bat -postpatch -nonrolling
Using configuration parameter file: D:\app\grid\18.0.0\grid\crs\install\crsconfig_params
The log of current session can be found at:
D:\app\Administrator\crsdata\node2\crsconfig\crs_postpatch_node2_2020-07-02_07-55-07AM.log
CRS-4123: Starting Oracle High Availability Services-managed resources
CRS-2672: Attempting to start 'ora.mdnsd' on 'node2'
CRS-2672: Attempting to start 'ora.evmd' on 'node2'
CRS-2676: Start of 'ora.mdnsd' on 'node2' succeeded
CRS-2676: Start of 'ora.evmd' on 'node2' succeeded
CRS-2672: Attempting to start 'ora.gpnpd' on 'node2'
CRS-2676: Start of 'ora.gpnpd' on 'node2' succeeded
CRS-2672: Attempting to start 'ora.gipcd' on 'node2'
CRS-2676: Start of 'ora.gipcd' on 'node2' succeeded
CRS-2672: Attempting to start 'ora.crf' on 'node2'
CRS-2672: Attempting to start 'ora.cssdmonitor' on 'node2'
CRS-2676: Start of 'ora.crf' on 'node2' succeeded
CRS-2676: Start of 'ora.cssdmonitor' on 'node2' succeeded
CRS-2672: Attempting to start 'ora.cssd' on 'node2'
CRS-2676: Start of 'ora.cssd' on 'node2' succeeded
CRS-2672: Attempting to start 'ora.ctssd' on 'node2'
CRS-5014: Agent "ORAROOTAGENT" timed out starting process "D:\app\grid\18.0.0\grid\bin\acfsload.bat" for action "check": details at "(:CLSN00009:)" in "D:\app\Administrator\diag\crs\node2\crs\trace\ohasd_orarootagent_system.trc"
CRS-2676: Start of 'ora.ctssd' on 'node2' succeeded
CRS-2672: Attempting to start 'ora.asm' on 'node2'
CRS-2672: Attempting to start 'ora.crsd' on 'node2'
CRS-2676: Start of 'ora.asm' on 'node2' succeeded
CRS-5014: Agent "ORAROOTAGENT" timed out starting process "D:\app\grid\18.0.0\grid\bin\acfsload.bat" for action "check": details at "(:CLSN00009:)" in "D:\app\Administrator\diag\crs\node2\crs\trace\ohasd_orarootagent_system.trc"
CRS-2676: Start of 'ora.crsd' on 'node2' succeeded
CRS-5014: Agent "ORAROOTAGENT" timed out starting process "D:\app\grid\18.0.0\grid\bin\acfsload.bat" for action "check": details at "(:CLSN00009:)" in "D:\app\Administrator\diag\crs\node2\crs\trace\ohasd_orarootagent_system.trc"
CRS-6017: Processing resource auto-start for servers: node2
CRS-2672: Attempting to start 'ora.ASMNET1LSNR_ASM.lsnr' on 'node2'
CRS-2677: Stop of 'ora.node2.vip' on 'node1' succeeded
CRS-2672: Attempting to start 'ora.node2.vip' on 'node2'
CRS-2676: Start of 'ora.ASMNET1LSNR_ASM.lsnr' on 'node2' succeeded
CRS-2676: Start of 'ora.node2.vip' on 'node2' succeeded
CRS-2672: Attempting to start 'ora.LISTENER.lsnr' on 'node2'
CRS-2676: Start of 'ora.ons' on 'node2' succeeded
CRS-2676: Start of 'ora.LISTENER_SCAN1.lsnr' on 'node2' succeeded
CRS-2676: Start of 'ora.LISTENER.lsnr' on 'node2' succeeded
CRS-2672: Attempting to start 'ora.asm' on 'node2'
CRS-2676: Start of 'ora.asm' on 'node2' succeeded
CRS-2672: Attempting to start 'ora.DATA.dg' on 'node2'
CRS-2676: Start of 'ora.DATA.dg' on 'node2' succeeded
CRS-6016: Resource auto-start has completed for server node2
CRS-6024: Completed start of Oracle Cluster Ready Services-managed resources
CRS-4123: Oracle High Availability Services has been started.
Oracle Clusterware active version on the cluster is [18.0.0.0.0]. The cluster upgrade state is [NORMAL]. The cluster active patch level is [1801138106].
SQL Patching tool version 18.0.0.0.0 Production on Thu Jul 2 08:27:43 2020
Copyright (c) 2012, 2020, Oracle. All rights reserved.

Log file for this invocation: D:\app\Administrator\cfgtoollogs\sqlpatch\sqlpatch_11068_2020_07_02_08_27_44\sqlpatch_invocation.log

Connecting to database...OK
Gathering database info...done

Note: Datapatch will only apply or rollback SQL fixes for PDBs
that are in an open state, no patches will be applied to closed PDBs.
Please refer to Note: Datapatch: Database 12c Post Patch SQL Automation
(Doc ID 1585822.1)

Bootstrapping registry and package to current versions...done
Determining current state...done

Current state of interim SQL patches:
Interim patch 28267731 (WINDOWS OJVM BUNDLE PATCH : 18.3.0.0.180717 (28267731)):
Binary registry: Not installed
PDB CDB$ROOT: Applied successfully on 03-APR-19 10.33.03.310000 PM
PDB GIMR_DSCREP_10: Applied successfully on 03-APR-19 10.54.59.537000 PM
PDB PDB$SEED: Applied successfully on 03-APR-19 10.54.59.537000 PM

Current state of release update SQL patches:
Binary registry:
18.10.0.0.0 Release_Update 2003112140: Installed
PDB CDB$ROOT:
Applied 18.3.0.0.0 Release_Update 1808132056 successfully on 03-APR-19 10.33.03.224000 PM
PDB GIMR_DSCREP_10:
Applied 18.3.0.0.0 Release_Update 1808132056 successfully on 03-APR-19 10.54.59.250000 PM
PDB PDB$SEED:
Applied 18.3.0.0.0 Release_Update 1808132056 successfully on 03-APR-19 10.54.59.250000 PM

Adding patches to installation queue and performing prereq checks...done
Installation queue:
For the following PDBs: CDB$ROOT PDB$SEED GIMR_DSCREP_10
The following interim patches will be rolled back:
28267731 (WINDOWS OJVM BUNDLE PATCH : 18.3.0.0.180717 (28267731))
Patch 30901451 (Windows Database Bundle Patch : 18.10.0.0.200414 (30901451)):
Apply from 18.3.0.0.0 Release_Update 1808132056 to 18.10.0.0.0 Release_Update 2003112140
No interim patches need to be applied

Installing patches...
Patch installation complete. Total patches installed: 6

Validating logfiles...done
Patch 28267731 rollback (pdb CDB$ROOT): SUCCESS
logfile: D:\app\Administrator\cfgtoollogs\sqlpatch\28267731\22301563/28267731_rollback__MGMTDB_CDBROOT_2020Jul02_08_40_07.log (no errors)
Patch 30901451 apply (pdb CDB$ROOT): SUCCESS
logfile: D:\app\Administrator\cfgtoollogs\sqlpatch\30901451\23453832/30901451_apply__MGMTDB_CDBROOT_2020Jul02_08_40_21.log (no errors)
Patch 28267731 rollback (pdb PDB$SEED): SUCCESS
logfile: D:\app\Administrator\cfgtoollogs\sqlpatch\28267731\22301563/28267731_rollback__MGMTDB_PDBSEED_2020Jul02_08_58_51.log (no errors)
Patch 30901451 apply (pdb PDB$SEED): SUCCESS
logfile: D:\app\Administrator\cfgtoollogs\sqlpatch\30901451\23453832/30901451_apply__MGMTDB_PDBSEED_2020Jul02_08_59_12.log (no errors)
Patch 28267731 rollback (pdb GIMR_DSCREP_10): SUCCESS
logfile: D:\app\Administrator\cfgtoollogs\sqlpatch\28267731\22301563/28267731_rollback__MGMTDB_GIMR_DSCREP_10_2020Jul02_08_58_50.log (no errors)
Patch 30901451 apply (pdb GIMR_DSCREP_10): SUCCESS
logfile: D:\app\Administrator\cfgtoollogs\sqlpatch\30901451\23453832/30901451_apply__MGMTDB_GIMR_DSCREP_10_2020Jul02_08_59_09.log (no errors)
SQL Patching tool complete on Thu Jul 2 09:14:33 2020
[Worker 2] [ 2020-07-02 09:14:44.626 UTC ] [Semaphore.acquire:109] SyncBufferFull:Acquire called by thread Worker 2 m_count=0

[Worker 0] [ 2020-07-02 09:14:44.635 UTC ] [Semaphore.acquire:109] SyncBufferFull:Acquire called by thread Worker 0 m_count=0

[Worker 3] [ 2020-07-02 09:14:44.646 UTC ] [Semaphore.acquire:109] SyncBufferFull:Acquire called by thread Worker 3 m_count=0

[Worker 1] [ 2020-07-02 09:14:44.655 UTC ] [Semaphore.acquire:109] SyncBufferFull:Acquire called by thread Worker 1 m_count=0

[Worker 3] [ 2020-07-02 09:14:44.646 UTC ] [Semaphore.acquire:109] SyncBufferFull:Acquire called by thread Worker 3 m_count=0

[Worker 1] [ 2020-07-02 09:14:44.655 UTC ] [Semaphore.acquire:109] SyncBufferFull:Acquire called by thread Worker 1 m_count=0

[GetActiveNodesThread] [ 2020-07-02 09:14:44.656 UTC ] [Semaphore.acquire:109] SyncBufferFull:Acquire called by thread GetActiveNodesThread m_count=0

2020/07/02 09:18:54 CLSRSC-180: An error occurred while executing the command ''D:\app\grid\18.0.0\grid\bin\mgmtca' <--**
Died at D:\app\grid\18.0.0\grid\crs\install/crspatch.pm line 1821.

>

 

 mgmtca.trc shows the following error.

mgmtca.trc

----
[main] [ 2020-07-02 09:18:50.839 UTC ] [MgmtUtil.isMgmtdbOnCurrentNode:193] Management DB is running on node2. Local node is node2
[main] [ 2020-07-02 09:18:50.850 UTC ] [Util.<init>:103] Util Instance created.
[main] [ 2020-07-02 09:18:50.850 UTC ] [has.UtilNative.Native] prsr_trace: Native: getCRSHome

[main] [ 2020-07-02 09:18:50.851 UTC ] [has.UtilNative.Native] prsr_trace: Native: getCRSHome crs_home=D:\app\grid\18.0.0\grid(**)
[main] [ 2020-07-02 09:18:50.851 UTC ] [HASContext.getCRSHome:643] D:\app\grid\18.0.0\grid
[main] [ 2020-07-02 09:18:50.851 UTC ] [Util.getCRSHome:612] getCRSHome: ret=D:\app\grid\18.0.0\grid
[main] [ 2020-07-02 09:18:50.851 UTC ] [Mgmtjdbc.connectMGMTDB:413] Connection String=jdbc:oracle:oci:@(DESCRIPTION=(ADDRESS=(PROTOCOL=beq)(PROGRAM=D:\app\grid\18.0.0\grid\bin\oracle)(ARGV0=oracle-MGMTDB)(ARGS='(DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq)))')(ENVS='ORACLE_HOME=D:\app\grid\18.0.0\grid,ORACLE_SID=-MGMTDB')))
java.lang.Error: Incompatible version of libocijdbc[Jdbc:180000, Jdbc-OCI:189000 <--** version mismatch.
at oracle.jdbc.driver.T2CConnection$1.run(T2CConnection.java:4300)
at java.security.AccessController.doPrivileged(Native Method)
at oracle.jdbc.driver.T2CConnection.loadNativeLibrary(T2CConnection.java:4293)
at oracle.jdbc.driver.T2CConnection.logon(T2CConnection.java:478)
at oracle.jdbc.driver.PhysicalConnection.connect(PhysicalConnection.java:782)
at oracle.jdbc.driver.T2CDriverExtension.getConnection(T2CDriverExtension.java:60)
at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:704)
at java.sql.DriverManager.getConnection(DriverManager.java:664)
at java.sql.DriverManager.getConnection(DriverManager.java:208)
at oracle.cluster.mgmtcommon.Mgmtjdbc.connectMGMTDB(Mgmtjdbc.java:418)
at oracle.cluster.mgmtcommon.Mgmtjdbc.connect(Mgmtjdbc.java:393)
at oracle.cluster.mgmtcommon.MgmtUtil.getClusterVersion(MgmtUtil.java:1117)
at oracle.cluster.mgmtca.Mgmtca.execute(Mgmtca.java:508)
at oracle.cluster.mgmtca.Mgmtca.main(Mgmtca.java:335)
------

 

 

Changes

 apply WINBP(18.10.0.0.200414) on RAC environment

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.