Home Page for the TeradataForum
 

Archives of the TeradataForum

Message Posted: Mon, 05 Mar 2007 @ 08:01:28 GMT


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


Subj:   Release locks left by failed backup
 
From:   Zhang Charles

Hi all,

We have a situation in Teradata we have to deal with and I'm wondering if you are able to help with advice -

The Teradata backup job sometimes is killed by the operator when it takes too long and could affect the morning's loading process. When the operator kills the backup, there are often some locks still locking the databases, which blocks the multi load jobs. We are required to write a script that can be run by the operator of schedule to run automatically to release the database locks. I have a few of questions -

1. what would happen if the operator accidentally runs the script when the backup is still running? Do it corrupt the backup only or could corrupt the databases involved?

2. what would happen if a multi load job is running to load data to a table in a database and a release database lock command is run against the database?

3. we have a ferret script that can report the diskspace usage like this -

     ------------------------------------------
     output over D:\DBA\Log\packfsp10.out
     enable script
     showspace /s
     packdisk fsp20
     y
     showspace /s
     y
     quit
     EOF
     ------------------------------------------

Can we use a similar script to report databases locks ?


Thanks a lot,

Charles



     
  <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