Re: Question - Cause of DATA BLOCK Corruption?

We have had corruption in data files from disk controller failures, we think.

I did notice that in your trace file, the error occured in the rollback database (by file name). If it was in a rollback segment, then if the segment collapsed back to its optimal length (check the storage parms), then the exports, etc will run fine. If it is a disk corrupt area, you won't find it untill a rollback segment tries to use it again.

In article <6oj1to$kdo$1_at_flood.xnet.com>,   jjy_at_xnet.com wrote:
> In comp.databases.oracle.misc "John P. Higgins" <jh33378_at_deere.com> writes:
> : You said Oracle's directories are NFS mounted -- did this include the
> : corrupted file?
> :
> : We NFS mounted data files on a development system some years back. Worked
> : fine until one day corruption happened. That was when I found out the
> : Oracle does not support this!
> :
>
> Sorry.
>
> I should clarify: The files reside on the same machine as the RDBMS.
> That is, no NFS to access any Oracle data files.
>
> However, the directories themselves are exported so that other machines
> can "see" them. But our application only talks to the DB via Pro*C code
> which then uses the files. That aspect is local. I believe this probably
> isn't a problem, right?
>
> So the real question is: Is there a problem with exporting filesystems
> even if the .dbf files are not touched that way?
>
> Jim
>

-----== Posted via Deja News, The Leader in Internet Discussion ==----- http://www.dejanews.com/rg_mkgrp.xp Create Your Own Free Member Forum Received on Thu Jul 16 1998 - 00:00:00 CDT