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;           ...
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

Change the WebLogic password in EBS 12.2

Change the WebLogic password How do you change password  in EBS 12.2 for weblogic  The following sections show the steps for updating the WebLogic password for Txk Delta 7 and later and for versions earlier than Txk Delta 7. TKX DELTA 7 AND LATER The following steps apply to WebLogic Txk Delta 7 and later: ⦁ Run the following command to source the run filesystem, shut down all application tier services except the Admin Server, and ensure that no application services (except admin server and node manager) are running on the primary application server: ⦁ adstpall.sh apps/apps_password -mode=allnodes -skipNM -skipAdmin ⦁ Run the following command to change the Weblogic administration password and start the services: ⦁ perl $FND_TOP/patch/115/bin/txkUpdateEBSDomain.pl -action=updateAdminPassword The system prompts you for the Apps password, the old WebLogic password and the new WebLogic password. Following is some sample output from this process: $ perl $FND_...
Read more