Teradata Database Message 7447 - 7447 - Analytics Database - Teradata Vantage
Analytics Database Messages
- Deployment
- VantageCloud
- VantageCore
- Edition
- Enterprise
- IntelliFlex
- VMware
- Product
- Analytics Database
- Teradata Vantage
- Release Number
- 15.xx,16.xx,17.xx
- Published
- June 2022
- ft:locale
- en-US
- ft:lastEdition
- 2023-01-05
- dita:mapPath
- sfx1628096178347.ditamap
- dita:ditavalPath
- ft:empty
- dita:id
- B035-1096
- lifecycle
- latest
- Product Category
- Teradata Vantage™
- Message
- Mload table %TVMID cannot be released because fallback and NUSI exist.
- Explanation
- The user attempted to release an Mload Apply Phase or Restoration Lock on a table that has both fallback and non- unique secondary indexes. 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 and non-unique secondary indexes 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
- Drop the fallback and all non-unique secondary indexes and run the RELEASE MLOAD again. Alternatively, delete all rows or drop the table. 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.