ASA Database Administration Guide
  Backup and Data Recovery
    Backup and recovery tasks

Recovering uncommitted operations

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 wish to find information about transactions that were incomplete at the time of the failure.

To recover uncommitted operations from a transaction log (Sybase Central)

1. Do one of the following:

   • If you are connected to a database, in the left pane, select the Adaptive Server Anywhere plug-in, and then click the Utilities tab in the right pane. In the right pane, double-click Translate Log File.

   • If you are not connected to a database, click Tools > Adaptive Server Anywhere 9 > Translate Log File.

2. Follow the instructions in the wizard.

3. 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)

1. 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

2. Edit the translated log (SQL command file) in a text editor and identify the instructions you need.

   For more information on the Log Translation utility, see The Log Translation utility.

Note 

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.