Remote file

Type the base name to be used for creating temporary files during the load. We recommend that you enter a fully qualified name according to the server node.

The remote file is a base file name that DB2 will append with different extensions to create temporary files used to store messages and consistency points, and to delete phase information. The remote file resides on the server machine and is accessed by the DB2 instance exclusively. Any file name qualification must reflect the directory structure of the server, not the client, and the DB2 instance owner must have read and write permission on this file. You must ensure that more than one load is not issued using the same fully qualified remote file name.

Examples

In the following situations, where you either type a partially qualified name or no name at all, the indicated file name is used:

• If you are on the same machine as the database instance:

  No name given

  DB2 uses the name db2utmp and qualifies it with your current working directory. If you are loading data in more than one load process from this directory and you do not specify remote file names for each load process, the loads will clash.

  Partially qualified name given

  DB2 qualifies the name by using your current directory. You must ensure that more than one load is not issued from the same directory with the same remote file name.

• If you are on a different machine than the database instance:

  No name given

  DB2 generates a name that will reside in the database directory. The generated file name is not guaranteed to be unique; therefore, clashes between loads might occur.

  Partially qualified name given

  DB2 rejects the file name; the file name must be fully qualified from the client.

[ Top of Page | Table of Contents | Glossary | Index ]

[ DB2 List of Books | Search the DB2 Books ]