As of February 1, 2012, Genesys is no longer an affiliate of Alcatel-Lucent; any indication of such affiliation within Genesys products or packaging is no longer applicable. Please see the Genesys website at http://www.genesyslab.com for more details.
The following information applies to Genesys 7.6.x software and is important for you to note:
Genesys follows applicable third-party redistribution policies to the extent that Genesys solutions utilize functionality of commercial or non-commercial third parties. For specific information on any third-party software used in this product, see the Read Me.
Genesys Info Mart ships with Genesys Info Mart Administration Console. The specific release of Genesys Info Mart Administration Console tested with this release of Genesys Info Mart is indicated in the Genesys Info Mart 7.6.x Release Note.
Genesys Info Mart 7.6 interoperates with Interaction Concentrator 8.0, starting with Genesys Info Mart release 7.6.007, and supports those features of Interaction Concentrator 8.0 that replicate Interaction Concentrator 7.6.1 functionality. In addition, Genesys Info Mart supports the following new Interaction Concentrator 8.0 functionality:
If Genesys Info Mart server running on AIX with certain versions of IBM Java is stopped via Genesys Solution Control Interface (SCI), the next time Genesys Info Mart server is started, the following error message is generated:
DEBUG main 55-35201 "GIM Listener - opening listener 'GIM_ETL - tcp://host_name:port_number'" WARN main 55-21407 "GIM Listener - error opening listener 'GIM_ETL - tcp://host_name:port_number'" Exception: 'com.genesyslab.platform.commons.protocol.ProtocolException: Failed to start acceptor'" INFO main 55-31108 "GIM Server - exiting"
The error indicates that Genesys Info Mart is trying to open a port that is still occupied (has not been released). The error was observed on AIX running with IBM Java 1.5 SR9 and SR11, but not with IBM Java 1.5 SR5 or SR8.
If you are upgrading Interaction Concentrator to release 7.6.1 in your Genesys Info Mart deployment, please note the following. Code corrections delivered in Interaction Concentrator release 7.6.1 relating to the storage of user data history can result in differences in the way Genesys Info Mart now populates user data-based facts. (See the Interaction Concentrator 7.6 Release Note for information about the code corrections per ER# 191528711 and ER# 205574746.) Please refer to the Product Advisory for Genesys Info Mart 7.5 and 7.6 of December 19, 2008 for detailed information about the differences in, and examples of, user data propagation in Genesys Info Mart.
For installations where the Genesys Info Mart Server connects to a Staging Area database on Oracle using a 10.1.x version of the Oracle client,
Job_InitializeGIM may fail with the following error:
msgText="Job Job_InitializeGIM failed with error org.hibernate.exception.GenericJDBCException: Could not execute JDBC batch updateCaused by: java.sql.BatchUpdateException: ORA-01458: invalid length inside variable character string
You can resolve this error by upgrading the Oracle client to a 10.2.x version on the machine that hosts the Genesys Info Mart Server.
For a Staging Area database using Oracle 10g, changing the database configuration parameter
similar can result in the following error during
Oracle <vdcqy> error message for operation <OCIStmtExecute>: <ORA-01427: single-row subquery returns more than one row.>
To avoid receiving this error, Genesys Info Mart requires that you leave the
cursor_sharing parameter set to
Genesys Info Mart requires that Interaction Concentrator release 7.5.000.22 or higher be installed. Several new features require Interaction Concentrator 7.6.000.20 or higher to be installed. See the Genesys Info Mart Deployment Guide for information about these new features.
If your Staging Area database uses Microsoft SQL Server 2000 Service Pack (SP) 4, you must add
trace flag 9059 to the SQL Server startup parameters. If you do not add this trace flag, the performance of the job that transforms extracted data (
Job_TransformGIM) is significantly degraded. For more information on trace flag, see the section describing how to use trace flag to revert to the behavior in SQL Server 2000 SP3 in the Microsoft fix document located at:
For deployments where Genesys Info Mart is installed on a 64-bit Windows operating system, and where Genesys Info Mart accesses Oracle databases, Genesys Info Mart requires you to install a Java Development Kit (JDK). If you are installing a 32-bit JDK for Genesys Info Mart on a 64-bit Windows operating system, the default installation folder is under
[drive_path]:\Program Files (x86)\ (for example:
C:\Program Files (x86)\). There is a known bug (3807408) in Oracle that causes authentication errors when the executable path contains parentheses. Genesys recommends installing the JDK using a folder that does not contain parentheses. Refer to Oracle MetaLink article 334528.1 for more information.
When Genesys Voice Platform (GVP) 7.5 is deployed in
Network mode, the
CallUUID attribute is not present in the reporting events that are sent to GVP Voice Application Reporter (VAR). As a result, your report queries are not able to connect the data in the
GVP_CALL_FACT table to the
INTERACTION_FACT table because Genesys Info Mart will not use the
CallUUID attribute to populate
INTERACTION_ID in the
GVP_CALL_FACT table. This limitation does not exist when using GVP 7.6.
Installing the Sun JDK may enable the Java Update feature for the included Java Runtime Environment (JRE). This automatic update feature may cause new versions of Java to be automatically installed, changing the
PATH environment variable. Genesys recommends that you disable the automatic update feature. Please refer to the Sun JDK documentation for specific instructions about using the Java Control Panel and the Java Update feature.
If a customer abandons a chat session while queued in a virtual queue, Interaction Server 7.5 will generate an
EventDiverted event rather than an
EventAbandoned event. As a result, Genesys Info Mart will not correctly reflect
Chats Abandoned While in Queue information for virtual queue chat scenarios. This limitation does not exist when using Interaction Server 7.6. (ER# 108394724)
Genesys Outbound Notification (OBN) Manager does not attach the
GSW_CALL_ATTEMPT_GUID key-value pair when reporting a negative call result (for example—busy, no answer, system information tone) to Outbound Contact Solution server. As a result, your report queries are not able to connect the
CONTACT_ATTEMPT_FACT table rows that represent failed contact attempts to their corresponding
INTERACTION_FACT table rows because Genesys Info Mart cannot use the
GSW_CALL_ATTEMPT_GUID to populate
INTERACTION_ID in the
Top of Page