ERROR: RC-50014: Fatal: Execution of AutoConfig was failed Raised by oracle.apps.ad.clone.ApplyApplTop

-

Overview of AutoConfig RC-50014 Error

During Oracle E-Business Suite (EBS) cloning, environment patching, or system configuration updates, running adconfig.sh (AutoConfig) is mandatory to synchronize context files with system templates.

A common failure during the ApplyApplTop execution phase triggers the error: ERROR: RC-50014: Fatal: Execution of AutoConfig failed

This error indicates that the underlying deployment script was unable to execute terminal commands or write XML driver properties to the application file system, bringing the clone or patching process to a complete halt.


Root Causes

The RC-50014 exception usually points to one of three underlying system issues:

  1. Permission Mismatches: The Linux account running AutoConfig lacks read/write/execute permissions on APPL_TOP or sub-directories (e.g., inst/apps/$CONTEXT_NAME/admin/log).

  2. Environment Variable Corruption: Missing or incorrectly set PATH, LD_LIBRARY_PATH, or ORACLE_HOME variables in the APPS tier environment file.

  3. Stale/Locked Drivers: File lock issues on configuration drivers or running database processes preventing temp file writes during execution.


Troubleshooting & Fix

Step 1: Analyze the Log Files

To identify the exact command that failed inside AutoConfig, navigate to the log directory referenced in your execution output:

cd $INST_TOP/admin/log/

ls -lrt

view <TIMESTAMP>_AutoConfig.log

Search for RC-50014 or Exit Status: 1 inside the log file to identify the precise perl script or binary that threw the exception.

 

Step 2: Correct Ownership and File Permissions

Ensure the application tier user owns the entire installation directory:

chown -R applmgr:appldev $APPL_TOP

chown -R applmgr:appldev $INST_TOP

chmod -R 755 $INST_TOP/admin/scripts


Step 3: Source the APPS Environment

Ensure you source the correct context file before executing AutoConfig manually:

cd $APPL_TOP

. ./APPS<CONTEXT_NAME>.env


Step 4: Re-run AutoConfig

Run AutoConfig directly from the scripts directory to confirm the fix:

cd $ADMIN_SCRIPTS_HOME

./adconfig.sh


The detailed step-by-step process is given below.

While performing clone in one of my Oracle EBS R12.2 patch environment, I faced an issue in the autoconfig process though the clone(Rapid clone) process completed successfully.

Below is the excerpt of the rapid clone and autoconfig log files.

RC Log:

Log file located at /op01/oracle/<Instance_Name>/fs1/inst/apps/<Instance_Name>_<hostname>/admin/log/clone/ApplyAppsTier_09261049.log

  /     50% completed       <Sep 26, 2023 11:26:47 AM PDT> <Warning> <JNDI> <BEA-050001> <WLContext.close() was called in a different thread than the one in which it was created.>

  |    100% completed


Completed Apply...

Tue Sep 26 11:29:26 2023


Running:

/op01/oracle/<Instance_Name>/fs1/EBSapps/10.1.2/bin/sqlplus -s /nolog > /op01/oracle/<Instance_Name>/fs1/EBSapps/comn/clone/bin/truncate_ad_nodes_config_status.log 2>&1


Running:

/op01/oracle/<Instance_Name>/fs1/EBSapps/10.1.2/bin/sqlplus -s /nolog > /op01/oracle/<Instance_Name>/fs1/EBSapps/comn/clone/bin/update_patchbase.log 2>&1


Running:

/op01/oracle/<Instance_Name>/fs1/EBSapps/10.1.2/bin/sqlplus -s /nolog > /op01/oracle/<Instance_Name>/fs1/EBSapps/comn/clone/bin/delete_adopvalidnodes.log 2>&1


Skipping the starting of services

INFO :  Rapid Clone completed successfully , but the AutoConfig run recorded  some errors.

Please review the AutoConfig section in the logfile.  and Re-Run the entire cloning cycle , after fixing the problem. 


Autoconfig log:

WARNING: [AutoConfig Error Report]


