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:

• Reorganize the dictionary table using the database reorganization utility (pdrorg).
• Extend the data dictionary RDAREAs using the database structure modification utility (pdmod).

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-4 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 S	5 + 5 S	5 + 15 S	5 + 20 S	5 + 125 S
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 + 5 S	3 + 5 S	3 + 15 S	3 + 20 S	3 + 25 S
SQL_VIEW_DEF table	2 + 10 S	3 + 10 S	2 + 40 S	2 + 65 S	2 + 70 S
SQL_DIV_COLUMN table#1	--	--	--	1	--
SQL_ROUTINES table#2	--	--	4 + 30 S	4 + 30 S	--
SQL_ROUTINE_PARAMS table#2	--	--	2 + 20 S	2 + 20 S	--

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.

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

• Master directory RDAREA
• Data directory RDAREA
• Data dictionary RDAREAs
• RDAREAs containing audit trail tables (applicable when the security audit facility is used)

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.

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 configuration, 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:

• Message log file or syslog file

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.

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.

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.

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.

With each version and revision, HiRDB revises the default values that are assumed when you omit HiRDB system definition operands. HiRDB version 09-50 and later offers two modes for the default behavior when operands are omitted: recommended mode, which assumes the recommended default values, and compatibility mode, which uses the default values for a specific version of HiRDB. Normally, to build a more secure system, we suggest that you apply the recommended mode, which greatly reduces the number of operands that must be specified. In version 09-50 and later, to use the default values for a specific version, apply the compatibility mode, and do not specify the operand pd_sysdef_default_option.

• If you are upgrading from a version earlier than 09-50
  For details about the advantages and disadvantages of changing the default values, see Changes to HiRDB system definitions by version and revision in the manual HiRDB Version 9 System Definition. After checking the default values, if you decide to focus on compatibility with the previous version, you can apply the compatibility mode to make the default values the same as in the previous version. However, in this case all of the operands will have the previous version's default values, so we recommend specifying the recommended values on a per-operand basis.
  
• If you are upgrading from a version earlier than 07-00, or if you are specifying the operand pd_sysdef_default_option
  In addition to the changes mentioned above in If you are upgrading from a version earlier than 09-50, see the description about upgrading from a version earlier than 09-50 in Operands whose default value depends on the version and operands that are no longer needed in the manual HiRDB Version 9 System Definitions. Then, after taking note of the relevant advantages, consider specifying the recommended values on a per-operand basis.
  

With each version and revision, HiRDB revises the default values that are assumed when you omit utility options and SQL options.

If you are upgrading from a version earlier than 09-50, check the locations listed below regarding the advantages and disadvantages of changing the default values. After checking the default values, if you decide to focus on compatibility with the previous version, you can apply the compatibility mode to make the default values the same as in the previous version. However, in this case all of the operands will have the previous version's default values, so we recommend specifying the recommended values on a per-operand basis.

• Options and Control Statements Whose Default Value Is Changed or Whose Specification Is No Longer Needed After Upgrading in the manual HiRDB Version 9 Command Reference
• Changes to the default interpretation of SQL syntax by version and revision in the manual HiRDB Version 9 SQL Reference

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.

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 20. 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

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 configuration, 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:

• The total number of -n option values in the pdloginit command is the total number of records.
• Execute the pdlogls -d sys -s server-name -e command. The sum of the numbers of records (hexadecimal) that are output at the top of the Recode-count in the execution result is the total number of records.

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. For details about how to back up the HiRDB directory, see 2.3.1(4) Making a backup copy of the HiRDB directory.

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.

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.