This content has been marked as final. Show 1 reply
I haven't heard of that behavior before, particularly with respect to simple user error. In terms of the SDU mismatch, the following link (and the link it references) discussion the possibility the JDBC driver may be at fault:
SQL Developer 3.2 - Connection reset
Unfortunately the original poster on that thread never said whether the information was helpful. If it doesn't help you -- since upgrading to 3.1.07.42 started the problem -- you may wish to either:
1. Revert to the earlier SQL Developer release, if it remains as trouble-free as before, or
2. Upgrade to the newest 3.2 release.
SQL Developer Team