Client Shared Library does not get generated and no errors displayed, or relink error that libclntsh does not exist
(Doc ID 460078.1)
Last updated on OCTOBER 22, 2019
Applies to:Oracle Database - Enterprise Edition - Version 220.127.116.11 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
***Checked for relevance on 21-Jul-2011***
***Checked for relevance on 26-DEC-2012***
You are in the process of relinking, either manually, or automatically as part of a new install or while applying a patch or patchset.
The relink process is attempting to build a new client shared library.
If you were only running "genclntsh" or "make -f ins_rdbms.mk client_sharedlib", you notice that genclntsh runs, but does not create the client shared library (libclntsh) AND does not display an error.
If you already have the libclntsh libraries, you may find that the date/time stamp for the libraries does not get updated when you try to re-generate them (genclntsh).
If other relinks are done which expect to find the missing client shared library, you may notice relink errors similar to the following (depending on OS platform and Oracle version):
/usr/ccs/bin/ld: Can't find library: "clntsh"
/usr/bin/ld: cannot find -lclntsh
ld: fatal: file libclntsh.so: open failed: No such file or directory
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document