Teradata Database Message 7445 - 7445 - 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
- Mload table %TVMID cannot be released because fallback exists. See manual to release MLoad lock in Apply for fallback table.
- Explanation
- The user attempted to release an Mload Apply Phase or Restoration Lock on a table that has fallback. The table had been the target of an Mload that was aborted in the Apply Phase. There may be internal inconsistencies between the primary and its fallback because not all inputs may have been applied to the target table.
- Generated By
- STPERE
- For Whom
- User.
- Notes
- In order to be able to release an Mload Apply Phase or Restoration Lock, the table must not have fallback (and non-unique secondary indexes) or the table is empty.
- Remedy
- On systems that do not require always fallback, drop the fallback table; otherwise, delete all rows, drop the table or copy the contents to another table. Then, run the RELEASE MLOAD again. Once the table is fully available, it may be desirable to rerun the Mload job; but many Mload jobs should NOT be rerun, as rerunning them would violate logical data integrity. If the table must be abandoned, either drop or delete, and then regenerate the table or restore the table from backups.