[UNEXPECTED]Nodes are listed in the ADOP_VALID_NODES table but not in the FND_NODES table


[UNEXPECTED]Nodes are listed in the ADOP_VALID_NODES table but not in the FND_NODES table.




 bash-5.0$ adop phase=prepare 

Enter the APPS password:

Enter the SYSTEM password:

Enter the WLSADMIN password: Validating credentials. Initializing.

    Run Edition context  : /erp_appl/apps/fs2/inst/apps/ERPDEV7_au1637/appl/admin/ERPDEV7_au1637.xml

    Patch edition context: /erp_appl/apps/fs1/inst/apps/ERPDEV7_au1637/appl/admin/ERPDEV7_au1637.xml

    Patch file system free space: 252.29 GB Validating system setup.

    [UNEXPECTED]Nodes "appsnode1,appsnode2,appsnode3,appsnode4,appsnode5,appsnode6" are listed in the ADOP_VALID_NODES table but not in the FND_NODES table.

    [UNEXPECTED]To correct this, run AutoConfig on nodes "appsnode1,appsnode2,appsnode3,appsnode4,appsnode5,appsnode6"

    [UNEXPECTED]Error determining whether this is a multi-node instance 

[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)

bash-5.0$ 



Solution:-


Please ensure you have taken a valid backup of your DB & APPS Tier before doing below action plan.


1. Backup the fnd_oam_context_files, fnd_nodes, and adop_valid_nodes tables in the EBS env:


sqlplus apps/apps


create table fnd_oam_context_files_bkp1 as select * from fnd_oam_context_files;


create table fnd_nodes_bk1 as select * from fnd_nodes;


create table adop_valid_nodes_bk1 as select * from adop_valid_nodes;


2. Truncate the following tables:


truncate table applsys.fnd_oam_context_files;


truncate table applsys.fnd_nodes;


truncate table applsys.adop_valid_nodes;


3. Run AutoConfig on the DB tier


4. Run Autoconfig on the run file system.


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(SYS).


a. Disable the ebs_login trigger using the following SQL.


SQL> conn system


Enter password:


Connected.


SQL> show user


USER is “SYSTEM”


SQL>


SQL> alter trigger ebs_logon disable;


Trigger altered.


b. At this time Run autoconfig with the patch env sourced.


c. Enable the ebs_login trigger using the following SQL.


SQL> show user


USER is “SYSTEM”


SQL> alter trigger ebs_logon enable;


6. Check if entries are appropriate in the tables and if it looks good, you can go ahead with the prepare phase.

appsdbahelp

17+ years of experience in Oracle Database, Oracle Cloud Infrastructure(OCI), Oracle EBS on Cloud, Oracle E-Business Suite, DevOps tools, Oracle WebLogic, Oracle Application Server, Oracle Access Manager and various Operating System flavors including Redhat Linux, UNIX (Solaris, HP-UX) and Windows. Expert in Oracle9i/10g/11g/12c/19c database administration, upgrade, configuration and tuning. Experience in Oracle E-Business Suite technological stack, including architecture, installation, configuration, maintenance, tuning, cloning and patching procedures. Expert in Oracle Cloud Infrastructure(OCI), Oracle EBS On Cloud and Oracle EBS Cloud Manager Experience with Oracle Cloud Solution and Expert of Oracle ERP/Oracle HCM Cloud deployment Experience in Terraform, JSON and chef cloud infrastructure automation framework Knowledge of ASM, Data Guard, Real Application Cluster, Exadata and Exalogic Knowledge of Oracle Enterprise Manager(OEM) Grid Control, Oracle WebLogic, Oracle Internet Directory, Oracle Access Manager and Apache Ability to analyze problem, develops solutions and bring program/project execution to completion.

Post a Comment

Previous Post Next Post