Nodes “xxxxxx” are listed in the ADOP_VALID_NODES table but not in the FND_NODES table.

[appluat@xxxxxxxx 20190311_165041]$ adop phase =prepare

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

Validating credentials.
ERROR: Invalid WebLogic Admin Server user credentials supplied.
Warning: Your system may have a limit on the number of failed login attempts before the account is locked out.
Enter the WLSADMIN password:

Validating credentials.

Initializing.
Run Edition context : /u01/oracle/xxxxxxxx/fs1/inst/apps/xxxxxxxx_xxxxxxxx/appl/admin/xxxxxxxx_xxxxxxxx.xml
Patch edition context: /u01/oracle/xxxxxxxx/fs2/inst/apps/xxxxxxxx_xxxxxxxx/appl/admin/xxxxxxxx_xxxxxxxx.xml
Patch file system free space: 80.34 GB

Validating system setup.
[UNEXPECTED]Nodes “xxxxxx” are listed in the ADOP_VALID_NODES table but not in the FND_NODES table.
[UNEXPECTED]To correct this, run AutoConfig on nodes “xxxxxxxx”
[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)
[appluat@xxxxxxxx 20190311_165041]$

 

Fix:

Please take a valid backup of your entire System (DB + Appl Tier) to restore if any discrepancies.
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
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.
a. Disable the ebs_login trigger using the following SQL.
SQL> alter trigger ebs_logon disable;
b. At this time Run autoconfig with the patch env sourced.
c.. Enable the ebs_login trigger using the following SQL.
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.