[ binlogs and full disk scenario ]
Starting with 4.1.9 full disk scenarios have been improved by pausing all query threads, until some drive space is freed up. This is a great improvement since no data is lost as in previous versions, but it does prevent the database from being updated even when the binlogs are on a seperate drive, and it's only the binlog drive that has run out of space.
Does anyone know how to keep the database from being effected negatively when a binlog drive fills up?
It would be nice to have the ability to toggle the binlog option on the fly, while the database is still up and running instead of just a startup option.
Subject
Views
Written By
Posted
[ binlogs and full disk scenario ]
3152
May 04, 2005 09:46AM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.