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.
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.
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 RDAREA | Number of free segments required in data dictionary RDAREA | ||||
---|---|---|---|---|---|
Upgrading from 07-00 or later | Upgrading from 06-00 or later | Upgrading from 05-02 or later | Upgrading from 03-00 or later | Upgrading from 02-05 or earlier | |
SQL_TABLES table | 1 | 3 | 3 | 3 | 3 |
SQL_COLUMNS table | 4 + ![]() ![]() ![]() | 5 + ![]() ![]() ![]() | 5 + ![]() ![]() ![]() | 5 +![]() ![]() ![]() | 5 + 1![]() ![]() ![]() |
SQL_INDEXES table | 1 | 1 | 4 | 4 | 4 |
SQL_TABLE_PRIVILEGES table | 1 | 1 | 3 | 3 | 3 |
SQL_INDEX_COLINF table | 1 | 1 | 3 | 3 | 3 |
SQL_VIEW_TABLE_USAGE table | 2 | 3 | 4 | 4 | 4 |
SQL_VIEWS table | 2 + ![]() ![]() ![]() | 3 + ![]() ![]() ![]() | 3 + ![]() ![]() ![]() | 3 + ![]() ![]() ![]() | 3 + ![]() ![]() ![]() |
SQL_VIEW_DEF table | 2 + ![]() ![]() ![]() | 3 + ![]() ![]() ![]() | 2 + ![]() ![]() ![]() | 2 + ![]() ![]() ![]() | 2 + ![]() ![]() ![]() |
SQL_DIV_COLUMN table#1 | -- | -- | -- | 1 | -- |
SQL_ROUTINES table#2 | -- | -- | 4 + ![]() ![]() ![]() | 4 + ![]() ![]() ![]() | -- |
SQL_ROUTINE_PARAMS table#2 | -- | -- | 2 + ![]() ![]() ![]() | 2 + ![]() ![]() ![]() | -- |
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:
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.
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.
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.
To check the status of a unit whose HiRDB is to be upgraded, execute the pdls -d ust command.
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.
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.
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.
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.
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.
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:
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:
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.
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.
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.
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 version | Added reserved words |
---|---|
06-00 | GET_JAVA_STORED_ROUTINE_SOURCE, IS_USER_CONTAINED_IN_HDS_GROUP |
06-01 | None |
06-02 | BIT_AND_TEST |
07-00 | CONDITION, EXIT, HANDLER, TIMESTAMP_FORMAT, VARCHAR_FORMAT |
07-01 | FREE, LOCATOR |
07-02 | None |
07-03 | OVER |
08-00 | ENCRYPT |
08-01 | None |
08-02 | COUNT_FLOAT, SQLCODE_OF_LAST_CONDITION, SQLERRM_OF_LAST_CONDITION, XML, XMLAGG, XMLEXISTS, XMLQUERY, XMLSERIALIZE |
08-03 | None |
08-04 | XMLPARSE |
08-05 | None |
09-00 | None |
09-01 | None |
09-02 | None |
09-03 | COMPRESSED |
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.