Compartilhar via

2.2.6.6 TRUN_TXBEGIN_ERRORS

  • Artigo

The TRUN_TXBEGIN_ERRORS enumeration defines the completion status values for requests from an application to perform the following steps in a transaction: begin, set time-out, commit, or abort a transaction.  

 typedef  enum 
 {
   TRUN_TXBEGIN_ERROR_NO_MEM = 1,
   TRUN_TXBEGIN_ERROR_BEGIN_LOG_FULL = 20,
   TRUN_TXBEGIN_ERROR_NOTIFY_ABORTED = 30,
   TRUN_TXBEGIN_ERROR_NOTIFY_COMMITTED = 31,
   TRUN_TXBEGIN_ERROR_NOTIFY_INDOUBT = 32,
   TRUN_TXBEGIN_ERROR_DUPLICATE_GUID = 33
 } TRUN_TXBEGIN_ERRORS;

TRUN_TXBEGIN_ERROR_NO_MEM:  There was insufficient memory to allocate the data structures necessary to create the new transaction.

TRUN_TXBEGIN_ERROR_BEGIN_LOG_FULL:  There was insufficient space in the transaction manager log to accommodate a new transaction.

TRUN_TXBEGIN_ERROR_NOTIFY_ABORTED:  The transaction has aborted.

TRUN_TXBEGIN_ERROR_NOTIFY_COMMITTED:  The transaction has committed.

TRUN_TXBEGIN_ERROR_NOTIFY_INDOUBT:  The transaction has completed, but the outcome is no longer determinable. This occurs if the transaction manager delegated the commit decision to a subordinate through the single-phase commit protocol and if the connection to that subordinate terminated before the result could be reported.

TRUN_TXBEGIN_ERROR_DUPLICATE_GUID:  An attempt was made to create or promote a transaction, but a transaction with the specified transaction identifier already exists.