MAINTAINING THE DOMINO AND DB2 ENVIRONMENT
During this procedure, you will be issuing a command where you specify a name for the restored database. The abbreviation restoreDB is used to represent that database.
This procedure can be used with a tablespace or database level backup image.
Prerequisites
All tablestores that are restored with this procedure are placed in the database, restoreDB.
1. From the DB2 Command Line Processor (CLP), type this command:
DB2 automatically reassigns a new storage PATH for system-managed space (SMS) tablespaces, for example, SYSCATSPACE or DOMINO. This did not automatically occur in some early versions of UDB 8.1.
Note The IGNORE ROLLFORWARD CONTAINER OPERATIONS option is important. In the event the transaction logs contain operations on the original tablespace containers, any attempt to replay the container operations, which in and of themselves are rare, will run into problems since that container will already be in use by another database.
Containers that are relative to the database directory do not need to be redirected since they are created under the new database’s database directory. For example, SYSCATSPACE and DOMINO tablespaces for a DB2 database being used by Domino should be defined as SMS tablespaces with storage relative to the new database's directory.
Note To see a sample output generated by the command in Step 5, see "Sample output" at the end of this procedure.
9. Complete the recovery. You can choose to perform a recovery to a specific point in time or a recovery to the end of logs. The target of the ROLLFORWARD command is now the new DB2 database, not the source DB2 database as in the examples above. Enter this command to complete the recovery:
Sample output
Changed path to log files (NEWLOGPATH) =
Path to log files = :\newdb\logs\
(for our example)
Overflow log path (OVERFLOWLOGPATH) =
Mirror log path (MIRRORLOGPATH) =
First active log file = S0000002.LOG