Cisco Bug: CSCua85003 - Purge getOldestDate should remove tables not dependent on time
Jan 04, 2013
- Cisco Unified Contact Center Express
Known Affected Releases
Symptom: Under Load Conditions, when scheduled purge kicks off as a result of Database size getting exceeded beyond the threshold - The oldest date of purge does not get altered after purge has been performed. This results in Purge doing the deletion on the same range of data effectively not deleting any records. Conditions: Load condition and Historical Database size should exceed the configured threshold limits.
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