Cisco Bug: CSCtb63064 - Syslog error message/alarm for DB Connect error not logged immediately
Feb 28, 2013
- Cisco Unified Communications Manager IM & Presence Service
- Cisco Unified Presence Version 8.0
Known Affected Releases
Symptom: An external DB was configured for compliance and then it was verified that the IM's were properly being logged into it. Then the network cable to the external db box was unplugged(11:18 AM) . Syslog did not show any alarms immediately. Later when one user sent an IM, there was an odbcconnection error reported to the syslog(11:23 AM, still no external DB connect Error alarm). At 11:28 when another user sent an IM the XCPExternalDBConnectError was reported to syslog. When the cable was plugged back in, the informational alarm telling that the connection was restored was displayed only after IM exchange and not immediately. Also it was logged as an error alarm in the RTMT tool and UNKNOWN_ALARM in CiscoSyslog. In short, the condition is detected only after the "next" DB access after the DB is unavailable or restored. It is desired that the condition be detected on the failure...not the next DB attempt after the failure. Conditions: CUP server running 8.0(1) or greater with an external DB configured.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases