My Oracle Support Banner

opatchauto fails with "MGTCA-1005 : Could not connect to the GIMR. Listener refused the connection with the following error: ORA-12514, TNS:listener does not currently know of service requested in connect descriptor" (Doc ID 3061636.1)

Last updated on DECEMBER 15, 2024

Applies to:

Oracle Database - Enterprise Edition - Version 19.3.0.0.0 and later
Information in this document applies to any platform.

Symptoms

opatchauto fails on 2nd Node , during MGMTDB PostPatch(Datapatch) Actions, as shown below -

$ opatchauto apply <Patch 36916690 Unzip Location>
System initialization log file is <GI Home>/cfgtoollogs/opatchautodb/systemconfig2024-11-09_05-18-13AM.log.

Session log file is <GI Home>/cfgtoollogs/opatchauto/opatchauto2024-11-09_05-18-52AM.log
The id for this session is PUB2

Executing OPatch prereq operations to verify patch applicability on home <GI Home>
Patch applicability verified successfully on home <GI Home>

Executing OPatch prereq operations to verify patch applicability on home <ORACLE Home>
Patch applicability verified successfully on home <ORACLE Home>

Executing patch validation checks on home <GI Home>
Patch validation checks successfully completed on home <GI Home>

Executing patch validation checks on home <ORACLE Home>
Patch validation checks successfully completed on home <ORACLE Home>

Verifying SQL patch applicability on home <ORACLE Home>
SQL patch applicability verified successfully on home <ORACLE Home>

Preparing to bring down database service on home <ORACLE Home>
Successfully prepared home <ORACLE Home> to bring down database service

Performing prepatch operations on CRS - bringing down CRS service on home <GI Home>
Prepatch operation log file location: <GRID Base>/crsdata/<Node2>/crsconfig/crs_prepatch_apply_inplace_<Node2>_2024-11-09_05-44-23AM.log
CRS service brought down successfully on home <GI Home>

Performing prepatch operation on home <ORACLE Home>
Prepatch operation completed successfully on home <ORACLE Home>

Start applying binary patch on home <ORACLE Home>
Binary patch applied successfully on home <ORACLE Home>

Running rootadd_rdbms.sh on home <ORACLE Home>
Successfully executed rootadd_rdbms.sh on home <ORACLE Home>

Performing postpatch operation on home <ORACLE Home>
Postpatch operation completed successfully on home <ORACLE Home>

Start applying binary patch on home <GI Home>
Binary patch applied successfully on home <GI Home>

Running rootadd_rdbms.sh on home <GI Home>
Successfully executed rootadd_rdbms.sh on home <GI Home>

Performing postpatch operations on CRS - starting CRS service on home <GI Home>
Postpatch operation log file location: <GRID Base>/crsdata/<Node2>/crsconfig/crs_postpatch_apply_inplace_<Node2>_2024-11-09_06-27-42AM.log
Failed to start CRS service on home <GI Home>

