UNEXPECTED Nodes X are listed in the ADOP_VALID_NODES table but not in the FND_NODES table

Error : 

adop phase=FS_CLONE failed with below error.

Validating system setup.

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

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

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

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

      sqlplus applsys/pwd

sqlplus applsys/****@PDB

create table fnd_oam_context_files_bkp26jan as select * from fnd_oam_context_files;

create table fnd_nodes_bk26jan23 as select * from fnd_nodes;

create table adop_valid_nodes_bk26jan23 as select * from adop_valid_nodes;

02. Truncate the following tables:

truncate table fnd_oam_context_files;

truncate table fnd_nodes;

truncate table adop_valid_nodes;

03.  Run AutoConfig on the DB tier

        Confirm Autoconfig completes successfully

04. Stop application service.

05. Run Autoconfig on the run file system.

echo $FILE_EDITION

run

Confirm Autoconfig completes successfully

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.

06.Logon to sqlplus as system(sqlplus system/****@PDB): alter trigger ebs_logon disable;

07.  Run Autoconfig on the patch file system

echo $FILE_EDITION

patch

08. Logon to sqlplus as system(sqlplus system/****@PDB): alter trigger ebs_logon enable;

09. After Autoconfig has been run successfully on all nodes, run the following two (2) queries in 

order to verify the tables have been correctly populated:

SQL>

        set pagesize 5

        set linesize 132

        col node_name format a15

        col server_id format a8

        col server_address format a15

        col platform_code format a4

        col webhost format a12

        col domain format a20

        col virtual_ip format a12

select  node_id,  platform_code, support_db D, support_cp C, support_admin A, 

support_forms F, support_web W, node_name, server_id, server_address, domain, webhost, virtual_ip, 

status from fnd_nodes order by node_id;

SQL>

        set pagesize 5

        set linesize 132

        col NAME format A20

        col VERSION format A12

        col PATH format A110

        col STATUS format A10

select NAME,VERSION,PATH, STATUS from FND_OAM_CONTEXT_FILES;

 10. Start application service.