[750]: Too many SQL statements (work rolled back)

[Former Member]

Hello all,

While executing a batch-job that takes around 20 hours and highly interacts with a MaxDB instance, the batch job failed to execute a select query after around 19 hours with the following exception:

[750]: Too many SQL statements (work rolled back)

(We use MaxDB Server Version 7.6.3.15 on RedHat Linux.)

The statement is a simple select statement that is newly created for each query sent to the database, so it's not a prepared statement (which would be the better solution for that batch-job, of course).

I found that the same error was obviously a problem in older versions (up to version 7.3.0.6), as can be read here:

http://lists.mysql.com/maxdb/1093

http://lists.mysql.com/maxdb/1599

It seems to be the 'several millions'-problem again, or is that caused by another reason?

Thank you for any comment on this.

Gabriel Matter

[Former Member]

Hallo,

you are right, it seems to be the same topic.

Is it possible that monitoring is switched on in your context?

To explain: if monitoring is not switched on, those statement-numbers may be recycled after some time, but in case monitoring is switched on, this is not allowed and this error may occur.

Elke

[Former Member]

Hello Elke

Thank you. In dbstudio we found the options

Command Monitor: OFF and

Resource Monitor: OFF

which are both turned off.

Or do you mean another monitoring mode?

Thank you,

Gabriel