Teradata Database Message 3989 - 3989 - 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
- The request resulted in a cursor conflict.
- Explanation
- This is only a warning to let the user know that a cursor conflict exists involving the table referenced by the request. Cursor conflict occurs when one of the following situations happens within a transaction: 1) The request is a searched update or delete on a table that has already been modified through a cursor that is still open. 2) The request is an update or delete made through a cursor on a table that has been modified by another opened cursor while the first cursor was still open. 3) The request is an update or delete made through a cursor on a table that has already been modified by a searched update or delete while the cursor was still open. Note: The request is still processed despite the warning.
- Generated By
- Gnc modules.
- For Whom
- End User.
- Notes
- None
- Remedy
- None.