2 Replies Latest reply on Jun 16, 2014 2:54 PM by Gary Graham-Oracle

    get java.lang.NullPointerException on connecting to database from sql developer 4




      I installed sql developer (  sqldeveloper- ) including jre version, imported definitions from previous version

      Start sqldeveloper and get next error on connecting to DB ( worked well on previous 401 version )

      What is the problem ?


          at oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:1189)

          at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1289)

          at oracle.jdbc.driver.OracleStatement.executeInternal(OracleStatement.java:1909)

          at oracle.jdbc.driver.OracleStatement.execute(OracleStatement.java:1871)

          at oracle.jdbc.driver.OracleStatementWrapper.execute(OracleStatementWrapper.java:318)

          at oracle.dbtools.db.DBUtil.hasAccess(DBUtil.java:1817)

          at oracle.dbtools.raptor.query.QueryUtils.checkNonOracleAccess(QueryUtils.java:506)

          at oracle.dbtools.raptor.query.QueryUtils.getQuery(QueryUtils.java:337)

          at oracle.dbtools.raptor.query.QueryUtils.getQuery(QueryUtils.java:242)

          at oracle.dbtools.raptor.query.ObjectQueries.getQuery(ObjectQueries.java:42)

          at oracle.dbtools.raptor.navigator.db.xml.XmlObjectFactory.createFolderInstance(XmlObjectFactory.java:49)

          at oracle.dbtools.raptor.navigator.db.xml.XmlTypeOwnerInstance.listTypeFolders(XmlTypeOwnerInstance.java:93)

          at oracle.dbtools.raptor.navigator.db.impl.TypeContainerTreeNode.loadTypeFolders(TypeContainerTreeNode.java:111)

          at oracle.dbtools.raptor.navigator.db.impl.DatabaseTreeNode$LoadTask.doWork(DatabaseTreeNode.java:184)

          at oracle.dbtools.raptor.navigator.db.impl.DatabaseTreeNode$LoadTask.doWork(DatabaseTreeNode.java:112)

          at oracle.dbtools.raptor.backgroundTask.RaptorTask.call(RaptorTask.java:193)

          at java.util.concurrent.FutureTask.run(FutureTask.java:262)

          at oracle.dbtools.raptor.backgroundTask.RaptorTaskManager$RaptorFutureTask.run(RaptorTaskManager.java:554)

          at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)

          at java.util.concurrent.FutureTask.run(FutureTask.java:262)

          at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)

          at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)

          at java.lang.Thread.run(Thread.java:745)

        • 1. Re: get java.lang.NullPointerException on connecting to database from sql developer 4

          Was it 'installed' into a new folder? Or into the same folder a previous version was in?


          Was the previous version a 32 bit version? Do you now have both 32 bit and 64 bit versions in your environment variables (e.g. PATH)?


          Could you be mixing 32/64 bit modules?

          • 2. Re: get java.lang.NullPointerException on connecting to database from sql developer 4
            Gary Graham-Oracle

            As a first step, you need to make sure the 4.0.2 install is correct and there was no issue with the user settings migration from 4.0.1.  Did you...

            1. Install 4.0.2, into an empty folder?  Never unzip into an prior installation's folder!

            2. Download and install  latest jdk1.7.0_xx update?  (If not using Windows 64-bit zip download which already includes a recent JDK 7). 

            3. Try not migrating user settings from a prior installation?

            If you suspect user settings corruption, upon first-time launch after upgrade, do NOT migrate user settings.  If you already migrated, try renaming or deleting these folders (assuming your platform is Windows), then relaunch without user settings migration...

            1. %APPDATA%\SQL Developer\system4.

            2. %APPDATA%\sqldeveloper

            In fact, adjusted for the specific system<n.n.n.n.n> folder, this step is the "gold standard" for verifying user settings corruption is not the problem.  It also helps ensure SQL Developer is not pointing to some older JDK still installed on the machine.




            SQL Developer Team