Entering content frame

Function documentation Transport Mode Locate the document in the library structure

In transport mode the user is interactively prompted for input to export application data from one database instance and import it into another database instance. The input parameters and the Loader configuration file are used to generate and execute the syntax of the Loader commands.

The generated Loader commands are optionally displayed on the console and the user can then use them as templates for commands he has written himself. In the actual transport mode, no knowledge of the loader syntax is required.

Use

In transport mode the user designs a transformation package in an interactive menu by entering the direction of the transport (export from one database instance, import to an database instance or transport between database instances), the database connection parameters and the database part to be transported. This specifies the content of the package that is to be transported. When designing the package the user may also choose the transport medium and the format in which the application data is to be transported during the transport.

Syntax

You can start Loader CLI in interactive transport mode. To do so, enter the following command:

loadercli –p

If you already want to influence the interactive menu when Loader CLI is called or if you want to call up an already generated transformation package, use the corresponding options.

See also:

Transport Mode: Options

Examples

Transport Mode: Examples

Features

A transformation package is designed for an Export. In addition to the design data, the package consists of the catalog data and application data of the database instance and the corresponding runtime data of the transformation.

You can execute this package. That is, the Loader processes the sequence of Loader commands generated from the package (the transformations) step by step (phase execute).

You do not have to execute a designed package immediately; you can choose to only generate the sequence of loader commands (phase generate). You can execute this generated package at a later time either as is or with minor modifications (phase execute). You can execute a generated transformation package either interactively or by means of the corresponding transport mode options.

After an export, the user has the option of starting the import of the package to another database instance by specifying the package name (interactively or by means of the corresponding transport mode options). In this case you can also either generate the import package or execute it immediately.

You can design and generate or even execute an export and its corresponding import package together, if you choose the transport transformation type.

Generated Design Data

The generated design data of the package includes the following data:

·        Command file: <package_name>.prt
This file contains the sequence of Loader commands generated from the design data. The user can modify the file and execute it in command file mode of the Loader. The sequence of these Loader commands is also copied to the log file.

·        Internal files: <package_name>.xml, <package_name>.PACKAGE, <package_name>.par, <package_name>.cfg
These files contain internal data and may not be changed.

Database Catalog Date

The database catalog data includes one or more catalog files, depending on which granularity of the database catalog was chosen for the export.

·        <database_name>.CATALOG: All metadata of the specified database was transformed.

·        <user_name>.CATALOG: The metadata that is owned by the specified user was transformed.

·        <schema_name>.CATALOG: The metadata of the specified schema was transformed.

·        <table_name>.CATALOG: The metadata of the specified table was transformed.

Application Data

The application data includes one or more catalog files, depending on which granularity of the database catalog was chosen for the export.

·        Mapping file:
  <database_name>.DATA0000
| <user_name>.DATA0000
| <schema_name>.DATA0000
The application data of the specified database, user or schema was transformed.

·        Data file:
  <database_name>.DATA000[<FILENO>]
| <user_name>.DATA000[<FILENO>]
| <schema_name>.DATA000[<FILENO>]

FILENO is the sequential numbering of the files for the application data if the dataset of a file exceeds 2 GB, which starts with 1.
The application data of the specified database, user or schema was transformed.

·        Application data of the table except for the values of the LONG columns: <table_name>.DATA
The application data of the specified table was transformed.

·        Application data of the LONG columns: <table_name>_<column_name>.DATA[<ROWNO>]
ROWNO is the sequential numbering of the data files starting with 1, if the LONG values for column value are exported to a separate file.
The application data of the specified LONG column of the table was transformed.

Runtime Data

The runtime data is included in the package file:

<database_name>.PACKAGE | <user_name>.PACKAGE | <schema_name>.PACKAGE

The package file contains the runtime data of a transformation of the specified database, user or schema.

Result

The requested commands are designed and generated and, if applicable, executed.

Each package contains a globally unique ID package_guid, a timestamp package_timestamp, that shows when the package was generated or executed and a package name package_name, which is identical to the timestamp by default. This information is displayed after an action is completed.

The export and import packages are stored in the package directory <loader_user_data>\packages in the following subdirectories:

Logging

The logging of the runtime behavior of the package, that is, the commands that are executed are logged in log file loader.prt

The Loader generates a transformation history transport.log, which records which package was generated and which package was executed. The transformation history is located in directory <loader_user_data>\packages.

The packages in the subdirectories of the directory <loader_user_data>\packages are identified by means of the unique ID package_guid and the timestamp package_timestamp.

Configuration

The configuration of the packages via the configuration file loader.cfg provides the user the option of making individual settings. For example, the storage directory of the packages and the assignment of package names can be configured with the parameters packagepath and packagename. The  configuration file  loader.cfg is located in directory <loader_application_data>\config.

See also:

Concepts of the Database System,  Directories, Log Files, Configuration Files

 

Leaving content frame