AutoConfig Profile Phase
Running Profile Process 9 of 11 for AD_TOP
Executing script in InstantiateFile:
$COMMON_TOP/admin/install/erppgjh1_erppgjh1/txkJavaMailerCfg.sh
script returned:
****************************************************
txkJavaMailerCfg.sh started at Wed Feb 11 11:06:24 EST 2009
The environment settings are as follows ...
ORACLE_HOME : /apps11i/erpapp/8.0.6
ORACLE_SID :
TWO_TASK : apps11i
PATH : /apps11i/erpapp/iAS/Apache/perl/bin:/apps11i/erpapp/8.0.6/bin:/apps11i/erpapp/appl/fnd/11.5.0/bin:/apps11i/erpapp/appl/ad/11.5.0/bin:$COMMON_TOP/util/java/1.4/j2sdk1.4.2_04/bin:$COMMON_TOP/util/unzip/unzip::/apps11i/erpapp/8.0.6/bin:/usr/bin:/usr/ccs/bin:/usr/sbin:/apps11i/erpapp/iAS/Apache/perl/bin:/apps11i/erpapp/AventX/bin:/apps11i/erpapp/iAS/Apache/perl/bin:/apps11i/erpapp/8.0.6/bin:$COMMON_TOP/util/java/1.4/j2sdk1.4.2_04/bin:$COMMON_TOP/util/unzip/unzip:/apps11i/erpapp/8.0.6/bin:/usr/bin:/usr/ccs/bin:/usr/sbin:/usr/local/bin:/usr/bin:/usr/openwin/bin:/usr/dt/bin:/sbin:/usr/sbin:/usr/platform/sun4u/sbin:/usr/ucb:/usr/ccs/bin:/usr/java/bin
LD_LIBRARY_PATH : /apps11i/erpapp/8.0.6/network/jre11/lib/sparc/native_threads:/apps11i/erpapp/appl/cz/11.5.0/bin:/apps11i/erpapp/8.0.6/lib:/usr/dt/lib:/usr/openwin/lib
Executable : /erppgjh1/erpapp/8.0.6/bin/sqlplus
The arguments passed to txkJavaMailerCfg.sql are as follows ...
USERNAME : -nopromptmsg
PASSWORD :
TWO_TASK : erppgjh1
URL_PROTO_GENERAL : http
PORT_GENERAL : 8020
-nopromptmsg erppgjh1 http 8020
SQL*Plus: Release 8.0.6.0.0 - Production on Wed Feb 11 11:06:25 2009
(c) Copyright 1999 Oracle Corporation. All rights reserved.
ERROR:
ORA-12154: TNS:could not resolve service name
ERRORCODE = 1 ERRORCODE_END
.end std out.
.end err out.
****************************************************
We have a TAR open with Oracle for this. They have advised us to apply TXK Rollup S patch 6372396:
ACTION PLAN
============
Please apply patch ='6372396' and retest issue this issue is addressed in
Bug 6443745 - CLNADMPRF.SH FAIL WITH ORA-12154 WHILE RUNNING AUTOCONFIG
and the fix is patch 6372396.
Applying the TXK Rollup S patch 6372396 resolved this problem.
We also faced this issue in instances which are already on TXK Rollup S. As a quick-fix we re-applied TXK Rollup S to correct this issue. I am still investigating this issue for a more logical fix.
1 comment:
This patch is applied and have fixed the issue.
Post a Comment