The following report lists errors AutoConfig encountered during each phase of its execution.  Errors are grouped by directory and phase.


The report format is:

      <filename>  <phase>  <return code where appropriate>


  [INSTANTIATE PHASE]

  AutoConfig could not successfully instantiate the following files:

    Directory: /op01/oracle/<Instance_Name>/fs1/inst/apps/<Instance_Name>_<hostname>/portal

      inst_log.html           INSTE8


  [APPLY PHASE]

  AutoConfig could not successfully execute the following scripts:

    Directory: /op01/oracle/<Instance_Name>/fs1/FMW_Home/webtier/perl/bin/perl -I /op01/oracle/<Instance_Name>/fs1/FMW_Home/webtier/perl/lib/5.10.0 -I /op01/oracle/<Instance_Name>/fs1/FMW_Home/webtier/perl/lib/site_perl/5.10.0 -I /op01/oracle/<Instance_Name>/fs1/EBSapps/appl/au/12.0.0/perl -I /op01/oracle/<Instance_Name>/fs1/FMW_Home/webtier/ohs/mod_perl/lib/site_perl/5.10.0/x86_64-linux-thread-multi /op01/oracle/<Instance_Name>/fs1/inst/apps/<Instance_Name>_<hostname>/admin/install


      txkGenADOPWrapper.pl    INSTE8_APPLY       1


AutoConfig is exiting with status 2

ERROR: RC-50014: Fatal: Execution of AutoConfig was failed

Raised by oracle.apps.ad.clone.ApplyApplTop


END: Executed runAutoConfig...


Exact Issue

Script Name    : txkGenADOPWrapper.pl

Script Version : 120.0.12020000.7

ERROR DESCRIPTION:


(*******FATAL ERROR*******

PROGRAM : (/op01/oracle/<Instance_Name>/fs1/inst/apps/<Instance_Name>_<hostname>/admin/install/txkGenADOPWrapper.pl)

TIME    : Tue Sep 26 11:12:32 2023

FUNCTION: TXK::SQLPLUS::_doExecute [ Level 3 ]

MESSAGES:

SQLPLUS error: buffer=


SQL*Plus: Release 10.1.0.5.0 - Production on Tue Sep 26 11:12:31 2023

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

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 3075


Disconnected from Oracle Database 19c EE Extreme Perf Release 19.0.0.0.0 - Production


STACK TRACE

 at /op01/oracle/<Instance_Name>/fs1/EBSapps/appl/au/12.0.0/perl/TXK/Error.pm line 168

        TXK::Error::abort('TXK::Error', 'HASH(0x229b1d8)') called at /op01/oracle/<Instance_Name>/fs1/EBSapps/appl/au/12.0.0/perl/TXK/Common.pm line 299

        TXK::Common::doError('TXK::SQLPLUS=HASH(0x3394ab0)', 'SQLPLUS error: buffer=\x{a}\x{a}SQL*Plus: Release 10.1.0.5.0 - Produc...', undef) called at /op01/oracle/<Instance_Name>/fs1/EBSapps/appl/au/12.0.0/perl/TXK/Common.pm line 314

        TXK::Common::setError('TXK::SQLPLUS=HASH(0x3394ab0)', 'SQLPLUS error: buffer=\x{a}\x{a}SQL*Plus: Release 10.1.0.5.0 - Produc...') called at /op01/oracle/<Instance_Name>/fs1/EBSapps/appl/au/12.0.0/perl/TXK/SQLPLUS.pm line 832

        TXK::SQLPLUS::_doExecute('TXK::SQLPLUS=HASH(0x3394ab0)', 0) called at /op01/oracle/<Instance_Name>/fs1/EBSapps/appl/au/12.0.0/perl/TXK/SQLPLUS.pm line 234

        TXK::SQLPLUS::execute('TXK::SQLPLUS=HASH(0x3394ab0)', 'HASH(0x321eb40)') called at /op01/oracle/<Instance_Name>/fs1/EBSapps/appl/au/12.0.0/perl/TXK/TechstackDB.pm line 623

        TXK::TechstackDB::_getSQLValue('TXK::TechstackDB=HASH(0x29d21d8)', 'SELECT ad_zd_adop.get_node_type(\'<hostname>\') FROM DUAL') called at /op01/oracle/<Instance_Name>/fs1/EBSapps/appl/au/12.0.0/perl/TXK/TechstackDB.pm line 575

        TXK::TechstackDB::getSQLValue('TXK::TechstackDB=HASH(0x29d21d8)', 'SELECT ad_zd_adop.get_node_type(\'<hostname>\') FROM DUAL') called at /op01/oracle/<Instance_Name>/fs1/inst/apps/<Instance_Name>_<hostname>/admin/install/txkGenADOPWrapper.pl line 506

        main::getNodeType() called at /op01/oracle/<Instance_Name>/fs1/inst/apps/<Instance_Name>_<hostname>/admin/install/txkGenADOPWrapper.pl line 202

        eval {...} called at /op01/oracle/<Instance_Name>/fs1/inst/apps/<Instance_Name>_<hostname>/admin/install/txkGenADOPWrapper.pl line 143

)

