1.5.1 Considerations when migrating to 64-bit mode

Organization of this subsection
(1) Incompatible files
(2) Operands with altered default values
(3) Differences in memory requirements
(4) Differences in the UOC interface

(1) Incompatible files

Files that were used by 32-bit mode HiRDB can generally be used by 64-bit mode HiRDB. However, the following files are not compatible with 64-bit mode HiRDB and cannot be used.

(2) Operands with altered default values

The default values of the HiRDB system definition operands shown in the following table change when HiRDB is migrated from 32-bit mode to 64-bit mode.

Table 1-6 Operands with altered default values

Operand nameSpecified itemDefault value in
32-bit mode
Default value in
64-bit mode
pd_work_buff_sizeWork table buffer size
  • HiRDB/Single Server: 384#
  • HiRDB/Parallel Server: 1024#
5120#
pd_fes_lck_pool_sizeLock pool size of front-end server{(pd_max_users value + 3) x (pd_max_access_tables value + 4)} [Figure]6{(pd_max_users value + 3) x (pd_max_access_tables value + 4)} [Figure]4
SHMMAXUpper limit for shared memory segment size200 MB1,024 MB
#
This is the default value if the pd_work_buff_mode operand is omitted or if pool is specified. The default value when each is specified as the pd_work_buff_mode operand remains unchanged.

(3) Differences in memory requirements

When HiRDB is migrated from 32-bit mode to 64-bit mode, more memory is required. For details about calculating memory requirements, see Chapter 15. Storage Requirements for HiRDB.

(4) Differences in the UOC interface

When HiRDB is migrated to 64-bit mode, the UOC interface changes for the database creation utility (pdload) and the database reorganization utility (pdrorg). This means that the UOC must be re-created. For details about the UOC interface, see the manual HiRDB Version 9 Command Reference.