Niall, thanks for the info. I wonder if a backport request of the fix to a 10.1.x patch by lots of users might speed things along? (like, dozens). I could get requests in from 5 CSIs as a "migration concern", or we just plain hold off on upgrades from 9.2 to 10.1 and wait for 10.2 + the first main patchset. Guess that means that I'll have to take a look at the 9.2.0.6 patchset. I had hoped to ignore it, stay on 9.2.0.5.3 and move to 10.1.0.3 instead. We'll see what patchsets Oracle announces on 18-Jan. Paul On Sat, 15 Jan 2005 15:55:17 +0000, Niall Litchfield <niall.litchfield@xxxxxxxxx> wrote: > It is bug 3615505 but not fixed in 10.1.0.3 as I suggested but - > ludicrously in my view - slated for 10.2. I bet if they were filling > up syslog with archiving completed successfully messages there would > be a patch by now. > > > -- > Niall Litchfield > Oracle DBA > http://www.niall.litchfield.dial.pipex.com > -- //www.freelists.org/webpage/oracle-l