1 person found this helpful
Given the following facts, I would guess this may be a side-effect of cleaning up code referencing RDBMS versions past their extended support end dates:
1. Oracle 9.2 extended support ended July 2010.
2. Database test instances readily available to SQL Developer Dev and QA groups currently include 10gR2 through 12cR1.
3. Backward compatibility of current JDBC driver versions becomes more and more problematic when using RDBMS releases early than current - 2 (12 - 2 = 10).
You may well be stuck at SQL Developer 3.2.2 for the operations against the 9i instance.
SQL Developer Team