Reporting levels, Special reports, Reporting levels special reports – HP PolyServe Software User Manual
Page 6

Advanced I/O Monitoring
3
Reporting Levels
The Core Reporting Elements can be provided at the following levels:
• Cluster-Wide Level
Provides aggregate information for all database instances on all nodes.
• Database Global Level
Limits information to a named database (e.g.,
PROD, DEV, FIN, DSS
).
• Instance Level
Limits information to a named instance (e.g., P
ROD1, PROD8, DEV1, FIN4,
DSS_6
).
• Node Level
Limits information to a named node (e.g., rac1.acme.com, rac6.acme.com).
This information is the aggregate of all instance activity on the named node. In
the case where a node hosts instances accessing different databases (e.g.,
$ORACLE_SID=PROD1
,
$ORACLE_SID=DEV1
), the Core Reporting Elements will
reflect the combined information for all instances on the named node.
Special Reports
Because MxODM has intimate understanding of Oracle file, process, and I/O
types, the mxodmstat(8) command offers very specialized reporting capabilities.
On complex clustered systems, it is nearly impossible to take a quick look at the
cluster-wide or per-instance activity for a given subsystem of the Oracle Server.
For instance, on an 8-node cluster with six
PROD
instances, two Dev instances,
and Parallel Query Slaves (PQO) active on only nodes 1 through 4 on the
PROD
database, a DBA will find it extremely difficult to associate cluster-wide impact to
the PQO activity. Likewise, quickly determining the
DBWR
activity for only the
PROD
instances on nodes 1 through 6 is nearly impossible—without MxODM.
MxODM offers “canned” reporting that focuses on the following key Oracle
“subsystems:”
• Parallel Query Option (PQO). This query returns the Core Reporting Elements
for only the Parallel Query Option slaves (e.g., ora_p000_PROD1,
ora_p001_PROD3, etc.). This is an extremely beneficial set of information as it