When DBC is running dangerously low on space and refusing to insert a row into one of the resource logging tables, the database will eventually stop functioning, as in new logins will be refused and queries running on the system will spool out.
Regular space checks needs to be performed on a system to maintain the system performance. CPU lost can be gained again, but if a system has exhausted space, one way out is to delete some data from that system. So, it is of utmost important that critical tables are regularly backed up, so such space crunch data can be deleted without any implications. When space issues happen, there are only two ways to counter this. First, obviously, is the more time and money-consuming:
- Add space ...
