Background documentationEXPORT USER Locate this document in the navigation structure

 

You can use the EXPORT USER command to export data and objects that are owned by the database user who is logged on to the database.

Prerequisites

You can use all of the demo data in database DEMODB. Start the Loader and log onto demo database DEMODB as database administrator MONA with the password RED. Use the session mode: loadercli -d demodb -u mona,red.

Activities

The data of user MONA is to be exported. You can make entries after the keyword CATALOG and/or DATA to select what is to be exported, the database catalog and/or the data belonging to the application.

Export of the Database Catalog of the Database User who is Logged On

You can export the database catalog information of the database user belonging to the application.

EXPORT USER

  CATALOG OUTSTREAM 'mona_ddl.catalog'

The database catalog (CATALOG) is exported in the DDL (default value) format.

See also: Loader, Data Stream

Exports the application data of the database user who is logged on

You can export the application data of the database user.

EXPORT USER

  DATA OUTSTREAM 'mona_pages.data'

The application data (DATA) is exported in the PAGES format (default value).

EXPORT DB

  DATA OUTSTREAM 'mona_records.data' RECORDS

The application data (DATA) is exported in the RECORDS format.

A PAGES export uses a database format (based on a page), and is therefore faster than an export that uses the RECORDS format of the Loader.

You may not change a data file in either case as the binary format is specific to the Loader.

See also: Loader, PAGES, RECORDS

Export of the Database Catalog and the Application Data of the Database User who is Logged On

You can export the data belonging to the application of the database user logged on to the database.

EXPORT USER

  CATALOG OUTSTREAM 'mona_ddl.catalog'

  DATA OUTSTREAM 'mona_pages.data'

Note the sequence of the syntax elements. Always enter the syntax element for exporting the database catalog first, and then the syntax element for exporting the application data.

Excluding Tables from the Export

By specifying a data stream after the keyword CONFIGURATION, you can exclude the application data of tables specified in this data stream. The tables must be identified in the data stream by specifying the schema and table name.

The CITY and HOTEL tables are to be excluded from the export. Create the hotel_table.configuration file with the following contents:

HOTEL,CITY

HOTEL,HOTEL

Specify the following export command in the Loader session mode. Note the sequence of the syntax elements. First, enter the syntax element that excludes the table from the export.

EXPORT USER

  CONFIGURATION INSTREAM 'hotel_table.configuration'

  CATALOG OUTSTREAM 'mona_ddl.catalog'

  DATA OUTSTREAM 'mona_pages.data'

The database catalog entries of all tables are always imported, regardless of the restrictions stipulated in hotel_table.configuration.

Additional Log Functions

If you specify a data stream after the keyword PACKAGE, the command entries from the SYSLOADER.TRANSFORMATIONMODEL table are exported to the specified data stream. This is an additional logging option. Always enter the PACKAGE syntax element as the last syntax element.

EXPORT USER

  CATALOG OUTSTREAM 'mona_ddl.catalog'

  PACKAGE OUTSTREAM 'mona_csv.package'

See also: Loader, Additional Log Functions (package_spec)

Complete Syntax of the EXPORT USER Command

Combining the syntax options can result in correspondingly complex commands. Observe the sequence of the syntax elements.

EXPORT USER

  CONFIGURATION INSTREAM FILE 'hotel_table.configuration' CSV ASCII

  CATALOG OUTSTREAM FILE 'mona_ddl.catalog' DDL

  DATA OUTSTREAM FILE 'mona_pages.data' PAGES

  PACKAGE OUTSTREAM FILE 'mona_csv.package' CSV

For a complete syntax description, see the EXPORT USER command in the Loader documentation.

More Information

Other example commands for Exporting

Corresponding Import command IMPORT USER

Session Mode