Start of change

Collecting data for failures after a point-in-time recovery

If you have an inaccessible or incorrect data in a table space after a point-in-time recovery, collect diagnostic information about your table space.

About this task

If a table space becomes inaccessible or incorrect output results
  1. After you run REORG to complete recovery to a point in time
  2. Before materialization of pending definition changes
  3. Check the integrity of your subsystem to diagnose the cause

Procedure

To collect data to diagnose table space failures after a point-in-time recovery:

  1. Save the output from the failed REORG TABLESPACE job.
  2. Run REPAIR DBD DIAGNOSE to ensure that the catalog is consistent with the directory.
  3. If you ran REPORT RECOVERY before you ran the point-in-time recovery, save the REPORT RECOVERY output.
  4. Examine the RECOVER output from the point-in-time recovery for error messages. Save that output. Correct the errors, and run the RECOVER job again.
  5. If the RECOVER completed successfully when you reran it in the previous step, run REORG TABLESPACE again to complete the point-in-time recovery.
  6. Examine the REORG TABLESPACE output from the previous step for error messages. Save that output. Correct the errors, and run the REORG TABLESPACE job again.
  7. If the REORG TABLESPACE job completed successfully when you reran it in the previous step, run REPORT RECOVERY to determine whether the appropriate records were inserted into the SYSIBM.SYSCOPY table by REORG TABLESPACE.
  8. Issue a SELECT * FROM SYSIBM.SYSPENDINGDDL, statement, and save the results.
  9. Run DSN1PRNT to dump the first few data pages of the table space, and validate the contents of the data rows. Save the output.
  10. Submit all saved output to IBM® Software Support.
End of change