Something very strange cropped up recently.
Alert log shows one database hanging as it can't archive:
ORA-19504
ORA-27044
OSD-04008
O/S-Error: There is not enough space on the disk.
Its Windoze 2K.
This happened at 8pm on a Sunday evening at 20:16hrs when the building is empty and I am safely at home :)
90 minutes later the redo log is archived successfully and the database continues on its merry way.
The alert.log shows 90 minutes worth of these errors as it tries to archive sequence # 7708, then suddenly it archives it. I certainly didn't intervene and no-one else in the department says they did ... so i'm a tad perplexed.
A space check on this disk done ten days previously shows 8.36Gb free. (Its only a small system). As part of regular maintenance Support clear out older archived logs so I can't see how many were generated since this last check.
Rather than plough through the alert logs, I thought I'd check v$archived_log. This shows me all the archival activity but only from a point AFTER the archival/space error.
i.e. :
02-Jun - Space check: 8.36Gb free.
12-Jun - archival / space issue
21-Jun - today space check: 5.5Gb free.
The v$archived_log view only has entries after 14 June. The instance was last rebooted on 11th May. What has happened to v$archived_log entries between 11th May and 14 June?
There were no incidents reported by users which is why this has only come to light now. I'm puzzled as to what else could have produced the ORA-19504 other than a full disk, and also what happened to the v$archived_log entries.
Any ideas?
(Its Standard Edition 9.2.0.5)