If a user inadvertently updates, inserts or deletes data in a table during the day and you need to recover the table to a prior point in time, you can recover to a checkpoint rather than an Image Copy or a quiesce point to reduce the amount of data loss. For example, if the user issued a “bad” query at 17:18 on March 29, 2018, you can print the checkpoint queue with DB2 utility DSNJU004. The output will look similar to:
CHECKPOINT QUEUE
18:40:10 MARCH 29, 2018
TIME OF CHECKPOINT 18:30:04 MARCH 29, 2018
BEGIN CHECKPOINT RBA 0000000023FDD4187405
END CHECKPOINT RBA 0000000023FDD4194000
END CHECKPOINT STCK 00D41A198B683F8E0A00
TIME OF CHECKPOINT 18:15:04 MARCH 29, 2018
BEGIN CHECKPOINT RBA 0000000023FDCE6AA615
END CHECKPOINT RBA 0000000023FDCE6B73E7
END CHECKPOINT STCK 00D41A16311B02B53A00
TIME OF CHECKPOINT 18:02:44 MARCH 29, 2018
BEGIN CHECKPOINT RBA 0000000023FDC976C806
END CHECKPOINT RBA 0000000023FDC9785E4F
END CHECKPOINT STCK 00D41A136F4ACE910800
TIME OF CHECKPOINT 17:47:44 MARCH 29, 2018
BEGIN CHECKPOINT RBA 0000000023FDC3A02EF2
END CHECKPOINT RBA 0000000023FDC3A11000
END CHECKPOINT STCK 00D41A1014FBDC3B0800
TIME OF CHECKPOINT 17:32:44 MARCH 29, 2018
BEGIN CHECKPOINT RBA 0000000023FDBDA9FBDC
END CHECKPOINT RBA 0000000023FDBDAAD967
END CHECKPOINT STCK 00D41A0CBAAD71430800
TIME OF CHECKPOINT 17:17:44 MARCH 29, 2018
BEGIN CHECKPOINT RBA 0000000023FDB7EAA020
END CHECKPOINT RBA 0000000023FDB7EC4622
END CHECKPOINT STCK 00D41A096060B5B53000
There is a checkpoint at 17:17 on March 29, 2018 that may be a good recovery point.
The tablespace can be recovered with
//SYSIN DD *
RECOVER TABLESPACE proddb00.prodts33
TORBA X'23FDB7EC4622'
/*
If you have an old table space with multiple tables, they will all be recovered to the RBA. Rebuild all the associated indices after the recovery completes.
