I'm still running into this '-8000 SERVERDB must be restarted' when updating LONG BYTE through a PreparedStatement. If anybody has any ideas what would cause this message to come up when the serverdb is actually up and running (because subsequent queries work no problem, it's just returned as an error by the current query) I'd be really grateful.
I had a quick look through the source and could see in vpr03.c that this error was given because a returncode of 'DATABASE NOT ACCESSIBLE' must have been in the SQL error struct but without looking too closely (I haven't used C for years) I lose track of why it isn't executing at vpr01EXECSQL.c where the cmd trace is called. Does anyone know whether there's some kind of space I'm exhausting or some workaround? No database messages shed any light at all, it isn't mentioned in KNLDIAG or the like. If I can change some configuration option and fix this it'll help me a lot. Here's my original post: I'm running 7.4.3.32 and inconsistently get '-8000 SERVERDB must be restarted', usually when trying to update or insert with LONG VARCHAR or LONG BYTE. Obviously the server db doesn't need to be restarted because all other queries work fine, and I don't get this consistently. Smaller quantities of data work fine, say if I write 5k it works, but if I write larger amounts, it sometimes doesn't work, but then when I return to smaller quantities it works fine. Sometimes I can write many large pieces of data to it and it will work for several attempts and then stop working. It's almost as if there's an area in the software allocated to this of a fixed size, which is cleaned out periodically (like every few minutes), which, once full, cannot accept any more data. This sounds very much like a configuration option somewhere. Perhaps I have the system misconfigured - I'd be grateful for any advice - searching for this particular message yields nothing in the archives. Many thanks for any light anyone can shed on this! -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
