Home Page for the TeradataForum
 

Archives of the TeradataForum

Message Posted: Fri, 29 Oct 2010 @ 13:27:40 GMT


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


Subj:   ABORTed due to deadlock issue
 
From:   Shindhe, Naveen

Hi,

We do run the ETL jobs via DataStage, most of the time the job runs successfully, but sometimes job gets aborted with the below reason.

     RDBMS code 2631: Transaction ABORTed due to deadlock.

      INSERT INTO
             TARGET_TABLE (LOCATION_NAME ,LOCATION_TYPE_CD ,LOCATION_ID,
     Location_Cd)
      VALUES
              (ORCHESTRATE.F_NAME,  ORCHESTRATE.DESC_GRP_NAME, ORCHESTRATE.Location_ID,
     ORCHESTRATE.Location_Cd) CREATE SET TABLE TARGET_TABLE ,NO FALLBACK ,
          NO BEFORE JOURNAL,
          NO AFTER JOURNAL,
          CHECKSUM = DEFAULT
          (
           LOCATION_ID INTEGER NOT NULL,
           LOCATION_CD CHAR(10) CHARACTER SET LATIN NOT CASESPECIFIC NOT NULL,
           LOCATION_NAME VARCHAR(100) CHARACTER SET LATIN NOT CASESPECIFIC,
           PARENT_ID INTEGER,
           LOCATION_TYPE_CD CHAR(4) CHARACTER SET LATIN NOT CASESPECIFIC NOT NULL)
     UNIQUE PRIMARY INDEX ( LOCATION_ID );

We do have ETL jobs running parallel, if at a time 5 to 6 jobs run at a time, which INSERT into the same table at a time we do get the deadlock issue.

Any suggestion would be appreciated.


Thank You,



     
  <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