Nonstop Database, HiRDB Version 9 System Operation Guide

[Contents][Index][Back][Next]

15.6.2 Example

This example changes the opening trigger attribute for user RDAREAs (RDAREA1 to RDAREA3) from INITIAL to SCHEDULE; it also changes the opening trigger attribute for all user RDAREAs other than RDAREA1 to RDAREA3 from INITIAL to DEFER. RDAREA1 to RDAREA3 are located in the same HiRDB file system area.

Procedure
  1. Terminate HiRDB normally.
  2. Modify the system common definitions.
  3. Start HiRDB normally.
  4. Use the pdhold command to place the RDAREAs in shutdown and closed status to change their opening trigger attributes.
  5. Create a control statements file for the pdmod command.
  6. Use the pdmod command to change the RDAREAs' opening trigger.
  7. Use the pdrels command to release the shutdown status of RDAREAs whose opening trigger attributes were changed, and then place them in open status.
The procedure step numbers correspond to the paragraph numbers in the explanation that follows. For example, step 3 above is explained in paragraph (3) below.
Organization of this subsection
(1) Terminate HiRDB normally
(2) Modify the system common definition
(3) Start HiRDB normally
(4) Use the pdhold command to place RDAREAs in shutdown and closed status to change their opening trigger attributes
(5) Create the control statements file for the pdmod command
(6) Use the pdmod command to change the RDAREAs' opening trigger
(7) Use the pdrels command to release shutdown status of RDAREAs whose opening trigger attributes were changed, then place them in open status

(1) Terminate HiRDB normally

 
pdstop
 

If you were to use the system reconfiguration command (pdchgconf command), you would not need to restart HiRDB normally in this step, because this command enables you to modify HiRDB system definitions while HiRDB is running. Note that HiRDB Advanced High Availability must be installed in order to use this command. For details about modifying HiRDB system definitions while HiRDB is running, see 9.2 Modifying HiRDB system definitions while HiRDB is running (system reconfiguration command).

(2) Modify the system common definition

The following specifications are made in the system common definition:

                :
set pd_rdarea_open_attribute_use = Y                      1
set pd_rdarea_open_attribute = DEFER                      2
                :

Explanation
  1. Specifies that DEFER or SCHEDULE is to be used as the opening trigger attribute for RDAREAs.
  2. Specifies DEFER as the default opening trigger attribute for all RDAREAs.

(3) Start HiRDB normally

 
pdstart
 

(4) Use the pdhold command to place RDAREAs in shutdown and closed status to change their opening trigger attributes

 
pdhold -r RDAREA1,RDAREA2,RDAREA3 -c
 

(5) Create the control statements file for the pdmod command

A control statements file that contains the pdmod command's alter rdarea statement (/pdmod/alter01) is created. The following are the contents of the control statements file:

 
alter rdarea RDAREA1 open attribute SCHEDULE;
alter rdarea RDAREA2 open attribute SCHEDULE;
alter rdarea RDAREA3 open attribute SCHEDULE;
 

Explanation
The opening trigger attributes for RDAREA1 to RDAREA3 are changed from DEFER to SCHEDULE.

(6) Use the pdmod command to change the RDAREAs' opening trigger

 
pdmod -a /pdmod/alter01
 

Explanation
-a: Specifies the name of the control statements file for the pdmod command created in step (5).
Reference note
The opening trigger specification does not take effect immediately when RDAREA is added by the database structure modification utility; immediately after adding the RDAREA, the INITIAL attribute takes effect. To enable the opening trigger specification to take effect, you must first terminate HiRDB, and then execute a restart. The opening trigger will then take effect regardless of the startup mode.

(7) Use the pdrels command to release shutdown status of RDAREAs whose opening trigger attributes were changed, then place them in open status

 
pdrels -r RDAREA1,RDAREA2,RDAREA3 -o
 

We recommend that after the command has executed you check whether the execution results are correct. For details on how to check command execution results, see the manual HiRDB Version 9 Command Reference.