starting sp_cop causes the following error in a new environment where Oracle and Shareplex were recently installed:
% ld.so.1: sp_cop: fatal: /var/adm/.splex/V-5.3/lib100/libclntsh.so.10.1: bad ELF type: ET_NONE
The ldd -s on sp_cop (which will uncover the library dependencies for sp_cop) did not provide much clue about any missing links to the libraries except for the clause that it is a bad ELF type:
.
.
find object=libclntsh.so.10.1; required by sp_cop
search path=/usr/openwin/lib:/opt/SUNWspro/lib:/usr/dt/lib:/opt/oracle/product/10.2.0.3/lib32 (LD_LIBRARY_PATH)
ignore path=/usr/openwin/lib (insecure directory name)
ignore path=/opt/SUNWspro/lib (insecure directory name)
ignore path=/usr/dt/lib (insecure directory name)
ignore path=/opt/oracle/product/10.2.0.3/lib32 (insecure directory name)
search path=/var/adm/.splex/V-5.3/lib100 (RPATH from file sp_cop)
trying path=/var/adm/.splex/V-5.3/lib100/libclntsh.so.10.1
search path=/lib:/usr/lib (default)
trying path=/lib/libclntsh.so.10.1
trying path=/usr/lib/libclntsh.so.10.1
libclntsh.so.10.1 => /var/adm/.splex/V-5.3/lib100/libclntsh.so.10.1 - bad ELF type: ET_NONE
.
.
Can be a library linking issue.
When Installing Oracle, sometimes certain steps may be left out inadvertently or run incorrectly without realizing the implications, namely interruption with certain functionality, or inability to run certain applications, which in this case happens to be Shareplex. The problem can also occur after an Oracle upgrade or an Oracle patch upgrade when certain steps may be omitted inadvertently. The anomaly can usually be corrected with ease without having to re-install Oracle and would involve one of the following steps (in the order of ease of running them)
a. Run genclntsh located in $ORACLE_HOME/bin directory to correct any shared library issues. The script genclntsh is used to create a single shared client library.
b. Run "relink all" from $ORACLE_HOME/bin to relink all Oracle libraries. Normally the Oracle libraries are relinked automatically during Oracle upgrade or Oracle patch upgrade but it may be required in case of OS patch upgrade, any issues during with libraries during Oracle upgrade, etc.
c. If "relink all" does not succeed, one can run the relink on a component by component basis. Here is the syntax:
cd $ORACLE_HOME/bin
relink
usage: relink >parameter<
accepted values for parameter: all, oracle, network, client, client_sharedlib,
interMedia, precomp, utilities, oemagent
After the libraries are relinked by one of the following, you should be able to start sp_cop. If the issue still persists, please contact Shareplex Support.
