Transaction Errors
The following table lists transaction-specific error messages.
|
Message |
Code |
Probable Cause |
|
META_E_TX_ROLLED_BACK |
0x80007400 |
Error in Transaction: The transaction was rolled back. The Commit request rolled back due to an error in the transaction or CMetaRepository::Deinitialize was called while a transaction was still open. |
|
META_E_TX_COMMIT_FAILED |
0x80007402 |
Commit Command Failed: The commit command to the Teradata Database failed. |
|
META_E_TX_ROLLBACK_ FAILED |
0x80007403 |
Rollback Command Failed: The rollback command to the Teradata Database failed. |
|
META_E_TX_ILLEGAL_ DDL_TYPE |
0x80007404 |
Unrecognized Type: A DDL specification contained an unrecognized type. This is an internal error. |
|
META_E_TX_HAS_ERROR |
0x80007405 |
Current Transaction Error: The current transaction is in an error state. The transaction must be closed by issuing a Rollback or issuing a Commit for each nesting level. |
|
META_E_TX_NO_ MATCHING_DDL_FOUND |
||
|
|
0x80007406 |
No outstanding DDL was found to retry: The application called the API CMetaRepository::RetryDDL but no outstanding DDL was found to retry. (If the application specified a transaction serial number, there were no outstanding DDL statements for that transaction. If the application did not specify a transaction serial number, there were no outstanding DDL statements for any transaction.) This normally indicates that the transaction specified (or all transactions, if none specified) either committed or rolled back successfully and does not require any repair through RetryDDL. This error code indicates that RetryDDL did not make any change to the repository. |
|
META_E_TX_INDEX_OUT_ OF_RANGE |
||
|
|
0x80007500L |
Index out of range: Specified transaction index is out of the initialized range. |