Error: 0509-150 Dependent module libsysapi.so could not be loaded - Automation Engine

Products

• CA Automic Workload Automation - Automation Engine

Issue/Introduction

When attempting to start Automation Engine components such as the Service Manager (ucybsmgr) or the Reporting Tool (ucybdbrt), particularly during DR activity or after a migration/upgrade, the following error occurs:

exec(): 0509-036 Cannot load program ./ucybsmgr because of the following errors: 0509-150 Dependent module libsysapi.so could not be loaded. 0509-022 Cannot load module libsysapi.so. 0509-026 System error: A file or directory in the path name does not exist.

 

Environment

• Product: Automic Workload Automation
• Component: Automation Engine
• Scenario: Post-migration (e.g., Oracle to PostgreSQL) or Disaster Recovery (DR) activities.

Cause

This issue is caused by an incorrect configuration of the LD_LIBRARY_PATH (or LIBPATH on AIX) environment variable. The utility or service is attempting to load shared object libraries (.so files) from the wrong directory, often pointing to the Server binary directory instead of the Utility binary directory, or vice versa.

Investigation using the ldd command revealed that the tool was loading libraries from the Automation Engine Server binary directory (.../server/bin/) instead of the Utility binary directory (.../utility/bin/)

For example, the incorrect output showed:

libsysapi.so => /path/to/server/bin/libsysapi.so

Instead of the correct path:

libsysapi.so => /path/to/utility/bin/libsysapi.so

Resolution

Update the environment variables to ensure the application loads the correct libraries:

1. Use the ldd command to identify which path is being used for the library: ldd ./ucybsmgr
2. Verify if libsysapi.so points to the .../server/bin/ directory when it should be .../utility/bin/ (or the correct component path).
3. Modify the LIBPATH (AIX) or LD_LIBRARY_PATH environment variable so that the path to the correct component's bin directory appears first.
4. Rerun the ldd command to confirm the correct libraries are mapped.
5. Restart the component.

If the issue persists, contact Support for further assistance.

Additional Information

db=9 trace showed the following db disconnect

PGSQuery:: DisconnectX(END) returned: 1.

PGSQuery:: PQclear (END) returned: 1.

PGSQuery:: PQfinish(END) returned: 1