Hi,

In a test server we have a corrupt data block in a table that is about
17GB in
size. DBVerify and validate structure both identified the same corrupt
block.
(File#f, block #y). Oracle is 10.2.0.4.

That table has a field named DATE, and there is an index on DATE.

Is there a way to use the index in order to identify the date(s)
of the data that was on the corrupt block?

For example, suppose that DBVerify and Validate Structure
indicate that file#100, block#99999 is corrupt.

Is there a way to check the value of the date field in index TABLE-
DATE
associated with this file/block?



Thanks,
QZ

On Jun 15, 1:39*pm, "if_inves... (AT) yahoo (DOT) com"
<basis_consult... (AT) hotmail (DOT) com> wrote:
Try doing a block dump or use the dd command to look at the data
inside the block.

On Jun 15, 10:39*am, "if_inves... (AT) yahoo (DOT) com"
<basis_consult... (AT) hotmail (DOT) com> wrote:
Richard Foote has an interesting article about ora_hash:
http://richardfoote.wordpress.com/20...ast-slow-burn/

I'm wondering if you could use that method to get the rowid of the
index, then use that rowid as a predicate on a query to see the date
in the index.

Just thinking out loud, of course. At least you could dump the index
block.

Rowid format: http://download.oracle.com/docs/cd/E...l.htm#BABFFFCE

jg
--
@home.com is bogus.
My respect for Symantec has increased:
http://web.signonsandiego.com/news/2...s-way-success/

You have the file number, block number and data object id of the table, so
you can use dbms_rowid to create a rowid for row 0 and row 4095 for that
block, then a query like:

select /*+ index_ffs(alias index) */
rowid,
date_column
from
table
where rowid between {rowid0} and {rowid4095}
and date_column is not null
;

Should do an index fast full scan of the index to return the data.


--
Regards

Jonathan Lewis
http://jonathanlewis.wordpress.com


"if_investor (AT) yahoo (DOT) com" <basis_consultant (AT) hotmail (DOT) com> wrote

On Jun 15, 1:39*pm, "if_inves... (AT) yahoo (DOT) com"
<basis_consult... (AT) hotmail (DOT) com> wrote:

If you have an RMAN backup of this database, you CAN restore just the
bad block.

On Jun 21, 7:19*pm, onedbguru <onedbg... (AT) yahoo (DOT) com> wrote:
.... with the backed up bad block :-O

jg
--
@home.com is bogus.
http://www.nytimes.com/2011/06/22/us/22infosys.html