Database Administration (MOSC)

MOSC Banner

How to identify "bad" index after analyze table validate structure cascade - from rdba or seg/obj.

edited Nov 15, 2012 10:33PM in Database Administration (MOSC) 4 comments
RDBMS Version: 10.2.0.4
Operating System and Version : Linux x86_64

After running 'analyze table <TABLE_NAME>  validate structure cascade online, a trace file showed:

row not found in index tsn: 20 rdba: 0x0500428c
env: (scn: 0x0006.8098c3d5 xid: 0x0013.002.00067ca1 uba: 0x0114f97a.e761.33 statement num=0 parent xid: xid: 0x0000.000.00000000 scn: 0x0006.63cdc395 8sch: scn: 0x0000.00000000)
col 0; len 3; (3): c2 30 5e
col 1; len 6; (6): 04 04 ea d5 00 1d
Block header dump: 0x0404ead5
Object id on Block? Y
seg/obj: 0x1441f csc: 0x06.8098c3ed itc: 10 flg: E typ: 1 - DATA
brn: 0 bdba: 0x404e08b ver: 0x01 opc: 0
inc: 0 exflg: 0

How can this be translated to find out which index is affected?  I've been given several suggestions by people, but none actually do this.  For example:

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center