Hi
We've been testing recovery scenarios:
we have a plan to alter tables to a new format (eg sizing various columns), then if we encounter application problems, we'd have to revert
(Running on MVS and DB2 V7)
Before doing the change, under testing I've run a COPY and then QUIESCE on a tablespace (contains 1 table), then:-
1) added some data, then a RECOVER (and REBUILD indexes) from the COPY taken earlier -works fine, the extra data has disappeared
2) dropped the table and recreated it in a new format, added new data into it - then to test the recovery scenario, tried the RECOVER from the old COPY dataset....only guess what, the table is still there in the new format - only EMPTY! (not really what I wanted )
Is this related to the fact that we've got a new table id, so the RECOVER doesn't recognise the table to be recovered?
Or is there a workaround, or whould we just have to keep the old DDL, and UNLOAD all the data before we start fiddling with the table !
Thanks
Gary
We've been testing recovery scenarios:
we have a plan to alter tables to a new format (eg sizing various columns), then if we encounter application problems, we'd have to revert
(Running on MVS and DB2 V7)
Before doing the change, under testing I've run a COPY and then QUIESCE on a tablespace (contains 1 table), then:-
1) added some data, then a RECOVER (and REBUILD indexes) from the COPY taken earlier -works fine, the extra data has disappeared
2) dropped the table and recreated it in a new format, added new data into it - then to test the recovery scenario, tried the RECOVER from the old COPY dataset....only guess what, the table is still there in the new format - only EMPTY! (not really what I wanted )
Is this related to the fact that we've got a new table id, so the RECOVER doesn't recognise the table to be recovered?
Or is there a workaround, or whould we just have to keep the old DDL, and UNLOAD all the data before we start fiddling with the table !
Thanks
Gary