Transport Mode 
In transport mode, the user is interactively prompted for input to export application data from one database and import it into another database. 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 can be displayed on the console. The user can then use them as templates for custom commands. In transport mode, no knowledge of the syntax of Loader is required.
Features
In transport mode, the user designs a transformation package in an interactive menu by entering the direction of the transport (export from one database, import into a database or transport between databases), the database connection parameters and the database part to be transported. This information defines the contents of the package to be transported. When designing the package, the user may also define the data carrier type and the format in which the application data is to be transported.
You can start Loader CLI in interactive transport mode. To do this, enter the following command:
Syntax
loadercli –p [<package_timestamp>]
With package_timestamp, you specify the name of the generated package (phase generate) for which an export or transport can be executed (phase execute) or the name of a package created during an export (phase execute) that can be imported. The default value for package_timestamp is the time stamp that specifies when the package was generated.
Note
The transport mode is available for 32 bit platforms only.
Activities
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 transformation package. That is, Loader processes the sequence of Loader commands (the transformations) determined by the transformation package step by step (phase execute).
You do not have to execute a designed transformation package immediately; you can choose to generate only the sequence of Loader commands (phase generate). You can execute this generated transformation 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, you can start the import of the transformation package to another database by specifying the package name (interactively or by specifying the name of the transformation 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 and even execute an export and its corresponding import package together if you choose the transport transformation type.
Command file |
<timestamp>.EXPORT <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 Loader command file mode |
Internal files |
<timestamp>.xml <timestamp>.pkg <timestamp>.par <timestamp>.cfg |
These files contain internal data and may not be changed. |
The database catalog data of a transformation package includes one or more CATALOG files, depending on the granularity of the database catalog chosen for the export.
CATALOG file |
<database_name>.CATALOG |
All metadata of the specified database was transformed. |
CATALOG file |
<database_user>.CATALOG |
The metadata owned by the specified user was transformed. |
CATALOG file |
<schema_name>.CATALOG |
The metadata of the specified schema was transformed. |
CATALOG file |
<table_name>.CATALOG |
The metadata of the specified table was transformed. |
The application data of a transformation package includes one or more catalog files, depending on the granularity of the database catalog chosen for the export.
Mapping file |
<database_name>.DATA0000 <database_user>.DATA0000 <schema_name>.DATA0000 |
The application data from the specified database, user or schema has been transformed. |
Data file |
<database_name>.DATA000[<FILENO>] <database_user>.DATA000[<FILENO>] <schema_name>.DATA000[<FILENO>] |
FILENO is the sequential number of the files for the application data if the data set of a file exceeds 2 GB. Numbering starts with 1. The application data from the specified database, user or schema has been transformed. |
Table data file |
<table_name>.DATA |
The application data from the specified table except for the values of the LOB columns has been transformed. |
Table LOB data file |
<table_name><column_name>.DATA[<ROWNO>] |
ROWNO is the sequential number of the data files, starting with 1, if the LOB values for the column value are exported to a separate file. The application data of the specified LOB column of the table has been transformed. |
PACKAGE file |
<timestamp>.PACKAGE |
The runtime data of a package is contained in the PACKAGE file |
Result
The requested commands are designed, generated and executed, if applicable. Each transformation package is given a time stamp package_timestamp that 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 transformation 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 directory: EXPORT and IMPORT directory are used.
Logging
Loader writes the following logs in transport mode:
loader_<timestamp>.log: Loader Log File
transport.log: Loader Transformation History
Configuration
Configuration of the transformation packages using configuration file loader.cfg provides the user with the option of making individual settings. Configuration file loader.cfg is located in directory <loader_application_data>\config. In the section [PACKAGE], you can for example, configure settings for creating the transformation package (how the name is chosen, where the packages are stored, and so on). Note the differences in upper and lowercase spelling when making entries in the configuration file.
Example
Loader Tutorial, Transport Mode
Example
Starting Loader in transport mode
loadercli —p
Information about the default Loader transformation history (Microsoft Windows)
Package history: 'C:\Users\D019124\AppData\Roaming\sdb\loader\log\transport.log'
Location of the configuration file (Microsoft Windows)
C:\Users\D019124\AppData\Roaming\sdb\loader\config\loader.cfg