In an APEX automation, we call a procedure that, in turn, calls dbms_stats.gather_table_stats for multiple tables. After a new deployment of our APEX application, the (unchanged) jobs fail with an error message that the job name is too long (34 characters instead of the allowed 32).
The job name (for gathering stats) gets generated automatically, e.g. APEX$AUTOMATION_12358554865558). By creating a new automation, we “solved” the issue for now; however, after the next deployment, we may have the same problem again.
ORA-00604: error occurred at recursive SQL level 3
ORA-06512: at "SYS.DBMS_STATS", line 40799
ORA-12899: value too large for column "SYS"."WRI$_OPTSTAT_OPR"."JOB_NAME" (actual: 34, maximum: 32)
ORA-06512: at "SYS.DBMS STATS", line 2258
ORA-06512: at "SYS.DBMS_STATS", line 40776
We experimented with the length of the name of the automation, but it does not look like we could influence the name of the generated job. We also noticed that the job name stays the same with each new call, but with different table names and session ids.