-
Analyze ALRT.LOG
Check ALRT.LOG
some contents looks like:
Errors in file: XXX\ora00293.trc
Errors in file: XXX\ora00123.trc
Errors in file: XXX\ora00302.trc
Errors in file: XXX\ora00077.trc
Errors in file: XXX\prodLGWR.trc
ORA-01110: Data file 6:XXXX
ORA-01114: IO Error writing block to file 6 (block #1)
ORA-27072: skgfdisp: I/O error
OSD-04008: WriteFile() Failure, unable to write to file
O/S-Error: (OS 5) Access is denied
Errors in file: XXX\ora00275.trc
I knew the media error occuried that time , And already recovered manually , from those message , Can we get a conclusion what's the cause of this error ?
-
Only thing you can tell from the message is
Oracle was unable to write to that file due to OS error.
It can be OS that locked the file, It can be "permissions" for the file, It can be hardware that caused problem.
Sanjay
-
What are you running?
I've seen this type of error on a Solaris box running Oracle 9.x and Using the Itelligent agent. The dbsnmp process has a memory leak on SOLARIS boes only which gobbles Swap space until it consumes it all... then the server grinds to a halt.
If you are on Solaris, do a top and see how much RES memeory the process is using. It it's using copious amounts, Kill this process to an see if it makes a difference. The process will automatically start after it's killed.
-
-
Oh.. well... I think that shelves the Solaris issue then.
Cheers,
