WP or CP on unix/linux will not start - receives LoadLibrary - libclntsh.so.11.1 error

Products

• CA Automic Workload Automation - Automation Engine

Issue/Introduction

WP or CP on unix/linux will not start - receives LoadLibrary - libclntsh.so.11.1 error

Environment

Release: AUTWAB99000-11.0-Automic Workload Automation-Base Edition
Component:

Resolution

Symptoms

When attempting to start the WPs or CPs on UNIX or LInux, the process fails and the following shows in the logs:

20150218/162707.735 - U0029120 UCUDB: Function LoadLibrary failed. Library 'ucuoci.so' error 'libclntsh.so.11.1: cannot open shared object file: No such file or directory'.

20150218/162707.735 - U0003611 DB OPEN executed. Return Code = '0000003531'

20150218/162707.736 - U0003620 Routine 'UCMAIN_R' forces trace because of error.

20150218/162707.736 - U0003450 The TRACE file was opened with the switches '0000000000000001'.

20150218/162707.736 - U0003380 Server 'UC4P#WP' version '10.0.0+hf.3.build.312' (Runtime '0/00:00:00', Log# '1', Trc# '1').

20150218/162707.736 - U0003491 There is a time difference of '0/00:00:00' or '0' seconds to the Primary Server.

20150218/162707.736 - U0003375 Server usage of the last minute '0%', the last 10 minutes '0%' and the last hour '0%'.

20150218/162707.736 - U0003531 UCUDB: Error while checking data source (e.g. code conversion or driver problem, see log file).

20150218/162707.766 - U0003449 Output to the TRACE file is finished.

20150218/162707.766 - U0003531 UCUDB: Error while checking data source (e.g. code conversion or driver problem, see log file).

20150218/162707.766 - U0003410 UC4.Server 'UC4P#WP' version '10.0.0+hf.3.build.312' ended abnormally.

---

Cause

This is usually caused by incorrect environment variables, specifically the LD_LIBRARY_PATH - you can verify this by running the command:

env | grep LD_LIBRARY_PATH

and confirming if the automationengine /bin directory is in the resulting line

---

Resolution

A short term resolution is to from the automationengine /bin directory run the command:

export LD_LIBRARY_PATH=$PWD:$LD_LIBRARY_PATH

As a longer term resolution, an admin will need to be sure that the user's .profile includes the automationengine's /bin directory in the LD_LIBRARY_PATH.

---

Troubleshooting steps

If this error continues to occur after the steps above, open an Incident with Support with the following:

1) The results of an env command

2) The latest WP or CP log showing the error message