Background documentationEXPORT USER Command Locate this document in the navigation structure

 

You can use the Loader command EXPORT USER to export the data belonging to the application of the database user logged onto the database.

Prerequisites

You can use the EXPORT USER command to export objects owned by the database user logged on to the database.

Structure

Syntax Syntax

  1. <export_user_command> ::=
      EXPORT USER
        [<configuration_spec>]
        <catalog_data_outstream_part_spec>
        [<package_spec>]
        [<restart_spec>]
    
    <configuration_spec> ::=
      CONFIGURATION <instream_csv_spec>
    
    <catalog_data_outstream_part_spec> ::=
      <catalog_outstream_spec>
    | <data_outstream_part_spec>
    | <catalog_outstream_spec> <data_outstream_part_spec>
    <catalog_outstream_spec> ::=
      CATALOG <outstream_ddl_spec>
    <data_outstream_part_spec> ::=
      DATA <outstream_tableformat_spec>
    
    <package_spec> ::=
      PACKAGE <oustream_csv_spec>
    
    <restart_spec> ::=
      RESTART <package_guid>
    <package_guid> ::=
      <unsigned_integer>
End of the code.
<catalog_outstream_spec>, <data_outstream_part_spec>

Depending on whether the database catalog and/or application data is exported, the following data streams are generated during export:

  • Data stream for database catalog definitions CATALOG <outstream_ddl_spec>

  • Data stream for application data DATA <outstream_tableformat_spec>

System table SYSLOADER.TRANSFORMATIONMODEL and additional system tables are filled. Only one of the formats PAGES or RECORDS is possible for the data stream of the outstream_tableformat_spec application data.

See: Data Stream, PAGES, RECORDS

Syntax Syntax

  1. EXPORT USER
      [<configuration_spec>]
      <catalog_outstream_spec> <data_outstream_part_spec>
      [<package_spec>]
      [<restart_spec>]
End of the code.

This EXPORT USER command exports the data belonging to the application of the database user logged onto the database.

Syntax Syntax

  1. EXPORT USER
      <catalog_outstream_spec>
      [<package_spec>]
      [<restart_spec>]
End of the code.

This EXPORT USER command exports the catalog information belonging to the application for the database user who is logged on.

Syntax Syntax

  1. EXPORT USER
      [<configuration_spec>]
      <data_outstream_part_spec>
      [<package_spec>]
      [<restart_spec>]
End of the code.

This EXPORT USER command exports the application data of the database user who is logged on.

<configuration_spec>

You can exclude tables from the export.

  • If you do not specify a data stream using CONFIGURATION <instream_csv_spec>, all the application data is exported.

  • If you specify a data stream using CONFIGURATION <instream_csv_spec>, you can exclude the application data of selected tables from the export of the outstream_tableformat_spec application data. The tables must be identified in the data stream by specifying their schema and table name. The information about which tables are not exported is stored in the system tables. One way of displaying this information is to display the system table SYSLOADER.TRANSFORMATIONMODEL. The tables excluded from the export of the application data have the value TRUE in the EXCLUDE column.

The database catalog entries CATALOG <outstream_ddl_spec> are always exported for all tables, regardless of the restrictions set using CONFIGURATION <instream_csv_spec>.

<package_spec>

You can export system table SYSLOADER.TRANSFORMATIONMODEL.

  • If you specify a data stream using PACKAGE <outstream_csv_spec>, all entries in the SYSLOADER.TRANSFORMATIONMODEL table are exported to this data stream. We recommend you use this option to create a log of the export or import process.

  • If you do not specify a data stream using PACKAGE <outstream_csv_spec>, the system table SYSLOADER.TRANSFORMATIONMODEL is not exported.

See: Additional Log Functions (package_spec)

<restart_spec>

You can restart the export or import using the package_guid (ID created by Loader for every command at runtime. This integer is always 24 bytes long). The user can determine the package_guid of the corresponding export or import commands from the SYSLOADER.TRANSFORMATIONMODEL table or the log file. You can restart the command with the corresponding package_guid using the restart_spec syntax element.

See: Restarting

Result

The application data and/or the database catalog are exported to the data_outstream_part_spec and catalog_outstream_spec data streams. If necessary, all entries in the SYSLOADER.TRANSFORMATIONMODEL table are exported to the package_spec data stream. You can use the corresponding IMPORT command to restore the database catalog and/or the application data.

Errors: The export cannot be completed successfully. Loader writes the cause of the error to the log file. The values PACKAGEGUID and CLIENTNODE are also written to the log file. The PACKAGEGUID is required if you want to restart the export.

Example

Loader Tutorial, EXPORT USER