SQL0906N while opening cursor

[db2dude]

I am having an issue where I get an SQL0906N while I try to open a
cursor. The error says that the function is disabled due to a prior
error however I am not able to determine what that means.

The cursor does an insert into a table and the 'sql' itself is valid
otherwise the procedure would have errored at the "prepare" part.

Whats more confusing is that this procedure runs just fine on our TESt
environment and only starts misbehaving on the QA.

Any insights on what this could be? Are there any parameters or
registry variables which might be causing this kind of issue ?

The env is DB2 V9.1 FP2 on AIX 5.3 64Bit.

[db2dude]

On Sep 24, 6:33 pm, db2dude <[e-mail]:

I am having an issue where I get an SQL0906N while I try to open a
cursor. The error says that the function is disabled due to a prior
error however I am not able to determine what that means.

The cursor does an insert into a table and the 'sql' itself is valid
otherwise the procedure would have errored at the "prepare" part.

Whats more confusing is that this procedure runs just fine on our TESt
environment and only starts misbehaving on the QA.

Any insights on what this could be? Are there any parameters or
registry variables which might be causing this kind of issue ?

The env is DB2 V9.1 FP2 on AIX 5.3 64Bit.

Turns out the problem was due to DB2_SETUID_COMM_BUFFER registry
variable being set. The resolution was to compile the procedure with
BLOCKING ALL (other option was to unset the registry variable or
increase the aslheap/rqrioblk which we did not try).