AAI Job Definitions fail to update after Autosys database migration due to JOID changes

Products

• Automation Analytics & Intelligence

Issue/Introduction

AAI scheduler job definitions do not update and job status remains behind after migrating an Autosys database (e.g., from RLS to QUA). The AAI logs may indicate that existing jobs are not found or updates are not being processed for the expected scheduler.

Environment

• Automation Analytics & Intelligence (AAI) 24.x
• Autosys Scheduler
• Database Migration (Oracle/SQL Server)

Cause

AAI uses the joid (Job ID) from the Autosys ujo_job table to determine the uniqueness of jobs. During a database migration, if the jobs are re-inserted rather than migrated as an exact database copy, the joid values change. AAI does not recognize the new joid values as the same jobs, preventing updates to existing definitions.

Resolution

1. Perform an Exact Database Migration Perform the migration again from the source Autosys database to the target database ensuring that it is an exact copy. This maintains the integrity of the joid values so AAI can continue processing updates without interruption.

2. Migrate to a New Scheduler in AAI If an exact copy is not possible, add the new Autosys instance as a new scheduler in AAI. Note the following impacts:

   • Historical run information for the old scheduler will not be associated with the new scheduler.
   • Existing jobstreams must be migrated to the new scheduler.