Skip to content

 
Accessibility Preferences
PowerView is
Off
Last Login: June 3, 2021 6:24 Switch to Cloud Rowaldo (0 Contact
Support Help
PM CST (Available) ) Us
 
 
Dashboard
Knowledge
Service Requests
Patches & Updates
Community
Certifications
Systems
Advanced Customer Services
Settings
Global Search

    Give
Feedback...
Copyright (c) 2021, Oracle. All rights reserved. Oracle Confidential.

How to Synchronize the AD tables FND_NODES, ADOP_VALID_NODES,

and FND_OAM_CONTEXT_FILES in 12.2 when adop fails. (Doc ID Bottom
2064223.1)

  Was this document helpful?

In this Document
Ye
s
Symptoms
No
Cause
 
Solution
 

  Document Details  

Type: PROBLEM
Status:
PUBLISHED
APPLIES TO: Last Major Update:
Jan 29, 2020
Last Update:
Apr 1, 2020
Oracle Applications DBA - Version 12.2 to Language: English
12.2.8 [Release 12.2Cloud to 12.2]
Oracle Concurrent Processing - Version 12.2.6    

to 12.2.8 [Release 12.2]

Information in this document applies to any
  Related Products
platform.
Oracle Applications DBA
SYMPTOMS Oracle Applications DBA
Oracle Concurrent
Processing
CASE 1:      

  Information Centers  
  Privacy
and
adop phase=prepare Security
Feature
Guidanc
e for all
Oracle
*******FATAL ERROR******* Products
(On
PROGRAM : (/appl/ad/12.0.0/bin/adzdoptl.pl) Premise)
[113.2]
TIME : Fri Oct 2 22:06:45 2015
FUNCTION: Oracle
ADOP::GlobalVars::_GetMandatoryArgs Catalog:
[ Level 1 ] Informat
ion
ERRORMSG: adop is not able to detect any Centers
valid application tier nodes in for All
ADOP_VALID_NODES table. Products
and
Services
Ensure autoconfig is run on all nodes. [50.2]

[STATEMENT] Please run adopscanlog

 

   

utility, using the command   Document References

"adopscanlog -latest=yes" No References available for this
to get the list of the log files along with snippet document.
of the error message corresponding to each log  

 
file.   Recently Viewed  
adop exiting with status = 255 (Fail) Error After Cloning Running: adop
phase=prepare [UNEXPECTED]adop cannot
detect any application tier nodes in
  FND_NODES table. Ensure ICM is running
and run autoconfig on all nodes
CASE 2: [1958466.1]

Oracle E-Business Suite Release 12

adop phase=apply / actualize_all Installation Guidelines [405565.1]

  How Determine The Hardware Specification

: CPU, DISK, RAM (Memory) For E-Business
R12.1.x Installation? [789438.1]

AutoInvoice Setup for Release 12: A Case

Study Using a Simple Script [1067402.1]

How to Setup a Remit-To Address in

Release 12 Oracle Receivables [1101666.1]
 Show More
 
[APPLY PHASE]
 

*******FATAL ERROR*******

AutoConfig could not successfully execute the

following scripts:

Directory:
<EBS_BASE>/fs#/FMW_Home/webtier/perl/
bin/perl -I
<EBS_BASE>/fs#/FMW_Home/webtier/perl/l
ib/5.10.0 -I
<EBS_BASE>/fs#/FMW_Home/webtier/perl/l
ib/site_perl/5.10.0 -I
<EBS_BASE>/fs#/EBSapps/appl/au/12.0.0/pe
rl -I
<EBS_BASE>/fs#/FMW_Home/webtier/ohs/
mod_perl/lib/site_perl/5.10.0/x86_64-linux-
thread-multi
/<EBS_BASE>/fs#/inst/apps/<SID_hostname
>/admin/install

txkGenADOPWrapper.pl INSTE8_APPLY 1

SQL> SQL> Connected.

SQL> SELECT
ad_zd_adop.get_node_type('<hostname>')
FROM DUAL
*
ERROR at line 1:
ORA-01422: exact fetch returns more than
requested number of rows
ORA-06512: at "APPS.AD_ZD_ADOP", line
3049

CAUSE

CASE 1: adop phase=prepare

In this case, The fnd_nodes table has NULL

for domain entry of this valid server.

Example Data Supporting the Conclusion

---------------
[table.applsys.fnd_nodes]

NODE     PLAT    D C A F W   

NODE_NAME    SERVER_ADDRESS    
DOMAIN    WEBHOST                             
VIRTUAL_IP        S
--------------------------------------------------------
--------------------------------------------------------
-----------------------------------------
12,121     226    N Y Y Y Y    NEW122APP1  
###.###.###.103     NULL       
new122app1.<host.domain>      
NULL               Y

CASE 2: adop phase=apply / actualize_all

[table.applsys.fnd_oam_context_files]

