Data Movement

Bind files used by the export, import and load utilities

A new bind file called db2uImpInsUpdate.bnd has been added to the import 9utility, with a default isolation level of Read Stability (RS). This bind 9file is used by the Import Utility only during INSERT_UPDATE. The import utility's 9INSERT, REPLACE and CREATE options still use the db2uimpm.bnd file.

The db2uImpInsUpdate.bnd bind file cannot be bound with the INSERT BUF 9option. Attempting to perform IMPORT INSERT_UPDATE while db2uImpInsUpdate.bnd 9is bound with INSERT BUF causes the import utility to fail, resulting in the 9following error:

SQL3525: The "INSERT_UPDATE" option is incompatible 9with the "INSERT BUF BIND ON DB2UIMPINSUPDATE.BND" option.

Using import with buffered inserts

Version 8.2 of the Data Movement Utilities Guide 9and Reference states:

The buffered inserts feature cannot be used 9in conjunction with import operations in which the INSERT_UPDATE parameter 9is specified. A new bind file (db2uimpm2.bnd) is introduced to enforce this 9restriction.

Due to the introduction of a new bind file, the statement should be:

The buffered inserts feature cannot be used in conjunction with import operations 9in which the INSERT_UPDATE parameter is specified. A new bind file (db2uImpInsUpdate.bnd) 9is introduced to enforce this restriction.

Index information lost when the import utility is used

You can use the import utility to recreate a table that was saved through 8the export utility.

The Data Movement topic "Using import to 8recreate an exported table" outlines attributes of the original table are not retained. In addition to the attributes which 8have already been documented, the following attributes are not retained:

8
• Index information: 8
  8
  • Include columns (if any)
  8
  • Index name, if the index is a primary-key index
  8
  • Descending order, if the index is a primary-key index (Ascending is the 8default)