is there a way to have the client get an SQL error instead of beeing suspended when the database is full?
For a specific application I need to continue even in case the database is full. But at the moment the database suspends the task serving the connection so that the SQL command blocks. Here is an excerpt from my knldiag:
2003-12-15 11:25:44 17161 WNG 39 Converte DB FULL(FBM): Task 47 suspended (22 pages changed 24554 blocks occupied 1046 blocks available)
I am looking for a connection property (I am using JDBC) or something the like, which can be set so that the SQL statement produces an error upon execution. Is there anything the like?
BTW: I am using SAP DB 7.4.3.27 on Linux Kernel 2.4.22.
I experience similar behaviour when the database's logs are full and not yet archived: the SQL connection blocks until that issue is solved. Is there a way to make the SQL command execution non blocking for this too?
Kind regards,
Torsten
-- Torsten Nitschke (geb. Hentschel) Team Lead Software Development
AuthentiDate International AG Grossenbaumer Weg 6 40472 Duesseldorf Phone : +49 (0)211 43 69 89 63 Fax : +49 (0)211 43 69 89 19
Erfahren Sie mehr unter: www.authentidate.de
Oder beim Enterprise Signature Day 11. Maerz 2004, Duesseldorf www.enterprise-signature-day.de
-- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
