Warning: Oracle DB is not supported with current version
The Database Growth scenario allows monitoring several KPIs related to the growth of the database over an extended period of time (up to one year). It provides information about the current size of the DB and alerts the user whenever the fill level is close to 100% or if there is an anomaly in the database growth.
The following databases are supported:
- HANA (Standalone or within a Netweaver stack. Apply all the corrections listed in the Central Notes)
This information is displayed on the main tile:
- DB Size
- DB Fill level
- DB Growth trend
The first two values are based on yesterday’s values while the trend depends on the configuration (8 weeks or 12 months).
DB Size refers to the size of the database in the file system (i.e. the sum of the size of all data files or occupied plus free memory in the database).
For HANA Databases, the value refers to the size of the data volumes (files datavolume_*.dat). This can be retrieved from M_VOLUME_FILES table.
DB Fill level describes the percentage of space which is consumed within the DB (occupied memory / (occupied + free memory)).
For HANA Databases, this is the the percentage of used data (and shadow pages) within the data volume file (datavolume_*.dat). This information can be retrieved from the monitoring table M_VOLUME_FILES. The data volume file extends automatically when the percentage of used data is close to 97~98%. Therefore, in normal situations, it should never reach 100% unless the space on the file system is not enough to extend the file. On the other hand, a percentage too low could be an indication of a fragmentation that could be fixed using the ALTER SYSTEM RECLAIM DATAVOLUME command. See SAP Note 1870858.
Trend shows the DB growth in the last week or month (depending on the configuration).
The Detailed View
The detail view provides the charts DB Growth and DB Size. The database size shows the amount of occupied and free memory.
Database Growth is the difference of the Occupied Memory value in two different time periods.
- DB_SIZE :
In fact DB size = occupied size + free size = 204.788 + 27.661 = 232.445
Using the RSRT1 transaction code and the 0HDB_MP05_Q0010 for HANADB and 0DBH_MP01_Q0030 for other DB types (ORA, DB2, etc).
After choosing the right filters, the returned result is :
We can validate the DB Size with this formula
Database size = Total Size / 1.024 = 238.024 / 1.024 = 232.445
- DB_FILL_LVL :
Using the RSRT1 transaction code and the 0HDB_MP05_Q0010 for HANADB and 0DBH_MP01_Q0030 for other DB types (ORA, DB2, etc):
After filtering on the database name and the system ID, the returned result is :
- DATABASE_TREND :
After choosing the right filters, the returned results are :
We can validate the DB Growth trend with this formula
Database growth of September 2018 = Used size of September 2018 - Used size of August 2018 = 217.789 - 212.796 = 4.993
Removed the statement about missing DB Growth in MSSQL. This is supported now.