Click here to view and discuss this page in DocCommentXchange. In the future, you will be sent there automatically.

SQL Anywhere 12.0.1 » SQL Anywhere Server - Database Administration » Starting and connecting to your database » Database file types » The transaction log

 

Outstanding transactions on connections

If you are performing a backup that renames or deletes the transaction log, incomplete transactions are carried forward to the new transaction log.

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 SQL Anywhere Console utility to determine which connection has outstanding transactions. If necessary, you can disconnect the user with a DROP CONNECTION statement.

 Determine which connection has an outstanding transaction (SQL)
  1. Connect to the database from Interactive SQL.

  2. Execute the sa_conn_info system procedure:

    CALL sa_conn_info;
  3. Inspect the UncommitOps column to see which connection has uncommitted operations.

    See sa_conn_info system procedure.

 Determine which connection has an outstanding transaction (SQL Anywhere Console utility)
  1. Connect to the database from the SQL Anywhere Console utility.

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

    dbconsole -c "UID=DBA;PWD=sql"

    See SQL Anywhere Console utility (dbconsole).

  2. Double-click each connection, and inspect the Uncommitted Ops entry to see which users have uncommitted operations.

 See also