Skip to Content
Jul 15, 2019 at 09:50 AM

SAP LaMa 3.0 Std reporting DBStatus read-only in SQL AOAG



Our SAP R/3 landscape is built on MS Windows 2012r2 / MS SQL server 2012r2. For Pre-Production and Production we use MS SQL Always-On Availability Group clusters to provide highly available database and Central Instance services.
When connecting SAP LaMa to the database nodes, the databases are discovered, but as per design only the Active node is allowed to be Read-Write and the Passive node is Read-only.
This configuration is reported as a warning in SAP LaMa.

I would prefer not to suppress the DBSTATUS metric, but I do not see any other way to avoid the warnings.
Is there a better way?
Does anyone else use this configuration? How do other people handle this scenario?


Daren Addison.