ADOP Issues

May 30, 2019

Share this post
Learn More

Adop Issues:

Adop is not to able to detect any valid application tier node entries in the ADOP_VALID_NODES table this is because of the mandatory service name “ebs_patch” in R12.2 has been missing in the listener. I’ve mentioned the steps how to take care of this issue in case if we face the same error on our environment.

Issue:

In R12.2, when we are running adop it is failing with the error message “adop is not able to detect any valid application tier nodes” at initial validation phase.

[applmgr@ebsdevr12]$  adop -validate

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

Validating credentials…

Initializing…
Run Edition context : /u01/oracle/DEV/fs1/inst/apps/DEV_ebsdevr12/appl/admin/DEV_ebsdevr12.xml
Patch edition context: / u01/oracle/DEV/fs2/inst/apps/DEV_ebsdevr12/appl/admin/DEV_ebsdevr12.xml
*******FATAL ERROR*******
PROGRAM : (/u01/oracle/DEV/fs1/EBSapps/appl/ad/12.0.0/bin/adzdoptl.pl)
TIME : Wed May 11 10:12:09 2019
FUNCTION: ADOP::GlobalVars::_GetMandatoryArgs [ Level 1 ]
ERRORMSG: adop is not able to detect any valid application tier nodes in
ADOP_VALID_NODES table. Ensure autoconfig is run on all nodes.

[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 = 255 (Fail)

Cause:

This is because that Database listener is not listening ebs_patch service which is mandatory in R12.2 application to work on any adop activities.

[oracle@ ebsdevr12]$ lsnrctl status $ORACLE_SID

LSNRCTL for Linux: Version 11.2.0.4.0 – Production on 11-May-2019 06:18:09

Copyright (c) 1991, 2013, Oracle.  All rights reserved.

Alias                     DEV

Listening Endpoints Summary…

Services Summary…

Service “DEV” has 2 instance(s).

Instance “DEV”, status UNKNOWN, has 1 handler(s) for this service…

Instance “DEV”, status READY, has 1 handler(s) for this service…

The command completed successfully

Solution:

    1. Make sure that Database init parameter has two service names ‘DEV, ebs_patch’ entries.
    2. Connect to database as sysdba. If this service name is not there then, set it using below command as shown below
      SQL> show parameter service_name;
      NAME                                 TYPE        VALUE
      ———————————— ———– ——————————
      service_names                        string      DEV, ebs_patch
      SQL> alter system set service_names=’DEV’,’ ebs_patch’ scope=both;
    3. Verify init parameter LOCAL_LISTENER. If it’s not set, then set it to <DB_NAME>_LOCAL as shown below.SQL> alter system set local_listener=’DEV_LOCAL’ scope=both;
    4. alter system register;
    5. Bounce application services, database services and then run the adop again.

Recent posts

Categories