1.5.2 How to migrate to 64-bit mode

The following figure illustrates how to migrate to 64-bit mode.

Figure 1-6 How to migrate to 64-bit mode

[Figure]

  1. Enter the pdstop command to terminate HiRDB normally.
  2. Use the pdstsinit command to increase the size of status files.
    See 17.3 Determining the size of status files to reestimate the size of status files. If necessary, use the pdstsinit command to increase the size of status files.
  3. Delete the pdplugin operand from the system common definition.
    Delete the pdplugin operand from the system common definition. Otherwise, HiRDB does not start normally after being upgraded to 64-bit mode.
  4. Upgrade HiRDB to 64-bit mode.
    Upgrade your HiRDB to 64-bit mode. For details about how to upgrade HiRDB, see 1.3 Upgrading HiRDB.
    Before upgrading HiRDB to 64-bit mode, check the data dictionary RDAREA for available space. In this case, you need the space discussed in 1.3.1 Before upgrading, plus the space for the following tables:
    SQL_TABLES table: 1 + [Figure]5 [Figure] S[Figure]
    SQL_VIEW_DEF table: 2 + [Figure]200 [Figure] S[Figure]
  5. The pdobjconv command starts automatically.
    The pdvrup command is executed during the upgrading procedure. When this pdvrup command terminates normally, the pdobjconv command#1 is executed automatically. If this command returns code#2 0 or 4, migration to 64-bit mode was successful. If the return code is neither 0 nor 4, continue the 64-bit-mode migration procedure with the procedure explained in 1.5.3 In the event of an SQL object migration error.
    #1: This command makes the view tables and SQL objects for procedures and functions created in 32-bit mode also available in 64-bit mode.
    #2: The KFPX21002-I message displays the return code. This message is output to the system log file and event log. If the return code is 8 or 12, the message is also output to the standard error output. The following explains the return code:
    0:
    The pdobjconv command terminated normally.
    4:
    There was a warning message, but the pdobjconv command terminated normally.
    8:
    A migration error occurred on some of the SQL objects. Check the cause of the error and correct it based on the message and pdobjconv command processing result (SQL object migration information). Another possibility is that a utility-execution error occurred.
    12:
    The pdobjconv command terminated abnormally. Check the cause of the error and correct it based on the message and pdobjconv command processing result (SQL object migration information). If you use the pdcancel command to cancel the pdobjconv command, or an error occurs in the pdobjconv command process, the command returns code 12.
  6. Enter the pdstop command to terminate HiRDB normally.
  7. Stop the HiRDB service.
  8. Uninstall the 32-bit-mode plug-ins.
    Uninstall each 32-bit-mode plug-in. For the installation procedure, see each plug-in's documentation.
  9. Install the 64-bit-mode plug-ins.
    Install the applicable 64-bit-mode plug-ins. For the installation procedure, see each plug-in's documentation.
  10. Start the HiRDB service.
  11. Specify the pdplugin operand in the system common definition.
    Specify the name of the 64-bit-mode plug-in in the pdplugin operand in the system common definition.
  12. Enter the pdstart command to start HiRDB.