Managing Serviceguard Extension for SAP, December 2007

Understanding Serviceguard Extension for SAP
Combining SGeSAP with Complementary Solutions
Chapter 1 45
• Results are provided in a report. Output format of this report may be
HTML or ASCII.
• Output reports may contain error interpretation text in order to help
during interpretation of the compare.
• All resources configured in a package may be easily added to the
resource DB by using the statement ANALYSE PACKAGE upon creation
of the Resource DB.
• It is possible to suppress acknowledged error messages. Changes in a
cluster setup, which may be OK, and may be acknowledged by
implementing an entry in an error exclusion table in order to
suppress them. No trigger to external systems would be created on
suppressed messages.
• The Cluster Consistency Monitor detects and reports all kinds of
setup problems of the monitor itself.
• The operation of the cluster monitor does not impact applications,
which are currently running due to the resource consumption of the
monitor is very low. Typically, the comparator takes less than 10
seconds in comparing two nodes, which includes the creation of the
resource DB.
• The use of the Cluster Consistency Monitor avoids fail over tests.
Due to the fact, that on a fail over test, only the startup of the
package on a secondary node is examined, potential problems which
may arise in case the application runs for a longer period on that
node are not recognized. The Cluster Consistency Monitor detects
even that class of problems as it simulates the view an application
would have toward the configurations of operating systems.
• The storage format of the resource DB is very dense. It allows fast
transfer even over wide area networks. Due to that density, memory
consumption during the comparator run or storage consumption for
the resource DB is very low.