Synchronize FND_NODES, ADOP_VALID_NODES, and FND_OAM_CONTEXT_FILES in 12.2

$ adop phase=prepare

  Enter the APPS password:
  Enter the SYSTEM password:
  Enter the WLSADMIN password:

Validating credentials...

Initializing...
  Run Edition context : /appl/admin/PROD_prodapp1.xml
  Patch edition context: /appl/admin/PROD_prodapp1.xml
*******FATAL ERROR*******
PROGRAM : (/appl/ad/12.0.0/bin/adzdoptl.pl)
TIME : Fri Oct 2 22:06:45 2015
FUNCTION: ADOP::GlobalVars::_GetMandatoryArgs [ Level 1 ]
ERRORMSG: adop is not able to detect any valid application tier nodes in ADOP_VALID_NODES table. 



solution ::

Bring down the application services

1. Backup the fnd_oam_context_files, fnd_nodes, and adop_valid_nodes tables in the EBS env:
      sqlplus applsys/pwd

      create table fnd_oam_context_files_bkp as select * from fnd_oam_context_files;
      create table fnd_nodes_bk as select * from fnd_nodes;
        create table adop_valid_nodes_bk as select * from adop_valid_nodes;

2. Truncate the following tables:

      truncate table fnd_oam_context_files;

      truncate table fnd_nodes;

      truncate table adop_valid_nodes;

       

3.  Run AutoConfig on the DB tier
        Confirm Autoconfig completes successfully

4.  Run Autoconfig on the run file system.
        Confirm Autoconfig completes successfully

5.  Run Autoconfig on the patch file system

Before running Autoconfig on the patch file system the ebs_login trigger MUST be disabled
After the successful completion of Autoconfig the ebs_login trigger MUST be re-enabled.

This needs to be done as the SYSTEM schema user.

a. Disable the ebs_login trigger using the following SQL.

    SQL> alter trigger ebs_logon disable;

•        At this time Run autoconfig with the patch env sourced.
•        Make sure Autoconfig completes ok

b. Enable the ebs_login trigger using the following SQL.

    SQL> alter trigger ebs_logon enable;