Home Page for the TeradataForum
 

Archives of the TeradataForum

Message Posted: Mon, 05 Mar 2007 @ 21:33:02 GMT


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


Subj:   Re: Release locks left by failed backup
 
From:   Mann, Shari

Charles,

As you have found, ARC does not automatically release locks if the job is cancelled or fails. The leftover HUT locks can be seen using the ShowLocks utility. This utility will show you what databases have HUT locks remaining. If there are no other ARC jobs running, these locks can be cancelled using the RELEASE LOCKS command via bteq.

The ARC Recovery manual provides the following warning regarding possible corruption:

Warning: Releasing a lock while another Teradata ARC job is running could result in data corruption and/or unexpected errors from ARCMAIN or the DBS.


If you have MultiLoads running at the same time, I would use Teradata Manager to see if any MLOAD processes are blocked. Since MLOAD can't attain its lock if ARC has the database locked, it will wait until the ARC lock is released. Once you manually release the ARC locks, the MLOAD will kickoff. I can't think of a situation where releasing HUT locks would cause adverse affects to MLOAD.

I hope this helps a little.


Good luck.

Shari

Shari Mann
Teradata Certified Master V2R5
AF-Tech Support Montgomery



     
  <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: 15 Jun 2023