A custom background job is being unexpectedly terminated by a scheduled cleanup job, even after explicitly marking it "Exclude from Cleanup" — how can the actual point of failure inside the custom job's own logic be pinpointed?

Q: A custom background job is being unexpectedly terminated by a scheduled cleanup job, even after explicitly marking it "Exclude from Cleanup" — how can the actual point of failure inside the custom job's own logic be pinpointed?

Sprinkle the custom job's PL/SQL with calls to Transaction_Sys.Log_Status_Info (not Set_Status_Info) at each meaningful step, logging both a marker message and relevant variable values — Log_Status_Info runs as an autonomous transaction and commits immediately, so its log entries survive even if the session running the job is later killed mid-execution, letting you see exactly how far the job got before being terminated rather than losing that information along with the rest of the rolled-back session.

Answer

Sprinkle the custom job's PL/SQL with calls to Transaction_Sys.Log_Status_Info (not Set_Status_Info) at each meaningful step, logging both a marker message and relevant variable values — Log_Status_Info runs as an autonomous transaction and commits immediately, so its log entries survive even if the session running the job is later killed mid-execution, letting you see exactly how far the job got before being terminated rather than losing that information along with the rest of the rolled-back session.

← Browse Developer Studio, deployment, and upgrades questions