CAUSE 1
This issue can be caused by the following:
There might be a temporary delay issue due to network latency or the load on the primary or secondary replica.
Each of the described reason might cause an alarm that might seem false.
CAUSE 2
The alarm raised does not check the database role.
RESOLUTION 1
Review the following
RESOLUTION 2
WORKAROUND
None
STATUS
This issue was logged as FOG-207 and has been fixed in the 6.0 and higher releases of the SQL Server cartridge.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. 이용 약관 개인정보 보호정책 Cookie Preference Center