4 Replies Latest reply on Aug 5, 2015 3:15 PM by KarstenH-dk

    Sqldev 4.1 and password expiration  inappropriateness

    KarstenH-dk

      Hi

       

      We are using password expiration.

       

      When sqldev 4.1 is facing the expiration-time within 10 days, it reponds with a stack of  warning/alert-boxes (20-30) which I have to accept or click-down before the real warning/alert shows

       

      pwdexp.jpg

      the real warning/alert

       

      expwarn.jpg

       

       

       

      After this I am connected

       

      regards Karsten

        • 1. Re: Sqldev 4.1 and password expiration  inappropriateness
          John McGinnis-Oracle

          Can you click the Details button and see what the stack trace that is being reported looks like?

           

          - John

          SQL Developer Team

          • 2. Re: Sqldev 4.1 and password expiration  inappropriateness
            KarstenH-dk

            sure did copy from the first warning they all looks the same

             

            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:2101)

              at oracle.jdbc.driver.T2CConnection.prepareCall(T2CConnection.java:53)

              at oracle.jdbc.driver.PhysicalConnection.prepareCall(PhysicalConnection.java:2039)

              at oracle.jdbc.driver.T2CConnection.prepareCall(T2CConnection.java:53)

              at oracle.jdbc.proxy.oracle$1dbtools$1raptor$1proxy$1driver$1oracle$1RaptorProxyOJDBCConnection$2oracle$1jdbc$1internal$1OracleConnection$$$Proxy.prepareCall(Unknown Source)

              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)

             

            /Karsten

            • 3. Re: Sqldev 4.1 and password expiration  inappropriateness
              John McGinnis-Oracle

              It looks like the error is probably not connected to the password expiration warning. The sequence of dialogs makes it seem like one is triggered by another, but the stack trace seems to indicate an error with one of the checks we do while building the list of supported object types in the tree. The expiration dialog is triggered separately when the database gives us a warning message.

               

              Can you try unexpiring the user's password and then connecting to see if the error dialogs still occur?

               

              - John

              SQL Developer Team

              • 4. Re: Sqldev 4.1 and password expiration  inappropriateness
                KarstenH-dk

                unexpiring the user's password seems to eliminate the error, which is not surprising I would think!


                It seemed to be related to the fact that the password had expired.

                /Karsten