I listed important ICON alarms below to be configured in every environment to reduce data loss for reporting application
|Detect Event||Alarm Condition||Description|
|09-25005||ICON_DATABASE_QUEUE_ERROR||Database queue [ID]: database error received: status [errnum], description: [errtxt]
Identifier of the database queue. One of the following values: CFG, GCC, GLS, GOS, or GUD.
The database error status number as reported by Database Server.
The database error description as reported by Database Server
The error may be triggered by internal conditions on your SQL Server, such as temporary unavailability or exhaustion of the disk space. Interaction Concentrator will try to resubmit failed transactions until SQL Server returns a positive response.
|09-25012||ICON_PERSISTENT_QUEUE_ERROR||Persistent Queue operation error: [errtxt]
Persistent queue error description.
An error occurred during the operations with the persistent queue
Interaction Concentrator will rename the database that caused an error and recreate a new one. The problem database file should be sent to Genesys Technical Support.
|09-25131||ICON_CONFIG_SYNCH_REQUIRED||Configuration data inconsistency is detected; reason: [reason]. Waiting for customer command….
Specific details as to why data inconsistency is suspected.
Indicates that Interaction Concentrator has detected a discrepancy between the configuration data in Interaction Database (IDB) and Configuration Database
Use the Interaction Concentrator resynchronization functionality (in particular, the start-cfg-sync configuration option) to synchronize the configuration data in IDB with the data in Configuration Database. Make sure the resynchronization process is complete before you run your ETL engine to extract data from IDB
Cancel Event is 09-25017
|09-25024||ICON_PRESERVE_ERROR||ICON cannot preserve or store the data: [errtxt]
Specific details regarding the error
Interaction Concentrator cannot preserve or store the data. There are many events that could cause ICON to generate this error, including operating systems errors, disk full, insufficient memory, system queue corruption, or internal software errors. Manual intervention is required
|09-25025||ICON_STORAGE_THRESHOLD_REACHED||Persistent storage backlog threshold reached: [errtxt]
Specific details regarding the backlog
Using the pq-backlog-alarm-threshold configuration option, you have defined a threshold that ICON is to observe when it is unable to write records to IDB. If this event appears, this limit has been reached and ICON can no longer backlog records to memory.
It is common for ICON to log this event following 09-25024
One of the configured backlog thresholds of persistent storage has been reached.
The amount of time it takes to clear the backlog depends on how much data from the abnormal condition must be flushed.