SYBASE Error 277 There was a transaction active when exiting the stored procedure '%.*s'. The tempo

 

Error 277

Severity

16

Error message text

There was a transaction active when exiting the stored procedure '%.*s'. The temporary table '%.*s' was dropped in this transaction either explicitly or implicitly. This transaction has been aborted to prevent database corruption.

Explanation

When exiting a stored procedure, Adaptive Server checks to see whether there is an active transaction (a transaction that has not been committed) and then checks to see whether any temporary objects exist for that uncommitted transaction.

If temporary objects exist, the transaction is rolled back, the temporary objects are dropped, and Error 277 is raised.

Action

In stored procedures, make sure all begin transaction statements have corresponding commit transaction or rollback transaction statements.

In chained mode, if there is no explicit begin transaction statement, an implicit begin transaction is issued. If you are using chained mode, an explicit commit transaction or rollback transaction statement is required to end the transaction.

If you confirm that all begin transaction statements have corresponding commit transaction or rollback transaction statements, check to see whether the stored procedure is exiting without completing its processing.

Versions in which this error is raised

All versions