" /> GIM ERROR in jon initialization - Genesys CTI User Forum

Poll

why the GIM job initialization completed unsuccessfully ??

why the GIM job initialization completed unsuccessfully ??
0 (0%)
why the GIM job initialization completed unsuccessfully ??
0 (0%)

Total Members Voted: 0

« previous next »
Pages: [1]   Go Down

Author Topic: GIM ERROR in jon initialization  (Read 4090 times)

Offline amine.riahi.idrissi

  • Newbie
  • *
  • Posts: 12
  • Karma: -1
GIM ERROR in jon initialization
« on: May 08, 2015, 09:57:04 AM »
Advertisement
Hi everyone,

Please can anyone tell me why the Gim job initialization completed unsuccessfully , below the log error :

update_idb_for_gim.sql version check FAIL: DAP=GimDAP_IDB, required=8.1.400.01, current=null;
20044 Job 'Job_InitializeGIM' completed unsuccessfully.

Thanks in advance.
Logged

Offline cavagnaro

  • Administrator
  • Hero Member
  • *****
  • Posts: 7641
  • Karma: 56330
Re: GIM ERROR in jon initialization
« Reply #1 on: May 08, 2015, 12:07:36 PM »
Lmao...without showing full logs which you can also read no clue
Logged

Offline amine.riahi.idrissi

  • Newbie
  • *
  • Posts: 12
  • Karma: -1
Re: GIM ERROR in jon initialization
« Reply #2 on: May 08, 2015, 04:44:18 PM »
below the error :

2015-05-08 09:00:53,741 INFO  ecp-1-1      25000 Exception com.genesyslab.gim.etl.exceptions.InvalidConfiguration: update_idb_for_gim.sql version check FAIL: DAP=GimDAP_IDB, required=8.1.400.01, current=null caused cancellation of 1 remaining tasks:
java.util.concurrent.ExecutionException: com.genesyslab.gim.etl.exceptions.InvalidConfiguration: update_idb_for_gim.sql version check FAIL: DAP=GimDAP_IDB, required=8.1.400.01, current=null
at java.util.concurrent.FutureTask.report(Unknown Source)
at java.util.concurrent.FutureTask.get(Unknown Source)
at com.genesyslab.gim.etl.util.BunchExecutorService.joinAll(BunchExecutorService.java:104)
at com.genesyslab.gim.etl.util.BunchExecutorService.invokeAll(BunchExecutorService.java:67)
at com.genesyslab.gim.etl.server.GenericJobStepContext.invokeAll(GenericJobStepContext.java:212)
at com.genesyslab.gim.etl.jobs.migrate.UpdateIdbForGim.runStep(UpdateIdbForGim.java:49)
at com.genesyslab.gim.etl.server.GenericJobTask.execute(GenericJobTask.java:66)
at com.genesyslab.gim.etl.server.CallableTransactionStep.runTransaction(CallableTransactionStep.java:29)
at com.genesyslab.gim.etl.server.CallableTransactionStep.runContext(CallableTransactionStep.java:55)
at com.genesyslab.gim.etl.server.CallableTransactionStep.call(CallableTransactionStep.java:75)
at com.genesyslab.gim.etl.server.CallableTransactionStep.call(CallableTransactionStep.java:13)
at com.genesyslab.gim.etl.util.StopWatchCallable.call(StopWatchCallable.java:32)
at com.genesyslab.gim.etl.server.JobStepRunner.callTask(JobStepRunner.java:239)
at com.genesyslab.gim.etl.server.JobStepRunner.access$200(JobStepRunner.java:32)
at com.genesyslab.gim.etl.server.JobStepRunner$2.call(JobStepRunner.java:223)
at com.genesyslab.gim.etl.server.JobStepRunner$2.call(JobStepRunner.java:221)
at com.genesyslab.gim.etl.server.JobStepRunner.runTask(JobStepRunner.java:230)
at com.genesyslab.gim.etl.server.JobStepRunner.runTasks(JobStepRunner.java:185)
at com.genesyslab.gim.etl.server.JobStepRunner.initAndRun(JobStepRunner.java:174)
at com.genesyslab.gim.etl.server.JobStepRunner.initAndRun(JobStepRunner.java:127)
at com.genesyslab.gim.etl.server.JobStepRunner.run(JobStepRunner.java:109)
at com.genesyslab.gim.etl.constants.JobInfo$9.call(JobInfo.java:226)
at com.genesyslab.gim.etl.constants.JobInfo$9.call(JobInfo.java:218)
at java.util.concurrent.FutureTask.run(Unknown Source)
at com.genesyslab.gim.etl.server.JobController$3.call(JobController.java:1026)
at com.genesyslab.gim.etl.server.JobController$3.call(JobController.java:1023)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: com.genesyslab.gim.etl.exceptions.InvalidConfiguration: update_idb_for_gim.sql version check FAIL: DAP=GimDAP_IDB, required=8.1.400.01, current=null
at com.genesyslab.gim.etl.jobs.migrate.UpdateIdbForGim.applyPatch(UpdateIdbForGim.java:102)
at com.genesyslab.gim.etl.jobs.migrate.UpdateIdbForGim.access$000(UpdateIdbForGim.java:24)
at com.genesyslab.gim.etl.jobs.migrate.UpdateIdbForGim$1.call(UpdateIdbForGim.java:44)
at com.genesyslab.gim.etl.jobs.migrate.UpdateIdbForGim$1.call(UpdateIdbForGim.java:41)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at com.genesyslab.gim.etl.util.VirtualExecutorService$Task.run(VirtualExecutorService.java:113)
... 3 more

