Thursday, 19 January 2023

Adcfgclone Fails while instantiating OHS Config - Trying to access DMZ


 /u01/TEST/R12apps/fs2/inst/apps/TEST_Mars/admin/log/clone/patch/txkSetOHSConfig_01567873/provision_01567873.log


Error :

=======


Connecting Run file system WLS domain using t3://Mars.Jayan.int:7006

WARNING: Run file system MBeanServerConnection is invalid

Looks like Run file system WLS domain MBeanServerConnection is unavailable!!!

Trying to read managed server name and host:port info from Patch context file available in fnd_oam_context_files table

For RUN file system Server Name, Listen Address:Listen Port map from database {=dmzMars.Jayan.int:, oacore_server2=dbfin

sfnyp01.Jayan.int:7207, oacore_server1=Mars.Jayan.int:7206, oacore_server3=dmzMars.Jayan.int:7215, f

orms-c4ws_server2=dmzMars.Jayan.int:7815, oafm_server2=dmzMars.Jayan.int:7615, forms-c4ws_server1=dbfinsfn

yp01.Jayan.int:7806, oafm_server1=Mars.Jayan.int:7606, forms_server1=Mars.Jayan.int:7406, forms_serv

er2=dmzMars.Jayan.int:7415}

For RUN file system Server Name, Listen Address:SSL Listen Port map from database {=dmzMars.Jayan.int:}

Populating map where key is host:port and value is managed server name

ERROR: Failed to populate map where key is host:port and value is managed server name

ERROR: String index out of range: -1




Cause :

=======

After database clone , while continuing with adcfgclone on appstier its trying to access DMZ node (dmzMars) which is not available or does not exist actually.


Solution:

==========


To overcome this error please follow the below steps.


1.  Backup the below files on Application Tier.


    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;


    If on ADK/TXK 8 or higher please include below query also.


    create table ad_nodes_config_status_bk as select * from ad_nodes_config_status;


2.  Truncate the below tables.


    truncate table fnd_oam_context_files;

    truncate table fnd_nodes;

    truncate table adop_valid_nodes;


    If on ADK/TXK 8 or higher please include below query also.


    truncate table ad_nodes_config_status;


3.  Run autoconfig on database Tier


    cd $ORACLE_HOME/appsutil/scripts/TEST_MARS/    

    sh adautocfg.sh


4.  Run Autoconfig on Application Tier


    cd $ADMIN_SCRIPTS_HOME

    sh adautocfg.sh


    Now rerun the adcfgclone on apps Tier , It completed Normal.


Reference : How to Synchronize the AD tables FND_NODES, ADOP_VALID_NODES, and FND_OAM_CONTEXT_FILES in 12.2 when adop fails. (Doc ID 2064223.1)

No comments:

Post a Comment