Registration

Dear SAP Community Member,
In order to fully benefit from what the SAP Community has to offer, please register at:
http://scn.sap.com
Thank you,
The SAP Community team.
Skip to end of metadata
Go to start of metadata

RZ20 - detailed information

This page provides detailed information about the SAP MaxDB/liveCache alert monitor (transaction RZ20).

Release information
How it works
Which collector gets which information?
What is to do if some nodes have obsolete values?


Release information

The information on this page is valid for:

  • the basis database of the SAP System as of SAP Release 4.6C SP 46, 4.6D SP 36, 6.10 SP 38, 6.20 SP 33 and >= 6.40
  • SAP liveCache/ remote SAP MaxDB databases as of SAP Release 4.6C SP 40, 4.6D SP 29, 6.10 SP 28, 6.20 SP 16 and >= 6.40

back to top

How it works

In the SAP MaxDB/liveCache alert monitoring trees in transaction RZ20 there is no data collection method assigned to each node. Instead 4 different data collectors exist which run in different time intervals to collect the required information for the different nodes. These collectors were implemented because several nodes get their information from the same database tables. It is faster to collect the data from these tables with one select and to update the status of several nodes at once than to select the same table for each node again.

back to top

Which collector gets which information?

Data collector A (highest runtime frequency)

The predefined runtime interval of this collector is 5 minutes (300 seconds).
It collects and reports the data for the following nodes of the SAP MaxDB/liveCache alert monitoring tree, if they are visible:

  • Properties
    • State
      • Current State (dbmrfc command db_state)
      • Update Possible (table DB_STATE)
      • Last Stop (table DB_STATE)
      • Last Restart (table SYSDD.SERVERDB_STATS)
      • Last Checkpoint (table INTERNAL_STATE)
  • Space Management
    • Data Area
      • Total Data Space (table SERVERDBSTATISTICS)
      • Free Data Space (table SERVERDBSTATISTICS - in case of db_full: table SYSDD.SERVERDB_STATS)
      • Used Data Space (table SERVERDBSTATISTICS)
    • Log Area
      • Total Log Space (table SERVERDBSTATISTICS)
      • Free Log Space (table SERVERDBSTATISTICS- in case of log_full: table SYSDD.SERVERDB_STATS)
      • Used Log Space (table SERVERDBSTATISTICS)
      • Log Writing (table DB_STATE)
      • Autosave Log (state: table INFO_STATE; whether it should be on or off: tables SDBAHSDB and SERVERDBSTATISTICS)
      • Last Log Page Number (table INTERNAL_STATE)
      • Last Log I/O Sequence Number (table INTERNAL_STATE)
  • Performance
    • User Tasks
      • Connect Wait (table DOMAIN.SYSMON_US)
    • Monitor
      • OMS Memory Analysis (table DB_STATE)
      • Database Trace (table DB_STATE)
  • Health
    • Bad Indexes
      • Number of Bad Indexes (table DB_STATE)

back to top

Data collector B (high runtime frequency)

The predefined runtime intervalof this collector is 15 minutes (900 seconds).
This collector

  1. updates the information in table SDBAHSDB:
    1. loads data of directory DBAHIST into table SDBAHSDB (backup actions, verify with dbmcli, ...)
    2. loads update statistics entries of table SDBAH into table SDBAHSDB
    3. loads update statistics and verify entries of table SDBAADAUPD into table SDBAHSDB
    4. SAP Release 4.6C to 6.40: deletes entries in table SDBAHSDB which are older than three months

