 |
 |
Archives of the TeradataForum
Message Posted: Fri, 30 Jun 2000 @ 15:57:33 GMT
Subj: | | Mload Restart |
|
From: | | Jeremy Christiansen |
This is rather embarrassing. I have an aborted mload in the application phase. The log table, work table, and error tables no longer
exist. Is there still a way to release the mload? (Of course the "release mload" command will not work in this situation.) I have no
concern regarding the possible corruption of my table. I know that the Mload did nothing to my table during its execution, it merely threw
some rows into an error table. So as long as I can release the mload I will be okay. I am looking for a quick fix here, I know that I can
drop the table and rebuild it, but that will take awhile.
| |