In the case of a HiRDB parallel server configuration, check for the system log file at the dictionary server and back-end server.

 
pdlogls -d sys
 

To unload the contents of the current file, swap the system log files. In the case of a HiRDB parallel server configuration, swap the system log files at the dictionary server and back-end server.

 
pdlogswap -d sys -w
 

Unload the contents of the current system log file checked in step (1). In the case of a HiRDB parallel server configuration, unload the contents of the current system log file at the dictionary server and back-end server.

 
pdlogunld -d sys -s bes1 -g log01 -o /unld/unldlog02
 

When the automatic log unloading facility is used

In this case, this step is not necessary. Use the pdlogatul command to confirm that the automatic log unloading facility is functioning. Also, use the pdlogls command to check if unloading has been completed.

 
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.

 
pdrstr -m /rdarea/mast/mast01 -b /pdcopy/backup01 -a
 -l /unld/unldlog02
 

#

If there are data dictionary LOB RDAREAs, use the -r option instead of the -a option to specify all of the RDAREAs other than data dictionary LOB RDAREAs.

Explanation

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

-b: Specifies the name of the backup file that stores the backup of all RDAREAs.

-a: Specifies that all RDAREAs are to be backed up.

-l: Specifies the name of the unload log file to use from the time the backup is made.

Back up the RDAREAs in case they are needed for the next database recovery.

 
pdcopy -m /rdarea/mast/mast01 -M x -b /pdcopy/backup02 -a
 

Explanation

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

-M: Specifies the backup acquisition mode.

-b: Specifies the name of the backup file.

-a: Specifies that all RDAREAs are to be backed up.

 
pdstop
 

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

This step is not necessary if there is no data dictionary LOB RDAREA.

The procedure for restoring the data dictionary LOB RDAREA (for storing objects) follows.

Procedure

1. Use the pdmod command to re-initialize the data dictionary LOB RDAREA for storing objects.
   

   pdmod -a /rdarea/conf/control2

2. Use ALTER ROUTINE to re-create the SQL objects of all stored routines and triggers.
   

   ALTER ROUTINE ALL

This step is not necessary if there is no list RDAREA.

Procedure

1. Shut down and close the list RDAREA.
   

   pdhold -r LISER1 -c

2. Use the pdmod command to re-initialize the RDAREA.
   

   pdmod -a /rdarea/conf/control3

3. Release the list RDAREA from shutdown and open it.
   

   pdrels -r LISER1 -o

This step is not necessary if there is no temporary table RDAREA.

Procedure

1. Shut down and close the temporary table RDAREA.
   

   pdhold -r TMPRDAREA -c

2. Use the pdmod command to re-initialize the RDAREA.
   

   pdmod -a /rdarea/conf/control4

3. Release the temporary table RDAREA from shutdown and open it.
   

   pdrels -r TMPRDAREA -o