Adrelink fails with ld cannot find lclntsh

1.Patch application was failing with the below error in Non production instance

/usr/bin/ld: cannot find -lclntsh

2.We observed that the issue was due to libclntsh soft link which was incorrect, As you can see below the soft link was pointing to the PROD
3. Run the script  $ORACLE_HOME/bin/genclntsh which will fix the soft link issue

[appstest@test001]$ sh genclntsh
[appstest@test001]$
[appstest@test001]$ pwd
/ebs/oracle/TEST/apps/tech_st/10.1.2/bin

4.Check the soft link  of libclntsh  again which will be corrected by the script we have run in 3rd script as seen in below screenshot.



5.Run the relink again which will be successfully now

Comments

Post a Comment

Popular posts from this blog

Steps to run Autoconfig for patch File system 12.2

1.       To run Autoconfig from the patch file system you must disable trigger ebs_login prior to running autoconfig. SQL> show user; USER is "SYSTEM" SQL> alter trigger ebs_logon disable; Trigger altered. 2.       Now run autoconfig with the patch env sourced [appltest@test001]$ echo $FILE_EDITION [appltest@test001]$patch [appltest@test001]$ adautocfg.sh Make sure Autoconfig completes ok      3. Enable the login trigger “alter trigger ebs_logon enable”                  SQL> conn system/Oracle4u                  Connected.                SQL> SQL> alter trigger ebs_logon enable;                 Trigger altered.
Read more

txkCfgUtlfileDir.pl -mode=getUtlFileDir as per Cloning Oracle E-Business Suite Release 12.1 with Multitenant Database using Rapid Clone (Doc ID 2560690.1) errors with ERRORMSG: Invalid APPS database user credentials

 txkCfgUtlfileDir.pl -mode=getUtlFileDir as per Cloning Oracle E-Business Suite Release 12.1 with Multitenant Database using Rapid Clone (Doc ID 2560690.1) errors with ERRORMSG: Invalid APPS database user credentials validate_apps_password.log Pattern found... ================ EXIT STATUS: 1 Invalid APPS database user credentials. Solution Check  lsnrctl status <listener_name>,check files under $TNS_ADMIN,check environment,Check if case sensitive login is enabled and if enabled,disable it
Read more

ADOP fs_clone failing with ERROR: Managed Server's are not in sync between file system context and DB context

 adop fs_clone failing with below error. +++++++++++++++++++++++++ configProperty id = Server11 Count for NodeIterator nextNode = 3 ERROR: Managed Server's are not in sync between file system context and DB context ERROR: Update Moveplan Fail START: Inside exitClone.... Updating status INCOMPLETE for ApplywlsTechStack START: Updating status INCOMPLETE for action ApplywlsTechStack END: Updated status INCOMPLETE for action ApplywlsTechStack SOLUTION Please follow the solution in  Doc ID 2232990.1  and advise accordingly To resolve the issue test the following steps in a development instance and then migrate accordingly: 1. Unlock the configuration in the weblogic console via the following steps: A. Open a browser and enter the weblogic console URL eg: https ://localhost:port/console as the administrator. B. Navigate to the weblogic server administration Applications Configuration console. C. Unlock the weblogic server configuration by clicking 'Release Configuration' option.
Read more