Home Page for the TeradataForum
 

Archives of the TeradataForum

Message Posted: Mon, 10 Mar 2003 @ 11:00:03 GMT


     
  <Prev Next>   <<First <Prev
Next>
Last>>
 


Subj:   Re: Identifying MLOAD Failures
 
From:   Julie Flanagan

Hi,

I attach sample script we use in all jobs before Multiloading which automates the release multiload process, if it is needed.

- It firstly checks for the existence of Log, Work, ET or UV tables in dbc.tables.

- If none are found, we skip the remainder of the code and go straight to the Multiload script.

- If any of them ARE found, we know the previous Multiload is incomplete. - We do not know yet whether it was in the Acquisition or Application phase.

By running the Release Multiload command, you will know by the Errorcode what state your multiload was in:

2572 - Table can't be released - was in application phase and Mload must be restarted.

0000 - Valid release. There was a previous Mload that failed in Acquisition phase.


Hope this is of some help. Julie.



     
  <Prev Next>   <<First <Prev
Next>
Last>>
 
 
 
 
 
 
 
 
 
  
  Top Home Privacy Feedback  
 
 
Copyright for the TeradataForum (TDATA-L), Manta BlueSky    
Copyright 2016 - All Rights Reserved    
Last Modified: 27 Dec 2016