Solving Operational Business Intelligence with InfoSphere Warehouse Advanced Edition

308 Solving Operational Business Intelligence with InfoSphere Warehouse Advanced Edition

8.5 Example recovery scenarios using Optim High

Performance Unload

The scenarios and example control files in this section illustrate how Optim High

Performance Unload can form a part of your recovery strategy using the

suggestions given in this document. The examples illustrate the recovery of

partitioned tables through backup images stored on TSM. These examples

cover:

򐂰 Recover existing partitioned tables using backup images on local disk.

򐂰 Recover dropped partitioned table using backup images on TSM and named

pipes.

򐂰 Recover data using non-production system and backup images on TSM.

The backup strategy for each table space was to back up one database partition

per node in parallel until the table space was backed up. In the following

examples, the same sequence was applied when unloading data.

8.5.1 Recover existing partitioned tables using backup images on

disk

This scenario uses Optim High Performance Unload to recover a partitioned

table from online table space backup images stored on disk. This scenario

applies where the table exists in the database but the contents have been

compromised or corruption has occurred.

The unload block must specify each path where backup images files exist.

Because the table to be recovered exists in the database, the database catalog

is referenced in the global control block rather than a catalog associated with a

backup image. This reduces the number of backup images to be read and

therefore increases the speed of the Optim High Performance Unload operation.

Example 8-4 shows the control file used in this scenario.

Example 8-4 Sample control file to unload data from disk

-- Global Block will use local database catalog

GLOBAL CONNECT TO TPCDS;

-- Unload Block specifies backup images for partitions 1 to 16

UNLOAD TABLESPACE

PART(1:16)

USING BACKUP DATABASE TPCDS TABLESPACE ("HASHTS") FROM

“/work1/backup”,”/work2/backup”,”/work3/backup”,

“/work4/backup”,”/work5/backup”,”/work6/backup”,

“/work7/backup”,”/work8/backup” ON SOURCE HOST TAKEN AT 2011033108;