Data Movement Utilities Guide and Reference

Using Export

Before Using Export

Before invoking the export utility, you must be connected to (or be able to implicitly connect to) the database from which the data will be exported. Since the utility will issue a COMMIT statement, you should complete all transactions and release all locks by performing either a COMMIT or a ROLLBACK before invoking export. Other user applications accessing the table using separate connections need not disconnect.

Invoking Export

The export utility can be invoked through:

• The command line processor (CLP).

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

     db2 export to staff.ixf of ixf select * from userid.staff
  

• The Export notebook in the Control Center. To open the Export notebook:
  1. From the Control Center, expand the object tree until you find the Tables or Views folder.
  2. Click on the folder you want to work with. Any existing tables or views are displayed in the pane on the right side of the window (the contents pane).
  3. Click the right mouse button on the table or view you want in the contents pane, and select Export from the pop-up menu. The Export 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), sqluexpr. For information about this API, see Export API. For general information about creating applications containing DB2 administrative APIs, see the Application Building Guide.