" /> Gim etl transform error - Genesys CTI User Forum

Author Topic: Gim etl transform error  (Read 4334 times)

Offline tim.reeve

  • Newbie
  • *
  • Posts: 7
  • Karma: 0
Gim etl transform error
« on: June 25, 2013, 09:48:47 AM »
Advertisement
Having changed the following values in config:

agg-gim-thld-QUEUE-IXN   
from voice - 5,15,15,5,15,15
to voice - 5,20,20,5,20,20

I'm now getting the following error in the gim log:

Unable to synchronize SCfg
09:10:01.819 Agg.Main common.TransformError: Exception during synchronization of existing configuration
09:10:01.819 Agg.Main Stack Trace:
09:10:01.819 Agg.Main at GIMAgg.GimInterfaceImpl.AggSCfg.parse(AggSCfg.java:101)
09:10:01.819 Agg.Main at GIMAgg.sync.SyncSCfg.isInSync(SyncSCfg.java:69)
09:10:01.819 Agg.Main at GIMAgg.sync.Synchronizer.isSynced(Synchronizer.java:86)
09:10:01.819 Agg.Main at GIMAgg.sync.Synchronizer.synchronize(Synchronizer.java:33)
09:10:01.819 Agg.Main at GIMAgg.Glue$2.synchronize(Glue.java:191)
09:10:01.819 Agg.Main at GIMAgg.GimInterfaceImpl.AggKeeper.executeCommand(AggKeeper.java:198)
09:10:01.819 Agg.Main at common.thread.SimpleMonitor.executeCommand(SimpleMonitor.java:43)
09:10:01.819 Agg.Main at common.thread.SimpleMonitor.run(SimpleMonitor.java:65)
09:10:01.819 Agg.Main at java.lang.Thread.run(Thread.java:662)
09:10:01.819 Agg.Main Caused by:
09:10:01.819 Agg.Main java.lang.AssertionError:
09:10:01.819 Agg.Main Stack Trace:
09:10:01.819 Agg.Main at common.Ensure.raise(Ensure.java:144)
09:10:01.819 Agg.Main at common.Ensure.ensureTrue(Ensure.java:64)
09:10:01.819 Agg.Main at common.Ensure.ensureTrue(Ensure.java:68)
09:10:01.819 Agg.Main at GIMAgg.sync.SCfgValues.make(SCfgValues.java:34)
09:10:01.819 Agg.Main at scheme.SCfgAcc.applyN(SCfgAcc.java:73)
09:10:01.819 Agg.Main at gnu.kawa.functions.ApplyToArgs.applyN(ApplyToArgs.java:139)
09:10:01.819 Agg.Main at scheme.scfg.processNodeset(scfg.ss:224)
09:10:01.819 Agg.Main at scheme.scfg.apply3(scfg.ss:213)
09:10:01.819 Agg.Main at gnu.expr.ModuleMethod.apply3(ModuleMethod.java:204)
09:10:01.819 Agg.Main at scheme.scfg.lambda9(scfg.ss:189)
09:10:01.819 Agg.Main at scheme.scfg.apply3(scfg.ss:189)
09:10:01.819 Agg.Main at gnu.expr.ModuleBody.applyN(ModuleBody.java:239)
09:10:01.819 Agg.Main at scheme.scfg.applyN(scfg.ss:40)
09:10:01.819 Agg.Main at gnu.expr.ModuleMethod.applyN(ModuleMethod.java:216)
09:10:01.819 Agg.Main at gnu.kawa.functions.ApplyToArgs.applyN(ApplyToArgs.java:139)
09:10:01.819 Agg.Main at gnu.mapping.ProcedureN.apply4(ProcedureN.java:59)
09:10:01.819 Agg.Main at scheme.scfg$frame0.lambda4(scfg.ss:137)
09:10:01.819 Agg.Main at scheme.scfg$frame0.apply2(scfg.ss:129)
09:10:01.819 Agg.Main at gnu.expr.ModuleMethod.apply2(ModuleMethod.java:198)
09:10:01.819 Agg.Main at kawa.lib.kawa.hashtable$HashTable.walk(hashtable.scm:45)
09:10:01.819 Agg.Main at gnu.kawa.slib.srfi69.hashTableWalk(srfi69.scm:141)
09:10:01.819 Agg.Main at scheme.scfg.scfgWalkAllNodesets(scfg.ss:127)
09:10:01.819 Agg.Main at scheme.scfg.apply3(scfg.ss:126)
09:10:01.819 Agg.Main at gnu.expr.ModuleMethod.apply3(ModuleMethod.java:204)
09:10:01.819 Agg.Main at scheme.scfg.scfgGather(scfg.ss:191)
09:10:01.819 Agg.Main at scheme.scfg.apply2(scfg.ss:183)
09:10:01.819 Agg.Main at gnu.expr.ModuleMethod.apply2(ModuleMethod.java:198)
09:10:01.819 Agg.Main at GIMAgg.GimInterfaceImpl.AggSCfg.parse(AggSCfg.java:87)
09:10:01.819 Agg.Main at GIMAgg.sync.SyncSCfg.isInSync(SyncSCfg.java:69)
09:10:01.819 Agg.Main at GIMAgg.sync.Synchronizer.isSynced(Synchronizer.java:86)
09:10:01.819 Agg.Main at GIMAgg.sync.Synchronizer.synchronize(Synchronizer.java:33)
09:10:01.819 Agg.Main at GIMAgg.Glue$2.synchronize(Glue.java:191)
09:10:01.819 Agg.Main at GIMAgg.GimInterfaceImpl.AggKeeper.executeCommand(AggKeeper.java:198)
09:10:01.819 Agg.Main at common.thread.SimpleMonitor.executeCommand(SimpleMonitor.java:43)
09:10:01.819 Agg.Main at common.thread.SimpleMonitor.run(SimpleMonitor.java:65)
09:10:01.819 Agg.Main at java.lang.Thread.run(Thread.java:662)

