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.
Data migration utilities
The onunload and onload utilities
The onunload and onload utilities provide the fastest way to move data between computers that use the same database server on the same platform.
Syntax of the onunload command
The onunload command unloads data from a database and writes a database or table into a file on tape or disk.
onunload destination parameters
The onunload utility supports tape or file destination options.

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
  - Migration of data between database servers
  - Data migration utilities
    - External tables
      External tables are a fast and versatile method for moving data between database servers. External tables are the fastest method for loading data into a RAW table with no indexes.
    - The dbexport and dbimport utilities
      The dbexport and dbimport utilities import and export a database and its schema to disk or tape.
    - The dbload utility
      The dbload utility loads data into databases or tables that Informix® products created. It transfers data from one or more text files into one or more existing tables.
    - The dbschema utility
      The dbschema utility displays the SQL statements (the schema) that are necessary to replicate database objects.
    - The LOAD and UNLOAD statements
      You can use the SQL LOAD and UNLOAD statements to move data. The LOAD statement is moderately fast and easy to use, but it only accepts specified data formats. You usually use the LOAD statement with data that is prepared with an UNLOAD statement.
    - The onunload and onload utilities
      The onunload and onload utilities provide the fastest way to move data between computers that use the same database server on the same platform.
      - Guidelines for when to use the onunload and onload utilities
        You can use onunload and onload only when certain conditions are met.
      - Requirements for using the onload and onunload utilities
        The onload and onunload utilities have limitations. You can use these utilities only to move data between database servers of the same version on the same operating system. You cannot modify the database schema, logging must be turned off, and the utilities can be difficult to use.
      - How the onunload and onload utilities work
        The onunload utility, which unloads data from a database, writes a database or table into a file on tape or disk. The onload utility loads data that was created with the onunload command into the database server.
      - Syntax of the onunload command
        The onunload command unloads data from a database and writes a database or table into a file on tape or disk.
        onunload destination parameters
        The onunload utility supports tape or file destination options.
        Constraints that affect onunload
        When you use the onunload utility, you must be aware of constraints that affect how you load the data on the onunload tape.
        Privileges for database or table unloading
        To unload a database, you must have DBA privileges for the database or be user informix. To unload a table, you must either own the table, have DBA privileges for the database in which the table resides, or be user informix.
        Tables that are unloaded with a database
        If you unload a database, all of the tables in the database, including the system catalog tables, are unloaded.
        Data that is unloaded with a table
        If you unload a table, onunload unloads the table data and information from the systables, systables, syscolumns, sysindexes, and sysblobs system catalog tables.
        Locking during unload operation
        During the unload operation, the database or table is locked in shared mode. An error is returned if onunload cannot obtain a shared lock.
      - Logging mode
        The onunload utility does not preserve the logging mode of a database. After you load the database with onload, you can make a database ANSI compliant or add logging.
      - Syntax of the onload command
        The onload command loads data that was created with the onunload command into the database server.
      - Moving a database between computers with the onunload and onload utilities
        You can use the onunload and onload utilities to move a complete database from one computer to another.
      - Moving a table between computers with the onunload and onload utilities
        You can use the onunload and onload utilities to move a table from one computer to another.
      - Moving a table between dbspaces with the onunload and onload utilities
        You can use the onunload and onload utilities to move a table from one dbspace to another dbspace on the same computer.
    - The onmode utility reversion option
      You use the -b option of the onmode utility to revert to the older database server from which you converted.
    - The onrestorept utility
      You can use the onrestorept utility to restore the database server back to the state that it was in just before the start of the failed upgrade.

onunload destination parameters

The onunload utility supports tape or file destination options.

The following syntax diagram fragment shows onunload destination parameters

Destination parameters

{ | -l | -bblocksize | -s tapesize | -tsource } ^{(explicit id )}


Element	Purpose	Key Considerations
-b *blocksize*	Specifies in kilobytes the block size of the tape device	Requirement: The *blocksize* must be an integer. Additional Information: This option overrides the default value in TAPEBLK or LTAPEBLK.
-l	Directs onunload to read the values for tape device, block size, and tape size from LTAPEDEV, LTAPEBLK, and LTAPESIZE, respectively	None.
-s *tapesize*	Specifies in kilobytes the amount of data that can be stored on the tape	Requirement: The *tapesize* must be an integer. To write to the end of the tape, specify a tape size of `0`. If you do not specify `0`, then the maximum *tapesize* is 2 097 151 KB. Additional Information: This option overrides the default value in TAPESIZE or LTAPESIZE.
-t *source*	Specifies the path name of the file on disk or of the tape device where the input tape is mounted	Additional Information: This option overrides the tape device specified by TAPEDEV or LTAPEDEV. The path name must be a valid path name.

¹ Only one occurrence of each option allowed. More than one option can occur in a single invocation.