This page was last edited on August 28, 2015, at 16:07.
Comments or questions about this documentation? Contact us for support!
Genesys Info Mart Release Notes
Release Date | Release Type | Restrictions | AIX | Linux | Solaris | Windows |
---|---|---|---|---|---|---|
05/11/15 | Hot Fix | X | X | X | X |
This release contains the following new features and enhancements:
This release contains the following resolved issues:
In deployments with a partitioned database schema, the extraction job now successfully handles scenarios similar to the following:
Previously in such scenarios, the extraction job might fail during merge processing and generate a message similar to the following:
Unique Constraint Violation for SQL [INSERT INTO GIDB_G_IR_V ...]; ORA-00001: unique constraint (GIM_ETL_ORACLE_8XX.I_G_IR_V_IRID) violated
(GIM-9888)
The performance of the transformation job has been improved in certain scenarios in which a multimedia virtual queue is configured to link to user data (link-msf-userdata=true). Previously, if the virtual queue was associated with a "runaway strategy," transformation job performance was hindered because the job produced too many rows in the TMP_UDH_MM table. (GIM-9885)
Genesys Info Mart now correctly transforms data from the GM_L_USERDATA table when values in the G_STOP_REASON field exceed 50 characters. Previously in such scenarios, the transformation job might have failed with the following error:
error code=12,899; ORA-12899: value too large for column "GSYS_INFOMART"."TMP_IRF_MM"."CALL_STOP_REASON" (actual: 74, maximum: 50)
(GIM-9818)