Friday 12 April 2019

adcfgclone Fails on Apps Tier with Error : sqlplus: error while loading shared libraries: libclntsh.so.10.1: cannot open shared object file: No such file or directory (Doc ID 2390797.1)

Error:
adcfgclone Fails on Apps Tier with below error which is reported in RCloneApplyAppstier_04200721.log /u01/TEMP/app/fs1/EBSapps/10.1.2/bin/sqlplus: error while loading shared libraries: libsqlplus.so: cannot open shared object file: No such file or directory <<<<<<< *******FATAL ERROR******* PROGRAM : (/u01/xxx/app/fs1/xxx/appl/fnd/12.0.0/patch/115/bin/txkManageDBConnectionPool.pl) TIME : Fri Apr 20 07:25:59 2018 FUNCTION: main::validateAppsSchemaCredentials [ Level 1 ] ERRORMSG: Invalid APPS database user credentials. No updates Performed /u01/TEMP/app/fs1/EBSapps/10.1.2/bin/sqlplus: error while loading shared libraries: libclntsh.so.10.1: cannot open shared object file: No such file or directory <<<<< *******FATAL ERROR******* PROGRAM : (/u01/xxx/app/fs1/xxx/appl/fnd/12.0.0/patch/115/bin/txkChkFormsLaunchMethod.pl) TIME : Fri Apr 20 07:26:06 2018 FUNCTION: [ Level 1 ] ERRORMSG: *******FATAL ERROR******* PROGRAM : (/u01/xxx/app/fs1/xx/appl/fnd/12.0.0/patch/115/bin/txkChkFormsLaunchMethod.pl) TIME : Fri Apr 20 07:26:06 2018 FUNCTION: main::validateAppsSchemaCredentials [ Level 1 ] ERRORMSG: Invalid APPS database user credentials. START: Executing /u01/xxx/app/fs1/inst/apps/xxxx/admin/install/txkWfClone.sh -nopromptmsg txkWfClone.sh exited with status 127 ERROR: txkWfClone.sh execution failed, exit code 127 == 20APR2018_Logfiles\run\fmwT2PApply\CLONE2018-04-20_07-21-34_1451479129.log == /bin/chmod: cannot access '/u01/xx/app/fs1/FMW_Home/webtier//lib32/libagtsh.so.1.0': No such file or directory /bin/chmod: cannot access '/u01/xxx/app/fs1/FMW_Home/webtier//lib32/libclntsh.so.11.1': No such file or directory == 20APR2018_Logfiles\run\fmwT2PApply\CLONE2018-04-20_07-21-34_1451479129.error == WARNING : Apr 20, 2018 07:23:21 - WARNING - CLONE-20247 Not all file permission operations are successful. WARNING : Apr 20, 2018 07:23:21 - CAUSE - CLONE-20247 Some files were missing from the Oracle Home /u01/xxx/app/fs1/FMW_Home/webtier/. WARNING : Apr 20, 2018 07:23:21 - ACTION - CLONE-20247 Check the clone log file and permission restore log file /u01/xxx/app/fs1/inst/apps/xxx/admin/log/clone/run/fmwT2PApply/1524198199575_permissionApplyOuput.log for more details about the missing files. == 1524198199575_permissionApplyOuput.log == /bin/chmod: cannot access '/u01/xxx/app/fs1/FMW_Home/webtier//lib32/libagtsh.so.1.0': No such file or directory /bin/chmod: cannot access '/u01/xxx/app/fs1/FMW_Home/webtier//lib32/libclntsh.so.11.1': No such file or directory $ sh /u01/xxx/fs1/inst/apps/xxxx/admin/install/txkWfClone.sh txkWfClone.sh started at Sun Apr 22 14:48:28 +03 2018
The environment settings are as follows ... ORACLE_HOME : /u01/xxx/fs1/xxx/10.1.2 ORACLE_SID : TWO_TASK : CLONE PATH : ------ Executable : /u01/TEST/fs1/EBSapps/10.1.2/bin/sqlplus Enter the APPS username: apps Enter the APPS password: sqlplus: error while loading shared libraries: libclntsh.so.10.1: cannot open shared object file: No such file or directory ERRORCODE = 127 ERRORCODE_END

Change:

Issue happens only on Oracle Linux 7 and Red Hat Enterprise Linux 7

Issue only when performing clone, There might other instance which are working fine.

Cause:

binutils RPM is on higher version 2.27 whereas as per document Oracle E-Business Suite Installation and Upgrade Notes Release 12 (12.2) for Linux x86-64 (Doc ID 1330701.1) below version is expected.

binutils-2.23.52.0.1-16.el7.x86_64


Version of RPM can be determined using below query: 

rpm -qa --queryformat "%{NAME}-%{VERSION}-%{RELEASE}(%{ARCH})\n" | grep binutils

Solution:

To implement the solution, please execute the following steps:

1. Check version of binutils RPM using below command rpm -qa --queryformat "%{NAME}-%{VERSION}-%{RELEASE}(%{ARCH})\n" | grep binutils

2. If the version of RPM higher version than binutils-2.23.52.0.1-16.el7.x86_64 version then

3. Download the rpm below

binutils-2.23.52.0.1-16.el7.x86_64.rpm

4. Install RPM

rpm -U --force binutils-2.23.52.0.1-16.el7.x86_64.rpm


5. Retest the issue

Source: Metalink

No comments:

Post a Comment