Constraints That Affect onunload

The onunload utility can unload data more quickly than either dbexport or the UNLOAD statement because onunload copies the data in binary format and in page-sized units. The following constraints apply to onunload:

• You must load the data on the onunload tape into a database or table that your database server (excluding SE) manages.
• You can use onunload and onload with Dynamic Server 10.0, 9.40, 9.30, or 9.2x if the databases contain only legacy data types and no extended data types.
• You must load the tape that onunload writes onto a computer with the same page size and the same representation of numeric data as the original computer.
• You must read the file that onunload creates with the onload utility of the same version of your database server. You cannot use onunload and onload to move data from one version to another.
• When you unload a complete database, you cannot modify the ownership of database objects (such as tables, indexes, and views) until after you finish reloading the database.
• When you unload and load a table, onunload does not preserve access privileges, synonyms, views, constraints, triggers, or default values that were associated with the original tables. Before you run onunload, use the dbschema utility to obtain a listing of the access privileges, synonyms, views, constraints, triggers, and default values. After you finish loading the table, use dbschema to re-create the specific information for the table.