With this Loader command, you can control the loading of all application data and the corresponding database catalog information.
<dbload_statement>
::=
DBLOAD [<configurationstream_spec
>] <cataloginstream_spec
> <datainstream_spec
> [<packagestream_spec
>]
[<restart>]
You can also use the keywords LOAD DB instead of the keyword DBLOAD.
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.
The DBLOAD command combines the commands CATALOGLOAD ALL and TABLELOAD ALL.
You can use external backup tools to load data.
At least two data streams are required when loading:
· Data stream for the database catalog definitions <cataloginstream_spec>
· Data stream for the application data <datainstream_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.
· Unless you specify the data stream <configurationstream_spec>, all of the data contained in the data streams <cataloginstream_spec> and <datainstream_spec> is loaded.
·
By specifying
a data stream <configurationstream_spec>, you can exclude the
application data of selected tables from the application data being loaded
<datainstream_spec>.
The tables must be
identified in the data stream by the specification of 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 column EXCLUDE.
The database catalog entries (<cataloginstream_spec>) of all tables are always loaded, regardless of the restrictions made in <configurationstream_spec>.
When making the required specifications in the data stream <configurationstream_spec>, you need to choose between the following variants depending on the medium from which you are loading the data streams:
·
Variant 1:
Loading from a file (FILE)
The data stream must contain entries for the positions of table data that is
to be excluded from the load process. You can find this information in
the specifications for the data stream <packagestream_spec> of the corresponding DBEXTRACT
command.
·
Variant 2:
Loading using a pipe (PIPE)
The tables specified in the data stream are excluded from the
transformation.
· When you specify a data stream <packagestream_spec>, all entries of 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 <packagestream_spec>, the system table TRANSFORMATIONPACKAGES is not unloaded.
The application data and the database catalog definitions are loaded using the data streams <datainstream_spec> and <cataloginstream_spec>.
If necessary, all entries of the table TRANSFORMATIONPACKAGES are unloaded in the data stream <packagestream_spec>.
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.