Home Page for the TeradataForum
 

Archives of the TeradataForum

Message Posted: Wed, 21 Nov 2007 @ 09:20:04 GMT


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


Subj:   LSN Error with MLOAD
 
From:   OmerAl

HI,

We have been facing this issue for more than 2 weeks now and have not been able to resolve it.

Following is the error:

     04:16:36 UTY0817 MultiLoad submitting the following request:
     ET;

     -------------------------------------------------------------
     -                                                           -
     -          MultiLoad Application Phase                      -
     -                                                           -
     -------------------------------------------------------------

     **** 04:16:36 UTY0817 MultiLoad submitting the following request:

     EXEC MLOAD P0_STG_BNKS.MACIS;

     **** 04:18:23 UTY0805 RDBMS failure, 2656: MACIS Load error:
                   bad internal status - LSN not found.


     -------------------------------------------------------------
     -                                                           -
     -          Logoff/Disconnect                                -
     -                                                           -
     -------------------------------------------------------------

     **** 04:18:24 UTY6215 The restart log table has NOT been dropped.
     **** 04:18:24 UTY6212 A successful disconnect was made from the RDBMS.
     **** 04:18:24 UTY2410 Total processor time used = '7.40625 Seconds'

       .       Start : 04:15:38 - SUN NOV 04, 2007
       .       End   : 04:18:24 - SUN NOV 04, 2007
       .       Highest return code encountered = '12'.

The LSN error is becoming a huge problem because it applies a set of rows and fails in the middle. Re-starting does resolve the issue and the job completes but I am not sure what happens in terms of updates i.e. does it update properly. Actually we are invoking MLOAD through INFORMATICA and we had moved the INFORMATICA server to a different location. Since then we have started getting this error. Also, this error only occurs when INFORMATICA production machine invokes MLOAD and not on the INFORMATICA development machine. The Teradata box for both the ETL environments is the same.

This error is very frequent and happens 7-8 times a day. Has anyone come across this before?


Thanks.



     
  <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