Home Page for the TeradataForum

Archives of the TeradataForum

Message Posted: Tue, 01 Jan 2002 @ 12:05:07 GMT

  <Prev Next>   <<First <Prev

Subj:   Re: Identifying row failed in CHECKTABLE
From:   Dennis Calkins

"CORPDBP2"."PROVGACT4T" starting at 14:27:06 01/11/05.
  Table id 0007H EE70H, Fallback.
    2764: Data row not indexed by USI.
          Data AMP 00010, Primary Data subtable
          USI id 4
          Data row id 96C4H 793BH 0000H 0001H
  1 error(s) reported.


From a Support point of view this error means the secondary index is corrupted. The recommended fix is to Drop and recreate the secondary index since there is no other way to fix this without losing data from the base table which isn't acceptable.

ths USI id 4 means it is the First Secondary index on the table since index tables have subtable ids in multiples of 4. (the primary index ID is 0 ).

therefore if you do a


and look at the indexes at the end of the display you should be able to figure out which is the first secondary index.

Drop it and recreate it.

As for trying to figure out why the index is corrupted, I guess if you could identify when the row was added (Maybe that is why you posted this question) you might be able to identify a CRASH or a Disk array event which could explain the corruption.

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