interaction_resource_fact table not showing records

[husam]

Hi Team, please accept my apologies if this is posted in the wrong forum.

We have setup a fresh environment of Genesys, made couple of test calls everything is working fine. We can view call records in  [GIDB_G_ROUTE_RESULT_V] table, the ICON_Voice is pushing the data properly to Infomart. We are facing an issue with [INTERACTION_RESOURCE_FACT] table where we cannot see any records. Below is the only error which we see in the ETL logs.

Transformation of chunk '{42: 1377550800-1377550800, maxChunkTS=2013-08-26 21:06:16(1377551176), proc status=MERGED_VOICE}' has been postponed due to delayed data '(1970-01-01 00:00:00[0]) in call related tables'

Please respond, any help will be appreciated.

[Kubig]

As first, I must repair your expression, that ICON push data to the GIM database, it is not true. GIM takes the data from IDB database self. It is just a note.

Back to the problem,as first step try to check your GIM deployment , if you have all configured properly,particular roles for each data access point and etc. This error means, that all data from IDB being extracted, but not being moved to GIM interaction tables.

[husam]

Thank you for the correction, we have validated all roles as they are most important. It is just the Transform job we see the error (WARN)

All roles are set correctly, and there are no errors in the ICON logs and schedule jobs extracts and transforms run without error.

In the warn message we see 20110

2013-08-27 17:57:55,179 WARN  ecp-1-44    [b]20110[/b] Transformation of chunk '{43: 1377550800-1377550800, maxChunkTS=2013-08-26 21:08:20(1377551300), proc status=MERGED_VOICE}' has been postponed due to delayed data '(1970-01-01 00:00:00[0]) in call related tables'.

I have tried searching this value, it means that the data is being delayed for some reason. Response appreciated. Thanks.

[Kubig]

Just a hint from Genesys:

To prevent excessive or unnecessary delays, a configuration option in the [gim-etl] section, delayed-data-threshold, enables you to specify a timeout after which Genesys Info Mart logs a detailed message (55-20110) if expected data does not arrive. It is recommended to set this alarm so that the reasons for delayed data can be investigated

Depending on the situation, appropriate action could include:
- Temporarily disabling the unavailable data source
- Temporarily stopping the ETL scheduler so the next run of the extract job does not advance the high-water mark.

[husam]

If we set this it will just create the same message in SCI, however it may give us more, we can setup now, will update you shortly. Thanks.

[husam]

We did the Db rebuild,  made changes to the error handling section on the ETL options, we had execute changed to resume.

Now interaction_resource_fact table is showing the same number of records that are in [GIDB_G_ROUTE_RESULT_V], but we made 16 calls after the DB rebuilt which can be seen in the ICON DB, but [GIDB_G_ROUTE_RESULT_V] is only showing 15 and it took couple of hours to populate the Infomart DB, we are still waiting for one call to pop up at [GIDB_G_ROUTE_RESULT_V] of Infomart.

Any idea, how much time does it take Infomart take to get data from ICONDB. We have set the schedule for reporting from ICON to Infomart to every 5 minutes.

[Kubig]

For me is very strange this row from your log:

[code]' has been postponed due to delayed data '(1970-01-01 00:00:00[0]) in call related tables'.[/code] The date in the message is very odd, have you configured properly datetime tables for your timezone?