pdprgrenew (Update a HiRDB update version)
Function
The pdprgrenew command updates the active HiRDB to the HiRDB update version (HiRDB in the update directory that has been copied by the pdprgcopy command ($PDDIR/renew)). For details about upgrading to a HiRDB update version, see the HiRDB Version 8 Installation and Design Guide.
The command updates the files in the following HiRDB directories on the active HiRDB:
Directory | Description |
---|
$PDDIR/renew/bin | HiRDB operation commands and utilities |
$PDDIR/renew/lib | HiRDB libraries, message text files, and system definition analysis files |
$PDDIR/renew/client | HiRDB client libraries, operation commands, and utilities |
$PDDIR/renew/include | Header files used during UAP creation |
Executor
Format
- HiRDB-update-version-installation-directory/bin/pdprgrenew-- [-b] HiRDB-directory- |
Options
Specifies that HiRDB is to be restored to the status in effect before the pdprgrenew command was executed, such as when the pdprgrenew command terminates abnormally with KFPS04646-I (return code = 12).
Command arguments
- HiRDB-update-version-installation-directory
<path name> ((Linux version: 1-27; other: 1-128))
Specifies the HiRDB directory of the HiRDB that is to be updated to the HiRDB update version.
Rules
- The pdprgrenew command can be executed only while HiRDB is active.
- The pdprgrenew command must be executed at the server machine that contains the single server or where the system manager is located.
- Before executing the pdprgrenew command, you must use the pdprgcopy command to create an update directory ($PDDIR/renew). You cannot execute the pdprgrenew command if you haven't created this directory. Note that the update directory ($PDDIR/renew) is deleted when the pdprgrenew command terminates normally.
Notes
- The pdprgrenew command creates a backup directory ($PDDIR/renew_bak). If this directory already exists, rename it beforehand.
- When you execute the pdprgrenew command, system log files are swapped. Before executing the pdprgrenew command, make sure that there is enough space for operating with the updated HiRDB. If you execute the pdprgrenew 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 execute the pdprgrenew -b command. If there is no swappable system log file, you must add one. For details about how to handle when there is no swappable file, see the HiRDB Version 8 System Operation Guide.
- Although system log files are swapped when you execute the pdprgrenew 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 pdprgrenew command.
- If the active HiRDB is in the following status, you may not be able to update your HiRDB:
- For a HiRDB/Parallel Server, some of the units or servers have terminated (including units that have not started due to reduced activation).
- For a HiRDB/Parallel Server, a communication error has occurred in the network between units.
- A transaction or utility remains active 15 minutes after the pdprgrenew command was executed.
- The following limitations apply while the pdprgrenew command is executing:
- A UAP's response time may be delayed by the pdprgrenew command's execution time.
- If you execute another operation command or utility, execution of the pdprgrenew command may fail or an error message indicating that HiRDB has stopped may be displayed.
- To update an HiRDB that uses the system switchover facility, you must update both the running system and the standby system.
- All files in the HiRDB directory must be in the same HiRDB file system area as the HiRDB directory.
- For a client library that is used by a UAP connected to the HiRDB server, use version 07-00 or later. If you are using a library version earlier than 07-00, the current HiRDB client is disconnected.
- The result of the pdprgrenew command can be checked on the basis of the return code from execution of the command. A return value of 0 for this command indicates normal termination; 8 indicates abnormal termination (HiRDB status before updating); and 12 indicates abnormal termination (termination of HiRDB).
- During execution of the pdprgrenew command, error messages and abort codes relating to HiRDB startup and termination may be displayed. In this happens, there may be a problem in the environment, such as a shortage of resources required for starting the updated HiRDB. Take appropriate action according to the displayed error messages and abort code.
- If you are using Real Time SAN Replication based on the log-only synchronous method, and if you used the pdprgrenew command at the transaction execution site to replace HiRDB, also replace HiRDB at the log application site and then execute the preparations for log application. For details about the preparations for log application, see the manual HiRDB Version 8 Disaster Recovery System Configuration and Operation Guide.