Preparing for migration
Preparing for migration includes gathering information
about and backing up your data, so that you can reinstall the previous
version of the server and restore your data if you have a migration
problem. Preparing for migration is crucial for successful migration.
Procedure Review and complete all tasks that apply:
Reviewing changes in HCL OneDB product functionality .
Checking and configuring available space .
Configuring for recovery of restore point data in case an upgrade fails .
Renaming user-defined routines (UDRs) that
have the following names: CHARINDEX() , LEFT(), RIGHT(), INSTR(),
DEGREES(), RADIANS(), REVERSE(), SUBSTRING_INDEX(), LEN(), and SPACE().
These names are reserved for built-in SQL string manipulation
functions.
Adjusting settings:
If you use UNICODE, ensure that the GL_USEGLU environment
variable on the source server is set to the same value as the GL_USEGLU
environment variable on the target server.
Saving copies of the current configuration files .Saving a copy of the storage manager sm_versions file .
Closing all transactions and shutting down the source database server .
Initiating fast recovery to verify that no open transactions exist .
Verifying the integrity of the data .
Verifying that the database server is in quiescent mode .
Making a final backup of the source database server .
Verifying that the source database server is offline .
Reviewing changes in HCL OneDB product functionality Checking and configuring available space Before you migrate to the new version of HCL OneDB , you must make sure that you have enough available space for the new server, your data, and any other network and data tools that you use.Configuring for recovery of restore point data in case an upgrade fails By default, the CONVERSION_GUARD configuration parameter is enabled and a temporary directory is specified in the RESTORE_POINT_DIR configuration parameter. These configuration parameters specify information that OneDB can use if an upgrade fails. You can change the default values of these configuration parameters before beginning an upgrade. Saving copies of the current configuration files Save copies of the configuration files that exist for each instance of your source database server. Keep the copies available in case you decide to use the files after migrating or you need to revert to the source database server. Saving a copy of the storage manager sm_versions file Before you migrate to a later version of the database server, save a copy of your current sm_versions file, which should be in the $ INFORMIXDIR /etc directory.Preparing 12.10 BSON columns with DATE fields for upgrade Before you upgrade from HCL OneDB 12.10 you must unload binary JSON (BSON) columns with DATE fields into JSON format so that you can load them into HCL OneDB 14.10Closing all transactions and shutting down the source database server Before migrating, terminate all database server processes and shut down your source database server. This lets users exit and shuts down the database server gracefully. If you have long running sessions, you must also shut those down. Initiating fast recovery to verify that no open transactions exist A shutdown procedure does not guarantee a rollback of all open transactions. To guarantee that the source database server has no open transactions, put the source database server in quiescent mode and initiate fast recovery.Verifying the integrity of the data After verifying that no open transactions exist, verify the integrity of your data by running the oncheck utility. You can also verify the integrity of the reserve pages, extents, system catalog tables, data, and indexes. If you find any problems with the data, fix the problems before you make a final backup of the source database server.Verifying that the database server is in quiescent mode Before you make a final backup, verify that your source database server is in quiescent mode.Making a final backup of the source database server Use ON-Bar or ontape to make a level-0 backup of the source database server, including all storage spaces and all used logs. After you make a level-0 backup, also perform a complete backup of the logical log, including the current logical-log file. Verifying that the source database server is offline Before you install the new database server, verify that the source database server is offline. You must do this because the new database server uses the same files.
Have feedback?
Google Analytics is used to store comments and ratings. To provide a comment or rating for a topic, click Accept All Cookies or Allow All in Cookie Preferences in the footer of this page.