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:

Before upgrading, use the Windows Command Prompt window to execute commands and utilities.

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) Stopping the HiRDB service
(8) Stopping commands, utilities, applications, and HiRDB-linked programs
(9) Checking the memory requirements
(10) Checking the size of status files
(11) Checking the size of synchronization point dump files
(12) Checking the total number of records in the system log file
(13) Backing up the files in the HiRDB directory
(14) Upgrading option program products
(15) Confirming default values for HiRDB system definition operands
(16) Checking the added reserved words

(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 9 Command Reference.

Free space required for upgrading

Check the free space requirements indicated in the following table for the version of HiRDB being used prior to the upgrade. 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-5 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 table#1------1--
SQL_ROUTINES table#2----4 + [Figure]30 [Figure] S[Figure]4 + [Figure]30 [Figure] S[Figure]--
SQL_ROUTINE_PARAMS table#2----2 + [Figure]20 [Figure] S[Figure]2 + [Figure]20 [Figure] S[Figure]--
Legend:
--: 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:

Note that if you downgrade the version after you have successfully upgraded (for example, if you upgrade for test purposes and then downgrade to restore the original operations), you must first back up all 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 9 System Operation Guide or HiRDB Version 9 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 event log before this message, eliminate the cause of the error, and then start the service. After that, re-start the unit, and then terminate it normally with the pdstop command.

(7) Stopping the HiRDB service

Before performing a version upgrade, you must stop the HiRDB service. For details about stopping the service and checking that it has stopped, see the documentation provided with the operating system.

(8) Stopping commands, utilities, applications, and HiRDB-linked programs

Terminate commands, utilities, and applications. Before upgrading, also stop any linked program that accesses HiRDB, such as HiRDB Datareplicator, HiRDB Dataextractor, or JP1/PFM. 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 Chapter 15. 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 17.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 17.2 Determining the size of synchronization point dump files.

(12) 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# > 5,754,880/system-log-file-record-length
When upgrading from HiRDB Version 5.0 or earlier
Total-number-of-records# > 4,239,360/system-log-file-record-length
When upgrading from HiRDB Version 6 or earlier
Total-number-of-records# > 3,215,360/system-log-file-record-length
When upgrading from HiRDB Version 7 or earlier
Total-number-of-records# > 1,413,120/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:

(13) Backing up the files in the HiRDB directory

To be prepared for the possibility of upgrading errors, back up the files under the HiRDB directory (%PDDIR%\conf). Delete the backup copy after you have checked the operation of the new version.

(14) 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.4 Notes about option program products installation.

(15) Confirming default values for HiRDB system definition operands

The default values of some HiRDB system definition operands have been altered in versions 07-00 and 08-00 (default values are now recommended values). Also, some operands might now be omitted.

For this reason, when an upgrade is performed from, for example, 07-03 to 08-02, default values change for some operands. This means that the HiRDB operating environment might change after being upgraded. When changes in default values create problems, specify the operands shown below after upgrading so that default values do not change.

For details about operands whose default values have been changed, operands that no longer need to be specified, and the pd_sysdef_default_option operand, see the manual HiRDB Version 9 System Definition.

(16) Checking the added reserved words

With the extension of SQL, the reserved words listed below have been added to each version of HiRDB. An SQL statement containing a reserved word that is not enclosed in double-quotation marks might result in a syntax error after upgrading.

HiRDB versionAdded reserved words
06-00GET_JAVA_STORED_ROUTINE_SOURCE,
IS_USER_CONTAINED_IN_HDS_GROUP
06-01None
06-02BIT_AND_TEST
07-00CONDITION,
EXIT,
HANDLER,
TIMESTAMP_FORMAT,
VARCHAR_FORMAT
07-01FREE,
LOCATOR
07-02None
07-03OVER
08-00ENCRYPT
08-01None
08-02COUNT_FLOAT,
SQLCODE_OF_LAST_CONDITION,
SQLERRM_OF_LAST_CONDITION,
XML,
XMLAGG,
XMLEXISTS,
XMLQUERY,
XMLSERIALIZE
08-03None
08-04XMLPARSE
08-05None
09-00None
09-01None
09-02None
09-03COMPRESSED

If any of the added reserved words has been used without being enclosed in double-quotation marks, take appropriate action by referencing What to do if a name conflicts with an SQL reserved word in the manual HiRDB Version 9 SQL Reference.