1.3.1 Before upgrading

Before upgrading, make sure that the steps described below are taken. For a multi-HiRDB, you must apply the following actions to all directories:

Organization of this subsection
(1) Checking for available space
(2) Backing up system RDAREAs
(3) Checking the memory size
(4) Checking to see whether HiRDB is online
(5) Terminating HiRDB normally
(6) Checking the HiRDB status
(7) Releasing library sharing
(8) Terminating commands, utilities, applications, HiRDB Datareplicator, and HiRDB Dataextractor
(9) Checking the memory requirements
(10) Checking the size of status files
(11) Checking the size of synchronization point dump files
(12) Checking the operating system parameters
(13) Checking the total number of records in the system log file
(14) Backing up the files in the HiRDB directory
(15) Upgrading option program products

(1) Checking for available space

Use the database condition analysis utility (pddbst) to see if there is enough space in the data dictionary RDAREAs. If there is not enough space, allocate sufficient space using one of the following methods:

This space checking is required only when you are upgrading your HiRDB; it is not necessary when you are updating to the HiRDB update version.

For the utility execution method, see the manual HiRDB Version 8 Command Reference.

Free space required for upgrading

Check to see if you have enough free space, as shown in Table 1-4, according to the HiRDB version you are upgrading. If there is not enough space, an insufficient space error may occur when you start HiRDB or execute the pdvrup command after upgrading.

Table 1-4 Free space required for upgrading

Dictionary tables stored in data dictionary RDAREANumber of free segments required in data dictionary RDAREA
Upgrading from 07-00 or laterUpgrading from 06-00 or laterUpgrading from 05-02 or laterUpgrading from 03-00 or laterUpgrading from 02-05 or earlier
SQL_TABLES table13333
SQL_COLUMNS table4 + [Figure]5 [Figure] S[Figure]5 + [Figure]5 [Figure] S[Figure]5 + [Figure]15 [Figure] S[Figure]5 +[Figure]20 [Figure] S[Figure]5 + 1[Figure]25 [Figure] S[Figure]
SQL_INDEXES table11444
SQL_TABLE_PRIVILEGES table11333
SQL_INDEX_COLINF table11333
SQL_VIEW_TABLE_USAGE table23444
SQL_VIEWS table2 + [Figure]5 [Figure] S[Figure]3 + [Figure]5 [Figure] S[Figure]3 + [Figure]15 [Figure] S[Figure]3 + [Figure]20 [Figure] S[Figure]3 + [Figure]25 [Figure] S[Figure]
SQL_VIEW_DEF table2 + [Figure]10 [Figure] S[Figure]3 + [Figure]10 [Figure] S[Figure]2 + [Figure]40 [Figure] S[Figure]2 + [Figure]65 [Figure] S[Figure]2 + [Figure]70 [Figure] S[Figure]
SQL_DIV_COLUMN table1[Figure][Figure][Figure]1[Figure]
SQL_ROUTINES table2[Figure][Figure]4 + [Figure]30 [Figure] S[Figure]4 + [Figure]30 [Figure] S[Figure][Figure]
SQL_ROUTINE_PARAMS table2[Figure][Figure]2 + [Figure]20 [Figure] S[Figure]2 + [Figure]20 [Figure] S[Figure][Figure]
Legend:
[Figure]: Not applicable
S: Segment size of data dictionary RDAREA for storing the corresponding table
1 The table is not needed if no LOB column or data dictionary LOB RDAREA is defined.
2 The table is not needed if no stored procedure is defined.

(2) Backing up system RDAREAs

Use the database copy utility (pdcopy) to back up the following RDAREAs:

To back up the RDAREAs, use the following procedure:

  1. Use the pdstop command to terminate HiRDB normally.
  2. Use the pdstart -r command to start HiRDB.
  3. Use the database copy utility (pdcopy) to back up the RDAREAs. In this case, specify the reference/update-possible mode (-M x specified). For details about the backup procedure, see the manuals HiRDB Version 8 System Operation Guide or HiRDB Version 8 Command Reference.

(3) Checking the memory size

