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

Determining which connection has an outstanding transaction

If you are carrying out a backup that renames or deletes the transaction log on a database created with version 8.0 or later of Adaptive Server Anywhere, incomplete transactions are carried forward to the new transaction log.

If you are carrying out a backup that renames or deletes the transaction log on a database created with version 7.x or earlier of Adaptive Server Anywhere, however, and if there are outstanding transactions, the backup must wait until those transactions are complete before it can complete.

You can use a system procedure to determine which user has outstanding transactions. If there are not too many connections, you can also use the Console utility to determine which connection has outstanding connections.

To determine which connection has an outstanding transaction (SQL)

1. Connect to the database from Interactive SQL or another application that can call stored procedures.

2. Execute the sa_conn_info system procedure:

   call sa_conn_info

3. Inspect the UncmtOps column to see which connection has uncommitted operations.

   For more information, see sa_conn_info system procedure.

To determine which connection has an outstanding transaction (Console utility)

1. Connect to the database from the Console utility.

   For example, the following command connects to the default database using user ID DBA and password SQL:

   dbconsole -c "uid=DBA;pwd=SQL"

   For more information, see The Console utility.

2. Double-click each connection, and inspect the Uncommitted Ops entry to see which users have uncommitted operations. If necessary, you can disconnect the user to enable the backup to finish.