When recovering from media failure on the database file, the transaction log is intact. Recovery reapplies all committed transactions to the database. In some circumstances, you may want to find information about transactions that were incomplete at the time of the failure.
The Translate Log File Wizard helps you translate a log file into a .sql file from Sybase Central. You can also use the dbtran utility to translate a log file into a .sql file.
To recover uncommitted operations from a transaction log (Sybase Central)
From the Tools menu, choose SQL Anywhere 11 » Translate Log File.
Follow the instructions in the Translate Log File Wizard.
Edit the translated log (SQL command file) in a text editor and identify the instructions you need.
To recover uncommitted operations from a transaction log (Command line)
Run dbtran to convert the transaction log into a SQL command file, using the -a option to include uncommitted transactions. For example, the following command uses dbtran to convert a transaction log:
dbtran -a sample.log changes.sql |
Edit the translated log (SQL command file) in a text editor and identify the instructions you need.
For more information about the Log Translation utility, see Log Translation utility (dbtran).
The transaction log may or may not contain changes right up to the point where a failure occurred. It does contain any changes made before the end of the most recently committed transaction that made changes to the database.
| Send feedback about this page via email or DocCommentXchange | Copyright © 2008, iAnywhere Solutions, Inc. - SQL Anywhere 11.0.0 |