## Transport Mode

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 (phase generate) and execute (phase 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 the user has written him or herself. 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 data carrier type 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 [<package_timestamp>]

<package_timestamp> | Name of the generated package (phase generate) for which an export or transport can be executed (phase execute) or name of a package created during an export (phase execute) that can be imported Default value: time stamp that specifies when the package was generated

### Examples

Loader Tutorial, Transport Mode

### Features

A transformation package is designed for an export in transport mode. In addition to the design data, the package consists of the appropriate database catalog data and application data and the corresponding runtime data of the transformation, such as the transport log file.

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

You do not have to execute a designed package immediately; you can choose to generate only 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 specifying the name of the package after the option -p). 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 a package includes the following data:

● Command file:: <timestamp>.EXPORT or <timestamp>.IMPORT
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.

● Internal files: <timestamp>.xml, <timestamp>.pkg, <timestamp>.par, <timestamp>.cfg
These files contain internal data and may not be changed.

#### Database Catalog Date

The database catalog data of a package 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.

● <database_user>.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 of a package includes one or more catalog files, depending on which granularity of the database catalog was chosen for the export.

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

● Data file:
<database_name>.DATA000[<FILENO>]
| <database_user>.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 of a packet are contained in the PACKAGE file <timestamp>.PACKAGE.

### Result

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

Each package is given a time stamp package_timestamp, which shows when the package was generated or executed for the first time. If the default values are not changed, this time stamp is also the name of the package.

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

- EXPORT directory:
  export\<database_computer>\<database_name>\<package_timestamp>
- IMPORT directory:
  import\<database_computer>\<database_name>\<package_timestamp>
- Transport: EXPORT and IMPORT directory are used

#### Logging

The Loader writes the following logs in transport mode:

● Log File loader_<timestamp>.log

● Transformation History transport.log

#### Configuration

The configuration of the packages via the configuration file loader.cfg provides the user the option of making individual settings. The configuration file loader.cfg is located in directory <loader_application_data>\config.

You can, in the section [PACKAGE], for example, configure settings for creating the package (how should the name be chosen, where should the packages be stored etc.). Note the differences in upper and lowercase spelling when making entries in the configuration file.

See also:

Call Options of the Loader CLI

Concepts of the Database System, Log Files, Configuration Files

Installation Manual, Directories