REORG job fails or is delayed

Utility problems (LOAD, UNLOAD, REORG, RUNSTATS, COPY) usually trace to input data, object state, or job control.

What it means

• Utilities run outside normal SQL with their own rules and restrictive states.
• A failed utility can leave objects in states that block application SQL.

Common causes

• Input data violating table constraints (LOAD).
• Object already in a restrictive state.
• Insufficient sort work space for REORG.
• Stale statistics misleading the optimizer (RUNSTATS timing).

How to diagnose

• Read the utility SYSPRINT — it names the failing phase.
• Check object status with -DISPLAY.
• Verify input file format against the utility control cards.

How to fix it

• Fix the input data and rerun from the restart point.
• Clear restrictive states with the required utility.
• Allocate adequate sort work datasets.

Example: Check object state first

Restrictive states block both utilities and SQL.

Interview tip

• Q: How would you troubleshoot a REORG job fails or is delayed in production?
• A: I would read the utility SYSPRINT for the failing phase, check object state, fix input or state, and restart the utility.

Prevention checklist

• Validate input before LOAD.
• Schedule utilities outside application windows.
• Keep RUNSTATS current.