Oracle Client Update Restart Require

Products

• CA Automic Workload Automation - Automation Engine

Issue/Introduction

This article addresses whether a restart of the Automation Engine (AE) is required after updating the Oracle client on a Linux/UNIX server and provides guidance on updating associated JDBC drivers.

Environment

• Product: Automic Automation Engine
• Version: 24.x and above
• Database: Oracle
• OS: Linux / UNIX

Cause

Technical inquiry regarding maintenance procedures during an Oracle client upgrade.

Resolution

Yes, a restart is recommended of the components tied to the Oracle client (CPs/WPs). 

Follow these steps to ensure a clean update:

1. Stop the AE components
2. Update the Oracle client on the server.
3. Update the JDBC JAR files in the server/bin/lib directory. Copy the new versions of the following files from the updated Oracle client installation:
   • ojdbc8.jar
   • xdb6.jar
   • xmlparserv2.jar
   • orai18n.jar (if present) 
4. Remove the old versions of these JAR files from the directory.
5. Verify library links using the ldd command on the engine binaries (e.g. ucsrvcp/ucsrvwp - as noted here: Installing the AE - UNIX) to ensure htey point to the correct Oracle client path.
6. Restart the AE components

 

If running multiple AE nodes, update the Oracle clients consistently across all of them at the same time. Mixed-version drift across nodes could contribute to intermittent DB errors.