Administers the transaction log for a database.
dblog [ options ] database-file
| 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). |
| -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. For strongly encrypted databases, you must specify either -ek or -ep, but not both. The command will fail if you do not specify the correct 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 will fail if you do not specify the correct key for a strongly encrypted database. |
| -g n |
Use this option if you are using the Log Transfer Manager to participate in a Replication Server installation. It can be used after a backup is restored, to set the generation number. It performs the same function as the following Replication Server function: dbcc settrunc( 'ltm', 'gen_id', n ) For information about generation numbers and dbcc, see your Replication Server documentation. |
| -il |
This option can be used if you have stopped using the Log Transfer Manager to participate in a Replication Server installation on this database, but continue to use SQL Remote or MobiLink synchronization. It resets the Log Transfer Manager log offset that is kept for the delete_old_logs option, allowing transaction logs to be deleted when they are no longer needed. It performs the same function as the following Replication Server function: dbcc settrunc( 'ltm', 'ignore' ) For information about dbcc, see your Replication Server documentation. |
| -ir | This option can be used if you have stopped using SQL Remote on this database, but continue to use the Log Transfer Manager or MobiLink synchronization. It resets the SQL Remote log offset that is kept for the delete_old_logs option, allowing transaction logs to be deleted when they are no longer needed. |
| -is | This option can be used if you have stopped using MobiLink synchronization on this database, but continue to use the Log Transfer Manager or SQL Remote. It resets the MobiLink log offset that is kept for the delete_old_logs option, allowing transaction logs to be deleted when they are no longer needed. |
| -m mirror-name | This option sets a file name for a new transaction log mirror. If the database is not currently using a transaction log mirror, it starts using one. If the database is already using a transaction log mirror, it changes to using the new file as its transaction log mirror. |
| -n | Stop using a transaction log, and stop using a mirror log. Without a transaction log, the database can no longer participate in data replication or use the transaction log in data recovery. If a SQL Remote, Log Transfer Manager, or dbmlsync truncation offset exists, the transaction log cannot be removed unless the corresponding ignore option (-il for the Log Transfer Manager, -ir for SQL Remote, or -is for dbmlsync) is also specified. You cannot stop using a transaction log if the database has auditing turned on (unless you first turn auditing off). |
| -o file-name | Write output messages to the named file. |
| -q | Run in quiet mode—do not display messages. |
| -r | For databases that maintain a mirrored transaction log, this option changes their behavior to maintain only a single transaction log. |
| -t log-name | This option sets a file name for a new transaction log. If the database is not currently using a transaction log, it starts using one. If the database is already using a transaction log, it changes to using the new file as its transaction log. |
| -x n | For use when reloading a SQL Remote consolidated database. This option resets the transaction log current relative offset to n, so that the database can take part in replication. See Unloading and reloading a database participating in replication. |
| -z n | For use when reloading a SQL Remote consolidated database. This option resets the transaction log starting offset to n, so that the database can take part in replication. See Unloading and reloading a database participating in replication. |
The dblog utility allows you to display or change the name of the transaction log or transaction log mirror associated with a database. You can also stop a database from maintaining a transaction log or mirror, or start maintaining a transaction log or mirror.
A transaction log mirror is a duplicate copy of a transaction log, maintained by the database in tandem.
The name of the transaction log is first set when the database is initialized. The Transaction Log utility works with database files. The database server must not be running on that database when the transaction log file name is changed (or an error message appears).
The utility displays additional information about the transaction log, including the following:
You can access the Transaction Log utility in the following ways:
From Sybase Central, using the Change Log File Settings wizard. See Changing the location of a transaction log.
From Interactive SQL, using the ALTER DATABASE dbfile ALTER LOG statement. See ALTER DATABASE statement.
At a command prompt, using the dblog command.
Exit codes are 0 (success) or non-zero (failure). See Software component exit codes.