ORACLE 31495 Errors:

Kgen batch jobs can sometimes fail with Oracle 31495 errors.

Upon receiving this type of error for a job failure first ops should wait 2-3 min then restart the job.

If the job fails again with the same error then contact the Environment Team to flush the buffer and clear backend sessions.  Once that is done by the Env Team Ops can restart the job.

If job fails again, wait 10 min then restart the job again.

 

kGen0733 Failure while inserting --------- - row exists with the same key.

Try to restart if fails again, wait 5 min and restart again. If fails again contact application support.

 

Job failures (Example: PKGBEYEX%):

kGen2330 Error in routine dgn_upd_prwtnr. – restart until successful.

 

PKG%HOLE% job failures:

error :REGION_HOLES_IN_PAGES: fDO_HOLES_IN_PAGES                                                                                  

ERROR CREATING TABLE CURR_ISSUE_ADS

ORA-00955: name is already used by an existing object

!!!!! Message  @@@0000 was not found.                               

--- PG  HOLES IN PAGES PROCESS HAS TERMINATED WITH ERROR ---

Application run ended

Application run ended with failure.

Wait 10 min and restart, if fails again, wait 20 min and restart.

 

PKGPROJ% job failures:

Restart jobs until jobs complete successfully. If after 3 failures, contact application support.

 

 

Jobs running long after restarting or not showing up in application or database server:

Contact the CTL DBA to advise them to check for (inactive) sessions that are locking the database.

Example: We incurred an issue where a job for start onlines was running long we aborted and restarted and the job ran long again, it was due to inactive sessions locking 50% or more of the database resources on different tables. This kept new or active processes from getting the CPU or Database resources necessary to run correctly. CTL DBA should be able to check for sessions locking on the database.