Migrating an offline cluster to a new major version
If you are migrating from Informix 11.70 or later version to 14.10xC4 or later version, you stop all servers in the cluster during a period when downtime is acceptable. While the cluster if offline, you upgrade all the servers. You then start the primary followed by the secondary servers. You need not rebuild the cluster or clone the servers.
Before you begin
If you are migrating from Informix 11.50 or older version or migrating to 14.10xC3 or older version, you migrate only the primary server. During migration, the database server automatically removes secondary servers. After you migrate the primary server, you must rebuild the cluster by recreating all secondary servers. You can use the ifxclone utility to recreate secondary servers. This procedure also applies if you want to upgrade a cluster to a new PID or fix pack that requires standard conversion procedures.
Prerequisites:
- Complete the steps in Preparing for migration.
- Complete the steps in Preparing to migrate, upgrade, or revert clusters.
- Perform all migration operations as user informix.
About this task
Be sure to stop and start the servers in the cluster in the order shown in the following procedure.
Procedure
To migrate to a new version with high-availability clusters:
- Stop the Connection Manager by issuing the oncmsm -k connection_manager_name command.
-
If you are using a High-availability Data Replication (HDR) secondary server as a backup server
in case of contingencies:
-
Stop the secondary servers in the cluster in the following order:
- If you have remote standalone (RS) secondary servers, stop them by issuing the onmode -ky command.
- If you have shared disk (SD) servers, stop them by issuing the onmode -ky command.
- If you have an HDR secondary server, stop it by issuing the onmode -ky command.
- Stop the primary server by issuing the onmode -ky command.
- On each server, set the INFORMIXDIR environment variable to the full path name for the target installation.
- Ensure that all of the necessary configuration files are available in the target installation.
- Optional: Enable quick reversion to a consistent restore point if the migration fails. Do this by setting the CONVERSION_GUARD and RESTORE_POINT_DIR configuration parameters. (For more information, see Configuring for recovery of restore point data in case an upgrade fails.)
- Start the primary server by issuing an oninit command.
- Ensure that the conversion to the target server was successful and that the server is in multi-user mode.
-
If you are migrating from Informix 11.70 or later version to 14.10xC4 or later version, for HDR
and RSS servers,
- Enable quick reversion to a consistent restore point if the migration fails. Do this by setting the CONVERSION_GUARD and RESTORE_POINT_DIR configuration parameters. (For more information, see Configuring for recovery of restore point data in case an upgrade fails.)
- Start secondary server by issuing an oninit command.
- Check ‘onstat -g cluster’ output at primary server, and once HDR/RSS secondary server connected to primary server, force a checkpoint at primary server using ‘onmode -c’ command and make sure checkpoint is replayed at HDR/RSS secondary server.
- Start the Connection Manager by issuing an oncmsm command.
- If you are migrating from pre-11.10 versions of Informix® and need SD secondary servers on the primary server in a shared-disk cluster, set the primary server by issuing the onmode -d set SDS primary primary_server_name command.
- Start SD secondary servers by issuing oninit commands.
- Start the servers in the cluster and perform additional tasks in the following order:
-
If you are migrating from Informix 11.50 or older version or migrating to 14.10xC3 or older
version, for HDR ad RSS servers,
- Perform any additional standard migration tasks described in Migrating to the new version of Informix and in Completing required post-migration tasks.
- If you have Connection Manager configuration files that you created with a version of Informix® Client Software Development Kit (Client SDK) that is prior to version 3.70.xC3, you must convert the files. You must convert them because the older files are incompatible with the current version of the Connection Manager. For more information, see Converting older formats of the Connection Manager configuration file to the current format.
Results
The migration of all servers in the cluster is now complete.