You need 135 KB of memory to execute the upgrading command (pdvrup). Check your available memory space. Note that this action is not necessary when you are updating to the HiRDB update version.

(4) Checking to see whether HiRDB is online

Use the pdls command to see if all units are displayed as ACTIVE. If they are ACTIVE, use the pdstop command to terminate them normally.

(5) Terminating HiRDB normally

Before upgrading, terminate HiRDB normally. In the case of a HiRDB/Parallel Server, terminate HiRDB from the machine that contains the system manager. If HiRDB has already been terminated, check the following information to determine whether HiRDB has terminated normally:

If HiRDB has not terminated normally, enter the pdstart command to start HiRDB and then enter the pdstop command to terminate it normally.

(6) Checking the HiRDB status

To check the status of a unit whose HiRDB is to be upgraded, execute the pdls -d ust command.

When the termination status is 4 (unit status is STARTING or STOPPING):
HiRDB is engaged in start or termination processing. Re-execute the pdls -d ust command after the start or termination processing is completed.
When the termination status is 8 (unit status is PAUSE):
Restart of the process service has been cancelled due to an error. Check the KFPS00715-E message and the message that has been output to the syslog file before this message, eliminate the cause of the error, and then execute the pdrpause command. After that, re-start the unit, and then terminate it normally with the pdstop command.

(7) Releasing library sharing

If you are sharing libraries with multi-HiRDB, use the pdmemsv -d command to release library sharing. After upgrading HiRDB, use the pdmemsv command to share libraries again.

(8) Terminating commands, utilities, applications, HiRDB Datareplicator, and HiRDB Dataextractor

You must first terminate all commands, utilities, applications, HiRDB Datareplicator, and HiRDB Dataextractor. If any such item is running, deletion of executable files and shared libraries fails, resulting in an upgrading error.

(9) Checking the memory requirements

The memory requirements may increase when you upgrade the HiRDB version. You should check the HiRDB memory requirements in 16. Storage Requirements for HiRDB.

(10) Checking the size of status files

When you upgrade HiRDB, the size of the HiRDB status files may increase. You should check the size of the HiRDB status files as described in 18.3 Determining the size of status files.

(11) Checking the size of synchronization point dump files

When you upgrade HiRDB, the size of the HiRDB synchronization point dump files may increase. You should check the size of the HiRDB synchronization point dump files as described in 18.2 Determining the size of synchronization point dump files.

(12) Checking the operating system parameters

The operating system parameter values (or kernel parameter values) may change when the HiRDB version is updated. For details about how to estimate the operating system parameter values, see 21. Specifying OS Parameters.

Note
When the following conditions are satisfied, the values of the operating system parameters will have to be increased, so the values will need to be re-evaluated:
  • When upgrading from version 06-00 or earlier to version 06-01 or later
  • When 31 or more system log file groups are created

(13) Checking the total number of records in the system log file

If you are upgrading, check the total number of records in the system log files in overwrite enabled status. If the following condition is not satisfied, upgrading may fail:

When upgrading from HiRDB Version 4.0 or earlier
Total-number-of-records* > 5754880/system-log-file-record-length
When upgrading from HiRDB Version 5.0 or earlier
Total-number-of-records* > 4239360/system-log-file-record-length
When upgrading from HiRDB Version 6 or earlier
Total-number-of-records* > 3215360/system-log-file-record-length
When upgrading from HiRDB Version 7 or earlier
Total-number-of-records* > 1413120/system-log-file-record-length

For a HiRDB/Parallel Server, check the total number of records in the system log files (overwrite enabled status) at the dictionary server.

* Use one of the following methods to check the total number of records in the system log files:

(14) Backing up the files in the HiRDB directory

In case of an upgrading error, make a backup copy of the files in the HiRDB directory. Delete this backup copy after checking the operation of new version. For the procedure for backing up the HiRDB directory, see 2.3.1 Creating the HiRDB directory.

(15) Upgrading option program products

If option program products were used with HiRDB before upgrading, those option program products must be upgraded to the same version as HiRDB. For details about option program products, see 2.2.2 Installing option program product.