Client/server environments and import

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 cannot 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 4 KB.
  • 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.