Re: 4Gb datafiles & Oracle 8.0.5 on NT4 (sp5 )

There is a bug with Oracle8 on NT involving files over 4Gb. Don't do it. See bug report #711563:

In Oracle8 prior to 8.0.4.3.5, datafile resizing or auto-extension to a size greater than 4 Gb results in a datafile corruption error. Under certain conditions, the database may be unrecoverable and data may be permanently lost. This bug is specific to Oracle on NT only.

Supposedly, this is correct in 8.0.5, but I wouldn't risk it. My rule of thumb on max datafile size is 2Gb.

Regards,
--
David C. Sisk
Need tech info on Oracle? Visit The Unofficial ORACLE on NT site at http://www.ipass.net/~davesisk/oont.htm Like original modern rock? Listen to song samples and buy a CD at http://www.mp3.com/disparityofcult

Jeroen v.d. Goorbergh wrote in message <7qj5tq$d6q_at_romeo.logica.co.uk>...
>Hello everybody,
>
> I experienced some problems with automatic and manual resizing of
>datafiles containing the most important index of my entire database. During
>resizing a file to appox. 4Gb it collapsed from its original size (3.5
Gb)
>to appox. 350Mb!!! Bye, bye index!!! My Alert File didn't offer me any
>helpful clues to what the cause of the problem might have been. It did
>contain a O/S error (:OS 38 Reached end of file) indicating that the
problem
>is probably an NT feature of some kind. I checked the Event Log but saw
>nothing unusual. I called Oracle Support but they couldn't help me either,
>which I found a bit strange. I don't believe were the only one working and
>experiencing problems with large datafiles.
> Am I to understand that NT can't handle files larger than 4Gb? If so,
>what is the maximum filesize I should be aiming for?
>
>Cheers,
>
>Jeroen van der Goorbergh
>
>PS
>For now I recreated (not rebuild!) the index on twelve datafiles (&
>tablespaces) in stead of two datafiles to avoid future problems, assuming
>the problem is caused by the large size of the files.
>
>
Received on Wed Sep 01 1999 - 21:20:38 CDT