Release Advisory

Interaction Concentrator

8.0.x

Genesys Telecommunications Laboratories, Inc. © 2009

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.

Link to 7.6 Product Release Advisory

The following information applies to Genesys 8.0.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.


Under certain circumstances, Interaction Concentrator configured with the cfg role may report the following error:

Std 25024 ICON cannot preserve or store the data: '[SQLITE] Error [1], text [cannot start a transaction within a transaction]'

If you receive the above error message, restart Interaction Concentrator and perform the resynchronization of configuration data. Refer to the Interaction Concentrator 8.0 User's Guide for resynchronization instructions. (ER# 179674419)


For large configuration environments, Genesys strongly recommends that a separate Interaction Concentrator instance be dedicated to handling configuration data. That is, this application should only have the cfg value for the role configuration option. (ER# 188354093)


When ICON is working in an environment with Configuration Server release 7.5, 7.6, or 8.0, keep in mind the following. Through its configuration history log mechanism, Configuration Server sends no more than 1000 notifications about changes in configuration data. This limits ICON's ability to identify missing configuration data when the number of changes exceeds 1000 during the ICON shutdown period. If you are performing heavy configuration updates while ICON is down, perform the resynchronization of configuration data immediately after the restart of ICON. Refer to the Interaction Concentrator 8.0 User's Guide for resynchronization instructions.


In Configuration Server 7.2, the precise time when configuration objects changed was not preserved in its history log. As a result, when changes in configuration were restored from Configuration Server's history log, the timestamp of such changes was not captured correctly in IDB. This situation occurred upon ICON disconnection from Configuration Server. This issue has been corrected in Configuration Server release 7.5. Refer to Configuration Server Release Notes or contact Genesys Technical Support for information on the current Generally Available version of Configuration Server.


Oracle Corporation provides a patch to address an Oracle limitation. On certain versions of Oracle, data writing requests may be processed incorrectly in configurations where two or more ICON instances are configured to write to two or more schemas created in one database. If your ICON environment is configured in this manner, Genesys recommends that you install this patch to avoid the possibility of ICON sending data to the wrong schema. Review the "Product Advisory for Interaction Concentrator 7.x and 8.x," issued on August 15, 2007, and updated on December 16, 2009, that is available on the Genesys Technical Support website, for more information about the specific versions of Oracle impacted and where you can get the patch. (ER# 31662487)


For 8.x releases, you can use a Microsoft Remote Desktop connection to install its components. Previously, for 7.x releases, Genesys did not recommend using it.


If you are using Interaction Concentrator 8.0 in an environment where Open Media interactions are processed, and where Genesys Info Mart release 7.5 is also deployed, do the following:


It is important for Genesys Info Mart users to review Genesys Info Mart documentation prior to deploying Interaction Concentrator and Interaction Database, to identify all dependencies. Please review the Genesys Info Mart 7.6 Deployment Guide, and the Deployment Procedure document for your particular release, if applicable.


Top of Page