My Oracle Support Banner

Users unable to view their own DB Objects in SQL Developer 4.0.x & 4.1.x versions (Doc ID 2059545.1)

Last updated on MARCH 09, 2023

Applies to:

Oracle SQL Developer - Version 4.0.3 and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Information in this document applies to any platform.

Symptoms

On : SQL Developer 4.0.3.x.x & 4.1.x.x.x version, Browsing Objects
OS : MS Windows 7 (64 bit)

After switching from Instant Client from 11.2.0.4.0 to 12.1.0.2 and SQL Developer 4.0.3.x.x users are not able to view their own DB objects. When the same users login via SQL*Plus it gives ORA-28011 error and connects to DB.

ERROR
ORA-28011 : The account will expire soon; change your password now
Vendor Code: 28011

 



 

 

 

 

 

 

 

 

 

 

In SQL Developer 4.1.x.x.x you will be able to login fine for the first time. However, Subsequent logins will throw following error & then SQL Developer session hangs.

 

 

 

 

 

 

 

 

 

 

 

If you Click on the 'Details' button you will see the below detailed exception.

java.lang.ArithmeticException: / by zero
at oracle.jdbc.driver.OraclePreparedStatement.<init>(OraclePreparedStatement.java:1387)
at oracle.jdbc.driver.OracleCallableStatement.<init>(OracleCallableStatement.java:102)
at oracle.jdbc.driver.T2CCallableStatement.<init>(T2CCallableStatement.java:110)
at oracle.jdbc.driver.T2CDriverExtension.allocateCallableStatement(T2CDriverExtension.java:96)
at oracle.jdbc.driver.PhysicalConnection.prepareCall(PhysicalConnection.java:2107)
at oracle.jdbc.driver.T2CConnection.prepareCall(T2CConnection.java:53)
at oracle.jdbc.driver.PhysicalConnection.prepareCall(PhysicalConnection.java:2045)
at oracle.jdbc.driver.T2CConnection.prepareCall(T2CConnection.java:53)
at oracle.dbtools.db.OracleUtil.checkAccess(OracleUtil.java:409)
at oracle.dbtools.db.DBUtil.hasAccess(DBUtil.java:1898)
at oracle.dbtools.raptor.query.QueryUtils.checkNonOracleAccess(QueryUtils.java:589)
at oracle.dbtools.raptor.query.QueryUtils.getQuery(QueryUtils.java:399)
at oracle.dbtools.raptor.query.QueryUtils.getQuery(QueryUtils.java:250)
at oracle.dbtools.raptor.query.ObjectQueries.getQuery(ObjectQueries.java:43)
at oracle.dbtools.raptor.navigator.db.xml.XmlObjectFactory.createFolderInstance(XmlObjectFactory.java:60)
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:183)
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:266)
at oracle.dbtools.raptor.backgroundTask.RaptorTaskManager$RaptorFutureTask.run(RaptorTaskManager.java:621)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)

 

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.