Home
Migrating and upgrading
You can upgrade to the 14.10 release of HCL Informix® or migrate from other database servers to Informix. Upgrading is an in-place migration method that uses your existing hardware and operating system software. Some changes to the Informix database server can affect upgrading from a previous release.
Migrating Informix® database systems
The Informix® Migration Guide describes how to move data manually between databases, servers, and computers.
Migration to and reversion from 14.10
Migrating to Informix® 14.10
When you migrate to a new version of Informix®, you must complete required migration and post-migration tasks.
Migrating to the new version of Informix®
After you prepare your databases for migration, you can migrate to the new version of Informix®.
Customizing configuration files
When you initialize the new version of Informix®, which contains a new onconfig.std file, use the same configuration that the old database server used. After you observe the performance of new version, you can examine the new file for new configuration parameters that you might want to use and can you start to use the new and changed configuration parameters.

Migrating and upgrading
You can upgrade to the 14.10 release of HCL Informix® or migrate from other database servers to Informix. Upgrading is an in-place migration method that uses your existing hardware and operating system software. Some changes to the Informix database server can affect upgrading from a previous release.
- Migrating Informix® database systems
  The Informix® Migration Guide describes how to move data manually between databases, servers, and computers.
  - Overview of migration
  - Migration to and reversion from 14.10
    - Preparing for migration to Version 14.10
      Before you install the new version of Informix®, you must prepare the database server environment for migration by performing specified pre-migration tasks. If you are also migrating from 32-bit to 64-Bit database servers, you must perform additional tasks.
    - Enterprise Replication and migration
      You must coordinate the migration of all servers that are involved in data replication.
    - High-availability cluster migration
      You must coordinate the migration and reversion of all servers that are involved in high-availability clusters. You can use a rolling upgrade in some cases to update servers while the cluster is online, with minimal interruption to client applications. Otherwise, you must schedule cluster downtime to upgrade the servers. A cluster must be offline to reverse an upgrade or revert to an earlier release.
    - Migrating to Informix® 14.10
      When you migrate to a new version of Informix®, you must complete required migration and post-migration tasks.
      - Migrating to the new version of Informix®
        After you prepare your databases for migration, you can migrate to the new version of Informix®.
        Installing the new version of Informix®
        Install and configure the new version of Informix®.
        Setting environment variables
        After you install the current version of Informix®, verify that the INFORMIXDIR, INFORMIXSERVER, ONCONFIG, PATH, and INFORMIXSQLHOSTS (if used) environment variables are set to the correct values.
        Customizing configuration files
        When you initialize the new version of Informix®, which contains a new onconfig.std file, use the same configuration that the old database server used. After you observe the performance of new version, you can examine the new file for new configuration parameters that you might want to use and can you start to use the new and changed configuration parameters.
        Using SSL/TLS database connections
        Adding Communications Support Modules
        For communications with clients, you can optionally use a Communications Support Module (CSM) with the current version of Informix®. After you install the CSM components, create entries in the concsm.cfg file and in the options field of the sqlhosts file to configure the CSM.
        Installing or upgrading any DataBlade® modules
        After you install the new version of Informix®, you might need to install or upgrade any DataBlade® modules that you want to add to the database server.
        Starting the new version of Informix®
        After installing the new database server, start the server. Do not perform disk-space initialization, which overwrites whatever is on the disk space.
        Restoring to a previous consistent state after a failed upgrade
        If the CONVERSION_GUARD configuration parameter is enabled and an upgrade fails, you can run the onrestorept command to undo the changes that are made during the upgrade and restore Informix® to a consistent state.
      - Completing required post-migration tasks
        After you migrate, you must complete a series of post-migration tasks to prepare the new version of the server for use.
    - Reverting from Informix® Version 14.10
      You can revert to the version of the database server from which you migrated. When you run the reversion utility, you specify the target server for reversion and then Informix® checks your database. If necessary, Informix might tell you to drop new objects, before automatically converting your data into the target server.
  - Migration of data between database servers
  - Data migration utilities

Customizing configuration files

When you initialize the new version of Informix®, which contains a new onconfig.std file, use the same configuration that the old database server used. After you observe the performance of new version, you can examine the new file for new configuration parameters that you might want to use and can you start to use the new and changed configuration parameters.

Set the ALARMPROGRAM configuration parameter to either nothing or no_log.sh to prevent the generation of errors if the logical log fills during the migration. For more details, see Starting the new version of Informix. After the migration, change the value of ALARMPROGRAM to log_full.sh.

If the ALARMPROGRAM configuration parameter is set to the script alarmprogram.sh, set the value of BACKUPLOGS in alarmprogram.sh to N.

Important: To facilitate migration (and reversion), use the same values for your new database server for ROOTOFFSET , ROOTSIZE, and ROOTPATH that you used for the old database server. Also, keep the same size for physical logs and logical logs, including the same number of logical logs, and the same sqlhosts file.

For information about how to configure Informix®, see your Informix® Administrator's Guide. For information about how to tune the configuration parameters, see the Informix® Performance Guide.