K
keithg
Guest
(Progress 9.1E database running on Windows Server 2003 R2) We just had a database shut down due to its attempt to write to a full database extent on disk. It was attempting to write to extent file named "D1", but all activity should be written to the latest, variable extent named "D4". The first couple relevant lines in the log file start like this: APW 22:bkioWrite:Unknown O/S error during write APW 22:bkioWrite:Insufficient disk space during write Prior entries in the log file do not seem to indicate anything to be concerned about. They are just notes about users logging in, logging out, etc. Prior to those by 75 minutes is a section saying that an online backup completed successfully. Why would the database attempt writing to an already-full extent file?
Continue reading...
Continue reading...