AutoSys Cross-Instance Query Support in Mixed Oracle/PostgreSQL Environments

Products

• Autosys Workload Automation

Issue/Introduction

When migrating from Oracle to PostgreSQL using the AutoSys Data Migrator, users may wonder if a hybrid environment (where one instance is on PostgreSQL and the other remains on Oracle) is supported, specifically regarding cross-instance (X-instance) job dependencies.

Environment

Autosys 24.x

Resolution

This configuration is fully supported. AutoSys communication protocols are abstracted from the backend database.

Key Technical Details:

• Architectural Isolation: Instances are isolated via their respective $AUTOUSER directories. Each instance references its own config.$AUTOSERV for database connection strings and drivers.
• Shared Binaries: The core $AUTOSYS binaries dynamically load the required database client libraries based on the local environment variables.
• X-Instance Logic: Cross-instance dependencies rely on network communication (TCP/RPC) between Application Servers and Schedulers. Instance A queries Instance B’s Application Server; Instance B retrieves the status from its own local database (regardless of type) and returns the result over the network.
  
  
  

Best Practices for Migration:

1. Strict Profile Isolation: Ensure autosys.sh for the PostgreSQL instance sources the PostgreSQL client libraries in LD_LIBRARY_PATH, while the Oracle instance continues to source Oracle client libraries.
2. Unique Ports: Verify that Application Server and Scheduler ports remain unique between the two instances on the shared host.
3. Client Installation: Ensure native PostgreSQL client libraries are installed on all scheduler nodes before cutover.