"Schaefer, Peter" wrote: > > Hi! > > > I have run into a problem with SAP DB: when the database is full > > (according to the knldiag log file), commands executed against > > the database simply hang and never return. I would have expected > > a clean error message in this case. > > It's not a bug, it's actually a feature. Your client application > doesn't "hang" it just waits till you, the operator, appends more > devspace to the database using dbmcli. > > If you've done this - voila - your client applications continue > working.
That's nice, but how will the admin notice ? I'd like to able to at least send out an email... currently the client application simply runs into a timeout and all transaction data is lost -- that's not exactly high availability ;-) > Search the mailing list - this was discussed many times. Sorry, I wasn't aware of this. > > Obviously, this poses a major problem for 24/7 high availability > > applications, so my question is whether I could implement some > > regular check on the current fill state of the database. > > I don't think so. I really appreciate that behaviour. > > > Is there some SQL statement I could execute to get the current > > database fill state ? > > Dunno. Perhaps some SAPDB people can help here? Hope so too. Thanks, -- Marc-Andre Lemburg CEO eGenix.com Software GmbH ______________________________________________________________________ Company & Consulting: http://www.egenix.com/ Python Software: http://www.egenix.com/files/python/ _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
