Home Page for the TeradataForum
 

Archives of the TeradataForum

Message Posted: Fri, 16 Aug 2002 @ 20:27:40 GMT


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


Subj:   Re: RELEASE LOCK command error
 
From:   Anomy Anom

<-- Anonymously Posted: Friday, August 16, 2002 16:18 -->

The format of the RELEASE LOCK statement depends on whether you're using BTEQ or ARCMAIN to do the release lock. ARCMAIN wants ()'s and BTEQ doesn't. The options mentioned:

(1) ALL applies to releasing the locks on all amps - especially useful when amps are down (otherwise the lock is reapplied when the amp comes up)

(2) OVERRIDE applies to situations where the user releasing the lock is not the same as the user that applied the lock


The only purpose of a RELEASE LOCK is to release an ARCMAIN ("HUT") lock that was created by an ARCMAIN job. Note: ARCMAIN was originally HUTMAIN, where HUT stood for "host utility". You can see HUT locks with a showlocks, which you can run from the console or else from "HUTCNS" on the mainframe.

Fastload is another thing all together. Why did the fastload fail? If you know what the problem was, then dropping and recreating the target table and rerunning the job will work. If you hit the error limit and the job didn't complete, you might want to rerun the job without an error limit. If there are lots of records you might want to use a subset of the data. It depends whether all records failed or not.



     
  <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