Home Page for the TeradataForum
 

Archives of the TeradataForum

Message Posted: Wed, 23 Jul 2003 @ 20:05:35 GMT


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


Subj:   Wacky Mload
 
From:   Greg Bourgoin

We're currently having some sporadic problems with mload, or perhaps more specifically, OLE Load??? That's what I'm trying to find out.

The errors are happening at virtually anytime the mload is running. The only symptoms we're having is that the mload simply dissapears and the batch job (NT) has a return code of -1073741819. In this case the mload is running on our AWS (NT 4) with a source of a remote server running DB2 on AIX and the destination of our v2r4 server.

We're unable to recreate the problem manually. The mload log simply dies in the middle, actually, it dies anywhere in the process with the output showing the above, seamingly meaningless error code. Just want to be able to look for more clues to be able to give NCR more to chew on than 'it just disappears'.

Anyone seen something similar and found a problem with mload, oleload or communication between the two?



     
  <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