Archives of the TeradataForum

Message Posted: Thu, 06 Mar 2003 @ 15:10:03 GMT

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

Hi,

We have experienced the following Deadlock error a number of times recently. Each time, we've been creating temporary tables, none of which are accessed by other jobs - so we assume the deadlock is with a Dictionary table written to during the creation of this table(?)

Can someone confirm this or shed any light on it??

(We've read the manuals, ... we know what deadlock is, etc. etc. - just want to know why we are getting it in this particular instance, or how we can find out).

Thanks, Julie.

 CREATE SET TABLE MLSRDL10_TRAILER_RECON

  ,NO FALLBACK

  ,NO BEFORE JOURNAL

  ,NO AFTER JOURNAL

   (

     SRCE_SYS        SMALLINT                   NOT NULL COMPRESS 14

    ,SRCE_INST       SMALLINT                   NOT NULL COMPRESS 1

    ,PERIOD_DTE      DATE FORMAT 'YYYY-MM-DD'   NOT NULL

    ,TOT_DLY_INT_AMT DECIMAL(18,6)

    ,TOT_RECS        INTEGER                    NOT NULL
    ,LOAD_DTE        DATE FORMAT 'YYYY-MM-DD'   NOT NULL

    ,LOAD_TIME       INTEGER FORMAT '99:99:99'  NOT NULL

    )

  UNIQUE PRIMARY INDEX (PERIOD_DTE);

 21:09:45 UTY1008 RDBMS failure: 2631, Transaction ABORTed due to deadlock.
 21:09:45 UTY1017 Resubmitting the last request because a retryable error occurred
 21:09:47 UTY1016 'CREATE' request successful.

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