Home Page for the TeradataForum
 

Archives of the TeradataForum

Message Posted: Tue, 31 Aug 2010 @ 11:39:26 GMT


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


Subj:   Re: ETL jobs get aborted due to deadlock issue
 
From:   Shindhe, Naveen

Thank you for the replies.

The ETL jobs were trying to Insert the sQL query.

We do have around 30 sequencers for different countries, all are running under 1 user id ETLPROD.

Do you mean to say we should have different ids like ETLPROD_IN, ETLPROD_USA i.,e 30 times.

Below is the show table

     CREATE SET TABLE position_upd ,NO FALLBACK ,
          NO BEFORE JOURNAL,
          NO AFTER JOURNAL,
          CHECKSUM = DEFAULT
          (
           position_ID INTEGER NOT NULL,
           position_CD CHAR(10) CHARACTER SET LATIN NOT CASESPECIFIC NOT NULL,
           position_NAME VARCHAR(100) CHARACTER SET LATIN NOT CASESPECIFIC,
           PARENT_position_ID INTEGER,
           position_TYPE_CD CHAR(4) CHARACTER SET LATIN NOT CASESPECIFIC NOT NULL,
           INSERT_ID INTEGER,
           UPDATE_ID INTEGER)
     UNIQUE PRIMARY INDEX ( position_ID );

and below is the query which is used for insert in the ETL jobs

     INSERT INTO position_UPD
               (UPDATE_ID,
                position_NAME ,
                position_TYPE_CD ,
                position_ID,
                position_Cd)
            VALUES
               (ORCHESTRATE.Process_id ,
                ORCHESTRATE.F_NAME,
                ORCHESTRATE.DESC_GRP_NAME,
                ORCHESTRATE.position_ID,
                ORCHESTRATE.position_Cd)

Can we change anything in the table or query.


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