Home | Previous Page | Next Page   Data Migration Utilities > The onunload and onload Utilities > Constraints That Affect onload and onunload >

Logging During Loading

The onload utility performs all its loading within a transaction. This feature allows the changes to be rolled back if an error occurs.

When you use onload to create tables from an onunload input tape, onload can only load information into a database without logging. Thus, before you load a table into an existing, logged database, end logging for the database. You also might want to consider loading during off-peak hours. Otherwise, you might fill the logical-log files or consume excessive shared-memory resources. After you load the table, create a level-0 dbspace backup before you resume database logging.

When you use onload to create databases from an onunload input tape, the databases that result are not ANSI compliant and do not use transaction logging. You can make a database ANSI compliant or add logging after you load the database. (For more information about logging, refer to the IBM Informix: Guide to SQL Reference.)

Home | [ Top of Page | Previous Page | Next Page | Contents | Index ]