Home Page for the TeradataForum
 
https:

Archives of the TeradataForum

Message Posted: Mon, 06 Sep 2016 @ 00:32:42 GMT


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


Subj:   Re: Mload lock release automation
 
From:   Anomy Anom

<-- Anonymously Posted: Monday, September 05, 2016 19:18 -->

As other posters suggested, the preference should always be to restart from checkpoint, but if that's not possible due to how the ETL tool uses TPTAPI:

- See if log / work / error tables exist from prior run

- If so, attempt RELEASE MLOAD

- If that succeeds, or if it tells you MLOAD not active, drop the log / work / error tables

A Stored Procedure can help with the above

- If RELEASE MLOAD fails, get a human involved to look more closely

- NEVER automate RELEASE MLOAD IN APPLY



     
  <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: 24 Jul 2020