> My Question: how do I detect in a client program that the > JDBC connecction blocks because the database is full > or the log is full and the segments haven't been saved yet? > Do I really have to program an alarm for every SQL statement?
- for log full, the easiest way to prevent this situation is to activate the automatic backups of log segments - a future version of MaxDB will be able to add volumes automatically when a 'database full' situation is detected. Actually, the feature is available, but it isn't documented yet. - The general idea was that database administrators should keep an eye on the size of the database to prevent the 'database full' situation. This can be automated by writing a program that periodically queries the table INFO_STATE. Daniel Dittmar -- Daniel Dittmar SAP Labs Berlin [EMAIL PROTECTED] > Meine Frage ist: Wie kann ich von einem Client aus erkennen, > da� meine > JDBC-Connection "blockt", weil die Datenbank voll ist oder > weil die logs > voll und noch nicht archiviert sind. Mu� ich wirklich bei jedem > SQL-Statement selber einen Alarm programmieren? -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
