How to fix Unexpectednodes are listed in the ADOP_VALID_NODES table but not in the FND_NODES table.

by

Introduction:-

In this post we will fix the error ‘[UNEXPECTED]Nodes are listed in the ADOP_VALID_NODES table but not in the FND_NODES table’. This error is thrown because unexpectednodes are listed in adop_vali_nodes table.

Execution:-


In this section, we will execute the adop phase=prepare in EBS , so that we can apply the patches.

[applmgr@sa**apps ~]$ adop phase=prepare

Error:-

Enter the APPS password:

Enter the SYSTEM password:

Enter the WLSADMIN password:

Validating credentials.

Initializing.

    Run Edition context  : /oracle/EBSFS/fs1/inst/apps/UAT_sam**apps/appl/admin/UAT_sam**apps.xml

    Patch edition context: /oracle/EBSFS/fs2/inst/apps/UAT_sam**apps/appl/admin/UAT_sam***apps.xml

    Patch file system free space: 482.94 GB

Validating system setup.

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

    [UNEXPECTED]To correct this, run AutoConfig on nodes "erpbackup"

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

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

$sh autoconfig.sh

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 environment 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.

If this article, really helpful for you, may check another article related to Adop error.

You may check another article for same issue, click here.

Leave a Comment