Component : DB Independent Database Interface -

Solution : https://service.sap.com/sap/support/notes/193616 (SAP Service marketplace login required)

Summary :
SAP Note identifies issues with DB Connect failures post-Oracle Client installation on UNIX, lack of shared library information visibility, and duplication of dynamic libraries. Post static linking of R/ri tools up to Release 4.0B, dynamism introduced in Release 4.5A led to dependencies on runtime loaded shared libraries: DBMS library dbslib. and client-specific libraries like libclntsh.so for Oracle. Errors in Oracle Client Library placement (pre-PREPARE phase, Release 4.6B upgrade) cause DBCHK_PRE or PRE_IMPORT0 failures. Remedially, ensuring correct library path and version alignment between SAP tools and Oracle Client Libraries is advised.

Key words :
/tp connect <sid> pf=/usr/sap/put/bin/tpparam       -ddblibpath=/usr/sap/put/exeas, load             /usr/sap/mm1/sys/exe/run/dboraslib, dbms client library           oci_80500_shareddbsl shared library version   46c, /usr/sap/<sid>/sys/exe/run, shl_load /usr/sap/put/exe/dboraslib, -ddblibpath=/usr/sap/put/exefrom, db connect additional key words oracle 8, directory   /oracle/<oracle_client_release>_<bits>/lib, sap dbms library db<dbms>slib, tp ---> libclntsh ---> dboraslibthe logical sequence decides

Related Notes :

189591	Connect problems:4.6B, ORACLE, HP (64 bit) and DEC
180430	Installing the ORACLE client software for UNIX