Then it collects and reports the data for the following nodes of the SAP MaxDB/liveCache alert monitoring tree, if they are visible:

  • Properties
    • State
      • Current State (dbmrfc command db_state)
  • Space Management
    • Memory
      • Data Cache Usage - total (table MONITOR_CACHES)
      • Data Cache Usage - OMS Data (table MONITOR_CACHES)
      • Data Cache Usage - SQL Data (table MONITOR_CACHES)
      • Data Cache Usage - History/Undo (table MONITOR_CACHES)
      • Data Cache Usage - OMS History (table MONITOR_CACHES)
      • Data Cache Usage - OMS Rollback (table MONITOR_CACHES)
      • Out Of Memory Exceptions (table SYSDBA.MONITOR_OMS)
      • OMS Terminations (table SYSDBA.MONITOR_OMS)
      • Heap Usage (table OMS_HEAP_STATISTICS)
      • Heap Usage in KB (table OMS_HEAP_STATISTICS)
      • Maximum Heap Usage in KB (table ALLOCATORSTATISTICS)
      • System Heap in KB (table ALLOCATORSTATISTICS)
      • Parameter OMS_HEAP_LIMIT (KB) (dbmrfc command param_getvalue OMS_HEAP_LIMIT)
  • Performance
    • Caches
      • Data Cache Hitrate - total (table MONITOR_CACHES)
      • Data Cache Hitrate - OMS Data (table MONITOR_CACHES)
      • Data Cache Hitrate - SQL Data (table MONITOR_CACHES)
      • Data Cache Hitrate - History/Undo (table MONITOR_CACHES)
      • Data Cache Hitrate - OMS History (table MONITOR_CACHES)
      • Data Cache Hitrate - OMS Rollback (table MONITOR_CACHES)
      • Catalog Cache Hitrate (table MONITOR_CACHES)
      • Rollback Cache Hitrate (table MONITOR_CACHES)
      • Converter Cache Hitrate (table MONITOR_CACHES)
    • Monitor
      • Age of Oldest OMS Version (table DB_STATE)
      • Log Queue Overflows (table MONITOR)
      • Log Queue Overflows in % (table MONITOR)
    • Optimizer Statistics
      • Last Collection (table SDBAHSDB)
      • Last Collection Type (table SDBAHSDB)
  • Health
    • Database Structure Check
      • Last Successful Check (table SDBAHSDB)
      • Last Check Return Code (table SDBAHSDB)
      • Last Check Type (table SDBAHSDB)
  • External Analysis Tools
    • Database Analyzer
      • Status Database Analyzer (dbmrfc command dban_state)
      • Configuration File (dbmrfc command dban_state)
      • Log Directory (dbmrfc command dban_state)
      • Interval (dbmrfc command dban_state)
      • Started at (dbmrfc command dban_state)
  • Backup/Recovery
    • Last Backup
      • Last Successful Complete Data Backup (table SDBAHSDB)
      • Last Complete Data Backup Return Code (table SDBAHSDB)
    • Last Recovery
      • Last Restore Data (table SDBAHSDB)

back to top

Data collector C (medium runtime frequency)

The predefined runtime interval of this collector is 4 hours (14,400 seconds).
It collects and reports data for the following nodes of the SAP MaxDB/liveCache alert monitoring tree, if they are visible:

  • Properties
    • State
      • Current State (dbmrfc command db_state)
  • liveCache Applications
    • General
      • APO System Name (table LCALERTS)
      • APO Release Version (table LCALERTS)
      • LCApps Version (table LCALERTS)
      • Number of Work Processes (table LCALERTS)
    • Connections
      • LCA (table LCALERTS)
      • LDA (table LCALERTS)
      • LEA (table LCALERTS)
    • Periodic Jobs and Administration Reports (in an SCM system)
      • /SAPAPO/OM_REORG_DAILY (table LCALERTS)
      • /SAPAPO/OM_DELETE_OLD_SIMSESS (table LCALERTS)
      • /SAPAPO/DELETE_LC_ANCHORS (table LCALERTS)
    • Periodic Jobs and Administration Reports (in an AP system)
      • /LCAP/REORG_DAILY (table LCALERTS)
      • /LCAP/DELETE_OLD_SIMS (table LCALERTS)
      • SLCA_INIT_FOLLOW_UP (table LCALERTS)
    • Tracing
      • Number of Active Traces (table LCALERTS)
      • Number of Active Checks (table LCALERTS)
    • Miscellaneous
      • Critical Logging Event (table LCALERTS)
      • RFC Connections (table LCALERTS)

back to top

Data collector D (low runtime frequency)

The predefined runtime interval of this collector is 24 hours (86,400 seconds).
It collects and reports data for the following nodes of the SAP MaxDB/liveCache alert monitoring tree, if they are visible:

  • Properties
    • State
      • Current State (dbmrfc command db_state)
    • Installation
      • Kernel Version (dbmrfc command param_directget KERNELVERSION)
      • DBM Server Version (dbmrfc command dbm_version)
      • Platform (dbmrfc command dbm_version)

back to top

Used tables

Tables SDBAHSDB, SDBAADAUPD and SDBAH are located in the database of the monitoring system. The other tables are system tables of the monitored database.

Attention: The information from which table the data is selected is intended for support issues only. The system tables might be changed without any warning so you should not create own scripts/programs based on these tables!

back to top

What is to do if some nodes have obsolete values?

If a node of the SAP MaxDB/liveCache alert monitor tree has an obsolete value the reason for this is most probably that the responsible data collector got an error and does not run regularly anymore.
You can check the collector state in transaction RZ20 as follows:

  • Choose SAP CCMS Technical Expert Monitors -> All Monitoring Contexts.
  • Open node MaxDB Monitoring: <connection_name> -> Collectors and Internal -> Collectors. Here you can see also, when the different collectors did run the last time.
  • Mark the corresponding collector and choose Display detail.
  • In column Runtime status you'll find the current status of the collector.

If the status of the collector is AL_TD_RUN_FATAL_ERROR this collector can not run automatically anymore until you reset the status.
To reset the collector state choose Edit -> Method Status -> Reset -> Data Collection Method.
Then the collector will run in the predefined interval again and update all corresponding nodes in the tree.

back to top