Symptom
- Running custom scripts to start and stop BusinessObjects services and Tomcat.
- When the BusinessObjects services goes down below are the error traced in CMS logs,
Fail to initialize or uninitialize. Reason is The root server reported an err or Initialization Failure. (Reason: Database access error. Reason Loading shared object failed. First tried to load library clntsh and failed because of error: [ld.so.1: boe_cmsd: fatal: clntsh: open failed: No such file or directory].
Second tried to load library libclntsh.so and failed because of error:[ld.so.1: boe_cmsd: fatal: libclntsh.so: open failed: No such file or directory].Database access error. Reason Loading shared object failed.
First tried to load library clnt sh and failed because of error: [ld.so.1: boe_cmsd: fatal: clntsh: open failed: No such file or directory]. Second tried to load library libclntsh.so and failed because of error: [ld.so.1: boe_cmsd: fatal: libclntsh.so: open failed:
No such file or directory]. Error initializing database wrapper environment for DatabaseSubsystem.).:Database access error. Reason Loading shared object failed.First tried to load library clntsh and failed because of error:[ld.so.1: boe_cmsd: fatal: clntsh: open failed: No such file or directory]. Second tried to load library libclnts h.so and failed because of error: [ld.so.1: boe_cmsd: fatal: libclntsh.so: open failed: No such file or directory]. Error initializing database wrapper environment for DatabaseSubsystem.
Read more...
Environment
-
BusinessObjects Enterprise 3.1
-
Solaris 10
-
Tomcat 5.5
-
Oracle 11g Release 1.
Product
Keywords
load,library,clntsh,failed,LD_LIBRARY_PATH , KBA , BI-BIP-ADM , BI Servers, security, Crystal Reports in Launchpad , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.