Prem
It is possible that you have some corruption in your table. My advice
would be to immediately export the table. If there is any corruption on the
table, this will find it. If no corruption is reported, you will have a good
copy of your table to proceed with. If corruption is
Title: RE: how to find INDEX CORRUPTION ???
analyze table MSG_HISTORY validate structure cascade;
If there is a problem with the table or any indexes, you should receive an error message. Rebuild that object.
Validating the structure of the table locks it up so don't do this while anyone
Drop the index and recreate it without parallel clause. If your table is
having degree 1 , then make it 1 and then recreate index. It looks a old
bug for bitmap index on a table having degree 1.
Regards
Rafiq
Reply-To: [EMAIL PROTECTED]
To: Multiple recipients of list ORACLE-L [EMAIL
Thans Rafiq.
The degree for the table is 1.
SQL create index idx_mh_frommemno on msg_history ( frommemno );
this is what i did ?
either it's a bitmap or b-tree on this column (only) , it results in ORA-600.
i wonder why it happens so ?!
any clue !!
thanx once again.
Jp.
2003/04/03
Have you analyzed table msg_history with cascade structure option? do you
find any message in alert_log for any possible corruption. You index is
b-tree index as per syntax
Regards
Rafiq
Reply-To: [EMAIL PROTECTED]
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
Date: Wed,
