Migrating from 32-bit to 64-bit database servers
If you are migrating from a 32-bit version of OneDB to a 64-bit version of OneDB or reverting from a 64-bit version of OneDB, you might need to follow additional steps to update certain internal tables.
These steps are documented in the platform-specific machine notes that are provided with your database server.
For 32- to 64-bit migrations, change SHMBASE and STACKSIZE according to the onconfig.std configuration file for the new version.
All UDRs and DataBlade® modules that were built in 32-bit mode must be recompiled in 64-bit mode because they will not work with the 64-bit database server. If you have any UDRs that were developed in 32-bit mode, make sure that proper size and alignment of the data structures are used to work correctly on a 64-bit computer after recompiling in 64-bit mode. For more information, refer to the machine notes.
Migrating from 32-bit to 64-bit with collection types that use the SMALLINT data type
If you are moving your database from a 32-bit computer to a 64-bit computer and your database contains collection types that use the SMALLINT data type, you must take extra steps to prevent memory corruption. Collection types are the ROW, LIST, SET, and MULTISET data types. This restriction applies if you are upgrading from an older version of HCL OneDB™ on 32-bit to the current version of HCL OneDB on 64-bit, or if you are moving from 32-bit to 64-bit on the current version of HCL OneDB.
To migrate a database with SMALLINT collection types from 32-bit to 64-bit, use one of the following methods:
- Export and import the data.
- Export the data from the 32-bit computer.
- Import the data onto the 64-bit computer.
- Drop and recreate specific collection types and database objects.
- Drop the collection types that use the SMALLINT data type and all other database objects that reference them (such as tables, columns, SPL routines, triggers, indexes, and so on).
- Recreate the collections types and all the other necessary database objects.