Home Page for the TeradataForum

Archives of the TeradataForum

Message Posted: Sun, 09 Jan 2005 @ 21:53:03 GMT

  <Prev Next>   <<First <Prev

Subj:   Re: Geting the database name by using SQL which is locked by a failed backup job
From:   Prabhjot Sodhi


The methodology of dynamically releasing locks based on requirement seems good, but why don't you have a release lock at the end of the archive/backup job to release all jobs irrespective of the return status code (Error/warning/success).

At our site we have a release lock step, which is called irrespective of the job status. The only problem is if the TDP loses connection, but in that case you have many more things to worry than releasing arcmain job locks.

This also helps us automate and make the system running, in case of a job failure for media errors. The overnight support team, just runs the RELEASE lock step and re-start the back up again. The only problem is that we lose a couple of additional tapes. But that is still better than having a sleepless night!!!

Thanks & Regards,


  <Prev Next>   <<First <Prev
  Top Home Privacy Feedback  
Copyright for the TeradataForum (TDATA-L), Manta BlueSky    
Copyright 2016 - All Rights Reserved    
Last Modified: 15 Jun 2023