Data Movement Utilities Guide and Reference

Using Import

Before Using Import

Before invoking the import utility, you must be connected to (or be able to implicitly connect to) the database into which the data will be imported. Since the utility will issue a COMMIT or a ROLLBACK statement, you should complete all transactions and release all locks by performing either a COMMIT or a ROLLBACK before invoking import.

Invoking Import

The import utility can be invoked through:

• The command line processor (CLP).

  Following is an example of the IMPORT command issued through the CLP:

     db2 import from stafftab.ixf of ixf insert into userid.staff
  

• The Import notebook in the Control Center. To open the Import notebook:
  1. From the Control Center, expand the object tree until you find the Tables folder.
  2. Click on the Tables folder. Any existing tables are displayed in the pane on the right side of the window (the contents pane).
  3. Click the right mouse button on the table you want in the contents pane, and select Import from the pop-up menu. The Import notebook opens.

  For general information about the Control Center, see the Administration Guide. Detailed information is provided through the online help facility within the Control Center.

• An application programming interface (API), sqluimpr. For information about this API, see Import API. For general information about creating applications containing DB2 administrative APIs, see the Application Building Guide.

Using Import in a Client/Server Environment

When you import a file to a remote database, a stored procedure can be called to perform the import on the server. A stored procedure will not be called when:

• The application and database code pages are different.
• The file being imported is a multiple-part PC/IXF file.
• The method used for importing the data is either column name or relative column position.
• The target column list provided is longer than 4KB.
• An OS/2 or DOS client is importing a file from diskette.
• The LOBS FROM clause or the lobsinfile modifier is specified.
• The NULL INDICATORS clause is specified for ASC files.

When import uses a stored procedure, messages are created in the message file using the default language installed on the server. The messages are in the language of the application if the language at the client and the server are the same.

The import utility creates two temporary files in the tmp subdirectory of the sqllib directory (or the directory indicated by the DB2INSTPROF registry variable, if specified). One file is for data, and the other file is for messages generated by the import utility.

If you receive an error about writing or opening data on the server, ensure that:

• The directory exists.
• There is sufficient disk space for the files.
• The instance owner has write permission in the directory.