2015-05-08 09:00:53,741 INFO  ecp-1-1      30000 BunchExecutorService.doCancelAll (15,MINUTES) - enter
2015-05-08 09:00:53,741 INFO  ecp-1-1      30000 Canceling 1 futures: [java.util.concurrent.FutureTask@7ce0745e]
2015-05-08 09:00:53,741 ERROR ecp-1-3      20155 Database error: ORA-00942: table or view does not exist
; CODE=942; SQLSTATE=42000; DBError=SYNTAX_ERROR_OR_ACCESS_RULE_VIOLATION_UNSPECIFIED; SQL=[ SELECT G_DB_PARAMETERS.VAL FROM (select 1 as dummy from DUAL) DUAL LEFT OUTER JOIN GimDB.G_DB_PARAMETERS ON G_DB_PARAMETERS.SECT = 'GIM' AND G_DB_PARAMETERS.OPT = 'version' ], conn=1342095067,oracle.jdbc.driver.T4CConnection@4ffebedb.
2015-05-08 09:01:03,896 INFO  ecp-1-1      30000 BunchExecutorService.doCancelAll - exit returning true
2015-05-08 09:01:03,896 INFO  ecp-1-1      30000 com.genesyslab.gim.etl.exceptions.TaskExecutionException: com.genesyslab.gim.etl.exceptions.InvalidConfiguration: update_idb_for_gim.sql version check FAIL: DAP=GimDAP_IDB, required=8.1.400.01, current=null.UpdateIdbForGim threw runStep - TaskExecutionException
2015-05-08 09:01:03,896 WARN  ecp-1-1      20049 Job step 'UPDATE_IDB_FOR_GIM' failed. com.genesyslab.gim.etl.exceptions.InvalidConfiguration: update_idb_for_gim.sql version check FAIL: DAP=GimDAP_IDB, required=8.1.400.01, current=null.
com.genesyslab.gim.etl.exceptions.TaskExecutionException: com.genesyslab.gim.etl.exceptions.InvalidConfiguration: update_idb_for_gim.sql version check FAIL: DAP=GimDAP_IDB, required=8.1.400.01, current=null
at com.genesyslab.gim.etl.exceptions.ExceptionHandlers.wrap(ExceptionHandlers.java:23)
at com.genesyslab.gim.etl.exceptions.ExceptionHandlers.wrap(ExceptionHandlers.java:12)
at com.genesyslab.gim.etl.util.BunchExecutorService.invokeAll(BunchExecutorService.java:73)
at com.genesyslab.gim.etl.server.GenericJobStepContext.invokeAll(GenericJobStepContext.java:212)
at com.genesyslab.gim.etl.jobs.migrate.UpdateIdbForGim.runStep(UpdateIdbForGim.java:49)
at com.genesyslab.gim.etl.server.GenericJobTask.execute(GenericJobTask.java:66)
at com.genesyslab.gim.etl.server.CallableTransactionStep.runTransaction(CallableTransactionStep.java:29)
at com.genesyslab.gim.etl.server.CallableTransactionStep.runContext(CallableTransactionStep.java:55)
at com.genesyslab.gim.etl.server.CallableTransactionStep.call(CallableTransactionStep.java:75)
at com.genesyslab.gim.etl.server.CallableTransactionStep.call(CallableTransactionStep.java:13)
at com.genesyslab.gim.etl.util.StopWatchCallable.call(StopWatchCallable.java:32)
at com.genesyslab.gim.etl.server.JobStepRunner.callTask(JobStepRunner.java:239)
at com.genesyslab.gim.etl.server.JobStepRunner.access$200(JobStepRunner.java:32)
at com.genesyslab.gim.etl.server.JobStepRunner$2.call(JobStepRunner.java:223)
at com.genesyslab.gim.etl.server.JobStepRunner$2.call(JobStepRunner.java:221)
at com.genesyslab.gim.etl.server.JobStepRunner.runTask(JobStepRunner.java:230)
at com.genesyslab.gim.etl.server.JobStepRunner.runTasks(JobStepRunner.java:185)
at com.genesyslab.gim.etl.server.JobStepRunner.initAndRun(JobStepRunner.java:174)
at com.genesyslab.gim.etl.server.JobStepRunner.initAndRun(JobStepRunner.java:127)
at com.genesyslab.gim.etl.server.JobStepRunner.run(JobStepRunner.java:109)
at com.genesyslab.gim.etl.constants.JobInfo$9.call(JobInfo.java:226)
at com.genesyslab.gim.etl.constants.JobInfo$9.call(JobInfo.java:218)
at java.util.concurrent.FutureTask.run(Unknown Source)
at com.genesyslab.gim.etl.server.JobController$3.call(JobController.java:1026)
at com.genesyslab.gim.etl.server.JobController$3.call(JobController.java:1023)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: com.genesyslab.gim.etl.exceptions.InvalidConfiguration: update_idb_for_gim.sql version check FAIL: DAP=GimDAP_IDB, required=8.1.400.01, current=null
at com.genesyslab.gim.etl.jobs.migrate.UpdateIdbForGim.applyPatch(UpdateIdbForGim.java:102)
at com.genesyslab.gim.etl.jobs.migrate.UpdateIdbForGim.access$000(UpdateIdbForGim.java:24)
at com.genesyslab.gim.etl.jobs.migrate.UpdateIdbForGim$1.call(UpdateIdbForGim.java:44)
at com.genesyslab.gim.etl.jobs.migrate.UpdateIdbForGim$1.call(UpdateIdbForGim.java:41)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at com.genesyslab.gim.etl.util.VirtualExecutorService$Task.run(VirtualExecutorService.java:113)
... 3 more
Logged

Offline cavagnaro

  • Administrator
  • Hero Member
  • *****
  • Posts: 7641
  • Karma: 56330
Re: GIM ERROR in jon initialization
« Reply #3 on: May 08, 2015, 05:17:01 PM »
Well... Error is pretty self explanatory, anyone who reads it will understand. You have a null value where it expects a specific version. So...check your deployment procedure. Check BD tables and run needed sql scripts.
Logged

Offline amine.riahi.idrissi

  • Newbie
  • *
  • Posts: 12
  • Karma: -1
Re: GIM ERROR in jon initialization
« Reply #4 on: May 09, 2015, 12:37:03 AM »
i execute the DB sripts as described in the documentation
Logged

Offline cavagnaro

  • Administrator
  • Hero Member
  • *****
  • Posts: 7641
  • Karma: 56330
Re: GIM ERROR in jon initialization
« Reply #5 on: May 09, 2015, 02:26:39 AM »
At least check that table and its column value. Check which script does the initial insert of values or at GIM initialization log if it has any problem writing values.
Logged
Pages: [1]   Go Up
« previous next »