Reason: Under certain conditions, Interaction Database (IDB) data can fall out of synchronization with Configuration Server data. If this happens, Interaction Concentrator (ICON) instances and downstream reporting applications that rely on ICON data can produce results that are difficult to interpret. Under such conditions, you might consider resynchronizing IDB with the current configuration data. 

How to Resynchronize Configuration Data 

By default, Interaction Concentrator resynchronizes with Configuration Server every time it starts. However, you may need to manually resynchronize ICON and Configuration Server, as discussed in the following section. 

If you must resynchronize your configuration data in IDB, do the following while ICON is running: 

1. Verify that the ICON application with the role configuration option set to cfg, is started. 

2. In Genesys Administrator Extension, open the ICON Application and set the start-cfg-sync option to 0 on the Options tab. 

3. Save your update. 

4. Now change the option value set for the start-cfg-sync option to 1 on the Options tab. 

5. Apply this new setting. 

This action prompts Interaction Concentrator to start the resynchronization process. Once started, the resynchronization process continues until completion regardless of any subsequent changes to the option value. ICON logs a message when synchronization begins and when it completes. 

Important 

It does not suffice to pre-set the value of the start-cfg-sync option to 1 or to set it to any other nonzero value and then to 1. ICON starts synchronization only when it detects the change from 0 to 1. 

After ICON has retrieved all the data necessary for resynchronization from Configuration Server, ICON generates the following Standard-level log event: 

• 09-25017 Configuration objects are reloaded in IDB