Reads a database transaction log and sends committed changes to Replication Server.
dbltm [ options ]
| Option | Description |
|---|---|
| @data |
Use this option to read in options from the specified environment variable or configuration file. See Using configuration files. If you want to protect passwords or other information in the configuration file, you can use the File Hiding utility to obfuscate the contents of the configuration file. See File Hiding utility (dbfhide). |
| -A | Do not filter updates. By default, all changes made by the maintenance user are not replicated. If the -A option is set, these changes are replicated. This may be useful in non-hierarchical Replication Server installations, where a database acts as both a replicate site and as a primary site. |
| -C config_file |
Use the configuration file config_file to determine the LTM settings. The default configuration file is dbltm.cfg. See The LTM configuration file. |
| -I interface_file | (Uppercase I.) Use the named interfaces file. The interfaces file is the file created by DSEDIT and holds the connection information for Open Servers. The default interfaces file is SQL.ini in the ini subdirectory of your Sybase directory. |
| -M | This is used to initiate recovery actions. The LTM starts reading logs from the earliest available position. If the offline directory is specified in the configuration file, the LTM reads from the oldest offline log file. |
| -S LTM_name | Provides the server name for this LTM. The default LTM name is DBLTM_LTM. The LTM name must correspond to the Open Server name for the LTM that was entered in DSEDIT. |
| -dl | Display all messages in the LTM window or at a command prompt, as well as in the log file (if specified). |
| -ek key | This option allows you to specify the encryption key for strongly encrypted databases directly in the command. If you have a strongly encrypted database, you must provide the encryption key to use the database or transaction log in any way, including offline transaction logs. For strongly encrypted databases, you must specify either -ek or -ep, but not both. The command fails if you do not specify a key for a strongly encrypted database. |
| -ep | This option allows you to specify that you want to be prompted for the encryption key. This option causes a dialog box to appear, in which you enter the encryption key. It provides an extra measure of security by never allowing the encryption key to be seen in clear text. For strongly encrypted databases, you must specify either -ek or -ep, but not both. The command fails if you do not specify a key for a strongly encrypted database. |
| -o filename | Use a log file different from the default (dbltm.log). Write output messages from log transfer operations to this file. |
| -os size | Specify the maximum size of the output file, in bytes. The minimum value is 10000 (ten thousand). If the log file grows to the point where it would exceed this limit, it is renamed to yymmddxx.ltm. The value of xx in yymmddxx.ltm is incremented for each file created on a given day. |
|
-ot file | Use a log file different from the default (dbltm.log), and truncate the log file (all existing content is deleted) when the LTM starts. Output messages from log transfer operations are sent to this file for later review. |
| -q | Minimize the window when the LTM is started. |
| -s | Log all LTL commands that are generated by the LTM. This should be used only to diagnose problems, and is not recommended in a production environment. It carries a significant performance penalty. |
| -ud | You can run the LTM as a daemon on Unix operating systems. If you run in this manner, output is logged to the log file. |
| -ux | When -ux is specified, dbltm must be able to find a usable display. If it cannot find one, for example because the DISPLAY environment variable is not set or because the X window server is not running, dbltm fails to start. On Windows, the console appears automatically. |
| -v | Displays messages, other than LTL messages, for debugging purposes. |
The Log Transfer Manager (LTM) is also known as a replication agent. The LTM is required for any SQL Anywhere database that participates in a Replication Server installation as a primary site.
The SQL Anywhere LTM reads a database transaction log and sends committed changes to Replication Server. The LTM is not required at replicate sites.
The LTM sends committed changes to Replication Server in a language named Log Transfer Language (LTL).
By default, the LTM uses a log file named DBLTM.LOG to hold status and other messages. You can use options to change the name of this file and to change the volume and type of messages that are sent to it.
Exit codes are 0 (success) or non-zero (failure). See Software component exit codes.