Autoconfig Completed with error issue in applptmp
Introduction:
The objective of this blog is to overcome an error while running autoconfig in oracle EBS 12.2.10 application tier. While running autoconfig in application tier we have encountered this error.
Issue:
Autoconfig completed with error.
Cause:
Below is the cause that we have faced while running autoconfi in oracle EBS 12.2.10 application tier.
PROGRAM : (/u01/TOM/fs1/EBSapps/appl/fnd/12.0.0/patch/115/bin/txkCfgUtlfileDir.pl)
TIME : <Timestamp>
FUNCTION: main::checkApplpTmpOnFS [ Level 1 ]
ERRORMSG: Value /u01/TOM/fs1/inst/apps/<sid_hostname>/appltmp defined for s_applptmp context variable is INVALID.
)
ERRORCODE = 1 ERRORCODE_END
.end std out.
*** ALL THE FOLLOWING FILES ARE REQUIRED FOR RESOLVING RUNTIME ERRORS
*** Log File = /u01/TOM/fs1/inst/apps/<sid_hostname>/logs/appl/rgf/TXK_UTIL_DIR_<timestamp>/txkCfgUtlfileDir.log
/u01/TOM/fs1/EBSapps/appl/fnd/12.0.0/bin/txkCfgUtlfileDir.sh: There is no process to read data written to a pipe.
.end err out.
WARNING: [CVM Error Report]
The following report lists errors encountered during CVM Phase
<filename> <return code where appropriate>
/u01/TOM/fs1/EBSapps/appl/fnd/12.0.0/bin/txkCfgUtlfileDir.sh 1
No. of scripts failed in CVM phase: 1
Solution:
- In oracle DatabaseTier Source the PDB environment file using the following command:
$ORACLE_HOME/<pdb_name>_.env
[oracle@tomdb ~]$ cd $ORACLE_HOME [oracle@tomdb dbhome_1]$ ls *.envCDBTOM_db.env TOM_db.env
[oracle@tomdb dbhome_1]$ . TOM_db.env
- Manually add the specified $APPLPTMP variable directory location of apps tier node in text file named <DB_NAME>_utlfiledir.txt located in the database tier <ORACLE_HOME>/dbs directory .
TOM_utlfiledir.txt
[oracle@tomdb dbs]$ cat TOM_utlfiledir.txt#############################################################################
# This file stores the UTL FILE DIR parameter values used #
# by various EBS product teams #
# #
# ***** DO NOT CHANGE THE NAME OR LOCATION OF THIS FILE ***** #
# #
# IMPORTANT NOTES: #
# ================ #
# #
# 1. OS path should not be a symbolic link #
# #
# 2. OS path given in the list should physically exist with proper #
# permissions #
# #
# 3. OS path /usr/tmp which generally is a symbolic link is replaced with #
# <ORACLE_BASE>/temp/<PDB_NAME> #
# #
# Make sure that OS path <ORACLE_BASE>/temp/<PDB_NAME> exists #
# #
# 4. <APPLPTMP> variable on Apps Tier should match with one of the OS paths #
# in the list. Otherwise you need to modify <APPLPTMP> on all Apps tiers #
# and run Autoconfig #
# #
# 5. Ensure that all the paths defined in this file exist physically on the #
# server #
# #
# 6. Maximum allowed length of UTL_FILE_DIR parameter (combined length of #
# all paths separated by commas) is 4000 characters, hence ensure that #
# value does not exceed the limit #
# #
#===========================================================================#
# For reference, original contents of UTL_FILE_DIR without any updates are #
# retained in below file: #
# #
# /u01/oracle/TOM/19.11.0/dbhome_1/appsutil/log/TXK_UTIL_DIR_Fri_Dec_9_23_37_42_2022/TOM_utlfiledir.txt
#############################################################################
/u01/oracle/TOM/19.11.0/dbhome_1/temp/TOM_dev
- Then run
perl $ORACLE_HOME/appsutil/bin/txkCfgUtlfileDir.pl -contextfile=$CONTEXT_FILE -oraclehome=$ORACLE_HOME -outdir=$ORACLE_HOME/appsutil/log -mode=setUtlFileDir -skipdirvalidation=Yes
- Run autoconfig in apps tier node.
Conclusion:
After executing the above steps autoconfig completed successfully. In resolving the “s_applptmp” autoconfig issue, system functionality can be restored, emphasizing the importance of proactive configuration management in maintaining seamless software operations.