I add more redo log file to my datafiles, and issue the command :ALTER SYSTEM SWITCH LOGFILE ;
and the database crashed with this errors
Errors in file C:\oracle\admin\REVD\bdump\revdLGWR.TRC:
ORA-00321: log 3 of thread 1, cannot update log file header
ORA-00312: online log 3 thread 1: 'C:\ORACLE\ORADATA\REVD\REDO03.LOG'
ORA-27091: skgfqio: unable to queue I/O
OSD-04008: WriteFile() failure, unable to write to file
O/S-Error: (OS 5) Access is denied.
LGWR: terminating instance due to error 321
Somehow, there is a problem with 'C:\ORACLE\ORADATA\REVD\REDO03.LOG'
To fix this problem,
1. startup mount
2. drop logfile group 3
The OS 5 error could indicate that the permissions are not set correctly on this file.
some Backup or antivirus software has locked the file.
Oracle server needs exclusive access to its datafiles.
Disable the file locking in the backup and antivirus
Disable backup and scanning of Oracle datafiles.
To handle yourself, use your head. To handle others, use your heart
Jeff was right, corrupt redo log file.
Can you tell me why the datafile 3 was corrupted??? Was it b/c I issues ALTER SYSTEM SWITCH LOG FILE and not in the restrict mode??? Redo 3 is one of the old redo file and I didn't even touch it.
Ist of all this is a redo log file, not a datafile.
Did the oracle user have write permissions on this file ?
Once you have eliminated all of the impossible,
whatever remains however improbable,
must be true.
the redo3.log was corrupted so you need to start the database in mount stage and drop the corrupted file and start up the database. I hope you have two members in each group.
Could you please explain to me why the redo3.log was corrupted when I issued this command.
'ALTER SYSTEM SWITCH LOGIFLE'
The database already had three logs from 1 to 3 and I add three more log 4 to 6 and issue the command above. All the sudden, the database went down and the redo3.log was corrupted. Why was that ??? I have done couples times by issuing the command above. Am I supposed to put the database in restrict mode ???
What were the parameters used the create the new log groups. Were the sizes of these files the same as the old ones? And if the old ones were mirrored, did you mirroe the new ones also?
Listen, if possible, make a reboot of the system. It isn't so unusual for win2000 (sometimes even NT) to wrongly keep some locks on a file, and untill the system reboots is nothing to do.
A workaround is to force REWRITING the user-rights on that file.
Click Here to Expand Forum to Full Width