Emil Jennings wrote:The code is basically:
Basically, but not exactly, right? For example, the
cs.close() and
conn.close() statements in the finally clause throw
SQLException, but it is neither caught nor declared. So, this is not the code you're actually running. And until we see the full code (including how you handle these exceptions), I'm not convinced there are no other exceptions thrown by your code. Remember, the devil is in the detail.
Just to clarify: I tend to believe there's something wrong with your code, rather than assume it is Oracle's problem. The best you could do in this situation would be to create a
SSCCE that everybody (everybody with Oracle) could run to see the problem. It is very probable that in the process of creating the SSCCE (which, admittedly, can be a time consuming task) you'll discover the error.