Recovering table spaces—full and rollforward recovery

This procedure allows us to restore only part of a database. This can be useful in recovering from many types of failure scenarios, such as year-end batch jobs or monthly data migration, when they affect only tables confined into specific table spaces.

Getting ready

Identify the table space and the backup you want to use for this operation. Make sure users are not connected.

How to do it...

1. Full (version) recovery:

   We will first perform a full (version) recovery of a single table space:

   [db2inst1@nodedb21 ~]$ db2 "QUIESCE DATABASE IMMEDIATE FORCE CONNECTIONS"
   DB20000I  The QUIESCE DATABASE command completed successfully.
   [db2inst1@nodedb21 ~]$ db2 CONNECT RESET
   DB20000I  The SQL command completed successfully.[db2inst1@nodedb21 ~]$ db2 "RESTORE DATABASE POS 
     TABLESPACE (POS_TBLS) ONLINE 
     FROM "/xchng/backups" 
     TAKEN AT 20111125013459 
     WITH 2 BUFFERS BUFFER 1024 PARALLELISM 1 
     WITHOUT ROLLING FORWARD WITHOUT PROMPTING"
   SQL2537N  Roll...