> Thanks. Roman replied that it's a known bug. Now I have to try to
> come up with a test case, if it's even possible.

That's not 100% correct. So far I cannot confirm this bug when using a
CallableStatement and I do not see how it can happen. I was able to
reproduce it when using PreparedStatement with the {?= call ...} syntax. If
that's your case, please fill a bug report, so it is not forgotten.

Roman