Opening a Session: Loader CLI Options
You can call Loader using the Loader CLI Client ( LOADERCLI). By specifying the corresponding options, you can make various settings, including the settings in operating mode and connection information.
You can specify options when you call Loader CLI:
loadercli [ <options>]
Call up the help function to get an overview of all options:
loadercli -h
Operating Modes
Imports to Loader can be made in different operating modes: command file mode and session mode.
-
In command file mode, a command file written by the user is processed sequentially. The command file can contain any sequence of Loader commands and SQL statements.
-
In session mode the user can transfer the Loader commands and SQL statements to Loader directly via the console.
As of SAP MaxDB version 7.7, Database Studio database tool provides a GUI for Loader. More information: Database Studio
Setting up the Operating Mode: Loader CLI Options
The option required for determining the desired operating mode always has to be specified.
|
-b <command_file>[ <connect_options>] [ <in_output_options>] [ <version_options>] |
Loader CLI is transferred into command file mode if you specify option -b. More information: Command File Mode |
|
[ <connect_options>] [ <in_output_options>] [ <version_options>] |
Loader CLI is transferred into session mode if you specify neither option -p nor option -b. More information: Session Mode |
Further Loader CLI Options
|
-d <database_name> |
Name of database |
|
-u [ <database_user>[, <password>]] |
Name and password of database user |
| -U <user_key> | Name of the user key |
|
-n <database_computer>[: <port>] |
Name of database computer |
|
-s <schema_name> |
Name of schema |
|
-e <encryption> |
Encryption method |
More information: Opening a Database Session: Loader CLI Options
|
-o[w|a] <file_name> |
Name of output file |
|
-cs <separator> |
Command separator |
|
-ps <number> <string> |
Substitution parameter |
|
-E <number> |
Maximum number of errors allowed |
More information: Input and Output: Loader CLI Options
|
-V |
Version of Loader server |
|
-v |
Version of Loader CLI |
|
-R <installation_path> |
Directory containing the programs that are dependent on the version of the database software |
More information: Determing Version Information: Loader CLI Options
Before connecting to the database, Loader CLI evaluates the relevant options. Loader then executes the Loader commands and SQL statements in the command file (or those entered interactively). In all three operation modes, Loader writes a log file and, if appropriate, additional information ( Loader Log File, Loader Log Functions).
If errors occur when Loader commands or SQL statements are processed, the way in which Loader responds depends on the operation mode in which it was used.
-
Command file mode: After a defined number of errors, Loader stops processing Loader commands and SQL statements and closes. You can use the option -E to define the number of errors that Loader ignores before it stops processing commands. If you do not use the option -E, Loader stops running after the first command with an error. You cannot react to the errors when you are using Loader CLI.
-
Session mode: Loader reports the error that has occurred and then awaits further input for processing.
Loader Tutorial, Command File Mode, Session Mode