Announcement

Collapse
No announcement yet.

java.sql.SQLException: ORA-28112

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
  • #1

    java.sql.SQLException: ORA-28112

    Hi All,

    We are getting this exception when we login into OTM application.

    java.sql.SQLException: ORA-28112: failed to execute policy function

    Kindly advice if there is any solution available to resolve this issue.

    Thanks,
    Karthik.
    Tags: javasqlsqlexception, ora
  • #2
    Re: java.sql.SQLException: ORA-28112

    Is this part of a new install? Have you ran all of the post migration scripts? Did you also enable all of the Oracle parameters as per the admin guide?
    If my post was helpful please click on the Thanks! button

    MavenWire Hosting Admin
    15 years of OTM experience

    Comment

    • #3
      Re: java.sql.SQLException: ORA-28112

      Team,

      I am facing the same error. Please advice if its related to system issue or data issue.

      CAUGHT THE FOLLOWING EXCEPTION WHILE PROCESSING TRANSACTION: java.sql.SQLException: ORA-28112: failed to execute policy function


      java.sql.SQLException: ORA-28112: failed to execute policy function

      at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoe r.java:445)
      at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoe r.java:396)
      at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall. java:879)
      at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.jav a:450)
      at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java: 192)
      at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:5 31)
      at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4 CPreparedStatement.java:207)
      at oracle.jdbc.driver.T4CPreparedStatement.executeFor Describe(T4CPreparedStatement.java:884)
      at oracle.jdbc.driver.OracleStatement.executeMaybeDes cribe(OracleStatement.java:1167)
      at oracle.jdbc.driver.OracleStatement.doExecuteWithTi meout(OracleStatement.java:1289)
      at oracle.jdbc.driver.OraclePreparedStatement.execute Internal(OraclePreparedStatement.java:3584)
      at oracle.jdbc.driver.OraclePreparedStatement.execute Query(OraclePreparedStatement.java:362
      at oracle.jdbc.driver.OraclePreparedStatementWrapper. executeQuery(OraclePreparedStatementWrapper.java:1 493)
      at glog.util.jdbc.noserver.SqlPreparedStatement.execu teQuery(SqlPreparedStatement.java:35)
      at glog.util.jdbc.noserver.SqlQuery.executeQuery(SqlQ uery.java:164)
      at glog.util.jdbc.noserver.SqlQuery.resetArguments(Sq lQuery.java:137)
      at glog.util.jdbc.noserver.SqlQuery.open(SqlQuery.jav a:107)
      at glog.integration.application.location.ContactHelpe r.getContactInfoFromDatabase(ContactHelper.java:11 3)
      at glog.integration.application.location.ContactHelpe r.validatePrimaryContactConflict(ContactHelper.jav a:265)
      at glog.integration.application.location.ContactHelpe r.validatePrimaryContactConflict(ContactHelper.jav a:345)
      at glog.integration.application.location.LocationWrap per.validatePriorMapping(LocationWrapper.java:382)
      at glog.integration.xmlbasewrapper.XmlBaseWrapper.map (XmlBaseWrapper.java:197)
      at glog.integration.xmlbasewrapper.XmlBaseWrapper.per sistViaContainer(XmlBaseWrapper.java:362)
      at glog.integration.application.location.LocationWrap per.persistViaContainer(LocationWrapper.java:1041)
      at glog.integration.application.location.LocationInte rface.persistIndivXML(LocationInterface.java:97)
      at glog.integration.application.location.LocationInte rface.persistXML(LocationInterface.java:85)
      at glog.integration.application.BaseInterface.persist XMLBase(BaseInterface.java:195)
      at glog.integration.application.TransactionProcessor. processTransaction(TransactionProcessor.java:223)
      at glog.integration.application.TransactionProcessor. processTransaction(TransactionProcessor.java:353)
      at glog.server.workflow.transproc.TransProc.execute(T ransProc.java:110)
      at glog.server.workflow.SimpleWorkflow.execute(Simple Workflow.java:23)
      at glog.server.workflow.WorkflowSessionBean.execute(W orkflowSessionBean.java:64)
      at glog.server.workflow.WorkflowSessionNonTransServer SideEJBWrapper.execute(WorkflowSessionNonTransServ erSideEJBWrapper.java:3
      at glog.server.workflow.WorkflowSessionNonTransServer SideEJBWrapper_t6tuwu_EOImpl.__WL_invoke(Unknown Source)
      at weblogic.ejb.container.internal.SessionRemoteMetho dInvoker.invoke(SessionRemoteMethodInvoker.java:40 )
      at glog.server.workflow.WorkflowSessionNonTransServer SideEJBWrapper_t6tuwu_EOImpl.execute(Unknown Source)
      at glog.server.workflow.WorkflowManager.execute(Workf lowManager.java:352)
      at glog.server.workflow.Trigger.trigger(Trigger.java: 122)
      at glog.util.event.MemoryEventQueueRunnable.processEv ent(MemoryEventQueueRunnable.java:145)
      at glog.util.event.MemoryEventQueueRunnable.run(Memor yEventQueueRunnable.java:100)
      at glog.util.event.EventThread.run(EventThread.java:8 6)
      at java.lang.Thread.run(Thread.java:662)
      Cheers,
      -Neo

      Comment

      • #4
        Re: java.sql.SQLException: ORA-28112

        Hi Neo,

        Please answer below questions as asked by Nick in his post

        What is the version of OTM are you using?

        Is this part of a new install?

        Have you ran all of the post migration scripts?

        Did you also enable all of the Oracle parameters as per the admin guide?

        Thank you


        -Prasad-
        Let's connect on LinkedIn
        Mobile: +91 973 049 6886
        E-mail: [email protected]

        If my post was helpful, then click on the Like button

        Comment

        • #5
          Re: java.sql.SQLException: ORA-28112

          Its not new install but 6.3 version. Also all scripts were executed successfully.

          I resolved the issue by restarting the server. Not sure with the root cause but trying to figure out. If known surely will post.
          Cheers,
          -Neo

          Comment

          • #6
            Re: java.sql.SQLException: ORA-28112

            Hello Neo,

            We are experiencing the same exception in our OTM environment. As you have mentioned, we are able to recover the situation by the application restart.

            But finding it difficult to understand the root cause. Would like to know if you are able to come up with any findings on this.

            Regards,
            Siva

            Comment

            • #7
              Re: java.sql.SQLException: ORA-28112

              Hi Siva,

              Please provide below details,

              OTM Version you are using along with OPEN_CURSORS OTM database parameter

              Above error mainly occurred due to OPEN_CURSORS parameter exceed the limit defined in the database

              Thank you


              -Prasad-
              Let's connect on LinkedIn
              Mobile: +91 973 049 6886
              E-mail: [email protected]

              If my post was helpful, then click on the Like button

              Comment

              • #8
                Re: java.sql.SQLException: ORA-28112

                Hi Prasad,

                Please find the details below specific to our environment

                OTM version : 6.3.1
                OPEN_CURSORS : 3000

                Please let me know any further details required.

                Regards
                Siva

                Comment

                • #9
                  Re: java.sql.SQLException: ORA-28112

                  Hi Siva,

                  Thanks for the information

                  For OTM 6.3.1 OPEN_CURSORS parameter should be set to 3000 or more and which is OK in your case

                  However, sometimes in OTM Application there might be some sessions would not get close automatically which exceeds the limit defined at the database level

                  So, it throws the same error in OTM Application logs and need to restart OTM Application Server which removes all inactive sessions

                  Workaround: As per your DBA's suggestion, please increase OPEN_CURSORS parameter and check for any error

                  Thank you


                  -Prasad-
                  Let's connect on LinkedIn
                  Mobile: +91 973 049 6886
                  E-mail: [email protected]

                  If my post was helpful, then click on the Like button

                  Comment

                  Previous template Next
                  Working...
                  X