3 Replies Latest reply: Dec 24, 2013 6:03 AM by Kumar_Jaga RSS

    Start Graph scheduled tasks Completing with error

    NarasimhaRao

      Hi,

       

      We have installed the Oracle EBusiness Suite (R12.1.3.4) Extenstion V4 for Oracle Endeca,

      We have followed the all required steps from oracle support document/note : 1562372.1

       

      After integration, We have scheduled the task for task "Start Graph" but the task completing with below error message.

       

      2013-08-30 16:41:10,790 WARN 64605 [CALL_CENTRAL_FULL_LOAD_CONFIG_64605] Graph sandbox://Common/graph/FullLoad.grf finished with error. 
      2013-08-30 16:41:10,790 ERROR 64605 [WatchDog] Graph execution finished with error 
      2013-08-30 16:41:10,790 ERROR 64605 [WatchDog] Node CALL_CENTRAL_FULL_LOAD_CONFIG finished with status: ERROR 
      caused by: Graph 'sandbox://Common/graph/FullLoad.grf' failed! 
      2013-08-30 16:41:10,790 ERROR 64605 [WatchDog] Node CALL_CENTRAL_FULL_LOAD_CONFIG 
      error details: org.jetel.exception.JetelException: Graph 'sandbox://Common/graph/FullLoad.grf' failed! 
      at org.jetel.component.RunGraph.execute(RunGraph.java:280) at org.jetel.graph.Node.run(Node.java:453) 
      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:722) 
      2013-08-30 16:41:10,840 ERROR 64605 [WatchDog] !!! Phase finished with error - stopping graph run !!!

       

      Kindly help me in this issue.

        • 1. Re: Start Graph scheduled tasks Completing with error
          hero.wu

          Yes, I've met exactly the same error while doing FullLoad at ont module. My ebs env is configured with fresh database, not Vision Demo. I doubt whether it is because of no data then I met this error. But now I don't think no data is connected with this issue. Hope somebody could help with this.

           

          Parent error log:

          Element [ERROR_AUDIT_UPDATE:Error Audit Update]-Component pre-execute initialization failed.

                  at org.jetel.graph.Node.run(Node.java:446)

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

          Caused by: org.jetel.exception.JetelException: Cannot establish DB connection to JNDI:jdbc/ebsdb While trying to lookup 'jdbc.ebsdb' didn't find subcontext 'jdbc'. Resolved '' caused by: javax.naming.NameNotFoundException: While trying to lookup 'jdbc.ebsdb' didn't find subcontext 'jdbc'. Resolved ''; remaining name 'jdbc/ebsdb'

                  at org.jetel.component.DBExecute.initConnection(DBExecute.java:481)

                  at org.jetel.component.DBExecute.preExecute(DBExecute.java:415)

                  at org.jetel.graph.Node.run(Node.java:444)

                  ... 3 more

          Caused by: org.jetel.exception.JetelException: Cannot establish DB connection to JNDI:jdbc/ebsdb While trying to lookup 'jdbc.ebsdb' didn't find subcontext 'jdbc'. Resolved '' caused by: javax.naming.NameNotFoundException: While trying to lookup 'jdbc.ebsdb' didn't find subcontext 'jdbc'. Resolved ''; remaining name 'jdbc/ebsdb'

                  at org.jetel.connection.jdbc.DBConnection.connect(DBConnection.java:484)

                  at org.jetel.connection.jdbc.DBConnection.getConnection(DBConnection.java:465)

                  at org.jetel.component.DBExecute.initConnection(DBExecute.java:478)

                  ... 5 more

          Caused by: javax.naming.NameNotFoundException: While trying to lookup 'jdbc.ebsdb' didn't find subcontext 'jdbc'. Resolved ''; remaining name 'jdbc/ebsdb'

                  at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)

                  at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:247)

                  at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)

                  at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)

                  at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)

                  at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:412)

                  at javax.naming.InitialContext.lookup(InitialContext.java:411)

                  at org.jetel.connection.jdbc.DBConnection.connect(DBConnection.java:477)

                  ... 7 more

          • 2. Re: Start Graph scheduled tasks Completing with error
            kumar_1302

            The issue is Clover is not able to get the DB connection using the JNDI name 'jdbc/ebsdb', please check if the JNDI data-source is created correctly by logging into Integrator Domain Admin Server Console URL - http://<hostname>:7005/console

            • 3. Re: Start Graph scheduled tasks Completing with error
              Kumar_Jaga

              Hi,

               

               

              Am also getting same error while running fullloadgraph its showing status error like

               

              org.jetel.exception.JetelException: Graph 'sandbox://Common/graph/FullLoad.grf' failed!

                      at org.jetel.component.RunGraph.execute(RunGraph.java:280)

                      at org.jetel.graph.Node.run(Node.java:453)

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

               

               

               

               

                Graph 'sandbox://Common/graph/FullLoad.grf' failed!

               

              Please help me to fix this issue.

               

              Regards

              Kumar