Perform this operation only on user RDAREAs and user LOB RDAREAs (the original RDAREAs of user RDAREAs and the original RDAREAs of user LOB RDAREAs if the inner replica facility is used). If a row-partitioned table is defined, execute the pdrdrefls command with the -t option to identify the RDAREAs comprising the row-partitioned table.

If you need to recover more RDAREAs than the following example shows, add their names following the -r option.

 
pdrdrefls -k chk -e org -c ref
-r rdarea01,rdarea02
 

 
pdstop
 

If HiRDB cannot be terminated normally, enter the pdstop -f command to forcibly terminate it. This step is not necessary if HiRDB has already terminated abnormally.

Restore the RDAREAs to be recovered and all related RDAREAs. The related RDAREAs differ depending on which process has been executed since the last backup was acquired. For details about the related RDAREAs, see 6.3 RDAREAs to be backed up together. For example, if CREATE TABLE has been executed since the last backup was acquired, see CREATE TABLE in Table 6-3 RDAREAs to be backed up together.

 
pdrstr -m /rdarea/mast/mast01 -b /pdcopy/backup01 -r MASTER,DDIC,USER1,LOB11
 

Explanation

-m: Specifies the name of the first HiRDB file in the master directory RDAREA.

-b: Specifies the name of the backup file.

-r: Specifies the name of the RDAREA to be recovered.

MASTER: Master directory RDAREA

DDIC: Data dictionary RDAREA

USER1: User RDAREA (RDAREA to which a table was added)

LOB11: User LOB RDAREA (RDAREA that stores columns with BLOB attribute)

 
pdstart
 

If HiRDB already terminated abnormally as discussed in (2), or if it was forcibly terminated using the pdstop -f command, you must initialize the status file before starting HiRDB normally. First, enter the pdstsrm command to delete the status file and then enter the pdstsinit command to re-create the status file.