EBS R12.2 ADOP Patching & Issues

ADOP Patching Cycle

# Prepare for patching:
$ adop phase=prepare

# Apply patches:
$ adop phase=apply patches=<patch number>

# Finalize patch application:
$ adop phase=finalize

# Perform cutover:
$ adop phase=cutover

$ . <EBS_ROOT>/EBSapps.env run

These steps are performed post-cutover.
$ perl <AD_TOP>/bin/admkappsutil.pl

This will create the appsutil.zip file in <INST_TOP>/admin/out.

On the database tier, as the oracle user:

Copy or ftp the appsutil.zip file to the RDBMS_ORACLE_HOME, 

then run the following commands:

$ cd <RDBMS_ORACLE_HOME>
$ unzip -o appsutil.zip

Run AutoConfig on the database tier.

Run AutoConfig on the run file system of each application tier node.

Start the application tier services. 

# Perform cleanup:
$ adop phase=cleanup

$ adop phase=fs_clone 

ADOP Important queries 

select ADOP_SESSION_ID,PREPARE_STATUS,APPLY_STATUS,
FINALIZE_STATUS,CUTOVER_STATUS,CLEANUP_STATUS,
ABORT_STATUS,STATUS,ABANDON_FLAG,NODE_NAME 
from AD_ADOP_SESSIONS order by ADOP_SESSION_ID;

Note: STATUS
N - Not Applied In the current node but applied in other nodes
R - Patch Application is going on.
H - Patch failed in the middle. (Hard Failure)
F - Patch failed in the middle but user tried to skip some failures.
S - Patch Application succeeded after skipping the failed jobs.
Y - Patch Application succeeded.
C - Reserved for clone and config_clone. Indicates clone completed 

select ADOP_SESSION_ID, BUG_NUMBER, STATUS, 
APPLIED_FILE_SYSTEM_BASE, PATCH_FILE_SYSTEM_BASE, 
ADPATCH_OPTIONS, NODE_NAME, END_DATE, CLONE_STATUS
from ad_adop_session_patches
order by end_date desc; 

ADOP Patching Issues

Issue :

Error while running command: adop phase=prepare

ERROR at line 1:

ORA-20008: No Concurrent Manager is defined that can run concurrent program

ADZDPATCH

ORA-6512: at "APPS.AD_ZD_ADOP", line 240

Solution:

FNDLOAD
 apps/apps 0 Y UPLOAD $FND_TOP/patch/115/import/afcpprog.lct 
$AD_TOP/patch/115/import/US/adzdpatch.ldt - CUSTOM_MODE=FORCE