| Problem Summary |
DB Replication is not working correctly. Expert Advisor reports in CUIC shows entity (agent, assignment queue, etc.) ID numbers in place of entity names. |
| Error Message |
There are several possible methods of determining there is an issue with DB replication.
- In RTMT, view the Performance Tab > [SERVER_HOSTNAME]/Number of Replicates Created and State of Replication/Replicate_state
- If replication state does not equal "2" (healthy), then there is an error
- Check all of the servers. One may show a healthy status, but one or more of the other servers may show a status of "1" or "3" (not healthy).
- Check the output of the utils dbreplication status CLI command.
- Check the ercollect logs located in /common/download (requires root access). There will be *ifx* files (similar to [SERVER_HOSTNAME]_ifx_col_[DATE].tar), one file on each server (Primary Runtime, HA, and Reporting). Broken replication may show errors similar to:
Error returned 17 at 1031
Error returned 17 at 823
command failed -- participants required for operation specified (17)
|
| Possible Cause |
DB replication is out of synch. |
| Recommended Action |
Drop all replication data and re-synch DB replication.
From the CLI:
- Execute utils dbreplication stop on the Reporting Server and High Availability Server
- Execute utils dbreplication stop on the Primary Runtime Server
- Execute utils dbreplication dropadmin db on all servers
- Execute utils dbreplication reset all on the Primary Runtime Server
|
| Release |
Release 7.6(1) |
| Associated CDETS# |
None. |
