Any ideas what might be causing this?
There is a much earlier post for ver 3.0 of SQL Dev that points to the possibility that the following command should be added to the conf file
Is this needed in 3.2.2?
It certainly couldn't hurt to try, especially if your client OS is Windows, your database is configured as shared_server rather than dedicated, and so on as you can read about in older threads on this forum.
It also probably depends on the version of your JDBC driver. Prior to SQL Developer 4.0, the product will use the JDBC driver in your Oracle home, if any. Otherwise it uses the JDBC driver it ships with (22.214.171.124, I believe), or perhaps the one you may have replaced it with in your installation's sqldeveloper\jdbc\lib directory. The 4.0 EA's ship with the same version and are hard-wired to use only that directory location.
Supposedly 4.0 production will contain a JDBC driver selector UI.
Hope this helps,
SQL Developer Team
Is there a way to force/point ver 3.2.2 to use the jdbc driver that it comes with? Maybe 3.2.2 is picking up another jdbc driver on the client PC.
There was no changes made to the SQL Dev setup. It was downloaded from OTN, unzipped and then used. So we didn't change the jdbc driver.