Entering content frame

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

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

Prerequisite

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

You have unloaded the database catalog and its content using the DBEXTRACT command.

Syntax

<dbload_command> ::= DBLOAD [<configuration_instream_spec>] <catalog_instream_spec> <data_instream_spec> [<package_outstream_spec>] [<restart>]

<configuration_instream_spec> ::= CONFIGURATION <instream_spec>
<catalog_instream_spec> ::= CATALOG <instream_spec>
<data_instream_spec> ::= DATA <instream_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 LOAD DB instead of the keyword DBLOAD.

Explanation

The DBLOAD command combines the commands CATALOGLOAD ALL and TABLELOAD ALL.

You can use external backup tools to load data.

<catalog_instream_spec> und <data_instream_spec>

At least two data streams are required when loading:

·        Data stream for the database catalog definitions catalog_instream_spec

·        Data stream for the application data data_instream_spec

If you want to use the data streams generated with the DBEXTRACT command, specify these names.

The system table TRANSFORMATIONMODEL and other system tables are filled.

<configuration_instream_spec>

You can exclude tables from the load process.

Unless you specify the data stream configuration_instream_spec, all of the data contained in the catalog_instream_spec and data_instream_spec data streams.

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

The database catalog entries (catalog_instream_spec) of all tables are always loaded, 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 load process.

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

<restart>

You can restart the load 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 definitions are loaded using the data_instream_spec and data_instream_spec data streams.

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

Errors

The load 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