NAME S_CONTEXTFILE
S_CONTEXTTYPE S_CONTEXTNAME
Version Number SERIAL
APPL_TOP_NAME HOST
SHARED_FILE_SYSTEM EDITION

--------------------------------------------------------
--------------------------------------------------------
-----------------------------------------

<SID_hostname> ./<SID_hostname>.xml
APPL_TOP Context <SID_hostname>
120.401.12020000.85 6999 AT_<hostname>
<hostname> false run
<SID_hostname> ./<SID_hostname>.xml
APPL_TOP Context <SID_hostname>
120.401.12020000.85 6999 AT_<hostname>
<hostname> false run
<SID_hostname> ./<SID_hostname>.xml
APPL_TOP Context <SID_hostname>
120.401.12020000.85 7001 AT_<hostname>
<hostname> false patch
<SID_hostname> ./<SID_hostname>.xml
Database Context <SID_hostname>
120.52.12020000.11 0 NULL <hostname>
NULL database 

SOLUTION

Test the following steps in a cloned instance

first, and then migrate accordingly once the
desired result is confirmed:
 

NOTE: 1. Due to the method required for

"cleaning out" / "re-synchronizing" the
following tables, it is EXPECTED /
REQUIRED that the Applications have been
shutdown. 

                  The only thing running should be

the Database Tier.

           2. A full backup should be taken

before any testing begins.

1. Backup the fnd_oam_context_files,

fnd_nodes, and adop_valid_nodes tables, and
if on AD/TXK 8 or
higher; ad_nodes_config_status in the EBS env
nodes:

      Linux#> sqlplus

applsys/<pwd>
      SQLPlus#> create table
fnd_oam_context_files_bkp as
select * from
fnd_oam_context_files;

      SQLPlus#> create table

fnd_nodes_bk as select * from
fnd_nodes;

        SQLPlus#> create
table
adop_valid_nodes_bk as select *
from adop_valid_nodes;

      If on AD/TXK 8 or higher:

      SQLPlus#> create table

ad_nodes_config_status_bk as
select * from
ad_nodes_config_status;

 2. Truncate the following tables (Continue

from step 1):

      SQLPlus#> truncate table

fnd_oam_context_files;

      SQLPlus#> truncate table

fnd_nodes;

      SQLPlus#> truncate table

adop_valid_nodes;

      If on AD/TXK 8 or
higher:

      SQLPlus#> truncate table

ad_nodes_config_status;

3.  Run AutoConfig on the DB tier:

Source the <RDBMS_ORACLE_HOME> home.

Linux#> cd
<RDBMS_ORACLE_HOME>/appsutil/scripts/
<SID>_<HOSTNAME>/

Linux#> ./adautocfg.sh

              ... Confirm Autoconfig completes

successfully.

              ... If RAC, Repeat step 3 on all RAC nodes.

4.  Run Autoconfig on the run file system.

Linux#> source <EBS_BASE>/EBSapps.env

run

Linux#> cd $ADMIN_SCRIPTS_HOME

Linux#> ./adautocfg.sh

      ... Confirm Autoconfig completes

successfully.

      ... If more than one EBS node, repeat step 4

on all EBS nodes.

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.

a. Disable the ebs_login trigger using the

following SQL.

Linux#> sqlplus system/<pwd>

SQLPlus#> alter trigger ebs_logon

disable;

b. At this time Run autoconfig with the patch env

sourced .       

Linux#> source <EBS_BASE>/EBSapps.env

patch
Linux#> cd $ADMIN_SCRIPTS_HOME

Linux#> ./adautocfg.sh

... Confirm Autoconfig completes successfully

... If more than one EBS node, repeat step 5.b on

all EBS nodes.

c. Enable the ebs_login trigger using the

following SQL.

Linux#> sqlplus system/<pwd>

SQLPlus#> alter trigger

ebs_logon enable;

 6.  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;

 
Didn't find what you are looking for? Ask in Community...

Related
 
Product
s
 Oracle E-Business Suite  > Applications Technology > Lifecycle Management > Oracle Applications
DBA > Online Patching - OP > ADOP utilities

 Oracle E-Business Suite  > Applications Technology > Lifecycle Management > Oracle Applications

DBA > AD UTILITIES > ISSUES WITH FUNCTIONALITY OF AD UTILITIES

 Oracle E-Business Suite  > Applications Technology > Application Object Library > Oracle Concurrent

Processing > Post-Processing > Post-Processing

Keywords
ADOP; AUTOCONFIG; CONTEXT; CORRUPT; E-BUSINESS; EBS; FND_NODES; FND_OAM_CONTEXT_FILES;
SYNCHRONIZATION
 
Translation
s
 Japanese 日本語
 English Source

Back to Top
 
Copyright (c) 2021, Oracle. All rights reserved.   Legal Notices and Terms of Use   Privacy Statement