DBAsupport.com Forums - Powered by vBulletin
Results 1 to 5 of 5

Thread: Instance terminated due to LGWR error

  1. #1
    Join Date
    Sep 2000



    My Oracle instance dies because of LGWR error. The Alert Log file says that one log file could not be updated due to OS error: Access denied

    I use Oracle 8.1.5 standard edition on Windows NT

    What might be the problem?


  2. #2
    Join Date
    Feb 2001
    I Think that there might be problem in the file permissions for that Alert file because of which it might not be able to update the file.
    It is Also possible that the file might have been moved or corrupted.
    If this is the case a new alert log file might be created in the same destination which will alow the LGWR to update the log file whenever it tries to update the file.
    Please let me know if it helps in solving th problem

  3. #3
    Join Date
    Sep 2000
    I really don't know what might be the problem, since the DB has been started and working fine for more than a month, so there is not problem with the permissions.

    My teory i that maybe Oracle tries to use this file to write log records, but it might be still used by some other Oracle process so the OS (WinNT) does not allow it to be accessed. There was a quite big transaction going on while this happened. (But transactions like that one happened almost every day on this system for a month and it was fine till this happened).

    To solve the problem I dropped that log file (ALTER DATABASE DROP LOGFILE...) and created 8 new logfiles, so thus might prevent overlapping the processes that requuest same log file.

    Maybe is some bug of oracle...maybe it is a Winodws NT bug...

    ******* EXCERPT FROM THE ALERT LOG FILE *****************
    Errors in file D:\Oracle\admin\PROD\bdump\prodLGWR.TRC:
    ORA-00321: log 19 of thread 1, cannot update log file header
    ORA-00312: online log 19 thread 1: 'D:\ORACLE\ORADATA\LOG19.ORA'
    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.

  4. #4
    Join Date
    Oct 2000
    sounds like a corrupt block in the Log file.
    If you still have that file, you may want to run DB Verify to confirm this.

    - Rajeev

  5. #5
    Join Date
    Sep 2000
    So how do I prevent from this happening again? Sgould I use DB Verify on ORA files on regular basis?
    Since DB down time like this is not very acceptable thing :(

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts

Click Here to Expand Forum to Full Width