Start Node Manager in R12.2

In order to start Node Manager in r12.2. We must be use adnodemgrctl.sh script as below.

 

Source environment

$. /xxx/fs1/EBSapps/appl/APPSPHASE1_xxxtest.env 

cd $ADMIN_SCRIPTS_HOME


$sh adnodemgrctl.sh start


Once node manager started , Need to be check as below.


$sh adnodemgrctl.sh status

You are running adnodemgrctl.sh version 120.11.12020000.12

Enter the WebLogic Admin password:

The Node Manager is running

NodeManager log is located at /data05/EBS_FS_12.2.5/fs1/FMW_Home/wlserver_10.3/common/nodemanager/nmHome1


adnodemgrctl.sh: exiting with status 0


adnodemgrctl.sh: check the logfile /data05/EBS_FS_12.2.5/fs1/inst/apps/PHASE1_xxxtest/logs/appl/admin/log/adnodemgrctl.txt for more information ...


ORA-20099: E-Business Suite Patch Edition does not exist.

 [applmgr@xxxtest]$ sqlplus apps/xxxx

SQL*Plus: Release 10.1.0.5.0 - Production on Mon Dec 28 14:49:49 2020

Copyright (c) 1982, 2005, Oracle.  All rights reserved.

Enter password:

ERROR:

ORA-00604: error occurred at recursive SQL level 1

ORA-20099: E-Business Suite Patch Edition does not exist.

ORA-06512: at line 29



Root Cause:- 

The database patch edition was not active, where when attempting to connect to the database from the application-tier patch edition environment, it failed.


It is expected that autoconfig will fail with DB connection issues when the patch edition does not exist.
Due to a failed DB connection, it was unable to read Topology model for correct TNS config, so created tnsnames.ora from template "tnsnames_80.ora"
instead. As this "tnsnames_80.ora" template does not contain "_patch" alias entry you now have "ORA-12154: TNS:could not resolve the connect identifier specified" on the patch f/s.
For making autoconfig successful EBS_LOGON_TRIGGER needs to be disabled.
 
As seen from the provided inputs, autoconfig has failed in patch fllesystem with below error:

ORA-00604: error occurred at recursive SQL level 1
ORA-20099: E-Business Suite Patch Edition does not exist.
ORA-06512: at line 29

Fix:-

To implement the solution, please execute the following steps:

1.Source RUN File system environment.

. EBSapps.env Run

2. - As apps user disable logon trigger

exec ad_zd.ALTER_LOGON_TRIGGER('DISABLE');
commit;

or 
As system user.

SQL> alter trigger ebs_logon disable;

3. - Source PATCH file system env

4. Run AutoConfig

5. Connect to run filesystem by sourcing run fs environment


6. . As apps user enable logon trigger

exec ad_zd.ALTER_LOGON_TRIGGER('ENABLE');
commit;

or 

As system user:-

SQL> alter trigger ebs_logon enable;

7. Re-run AutoConfig in run fs once again.

For any failures kindly get back to us with the autoconfig logs for review.