can you pleae help me below.
We are facing an issue while selecting a rows from bcp_ca_drt.CON_HIS_APP table. The issue is being faced as the table is ‘Fallback’, and got error out during mload process. Also, to avoid such a situation, we are trying to create a table with ‘no fallback’ option, but the system is creating table with ‘fallback’ only.
I have tried releasing the table using
But both statement has not helped.
While executing the ‘Release mload bcp_ca_drt.CON_HIS_APP in apply;’ statement, Teradata shows error ‘Release Failed 7445: Mload table cannot be released because fallback exists.
can you please what is the solution? it's bit urgent ,
7445 Mload table %TVMID cannot be released because fallback exists.
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: Drop the fallback table 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.
In this situation, RELEASE MLOAD IN APPLY can't remove the application lock but will change it to a restoration lock.
Create a new table, and use a SELECT with an ACCESS lock to copy the (partially updated) rows; then DROP the old table.
You could also DELETE ALL from the table and do RELEASE MLOAD IN APPLY again to make the original table usable (though empty).
For future consideration: If RELEASE MLOAD fails, you should restart and allow the apply phase to complete if possible.
Don't drop log / work / error tables unless the RELEASE worked.
RELEASE MLOAD IN APPLY has always been a last resort, and is even more limited on newer systems where fallback is mandatory and can't be eliminated.
Please ignore the below, I just re-read the comment from @dnoeth to "restore the table from backups". Thanks.
Would it be ok (considering Fallback) to restore to a previous state, before mload failure using DSA? Or you think it can still cause issues? and dropping and re-creating is better solution?