This content has been marked as final. Show 2 replies
We had the same some time ago, not sure how we fixed it, but I think it had something to do with the Oracle JDBC-Driver (we use odbc14-10g.jar).
There was a bug in the first 10g Oracle JDBC driver. Fixed in the latest version!