Has anyone ever encountered this where in a Win NT/2k environment, if a
datafile is resized or autoextends to a 4Gb boundary and the database is in
archivelog mode, the file is marked offline and the only fix is to perform a
complete restore of the database rolling forward until a point in time prior
to the extension of the datafile. Especially in 9i?



I mean what does that mean exactly. I've had several other datafiles extend
beyond that boundary some time back and never encountered it, until recently
for one datafile. And when I was able to recover the datafile, I started
inserting to tables, where the datafile is now beyond that point.



//a



Oracle LazyDBA home page