This content has been marked as final. Show 4 replies
Have you tried using google? Here is the first result where the poster was able to solve his issue:
I don't believe that google hit is going to help this problem...
The first thing to do is to update your driver version to the
latest appropriate jar. It look very much like a driver bug.
I agree it is probably a driver issue. The code works fine most of the time, but when we see this issue it seems to put the majority of db connects in a stale state.
I have read many forums discussing this problem. There were several other possibilities such as an array lenght that is not long enough. But for this case an array is not being used.
It is a big deal for me to update the production driver so I was hoping for proof that this is a known problem for my exact driver version.
Thanks for the advice.
If you're having this problem in SQL Developer specifically, your SQL array fetch size setting may be too large. Check Preferences > Database > Advanced and play with the SQL array fetch size.