ERRORCODE = 1 ERRORCODE_END

.end std out.

.end err out.


****************************************************


Fixes I tried

[oracle@<hostname> scripts]$ sqlplus apps/<password>

COL node_name FORMAT A20

COL note_type FORMAT A10    

SELECT avn.node_name,

DECODE(EXTRACTVALUE(XMLType(focf.text),'//APPL_TOP_NAME'),

admin_node.appl_top, DECODE(avn.node_name,admin_node.node_name, 1,3),

DECODE(ROW_NUMBER() OVER (PARTITION BY EXTRACTVALUE(XMLType(focf.text),'//APPL_TOP_NAME')

ORDER BY avn.node_name),

1,2,4)) node_type

FROM

fnd_oam_context_files focf,

adop_valid_nodes avn,

(SELECT node_name,

EXTRACTVALUE(XMLType(text),'//APPL_TOP_NAME') appl_top

FROM fnd_oam_context_files

WHERE name NOT IN ('TEMPLATE','METADATA','config.txt')

AND CTX_TYPE='A'

AND (status IS NULL or UPPER(status) IN ('S','F'))

AND EXTRACTVALUE(XMLType(text),'//file_edition_type') = 'run'

AND EXTRACTVALUE(XMLType(text),'//oa_service_group_status[@oa_var=''s_web_admin_status'']')='enabled'

AND EXTRACTVALUE(XMLType(text),'//oa_service_list/oa_service[@type=''admin_server'']/oa_service_status')='enabled') admin_node

WHERE focf.name not IN ('TEMPLATE','METADATA','config.txt')

AND focf.CTX_TYPE='A'

AND (focf.status is null

or upper(focf.status) IN ('S','F'))

AND EXTRACTVALUE(XMLType(focf.text),'//file_edition_type') = 'run'

AND upper(focf.node_name)=upper(avn.node_name); 

NODE_NAME             NODE_TYPE

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

<hostname>                1

<hostname>                1

<hostname>                1

<hostname>                1


SQL>


  The meaning of various return values are:

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

    1 - Admin Node

    2 - Non-Shared master node

    3 - Admin Shared slave node

    4 - Shared slave node


since the above query returned more than 1 row of the same host, we need to disable the "s_web_admin_status" parameter on the application context file of the recently cloned node and Rerun autoconfig and confirm the issue is solved.


I tried but this doesn't fix the issue.

Ref: Doc ID 2212698.1


Then I tried

fnd_conc_clone.setup_clean; --> as apps user on DB tier

Autoconfig on DB

Autoconfig on APPS [Run fs]


Here also no changes happened.


Fix

As per Doc ID 2268532.1 Modify these two variables to 'enabled' in the RUN file system context file on the target server.


<oa_service_status oa_var="s_adminserverstatus">disabled</oa_service_status>

<oa_service_group_status oa_var="s_web_admin_status">disabled</oa_service_group_status>

to 

<oa_service_status oa_var="s_adminserverstatus">enabled</oa_service_status>

