[UNEXPECTED]Master node for the current patching cycle is node_name.

Error:

Checking for existing adop sessions.
    Continuing with existing session [Session ID: 13].
    [UNEXPECTED]Master node for the current patching cycle is Node_name.
    [UNEXPECTED]Options such as "allnodes=yes" or "allnodes=no action=db" must be run from the master node.
    [UNEXPECTED]Unrecoverable error occurred. Exiting current adop session.


[STATEMENT] Please run adopscanlog utility, using the command

"adopscanlog -latest=yes"

to get the list of the log files along with snippet of the error message corresponding to each log file.


adop exiting with status = 2 (Fail)


Cause:
This issue normally occurs on cloned instance due to invalid entries in ADOP_VALID_NODES and TXK_TCC_RESULTS table.
Refer: http://www.global-dba.com/2017/12/running-adop-fails-with-error-etcc-not.html

Solution:
Login with apps user and perform the following tasks.

SQL> create table apps.ad_adop_sessions_bkp as select * from apps.ad_adop_sessions;

Table created.

update apps.ad_adop_sessions
set node_name='node_name'
where ADOP_SESSION_ID=13

SQL> commit;

Commit complete.

SQL>

Now abort patch session and run cleanup:

$ adop phase=abort
$ adop phase=cleanup cleanup_mode=full

You can now run the patching successfully on cloned instance

adop phase=prepare ORA-20008: No Concurrent Manager is running that can run concurrent program

Error

Error while running command: adop phase=prepare

SQL> SQL> Connected.
SQL> select AD_ZD_ADOP.WAIT_FOR_CP_TO_RUN(10847151) from dual
       *
ERROR at line 1:
ORA-20008: No Concurrent Manager is running that can run concurrent program
ADZDPATCH
ORA-06512: at "APPS.AD_ZD_ADOP", line 282
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining 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.

Solution

Set the Run filesystem / environment and run command:

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

Reference: Doc ID 1587419.1

ADOP Prepare Phase Fails With "Error calling runFSSanityValidateConfig"

Error

[UNEXPECTED]Error occurred running "perl /u01/app/fs1/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPPreparePhaseSanityCheck.pl -contextfile=/u01/app/fs1/inst/apps/QA_erpqa/appl/admin/QA_erpqa.xml -patchcontextfile=/u01/app/fs2/inst/apps/QA_erpqa/appl/admin/QA_erpqa.xml -promptmsg=hide -mode=update -console=off -sessionid=7 -timestamp=20180211_103444 -outdir=/u01/app/fs_ne/EBSapps/log/adop/7/20180211_103444/prepare/erpqa -action=filesystemcheck"
    [UNEXPECTED]Error calling runFSSanityValidateConfig subroutine
    Stopping services on patch file system.
    Stopping admin server.
    Stopping node manager.
    [ERROR]     Prepare phase has failed.

Solution

To resolve the issue test the following steps in a development instance where the issue can be reproduced and then migrate accordingly:
1. Execute the following ABORT process:

$ adop phase=abort
$ adop phase=cleanup cleanup_mode=full
$ adop phase=fs_clone

2. Increase the file system space to 25 GBs (or more depending on your available resources).

3. Run the ADOP Prepare phase again:
$ adop phase=prepare

4. Confirm the prepare phase completes successfully and the above errors no longer appear in the log.

Reference: Doc ID 2223374.1

Error 1 occurred while Executing txkADOPValidation script on host

Error

Lines #(78-83):
    [PROCEDURE] Calling: /u01/app/fs1/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPValidations.pl
    [EVENT]     Log: /u01/app/fs_ne/EBSapps/log/adop/7/20180211_102321/prepare/validate/erpqa
    [UNEXPECTED]Error occurred running "perl /u01/app/fs1/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPValidations.pl  -contextfile=/u01/app/fs1/inst/apps/QA_erpqa/appl/admin/QA_erpqa.xml -patchctxfile=/u01/app/fs2/inst/apps/QA_erpqa/appl/admin/QA_erpqa.xml -phase=prepare -logloc=/u01/app/fs_ne/EBSapps/log/adop/7/20180211_102321/prepare/validate/erpqa -promptmsg=hide"
    [UNEXPECTED]Error 1 occurred while Executing txkADOPValidation script on erpqa
[PROCEDURE] [START 2018/02/11 10:24:20] Unlocking sessions table

[STATEMENT] Unlocking ad_adop_sessions table for erpqa with wait interval of 60 seconds and number of tries 2

Solution

To fix this issue test the following to upload the missing PATCH context file to the database:
1. Get the value of your patch context file.
    1.1. Source your PATCH file system
    1.2. Echo the value of $CONTEXT_FILE and take note of it. You will use this value in step #3.
2. Source the RUN filesystem
3. Execute the following command on the run filesystem to upload the patch context file to the database.

$ADJVAPRG oracle.apps.ad.autoconfig.oam.CtxSynchronizer \
action=upload \
contextfile=<Enter Your Full Patch Context XML File Location> \
logfile=/tmp/patchctxupload.log

For Example:

$ADJVAPRG oracle.apps.ad.autoconfig.oam.CtxSynchronizer \
action=upload \
contextfile=/data1/oracle/EBSDEV/fs2/inst/apps/EBSDEV_ebsapp01/appl/admin/EBSDEV_ebsapp01.xml \
logfile=/tmp/patchctxupload.log

 Note: the context file parameter should point to the physical location of the patch context file in your system
4. Run the following query and it should return one entry for the recently uploaded context file.

select distinct(PATH) from FND_OAM_CONTEXT_FILES where NAME not in ('TEMPLATE','METADATA','config.txt') and CTX_TYPE='A' and (status is null or upper(status) in ('S','F')) and EXTRACTVALUE(XMLType(TEXT),'//file_edition_type') = 'patch';

Reference: Doc ID 2090393.1

Running ADOP Fails With Error "ETCC Not Run In The Database Node"

Error:     ETCC not run in the database node [Node Name]
                The EBS Technology Codelevel Checker needs to be run on the database node.
                It is available as Patch 17537119.

Cause:
Mismatch in host name between FND_NODES and TXK_TCC_RESULTS tables.

Solution:
UPDATE applsys.txk_tcc_results SET node_name ='<node name>';


Run ADOP again and see if it fixes the issue.

Doc ID 2191678.1