Teradata Database Message 6605 - 6605 - Analytics Database - Teradata Vantage
Teradata® VantageCloud Lake - Analytics Database Messages
- Edition
- Lake
- Product
- Analytics Database
- Teradata Vantage
- Published
- October 2022
- Language
- English (United States)
- Last Update
- 2024-02-26
- dita:mapPath
- tzr1629746512312.ditamap
- dita:ditavalPath
- ft:empty
- dita:id
- vza1585613049811
- lifecycle
- latest
- Product Category
- Teradata® Vantage™
- Message
- A operation was attempted that made no sense given the current state
- Explanation
- This is primarily the result of requesting that an operation be performed the is not following the proper protocol. Some examples are: 1. Clean batch that is not in correct state (crash state or or done). 2. Asking for a commit sequence number for a batch not in crash state. 3. Sending change rows to a transaction that is not in the correct state. 4. Executing control messages out of sequence or inappropriately for a transaction and example would be requesting a request abort for an asynchronous transaction.
- Generated By
- Replication Services Call Interface (RCI)
- For Whom
- RSG (Relay Services Gateway)
- Notes
- None
- Remedy
- N/A