<oa_service_group_status oa_var="s_web_admin_status">enabled</oa_service_group_status>


Run autoconfig again. ===> sh $AD_TOP/bin/adconfig.sh contextfile=<RUN_CONTEXT_FILE>


Before:

SQL> SELECT ad_zd_adop.get_node_type('<hostname>') FROM DUAL;

SELECT ad_zd_adop.get_node_type('<hostname>') FROM DUAL

       *

ERROR at line 1:

ORA-20001: Node name <hostname> not found in adop repository tables

ORA-06512: at "APPS.AD_ZD_ADOP", line 3105


After:

SQL> SELECT ad_zd_adop.get_node_type('<hostname>') FROM DUAL;

AD_ZD_ADOP.GET_NODE_TYPE('<hostname>')

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

                                         1


Now run the autoconfig script. The issue should be fixed now.



****************************நன்றி****************************

Location: Chennai, Tamil Nadu, India

Comments

Post a Comment

Popular posts from this blog

Common R12.2 adcfgclone Issues

-
ERROR: Failed to configure the target system – Failed to enable EBS_LOGON trigger The clone procedure for EBS R12.2 is quite different when compared with EBS R12.1. This post covers very generic   issues we may encounter while configuring the target server as a part of clone Process. ERROR : 1 Checking the port pool 6 done: Port Pool 6 is free Report file located at /u01/appl_PROD/PROD/fs2/inst/apps/PRODERP_erpnode3/admin/out/portpool.lst The new APPL_TOP context file has been created : /u01/appl_PROD/PROD/fs2/inst/apps/PRODERP_erpnode3/appl/admin/PRODERP_erpnode3.xml Check Clone Context logfile /u01/appl_PROD/PROD/fs1/EBSapps/comn/clone/bin/CloneContextPatch_0811105848.log for details. FMW Pre-requisite check log file location : /u01/appl_PROD/PROD/fs1/EBSapps/comn/clone/FMW/logs/prereqcheck.log Running: FMW pre-req check... ERROR: Run file system configuration has failed Check the logfile /u01/appl_PROD/PROD/fs1/inst/apps/PRODERP_erpnode3/admin/l...
Read more

REP-3000: Internal error starting Oracle Toolkit

-
Image
Resolving "REP-3000: Internal error starting Oracle Toolkit" in Oracle EBS (11i / R12) When running concurrent programs in Oracle E-Business Suite (EBS) that produce PDF , PostScript , or HTML  output, DBAs frequently encounter the infamous runtime exception: ' REP-3000: Internal error starting Oracle Toolkit' .   This issue is notorious for disrupting the Output Post-Processor (OPP)  and concurrent manager operations across both Linux and UNIX platforms. In this post, we will examine the architectural reason behind the REP-3000 error, walk through testing the OS-level X11 display environment, update the EBS Context File, and ensure persistent display settings across AutoConfig executions.  1. Understanding the Cause: Why Does Oracle Reports Need a DISPLAY Variable? The core engine responsible for generating character-based, PDF, or PostScript reports in legacy Oracle Developer / Oracle Reports (such as ' rwrun'  or ' rwserver' ) relies on Oracle Toolk...
Read more

Error 404 -- Not Found From RFC 2068 hypertext Transfer Protocol -- HTTP/1.1

-
Image
In my environment we are having EBS(12.2.5) running with 12.1.0.2 database. One day in our DEV Instance  Front-End is not opening and faced the below error. So I followed the below steps as a solution and it worked. First, generate the JAR files Next, reload the generated jar files to the respective database  Now compile the APPS schema to reduce the count of Invalid objects. Once everything completed, you can clear your browser cache and try to login to the application., but normally the above steps will be accompanied by clearing the middle tier cache. So I gave the below steps to clear the middle tier cache from backend. To clear the cache, follow the below steps. Stop the application services Navigate to $OA_HTML/cabo/images/cache Take a backup of contents of the folder cache and then clear all the contents inside that cache folder Navigate to $OA_HTML/cabo/styles/cache Take a backup of contents of the folder ca...
Read more