Error ORA-12899 Value Too Large When Adding AutoSys Scheduler In AAI

Products

• Automation Analytics & Intelligence

Issue/Introduction

Adding an AutoSys scheduler hangs and remains in process for extended periods without completing ․​​​​‌​‍

ERROR MESSAGE:
"2026-02-25 07:59:55, 104 INFO [JammerManager] Converter for scheduler [scheduler-name] has not run; skipping Jammer this cycle․" 

"ERROR [SqlExceptionHelper] ORA-12899: value too large for column <SCHEMA_NAME>․JOBCONDITION․GLOBALVARIABLEVALUE (actual: XXX, maximum: 255)" 

SYMPTOMS:
    Scheduler integration stays in process for over 24 hours 
    The converter on the scheduler fails to run 
    Oracle database throws a generic JDBC exception for batch execution 

CONTEXT: This occurs when adding a new AutoSys scheduler to the AAI environment 

IMPACT: Administrators cannot successfully complete the scheduler integration

Environment

Automation Analytics & Intelligence (AAI) 24․X
Database: Oracle

Cause

AAI parses the sendevent command to extract the global variable name and value, then attempts to save the value into the JOBCONDITION globalvariablevalue column ․
This column is defined in the AAI Hibernate mapping with a maximum length of 255 characters ․
If an AutoSys job passes a global variable value exceeding this limit, Oracle rejects the insert with an ORA-12899 error.

Resolution

PREREQUISITES:

• Database access to run SQL queries against the AutoSys database

• Access to modify AutoSys jobs

STEPS:

1․ IDENTIFY THE PROBLEM JOB

Path/Command:
SELECT uj․JOB_NAME, ucj․* FROM UJO_COMMAND_JOB ucj LEFT JOIN UJO_JOB uj ON uj․JOID = ucj․JOID WHERE ucj․COMMAND LIKE 'sendevent%SET_GLOBAL%'

EXPECTED:
The query returns a list of jobs executing SET_GLOBAL commands
NOTE: This must be run on the AutoSys database

 

2․ VERIFY THE VARIABLE LENGTH

Path/Command:
SELECT j․job_name, UTL_RAW․CAST_TO_VARCHAR2(DBMS_LOB․SUBSTR(b․data, 4000, 1)) AS cmd_text FROM ujo_job j JOIN ujo_jobblob b ON j․joid = b․joid AND j․job_ver = b․job_ver AND j․over_num = b․over_num WHERE j․is_currver = 1 AND j․job_name = '[job-name]'

EXPECTED:
The command string reveals the exact length of the value being passed

 

3․ MODIFY OR DELETE THE AUTOSYS JOB

Access the AutoSys environment and either delete the problematic job or modify its command so the global variable value string is less than the 255-character limit

EXPECTED:
The job no longer exceeds the AAI database character constraint

 

VERIFY SUCCESS:

• Restart the AAI, scheduler add process

• Confirm the Jammer log no longer shows the ORA-12899 error

   

   

Additional Information

KNOWN LIMITATIONS:
The JOBCONDITION globalvariablevalue column is restricted to 255 characters by the Hibernate file configuration

PREVENTION:
Ensure all AutoSys jobs using SET_GLOBAL keep the defined variable values under 255 characters