Entering content frame

Background documentation DBEXTRACT Command Locate the document in its SAP Library structure

You can use this Loader command to control the unloading of all application data and the corresponding database catalog information.

Prerequisite

The DBEXTRACT command can only be executed by the database system administrator (SYSDBA user).

Syntax

<dbextract_command> ::= DBEXTRACT [<configuration_instream_spec>] <catalog_outstream_spec> <data_outstream_spec> [<package_outstream_spec>] [<restart>]

<configuration_instream_spec> ::= CONFIGURATION <instream_spec>
<catalog_outstream_spec> ::= CATALOG <outstream_spec>
<data_outstream_spec> ::= DATA <outstream_spec>
<package_outstream_spec> ::= PACKAGE <outstream_spec>
<restart> ::= RESTART <valPACKAGEGUID>

valPACKAGEGUID

ID that is generated during the Loader runtime for the commands that span more than one table

You can also use the keywords EXTRACT DB instead of the keyword DBEXTRACT.

Explanation

The DBEXTRACT command combines the commands CATALOGEXTRACT ALL and TABLEEXTRACT ALL. You can useexternal backup tools to unload data.

<catalog_outstream_spec> und <data_outstream_spec>

At least two data streams must be created when unloading:

·        Data stream for the database catalog definitions catalog_outstream_spec

·        Data stream for the application data data_outstream_spec

The system table TRANSFORMATIONMODEL and other system tables are filled.

<configuration_instream_spec>

You can exclude tables from the unload process.

·        Unless you specify the data stream configuration_instream_spec, all the application data is unloaded.

·        By specifying the data stream configuration_instream_spec, you can exclude the application data of selected tables from the unload process data_outstream_spec. The tables must be identified in the data stream by specifying their owner and the table name.
The information about which tables are not unloaded is stored in the system tables. You can display this information by displaying the system table TRANSFORMATIONPACKAGES. The tables excluded from the unload process for the application data have the value TRUE in the EXCLUDE column.

The database catalog entries (catalog_outstream_spec) of all tables are always unloaded, regardless of the restrictions made in configuration_instream_spec.

<package_outstream_spec>

You can unload the system table TRANSFORMATIONPACKAGES.

·        When you specify the data stream package_outstream_spec, all entries in the table TRANSFORMATIONPACKAGES are unloaded to this data stream. You are recommended to use this option to create a log of the unload process.

·        If you do not specify the data stream package_outstream_spec, the system table TRANSFORMATIONPACKAGES is not unloaded.

<restart>

You can restart the unload process.

The PACKAGEGUID and the host name of the client of the Loader are entered in the table TRANSFORMATIONPACKAGES and logged in the log file.

The user can determine the PACKAGEGUID from the table TRANSFORMATIONPACKAGES or from the log file to restart the command with the corresponding PACKAGEGUID.

Result

The application data and the database catalog are unloaded to the data_outstream_spec and catalog_outstream_spec data streams.

If necessary, all entries in the table TRANSFORMATIONPACKAGES are unloaded to the package_outstream_spec data stream.

You can use the corresponding DBLOAD command to restore the database catalog and the application data.

Errors

The unload process cannot be successfully completed. In this case, the Loader logs the cause of the error in 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 unload process.

 

Leaving content frame