Cannot identify any valid application tier nodes in ADOP_VALID_NODES table. Ensure AutoConfig has been run on all nodes.

Hello,

I got the below error while running adop and the issue has been fixed after i followed note id 2064223.1

I would suggest to read 2282694.1 also and see whether it applies to your issue. 

Error :

Initializing.
    Run Edition context  : /a01/appsclone/CLONE/fs2/inst/apps/CLONE_ahqtest/appl/admin/CLONE_ahqtest.xml
    Patch edition context: /a01/appsclone/CLONE/fs1/inst/apps/CLONE_ahqtest/appl/admin/CLONE_ahqtest.xml
*******FATAL ERROR*******
PROGRAM : (/a01/appsclone/CLONE/fs2/EBSapps/appl/ad/12.0.0/bin/adzdoptl.pl)
TIME    : Wed Nov 28 08:38:28 2018
FUNCTION: ADOP::GlobalVars::_GetMandatoryArgs [ Level 1 ]
ERRORMSG: Cannot identify any valid application tier nodes in
          ADOP_VALID_NODES table. Ensure AutoConfig has been run on all nodes.



Fix :

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;


After the fix i was able to run adop without any issue.


Thanks!

How to enable trace in ebs r12.2 from backend (if login page is not accessible)

Hi,

Test the following steps to enable FND Debug and / or AF Logging in E-Business Suite:

1. Source the run file system environment file.

2. Backup file:

   $INST_TOP/appl/admin/oacore_wls.properties

If you dont see the parameters, you can add them. 

3. Edit $INST_TOP/appl/admin/oacore_wls.properties and add the following lines (adjust the variables accordingly):

AFLOG_ENABLED=true
AFLOG_LEVEL=statement
AFLOG_MODULE=%
AFLOG_FILENAME=/tmp/aflog.txt

4. Re-start Middle tier services.

5. Reproduce the issue.

6. Collect the log file.

7. Disable logging by removing the lines which were addded to oacore_wls.properties and re-start services.

Please read login-failed-for-few-users-in-oracle

 

Thanks!

Sikky

[ERROR]: The value of s_patch_service_name is not set correctly in atleast one of the context files.

Hello,

I got the issue below while running prepare phase. I was able to fix the issue with the solution below and thus i am sharing it here.

Cause :

Query the below parameter in db context file.

grep  s_patch_service entry $CONTEXT_FILE

(This is was not present in my context file, thus the error was tripping)

Soultion :


1. Ensure that the below parameters in the database context file are set to: $ORACLE_HOME/appsutil/jre

"s_jretop , s_jdktop

Parameter "ADJVAPRG" needs to be set to $ORACLE_HOME/appsutil/jre/bin/java</ADJVAPRG>

2. Execute admkappstil.pl on the apps node.

3. Copy the generated appsutil.zip to db node and unzip.

4. Execute autoconfig on the database tier.

5. Ensure s_patch_service entry exists in the db context file. 

6. Re-test adop prepare phase.

7. Migrate the solution as appropriate to other environments.

Thats it.

EBS login analyzer

E-Business Suite Applications Login Analyzer (Doc ID 2319360.1)


 perl checkLogin.pl

  Enter the "APPS" password:

  Enter the "APPLSYSPUB" password:

  Prompt: Enter the Application User Name

  If you experiencing a login issue for a single, *specific* E-Business

  Suite User Account, please enter that user account name here.

  Otherwise press [Enter] if the issue affects all users.

how to apply driver in adop in R12.2.4

Hello,

Below driver file was supposed to apply during database migration from solaris to linux. As i felt the step provided in MOS note id does not have much detail. I thought it will be better if i provide steps in detail, it will be helpful for someone. This task seriously ate lot of time.

Create ConText objects

Certain ConText objects are not preserved by the import process. The consolidated export/import utility patch that you applied to the source administration server node in Section 1 contains a perl script, dpost_imp.pl, that you can run to generate an AutoPatch driver file. You use this driver file to call the scripts that create these objects. Run the following command:

bash-3.2$ perl $AU_TOP/patch/115/bin/dpost_imp.pl dpost_imp.drv 11

dpost_imp.drv --> User defined. you can choose any name with .drv extension.
11 --> version of your database. I used 11 since mine was 11.2.0.4

bash-3.2$ ls

dpost_imp.drv  dpost_imp.pl

driver file created as you can see above ls command.

Now copy "dpost_imp.drv"   to $AU_TOP/patch/115/driver

You must mention the driver file location like below. Below is the command to apply driver in adop in 12.2.4.

adop phase=apply options=nocopyportion,,nogenerateportion patchtop=$AU_TOP/patch/115/bin patches=driver:dpost_imp.drv hotpatch=yes

Thats it. you must be able to apply the driver.

Thanks!