Hi all!
Just a warning for those of you running Oracle on NT.
There's an extremely nasty bug specific to 8.1.6/8.1.7
on NT/Win2K (not sure if it affects 8.1.5) where a
datafile that is resize or autoextended exactly on a
4GB boundary cannot be resized. Bug 1668488.
Options:
1. PITR prior to when the datafile extended
2. Force the db open (requires full db export and
rebuild).
3. Clone a subset of the db containing the corrupted
datafile(s), force it open, export affected
tablespaces and import them into the original db.
4. Drop the corrupted datafiles to open the db and
then drop the tablespace to which the datafiles
belong.
Options 2 & 3 can result in logical corruption as
there's no way to rollback any uncommitted
transactions that have already been forced to disk.
Bug is not fixed in 8.1.6; it's scheduled for the
8.1.7.2 patchset.
Those of you with autoextend on your datafiles should
modify the maxsize to be less than 4GB or turn off
autoextend.
HTH,
-- Anita
__________________________________________________
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail - only $35
a year! http://personal.mail.yahoo.com/
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: A. Bardeen
INET: [EMAIL PROTECTED]
Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051
San Diego, California -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from). You may
also send the HELP command for other information (like subscribing).
