It's clear from the case notes that there are capacity issues involved. The latest updates in the case about the DA sync failure, and the one about DA health degraded are the same as the cases are the same.
Those should be one support case, for the same problem.
It appears from the research in the cases that the systems are either:
- Not currently resourced appropriately for the size of the items it's working with.
- Maintaining too many inactive and/or retired items which are causing memory usage to be excessive as they are loaded into the DA memory for use when needed.
The logging messages noted in the cases clearly show memory related usage problems on a regular basis.
I suspect you may have a large number of inactive and/or retired items in the environment being loaded into memory and causing the issue. This is often seen when the DA data source is set to sync inactive items. If excessive numbers of QoS related items have been created it can cause similar symptoms.
I'd recommend following the steps provided in those cases, working with support to clean up the system of old deleted and/or retired items and components. Once some of the load is decreased or resources are increased I suspect the problems will start to dissipate.
If they don't, once the system is cleaned up and not showing capacity or memory problems, then whatever issue remains will be more readily found and resolved.
These are VM systems according to the notes. It is also possible that the resources for the VMs are shared, not dedicated. If shared other systems sharing the resources may be causing an issue. VM resources for these systems in production environments should always be dedicated to avoid resource contention issues with other VMs sharing the resources.