1 person found this helpful
This is a known issue with 4.2EA; probably solved in a later release candidate. No such problem with 4.1.3 which I am using.
Is the defect system publicly visible?
Rolling back, and putting a watch on it.
Defects against an Early Adopter (EA) version reported here may or may not get logged formally as bugs in Oracle's bug database. Even when logged, such internal bugs will not be "published" for viewing by customers contracted with Oracle Support.
Typical practice with SQL Developer is to post a couple EA versions prior to the production release, usually spaced several months apart. So do keep a watch out here for the EA2 version.