I made the changes while gim_etl was started, not knowing this can cause problems.  I have re-started gim_etl several times, and even done a platform re-start but the error is still there (this is a Dev environment).  I have changed the options back to their original values while gim_etl was stopped, and the error is still coming.

I'm running the following app versions:

GIM ETL - 8.1.103.03
call concentrator - 8.1.000.28
db server - 8.1.100.04
statserver - 8.1.000.11

Any suggestions appreciated

Offline Kubig

  • Hero Member
  • *****
  • Posts: 2755
  • Karma: 44
Re: Gim etl transform error
« Reply #1 on: June 25, 2013, 11:26:18 AM »
Hi,

try to check file with name gim_etl_cfgs.xml, which is placed under install directory of GIM, that the config within this file equals to configuration in cfg db.

Offline tim.reeve

  • Newbie
  • *
  • Posts: 7
  • Karma: 0
Re: Gim etl transform error
« Reply #2 on: June 25, 2013, 11:55:52 AM »
Hi Kubig,  I've checked the file and the values match

-<i id="agg-gim-thld-QUEUE-IXN"><i v="5,15,15,5,15,15" k="default"/><i v="5,15,15,5,15,15" k="voice"/></i>

Thanks

Offline Kubig

  • Hero Member
  • *****
  • Posts: 2755
  • Karma: 44
Re: Gim etl transform error
« Reply #3 on: June 25, 2013, 12:17:21 PM »
Try to stop GIM and make change on mentioned options and then start GIM, do not make changes during the GIM is running

Offline tim.reeve

  • Newbie
  • *
  • Posts: 7
  • Karma: 0
Re: Gim etl transform error
« Reply #4 on: June 26, 2013, 08:00:40 AM »

Thanks Kubig, I now know this is the correct procedure but I still need a way to rectify the situation.  The error still appears in logs and aggregated data can not be reported on since the time the change was made.  The aggregate/transform etc jobs appear to run successfully according to the mgmt console.

I've looked at the table AGR_SCFG mentioned in the exception and the data didn't match the config for two other options agg-gim-thld-QUEUE-ACC and agg-gim-thld-QUEUE-ABN.  Could it be that this is the cause?  So there was a mismatch all along but my attempted change has forced it to process it, with the result of causing the exception I'm seeing?