Execution of [GIStartupAction] patch action failed, check log for more details. Failures:
Patch Target : <Node2>-><GI Home> Type[crs]
Details: [
---------------------------Patching Failed---------------------------------
Command execution failed during patching in home: <GI Home>, host: <Node2>.
Command failed: bash -c "LD_LIBRARY_PATH=<GI Home>/lib:<GI Home>/srvm/lib:/usr/products/grid/patch/36866740/36916690/36917416/files/lib:<GI Home>/lib:<GI Home>/lib:<GI Home>/srvm/lib:<GI Home>/lib:<GI Home>/srvm/lib:<GI Home>/lib <GI Home>/perl/bin/perl -I<GI Home>/perl/lib -I<GI Home>/opatchautocfg/db/dbtmp/bootstrap_<Node2>/patchwork/crs/install -I<GI Home>/opatchautocfg/db/dbtmp/bootstrap_<Node2>/patchwork/xag <GI Home>/opatchautocfg/db/dbtmp/bootstrap_<Node2>/patchwork/crs/install/rootcrs.pl -postpatch"
Command failure output:
Using configuration parameter file: <GI Home>/opatchautocfg/db/dbtmp/bootstrap_<Node2>/patchwork/crs/install/crsconfig_params
The log of current session can be found at:
<GRID Base>/crsdata/<Node2>/crsconfig/crs_postpatch_apply_inplace_<Node2>_2024-11-09_06-27-42AM.log
2024/11/09 06:27:57 CLSRSC-329: Replacing Clusterware entries in file 'oracle-ohasd.service'
Oracle Clusterware active version on the cluster is [19.0.0.0.0]. The cluster upgrade state is [NORMAL]. The cluster active patch level is [760403972].
SQL Patching tool version 19.25.0.0.0 Production on Sat Nov 9 06:32:37 2024
Copyright (c) 2012, 2024, Oracle. All rights reserved.

Log file for this invocation: <GRID Base>/cfgtoollogs/sqlpatch/sqlpatch_41570_2024_11_09_06_32_37/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:
No interim patches found

Current state of release update SQL patches:
Binary registry:
19.25.0.0.0 Release_Update 241010184253: Installed
PDB CDB$ROOT:
Applied 19.24.0.0.0 Release_Update 240627235157 successfully on 21-JUL-24 12.48.52.685257 AM
PDB GIMR_DSCREP_10:
Applied 19.24.0.0.0 Release_Update 240627235157 successfully on 21-JUL-24 12.50.00.103592 AM
PDB PDB$SEED:
Applied 19.24.0.0.0 Release_Update 240627235157 successfully on 21-JUL-24 12.50.01.873934 AM

Adding patches to installation queue and performing prereq checks...done
Installation queue:
For the following PDBs: CDB$ROOT PDB$SEED GIMR_DSCREP_10
No interim patches need to be rolled back
Patch 36912597 (Database Release Update : 19.25.0.0.241015 (36912597)):
Apply from 19.24.0.0.0 Release_Update 240627235157 to 19.25.0.0.0 Release_Update 241010184253
No interim patches need to be applied

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

Validating logfiles...done
Patch 36912597 apply (pdb CDB$ROOT): SUCCESS
logfile: <GRID Base>/cfgtoollogs/sqlpatch/36912597/25871884/36912597_apply__MGMTDB_CDBROOT_2024Nov09_06_34_11.log (no errors)
Patch 36912597 apply (pdb PDB$SEED): SUCCESS
logfile: <GRID Base>/cfgtoollogs/sqlpatch/36912597/25871884/36912597_apply__MGMTDB_PDBSEED_2024Nov09_06_35_05.log (no errors)
Patch 36912597 apply (pdb GIMR_DSCREP_10): SUCCESS
logfile: <GRID Base>/cfgtoollogs/sqlpatch/36912597/25871884/36912597_apply__MGMTDB_GIMR_DSCREP_10_2024Nov09_06_35_05.log (no errors)
SQL Patching tool complete on Sat Nov 9 06:35:54 2024
MGTCA-1005 : Could not connect to the GIMR.

Listener refused the connection with the following error:

ORA-12514, TNS:listener does not currently know of service requested in connect descriptor

2024/11/09 06:36:05 CLSRSC-180: An error occurred while executing the command '<GI Home>/bin/mgmtca applysql'

After fixing the cause of failure Run opatchauto resume

]
OPATCHAUTO-68061: The orchestration engine failed.
OPATCHAUTO-68061: The orchestration engine failed with return code 1
OPATCHAUTO-68061: Check the log for more details.
OPatchAuto failed.

OPatchauto session completed at Sat Nov 9 06:36:11 2024
Time taken to complete the session 77 minutes, 59 seconds

opatchauto failed with error code 42

CRS Postpatch Log shows 

2024-11-09 06:35:54: Starting to apply the application schema patches
2024-11-09 06:35:54: Running as user grid: <GRID Home>/bin/mgmtca applysql
2024-11-09 06:36:05: Removing file /tmp/WGXcV8PAVX
2024-11-09 06:36:05: Successfully removed file: /tmp/WGXcV8PAVX
2024-11-09 06:36:05: pipe exit code: 256
2024-11-09 06:36:05: /bin/su exited with rc=1

2024-11-09 06:36:05: Failed to apply the application schema patches
2024-11-09 06:36:05: Executing cmd: <GRID Home>/bin/clsecho -p has -f clsrsc -m 180 '<GRID Home>/bin/mgmtca applysql'
2024-11-09 06:36:06: Executing cmd: <GRID Home>/bin/clsecho -p has -f clsrsc -m 180 '<GRID Home>/bin/mgmtca applysql'
2024-11-09 06:36:06: Command output:
> CLSRSC-180: An error occurred while executing the command '<GRID Home>/bin/mgmtca applysql'
>End Command output
2024-11-09 06:36:06: CLSRSC-180: An error occurred while executing the command '<GRID Home>/bin/mgmtca applysql'
2024-11-09 06:36:06: ###### Begin DIE Stack Trace ######
2024-11-09 06:36:06: Package File Line Calling
2024-11-09 06:36:06: --------------- -------------------- ---- ----------
2024-11-09 06:36:06: 1: main rootcrs.pl 358 crsutils::dietrap
2024-11-09 06:36:06: 2: crspatch crspatch.pm 2072 main::__ANON__
2024-11-09 06:36:06: 3: crspatch crspatch.pm 2271 crspatch::performPostPatch
2024-11-09 06:36:06: 4: crspatch crspatch.pm 528 crspatch::crsPostPatch
2024-11-09 06:36:06: 5: main rootcrs.pl 371 crspatch::new
2024-11-09 06:36:06: ####### End DIE Stack Trace #######

2024-11-09 06:36:06: ROOTCRS_POSTPATCH checkpoint has failed



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
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.