**important _disable_logging is an advanced parameter and you should not be set** Hi please, in my test of upgrades I was using _disable_logging, to understand how it works. I had to do an upgrade from 9.2 to 9.2.0.4 to 10.2.
I'm not thinking in use on production. I only want to understand it.
I enabled it in the upgrade process and disable after the next upgrade step. Every thing was ok. Finally once migrated having _disable_logging=false I run a long script which run correctly and at the end of the script, I suppose in the moment of a logswitch, I got the following error:
ORA-00354: corrupt redo log block header ORA-00353: log corruption near block 2 change 105990334 time 05/11/2006 09:06:19 ORA-00312: online log 2 thread 1: 'E:\ORASERP\LOGFILES\LOG_2SERP.ORA' ORA-00312: online log 2 thread 1: 'D:\ORASERP\LOGFILES\LOG_2SERP.ORA'
I tried an ALTER DATABASE CLEAR UNARCHIVED LOGFILE 'E:\ORASERP\LOGFILES\LOG_2SERP.ORA'; and I received a message the file don't exists
Why does it happen? I suppose if I would had done an ALTER SYSTEM SWITCH LOGFILE; or an ALTER DATABASE CLEAR UNARCHIVED LOGFILE 'E:\ORASERP\LOGFILES\LOG_2SERP.ORA'; In some moment, this problem wouldn't had happen.
But I can't get it, why if everything was ok, in the moment of switch it get an error log corrupt.
Thank you :) -- Oracle Certified Profesional 9i 10g Orace Certified Professional Developer 6i
8 years of experience in Oracle 7,8i,9i,10g and developer 6i -- //www.freelists.org/webpage/oracle-l