Re: Read error in .dbf file on Sun server

1. STOP! dont tinker with the datafiles!!!! Never! You cannot copy existing good datafiles over duff ones to fix problems like that.
2. Log a call with Oracle Support.
3. Do what they tell you!

If it's a production database you cannot afford to tinker until you have logged a call with Oracle
Support. Otherwise you just dig a deeper hole.

Look at any syslog errors on the OS side, it sounds like you have a duff disk.

If you dont have support there are other solutions, like resizing the datafile below the bad spot on the disk, but this is very risky and may not work.

Alun

"Bill Hutchison" <billh_at_gci.net> wrote in message news:3cf6581b.6918338_at_news.gci.net...
> We have a read error which is reported when backing up with BRU,
> however it is apparently beyond the area which is used by Oracle at
> this point. It is the 2nd of two 50MB dbf files which are part of
> tablespace Prestige. I'm wondering if I can do a full export, shut
> down Oracle, rename the bad file to something else, copy the good
> file to the name of the former bad file, start Oracle, import the full
> export, then exclude the renamed bad file from the BRU backup and be
> in good shape.
>
> If that won't work because of internal structures in the .dbf files,
> what would be a better approach?
>
> Thanks!
> Bill Hutchison
> Anchorage Alaska
Received on Fri May 31 2002 - 04:47:57 CDT