failed to run Gim_etl Transform Jobs

Voice & Telephony
1

Hi all,
Pls help me that problem. I got Fail when run Gim_etl Transform Jobs.In Gim_etl log, i saw errors as follows:

Caused by: com.genesyslab.gim.etl.exceptions.JdbcUniqueConstraintViolationException: executeUpdate; Unique Constraint Violation for SQL [INSERT INTO dbo.TMP_UDH_SESSION_END SELECT TMP_UDH_CUR_MM.CALLID,TMP_UDH_CUR_MM.KEYNAME,TMP_UDH_CUR_MM.KEYVALUE FROM dbo.TMP_UDH_CUR_MM WHERE TMP_UDH_CUR_MM.KEYNAME = 'ChatServerSessionClientLeftAt']; SQLSTATE=23000; error code=2601; DBError=CONSTRAINT_VIOLATION_UNIQUENESS_VIOLATION; Cannot insert duplicate key row in object 'dbo.TMP_UDH_SESSION_END' with unique index 'I_T_UD_SESS_END'. The duplicate key value is (0000CaCXDCT10098).
	at com.genesyslab.gim.etl.exceptions.SQLExceptionTranslator.translate(SQLExceptionTranslator.java:41)
	at com.genesyslab.gim.etl.exceptions.SQLExceptionTranslator.translate(SQLExceptionTranslator.java:28)
	at com.genesyslab.gim.etl.util.jdbc.SQLUtils.executeUpdate(SQLUtils.java:1426)
	at com.genesyslab.gim.etl.util.jdbc.SQLUtils.executeUpdate(SQLUtils.java:1484)
	at com.genesyslab.gim.etl.util.jdbc.SQLUtils.executeUpdate(SQLUtils.java:1513)
	at com.genesyslab.gim.etl.jobs.transform.FillCoreTablesForCurChunk$FillTmpUdHistoryForCurChunk.runStep(FillCoreTablesForCurChunk.java:377)
	... 13 more
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Cannot insert duplicate key row in object 'dbo.TMP_UDH_SESSION_END' with unique index 'I_T_UD_SESS_END'. The duplicate key value is (0000CaCXDCT10098).

Thanks a lot !

2

You will probably need to open a ticket to fix this, since it is not in any Customer Care arcticle nor Release Notes.

The TMP tables are generated during transformation so probably tech support may send you a script to remove the duplicate data.

Genesys will probably ask you to gather GIM ETL logs and run the GETGIMDATA tool for some interaction after analyzing the logs.
I believe that you might get a response from Customer Care faster if you attached the output of this script on the database (assuming that there is any result):

select callid, keyname, changetype, count(1) from gim81.gidb_g_userdata_history_mm where keyname = ‘ChatServerSessionClientLeftAt’ and changetype <> 1
group by callid, keyname, changetype
having count(1) > 1

3

Thanks a lot hsujdik, The problem was Gim ETL. Genesys recommended to upgrade to lastest version of GIM :)>

4

I ran the query and then renamed the rows it found with another letter at the end, and it all started working fine!

Thanks a lot!

5

Hi, Javier

You shouldn’t manually update those records. The query I mentioned above was to help the Genesys Tech Support find the issue that hieutx posted.