Genesys CTI User Forum
Genesys CTI User Forum => Genesys CTI Technical Discussion => Topic started by: Lorenzo on December 06, 2006, 08:55:02 AM
-
We created new agents for the Call Center and modified the name of other agents which we added in an agent group.
We can see this result in the DMA :agents are seen in objects and their statistics are populated. Nevertheless, we cannot see these agents and their associated statistics in the Datamart database.
We guess the problem is therefore located in passing the info from the ODS to the Datamart database.
Here are the ETLRuntime config options :
------------------------------------------------------------------------------------------------------
[ETL_Agg_Only]
Command=java -Xmx256m -jar transform.jar -conf etl.properties -aggOnly -
Command0=loglevel=SQL-STATS:3,EVENT:3,COMMAND:3,START_AGG:3,AGG:9,INFO:9,WARNING:8,ERROR:9,_ALL_:0 -
Command1=maxLevelOfAgg=AGG_BY_YEAR -
Command2=updateStatsForLevel0Views -updateStatsForTablesAndIndexes
Priority=medium
StartTime=0:10+1:00
[ETL_Purging]
Command=java -jar purge.jar -conf purge.properties
Priority=medium
StartTime=01:00
[ETL_Tracking]
Command=java -jar conf_report.jar -conf etl.properties
Priority=medium
StartTime=00:45+0:15
[ETL_Trans_Only]
Command=java -Xmx256m -jar transform.jar -conf etl.properties -
Command0=loglevel=WAKE:3,START_WRITE_MON:3,DROP:9,WRITE:3,INFO:9,PURGE:9,WARNING:8,ERROR:9,_ALL_:0 -
Command1=maxNumberOfConnToDist=2
Priority=medium
StartTime=0:01+0:15
[Genesys ETL Service Starter]
Processes=ETL_Trans_Only,ETL_Agg_Only,ETL_Tracking,ETL_Purging
[Log]
Buffering=true
Expire=20
Segment=5000
Standard=X:\GenesysLog\ETL_Runtime\ETL_Runtime.log
Verbose=all
all=X:\GenesysLog\ETL_Runtime\ETL_Runtime.log
-------------------------------------------------------------------------------------------
Any help would be appreciated.
Best regards.
-
Which version of CCA components are you running?
-
I found that it took up to 2 days for new objects to appear for inclusion in reporting. Has it been that long?
-
it's been several days (at least 8 days).
For the version, we are in 7.0.
-
the exact version is 7.0.100.11
-
Hi,
Have you checked in the etl-log that ETL Tracking is running OK?
I once had a problem where the user/password from etl.properties had changed in CME. This made Tracking fail to log in to CME and find the changes.
-
Out of curiousity, why do you have tracking set to every 15 minutes? Is this not excessive? Could it be possible that you are kicking off the process too often? Do you add/change agent and queue information that much? Would every few hours work?
Ours is set to 01:00, and there have been no complaints, but we are also not a 24x7 call center.
Short did pose a good question - what do you see in the logs? My ETL is a little rusty, but is there a way to drop the Tracking output into a separate log (instead of or in addition to the common log), so you don't have to sift through the rest of the ETL output?
-
Maybe they need reports based on 15min intervals, by default they are setted up as it.
If the process is still running it will queue after it finish and then start the other.
-
Also had a thought that spawned Java sessions may actually be running into one another, if you are running the java bat and propoerties files at the same time as allowing Genesys to run them automagically through ETL. Perhaps if you stop all ETL activity and wait for all Java sesssions to finish *then* use Genesys (only) to maintain the various sessions for you.
This has happened to me before and it took a while to work out how to switch it over...
Tony
-
Yes, we just found the problem, it was linked to Java sessions. Tony, we followed your advice and it is now ok, although we do not know why this occurred recently and not before.
Thanks to everybody for all your thoughts, this forum is really great.