pdchgconf (Reconfigure the system)

Function

The pdchgconf command changes system definitions during HiRDB operation.

Before executing the pdchgconf command, check that the definitions after the change will be valid (execute the pdconfchk -d chgconf command).

You can use the pdchgconf command only if HiRDB Advanced High Availability has been installed.

Executor

HiRDB administrator

Format

pdchgconf

Options

None

Changing procedure

Figure 2-2 provides an overview of changing system definitions.

Figure 2-2 Overview of changing system definitions (pdchgconf command)

[Figure]

Explanation
  1. Before executing the pdchgconf command, create the chgconf directory in $PDDIR/conf in order to store the system definition file after the change. In the case of a HiRDB/Parallel Server, create this directory in all units.
  2. After copying all system definition files from $PDDIR/conf to the chgconf directory, make desired changes to the system definitions.
    For details about the system definitions that can be changed, see the HiRDB Version 8 System Operation Guide.
  3. Execute the pdchgconf command.
  4. When the pdchgconf command terminates, the system definition files before the changes are saved in the backconf directory in $PDDIR/conf.
  5. The system definition files after the changes are stored in $PDDIR/conf.

Rules

  1. The pdchgconf command can be executed only while HiRDB is active.
  2. The pdchgconf command must be executed at the server machine that contains the single server or where the system manager is located.

Notes

  1. You cannot use the pdchgconf command to change the pd_system_id or pd_master_file_name operand. Nor can you delete this information from the current system file or an overwrite-disabled system file. An attempt to change or delete this information will result in an error.
  2. You cannot make changes to system definitions that affect OS parameters (kernel parameters). To make such changes, use the normal procedure for changing system definitions (terminate HiRDB, make changes to the system definitions, and then re-start HiRDB).
  3. When you execute the pdchgconf command, the system log files are swapped. Before executing the pdchgconf command, make sure that there is enough space for operation with the new configuration. If you execute the pdchgconf command while there is no swappable system log file, HiRDB displays the KFPS01256-E message and stops (displays abort code Psjnf07 or Psjn381). If HiRDB has stopped, provide a swappable system log file and then start HiRDB. If there is no swappable system log file, you need to add one. For details about how to handle when there is no swappable file, see the HiRDB Version 8 System Operation Guide.
  4. Although the system log files are swapped when you execute the pdchgconf command, no message to that effect is displayed. Therefore, if you need the message log in the message log file, back up the message log file before executing the pdchgconf command.
  5. If the following conditions apply, you may not be able to execute the pdchgconf command:
    • For a HiRDB/Parallel Server, some units or servers have terminated (including reduced activation). If only recovery-unnecessary front-end servers are inactive, you may be able to execute the pdchgconf command; for details, see Notes when a recovery-unnecessary front-end server is used.
    • For a HiRDB/Parallel Server, a communication error has occurred in the network between units.
    • Updatable online reorganization is executing.
    • The pdrplstop command is executing.
    • A transaction or utility was still active 15 minutes after the pdchgconf command was executed.
    • HiRDB was started with the pdstart -r command.
    • While HiRDB Datareplicator is linked, the value of the pd_rpl_init_start operand does not match the actual data extraction mode.*
    * The details are as follows:
    Value of the pd_rpl_init_start operand before changeHiRDB Datareplicator linkage statusValue of the pd_rpl_init_start operand after changeWhether or not the pdchgconf command can be executed
    YActiveYY
    N or omittedN
    Has been stopped by the pdrplstop commandYN
    N or omittedY
    N or omittedInactiveYN
    N or omittedY
    Has been activated by the pdrplstart commandYY
    N or omittedN
    Legend:
    Y: Executable
    N: Not executable
  6. The following limitations apply while the pdchgconf command is executing:
    • UAP response time may be delayed. The guideline for the pdchgconf command's execution time is: time required for normal termination of HiRDB + time required for normal startup of HiRDB.
    • Do not execute any other operation command or utility.
    • The system switchover facility is not available. If the system switchover facility is used in the HA monitor's server mode, the standby system is stopped during execution of the pdchgconf command. In this case, update the system definitions after the pdchgconf command terminates normally and then restart the standby system. If the system switchover facility is using Hitachi HA Toolkit Extension, stop the standby system before executing the pdchgconf command, update the system definitions after the pdchgconf command terminates normally, and then restart the standby system.
  7. To add or delete a unit or server while HiRDB Datareplicator is linked, you must re-create HiRDB Datareplicator's extraction environment. If a HiRDB transaction is processed and data is added, updated, or deleted in the extracted database while HiRDB Datareplicator's extraction environment is being re-created, inconsistency occurs in the target database. In this case, do not use the pdchgconf command to change the configuration.
  8. If Real Time SAN Replication based on the log-only synchronous method is in use and the pdchgconf command is used, you must execute the preparations for log application. For details about Real Time SAN Replication, see the manual HiRDB Version 8 Disaster Recovery System Configuration and Operation Guide.
  9. If the pdchgconf command's execution fails, the system automatically restores the previous system definitions, using the system definition files stored in the backconf directory under $PDDIR/conf. If this recovery processing fails, HiRDB may terminate itself. In such a case, check the error messages and take appropriate action.
  10. During execution of the pdchgconf command, error messages and abort codes that accompany HiRDB startup and termination may be displayed. In such a case, there may be a problem with the new system definitions or environment. Take appropriate action according to the displayed error messages and abort codes.
  11. Return code 0 for the pdchgconf command indicates normal termination, and return code 8 indicates abnormal termination.
  12. While only recovery-unnecessary front-end servers are inactive, you still may not be able to execute the pdchgconf command in the following cases:
    • The pd_mode_conf operand value in the system definition is AUTO.
    • After the system definition is changed, a currently inactive unit's front-end server will no longer be a recovery-unnecessary front-end server.

Notes when a recovery-unnecessary front-end server is used

  1. If a recovery-unnecessary front-end server has stopped normally and the corresponding unit is running, the pdchgconf command cannot be executed.
  2. If all units are running except ones that contain a recovery-unnecessary front-end server and no individual server has stopped, the pdchgconf command can be executed even when a unit containing a recovery-unnecessary front-end server is inactive. However, if Notes 5 through 10 are true, the pdchgconf command cannot be executed.
    The pdchgconf command replaces the system definition file in $PDDIR/conf in the inactive unit with the system definition file in $PDDIR/conf/chgconf. The command then restarts the inactive unit in order to apply the new system definition. If a problem occurs, such as a machine shutdown or a network error, the pdchgconf command may not replace the system definition file in the inactive unit or may not restart the unit. In such a case, the command displays the KFPS04665-W message. If this message is displayed, you must take actions (i) and (ii) below before restarting the unit. If these actions are not taken, HiRDB cannot accept the correct changes to the system definition, resulting in invalid operation. If such invalid operation occurs, immediately terminate the corresponding unit and take actions (i) and (ii):
    (i) Replace the system definition file in $PDDIR/conf or $PDCONFPATH with the new one.
    (ii) Use the pdconfchk command to make sure that there are no differences in the system definitions between the units.