The following figure shows the action to take if an error occurs when system reconfiguration is executed.

Figure 9-1 Action to take if an error occurs when the system reconfiguration command is executed

(a) If an error occurs during the configuration change pre-processing stage

If an error occurs during this interval, determine the cause of the error based on the message that is issued. In addition, use the pdls command to check if HiRDB has stopped. If it has stopped, use the pdstart command to start HiRDB. In this case, HiRDB starts using the unchanged HiRDB system definitions.

A message or an abort code might be issued accompanying a HiRDB termination processing failure. In this case, take action based on the message or abort code that is issued.

(b) If an error occurs during the HiRDB system definition change processing stage

If an error occurs during this interval, check the usage status of the disk containing the HiRDB directory; also check the access privileges to the HiRDB system definition files. In addition, use the pdls command to check if HiRDB has stopped. If it has stopped, copy the unchanged HiRDB system definition files in the $PDDIR/conf/backconf directory into the $PDDIR/conf directory and recover the system. Then use the pdstart command to start HiRDB.

If a unit or server has been moved, check its connection to the disk.

(c) If an error occurs during the HiRDB system definition change post-processing stage

If an error occurs during this interval, the system reconfiguration command automatically restores the unchanged HiRDB system definitions. Determine the cause of the error based on the message that is issued. Then check the HiRDB system definitions in the $PDDIR/conf directory.

In addition, use the pdls command to check that HiRDB is running. If it is not running, use the pdstart command to start HiRDB. To start HiRDB using the changed HiRDB system definitions, copy the HiRDB system definition files in the $PDDIR/conf/chgconf directory into $PDDIR/conf, and then start HiRDB.

A message or an abort code might be issued accompanying a HiRDB startup processing failure. If this happens, there might be a problem with the changed HiRDB system definitions or environment, so take the following actions:

• Use the pdconfchk command to check the changed HiRDB system definitions.
• Based on the message, secure the resources needed to run the modified system configuration.
• Note that the system reconfiguration command cannot be used if an operating system parameter needs to be changed.

If a unit or server has been moved, the system reconfiguration command might not be able to restore the unchanged HiRDB system definitions. Check the connections to the disk. To start HiRDB using the unchanged HiRDB system definitions, copy the HiRDB system definitions from the $PDDIR/conf/backconf directory. To start HiRDB using the changed HiRDB system definitions, copy the HiRDB system definitions from the $PDDIR/conf/chgconf directory. Then use the pdstart command to start HiRDB.

If HiRDB cannot be started using the changed HiRDB system definitions, the unchanged definitions are restored automatically, and another attempt is made to start HiRDB. If HiRDB does not start using the unchanged HiRDB system definitions either, take action based on the error messages that are issued.

If the KFPS04665-W message is output, take action in accordance with the following procedure.

Procedure

1. Identify the unit indicated by the KFPS04665-W message.
2. Execute the pdls -d svr command to check the unit's status. Check the status in the execution results and determine whether STOP(A) is indicated for any unit.
3. If there is a unit with STOP(A), forcibly terminate that unit with the pdstop -z command.
4. Replace the HiRDB system definition files under $PDDIR/conf and $PDCONFPATH for the unit indicated in the KFPS04665-W message with the modified HiRDB system definition files.
5. Start the unit with the pdstart -u command.