Quantcast
Channel: Teradata Forums - All forums
Viewing all articles
Browse latest Browse all 27759

Mload table locks cannot be released because NUSI exists - response (1) by feinholz

$
0
0
According to the DBS engineer: Here is the explanation of error 7446. We process the primary data, the fallback data, and the NUSI data separately in the application phase. If there is an abort during this phase, the data between these sub-tables can be inconsistent. Allowing a ‘release mload’ to run can cause data integrity issue. The user should normally choose to restart and let the job complete. If for some reason, that cannot be done, it is required to drop any NUSI and fallback. Explanation: The user attempted to release an Mload Apply Phase or Restoration Lock on a table that has 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 non-unique secondary indexes because not all inputs may have been applied to the target table.

Viewing all articles
Browse latest Browse all 27759

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>