You have done a lot already. It's clear that some blocks or rows in a block
have a wrong structure.
Can't Oracle Support give you some events to set in init.ora to make an
export that skips the problem blocks?
And then make a hex dump of the skipped blocks. From the dumps you can
manually reconstruct the data, knowing how Oracle stores the different data
types. That's discussed in the Oracle Internals training. Result is a script
with insert into ... values ... statements to get missing data back.
A lot of work but when the data is important....
Hopefully it's only a few blocks. A colleague has done this once when we had
a few real corrupt blocks (it was V6.0.33 if I recall it well).
Martin Dohse <mdohse_at_web.de> schreef in berichtnieuws
3D693DFC.9000500_at_web.de...
| Anton Buijs wrote:
| > Is the database been stopped and started since the problem occurs?
| yes
|
| > a. analyze table X validate structure;
| done - same error; we too did an alter session set events to increase
| the error level, that led us to another inaccessable data block and - by
| examining the trace - to another problem, that we have 'malformed'
| data in some datasets (f.e. we found an attribute containing more bytes
| than it should have or 'corrupted' date strings)
|
| > b. use the dbverify utility for every file the table and its indexes
have
| will be next step at an allready planned downtime- unfortunately
| dbverify on nt is not possible while the datafile is accessed...
|
| martin
|
Received on Sun Aug 25 2002 - 15:54:10 CDT
