My Oracle Support Banner

During the Prepare Phase the ADZDPATCH Concurrent Program Fails With AD_ZD_ADOP.WAIT_FOR_CP_TO_RUN and Internal Manager Log Shows Routine AFPCAL Received Failure Code While Parsing or Running Your Concurrent Program CPMGR (Doc ID 2334520.1)

Last updated on OCTOBER 20, 2023

Applies to:

Oracle Concurrent Processing - Version 12.2.5 to 12.2.6 [Release 12.2]
Oracle Concurrent Processing - Version 12.2.8 to 12.2.8 [Release 12.2]
Information in this document applies to any platform.
Reviewed for relevance 1 May 19.

Symptoms

On : 12.2.5 version, Concurrent Manager Issues
Applying HRMS 2017 Patches and the pre-requisites are to upgrade AD,TXK, ATG_PF and HR delta levels.

During the Prepare Phase of the patching cycle, the ADZDPATCH Concurrent Program is failing.

Internal Manager is also unstable and fails to restart.



ERROR
-----------------------

Internal Manager log:

Routine &ROUTINE has attempted to start the internal concurrent manager.  The ICM is already running.  Contact you system administrator for further assistance.afpdlrq received an unsuccessful result from PL/SQL procedure or function FND_DCP.Request_Session_Lock.
Routine FND_DCP.REQUEST_SESSION_LOCK received a result code of 1 from the call to DBMS_LOCK.Request.
Possible DBMS_LOCK.Request resultCall to establish_icm failed
The Internal Concurrent Manager has encountered an error.
Review concurrent manager log file for more detailed information. :
Shutting down Internal Concurrent Manager :
List of errors encountered:
.............................................................................
_ 1 _
Routine AFPCSQ encountered an ORACLE error. .
Review your error messages for the cause of the error. (=<POINTER>)
.............................................................................
List of errors encountered:
.............................................................................
_ 1 _
Routine AFPCAL received failure code while parsing or running your
concurrent program CPMGR
Review your concurrent request log file for more detailed information.
Make sure you are passing arguments in the correct format.
.............................................................................
The <manager name> internal concurrent manager has terminated with status 1 - giving up.

 

ADZDPATCH.ldt log:
Submitting ADZDPATCH concurrent program.
   Waiting for conflicting requests to complete.
   [ERROR]     Failed to execute sql statement:
select AD_ZD_ADOP.WAIT_FOR_CP_TO_RUN(32251926) from dual
   [ERROR]     SQLPLUS error: buffer=
SQL*Plus: Release 10.1.0.5.0 - Production
Copyright (c) 1982, 2005, Oracle.  All rights reserved.
SQL> SQL> Connected.
SQL> select AD_ZD_ADOP.WAIT_FOR_CP_TO_RUN(32251926) from dual
      *
ERROR at line 1:
ORA-20008: No Concurrent Manager is defined that can run concurrent program
ADZDPATCH
ORA-06512: at "APPS.AD_ZD_ADOP", line 274
Disconnected from Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production
With the Partitioning, Automatic Storage Management, OLAP, Advanced Analytics
and Real Application Testing options

   [UNEXPECTED]Error calling runConcurrentProgram subroutine.
   Stopping services on patch file system.
   Stopping admin server.
   Stopping node manager.
   [ERROR]     Prepare phase 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


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