AutoSys Failed to Start Post-Sybase Upgrade: Missing libsybdb64.so Shared Object Library
Article ID: 428039
Updated On:
Products
Issue/Introduction
After upgrading the Sybase database environment, the AutoSys Application Server and Event Daemon failed to initialize. The system was unable to establish a connection to the event server, resulting in an immediate shutdown of the AutoSys services.
Error Message from Event Daemon Logs:
[01/28/2026 03:52:41] CAUAJM_E_90010 Unable to load libsybdb64 <libsybdb64.so: cannot open shared object file: No such file or directory>. [01/28/2026 03:52:41] init_syb failed with return code:4
Environment
-
Product: AutoSys Workload Automation 12.1
-
Operating System: Red Hat Enterprise Linux (RHEL) 9.7
-
Database: Sybase ASE (Upgraded from 16.0 SP04 PL06 to 16.1 SP00 PL01)
-
Instance Mode: Dual Server Mode
Cause
The issue was caused by an Environment Problem following the Sybase upgrade.
-
The critical library file libsybdb64.so was missing from the Sybase library directory.
-
Functionality: This library is a mandatory component of the Sybase DB-Library (DB-Lib) used by the AutoSys client to communicate with the Sybase ASE database.
-
During the upgrade process, this specific library was either not installed or was removed, preventing AutoSys from loading the database client interface
Resolution
issue was resolved by restoring the missing database client components.
-
Action Taken: The customer identified that the libsybdb64.so file was missing in the new Sybase installation path. The file was manually copied from a functioning AutoSys/Sybase instance into the local Sybase lib folder.
-
Verification: Once the library was restored and the environment variables (specifically those pointing to the Sybase library path) were verified, AutoSys services started successfully.
-
Note to Users: AutoSys does not manage or delete database client libraries; these must be maintained by the Database Administrator (DBA) or System Administrator during third-party software upgrades.
Feedback
