Reference: Database Monitoring Parameters

If the predicted point in time when the data area is exceeded is within the upcoming ADADataExCrit hours, the check status of ADA_DATAAREA is set to Critical.

If the predicted point in time when the data area is exceeded is within the upcoming ADADataExWarn hours, but not within the upcoming ADADataExCrit hours, the check status of ADA_DATAAREA is set to Warning, unless the ADADataUsageCrit threshold is exceeded.

Defines whether the forecasting algorithm is active or inactive. See Forecasting for more information.

If the data area usage exceeds the ADADataUsageCrit threshold, the check status is set to Critical.

You can define the threshold either in the percentage of the total size of the resource, or in KB, MB, or GB values of the remaining free space. In the first case, the parameter gets effective if the usage measured in % of the total space is higher than the defined threshold. In the second case, the parameter gets effective if the remaining free space is lower than the defined threshold.

If data area usage exceeds the ADADataUsageWarn threshold, but does not exceed the ADADataUsageCrit threshold, the check status is set to Warning, unless the data area is exhausted in less than ADADataExCrit hours.

You can define the threshold either in the percentage of the total size of the resource, or in KB, MB, or GB values of the remaining free space. In the first case, the parameter gets effective if the usage measured in % of the total space is higher than the defined threshold. In the second case, the parameter gets effective if the remaining free space is lower than the defined threshold.

If the predicted point in time when the log area is exceeded is within the upcoming ADALogExCrit hours, the check status of ADA_LOGAREA is set to Critical.

If the predicted point in time when the log area is exceeded is within the upcoming ADALogExWarn hours, but not within the upcoming ADALogExCrit hours, the check status of ADA_LOGAREA is set to Warning, unless the ADALogUsageCrit threshold is exceeded.

Defines whether the forecasting algorithm is active or inactive. See Forecasting for more information.

If the log area usage exceeds the ADALogUsageCrit threshold, the check status is set to Critical.

You can define the threshold either in the percentage of the total size of the resource, or in KB, MB, or GB values of the remaining free space. In the first case, the parameter gets effective if the usage measured in % of the total space is higher than the defined threshold. In the second case, the parameter gets effective if the remaining free space is lower than the defined threshold.

If log area usage exceeds the ADALogUsageWarn threshold, but does not exceed the ADALogUsageCrit threshold, the check status is set to Warning, unless the data area is exhausted in less than ADADataExCrit hours.

You can define the threshold either in the percentage of the total size of the resource, or in KB, MB, or GB values of the remaining free space. In the first case, the parameter gets effective if the usage measured in % of the total space is higher than the defined threshold. In the second case, the parameter gets effective if the remaining free space is lower than the defined threshold.

If the last successful full backup run is older than ANYBackupFullCritAge days, the check status is set to Critical.

If the last successful full backup run is older than ANYBackupFullWarnAge days, but still below ANYBackupFullCritAge, the check status is set to Warning.

ANY_Backup looks for ANYBackupSelectRange days back to find maintenance reports of backups. The default value is 60 days, so usually, there is no need to change this parameter since backups must be made far more often.

If the number of connections to the database exceeds ANYConnectionsNumCrit, the check status of ANY_Connections is set to Critical.

If the number of connections to the database exceeds ANYConnectionsNumWarn, but is still below ANYConnectionsNumCrit, the check status of ANY_Connections is set to Warning.

If the predicted point in time when the dbspace is exceeded is within the upcoming ANYDBExCrit hours, the check status of ANY_DBSpaces is set to Critical.

If the predicted point in time when the dbspace is exceeded is within the upcoming ANYDBExWarn hours, but not within the upcoming ANYDBExCrit hours, the check status of ANY_DBSpaces is set to Warning, unless the ANYDBUsageCrit threshold is exceeded.

Defines whether the forecasting algorithm is active or inactive. See Forecasting for more information.

If the dbspace usage exceeds the ANYDBUsageCrit threshold the check status is set to Critical.

You can define the threshold either in the percentage of the total size of the resource, or in KB, MB, or GB values of the remaining free space. In the first case, the parameter gets effective if the usage measured in % of the total space is higher than the defined threshold. In the second case, the parameter gets effective if the remaining free space is lower than the defined threshold.

If the data space usage of a database exceeds the ANYDBUsageWarn threshold the check status is set to Warning, unless the ANYDBUsageCrit threshold is exceeded.

You can define the threshold either in the percentage of the total size of the resource, or in KB, MB, or GB values of the remaining free space. In the first case, the parameter gets effective if the usage measured in % of the total space is higher than the defined threshold. In the second case, the parameter gets effective if the remaining free space is lower than the defined threshold.

If the predicted point in time when the transaction log space is exceeded is within the upcoming ANYLogExCrit hours, the check status of ANY_TransLog is set to Critical.

If the predicted point in time when the transaction log space is exceeded is within the upcoming ANYLogExWarn hours, but not within the upcoming ANYLogExCrit hours, the check status of ANY_TransLog is set to Warning, unless the ANYLogUsageCrit threshold is exceeded.

Defines whether the forecasting algorithm is active or inactive. See Forecasting for more information.

If the transaction log space usage exceeds the ANYLogUsageCrit threshold, the check status is set to Critical.

You can define the threshold either in the percentage of the total size of the resource, or in KB, MB, or GB values of the remaining free space. In the first case, the parameter gets effective if the usage measured in % of the total space is higher than the defined threshold. In the second case, the parameter gets effective if the remaining free space is lower than the defined threshold.

If the transaction log space usage of a database exceeds the ANYLogUsageWarn threshold, the check status is set to Warning unless the ANYLogUsageCrit threshold is exceeded.

You can define the threshold either in the percentage of the total size of the resource, or in KB, MB, or GB values of the remaining free space. In the first case, the parameter gets effective if the usage measured in % of the total space is higher than the defined threshold. In the second case, the parameter gets effective if the remaining free space is lower than the defined threshold.

Defines a Critical threshold for the ANY_Messages check. The check status will be Critical if the number of not excluded server messages with severity ERR is equal to or above ANYMessagesNumCrit.

Defines a Warning threshold for the ANY_Messages check. ANYMessagesNumWarn behaves exactly as ANYMessagesStatNumWarn, except that it configures daily check ANY_Messages

ANYMessagesExclude does exactly the same as ANYMessagesStatExclude, except that it configures daily check ANY_Messages. Please see documentation of ANYMessagesStatExclude below.

You can use this parameter to exclude certain server messages from being evaluated in ANY_MessagesStat check. There are two types of exclude specifications: a simple one, which filters on the server message text only, and an advanced one, which must be specified in the format msg_severity|msg_category|msg_text. A server message must match all three items of a fully-featured exclude specification to be excluded. Multiple exclude specifications must be separated by semicolon ;. Leading and trailing white spaces before or after the semicolon ; or pipe | character are gently ignored.

You may use wildcards * or ? to specify the server message text.

Defines a Critical threshold for the ANY_MessagesStat check. ANYMessagesStatNumCrit behaves exactly as ANYMessagesNumCrit, except that it configures RealTime Monitoring check ANY_MessagesStat.

Defines a Warning threshold for the ANY_MessagesStat check. The check status will be Warning if the number of not excluded server messages with severity ERR or WARN is equal to or above ANYMessagesStatNumWarn, unless the number of messages with severity ERR is equal to or above ANYMessagesStatNumCrit.

RealTime Monitoring check ANY_MessagesStat is designed to recover from check status Warning or Critical, so the check looks back for a time span defined by ANYMessagesStatTimespan only.

AutoChangeDetectionIgnore is used to exclude parameters from System Change Auto Detection. If, for example, a parameter value changes regularly and this behavior is well-known, you may add the parameter to the exclude list. The parameter value is still updated in the Avantra Database, but no change record will be created. Since there are several change detection objects, you must prefix the list with a keyword to indicate the object type.

For Databases, only DBPARAM is currently supported. Wildcard * is supported to define multiple parameters, e.g. DBPARAM: *MEMORY*, CPU_COUNT

If the last successful Backup is older than BackupAgeCrit days, the check status is set to Critical. You can define override this value on a per-day level using the corresponding Monitoring Exception Parameter.

If the last successful Backup is older than BackupAgeWarn days, but not older than BackupAgeCrit days, the check status is set to Warning. You can define override this value on a per-day level using the corresponding Monitoring Exception Parameter.

This parameter defines the time period (in hours) after which a Warning or Critical DB2_BACKUPSTAT or ORA_BRBACKUPSTAT check status are set back to Ok. This is to avoid showing the Warning or Critical condition all the time.

Defines the time interval between two DB2_BACKUPSTAT checks. By default the check runs in the BASIC cycle.

Defines the maximum age for the DB2 cost based optimizer statistics update where statistics are considered as up to date. DB2_CBO_STATS counts the number of tables/indexes not older than DB2CBOMaxAge. You may adapt this parameter if your CBO update runs are scheduled more or less frequently.

If the number of tables or indexes with statistics not older than DB2CBOMaxAge days is below DB2CBONumEntriesUpdCrit, DB2_CBO_STATS result will be Critical.

If the number of tables or indexes with statistics not older than DB2CBOMaxAge days is below DB2CBONumEntriesUpdWarn but not below DB2CBONumEntriesUpdCrit, the DB2_CBO_STATS result will be Warning.

You may set this parameter if the monitoring Avantra Agent has no access to the filesystem holding the DB2 installation, e.g. if you are using Agentless Monitoring.

In this case, the DB2_FSLOGARCH and DB2_DIAGLOG checks are not executed.

Defines a Critical threshold for the DB2_DIAGLOGcheck. The check status will be Critical if that many log entries considered as critical are found.

Defines a Warning threshold for the DB2_DIAGLOG check. The check status will be Warning if that many log entries considered as warning are found unless the DB2DiagLogCountCrit critical threshold is exceeded.

Designates an entry in the DB2 diagnostics log as critical.

Designates an entry in the DB2 diagnostics log as warning.

Consider only the last DB2DiagLogTimeSpan minutes of the log file.

Programs executing SQL statements on this list are not considered for the check result. Wildcard * is allowed. Multiple entries must be separated by ` ` (space). If your statement includes a space character, please escape it with a backslash \.

Defines whether or not excluded statements, which will not contribute to the check result, are displayed.

If for a particular SQL statement the amount of logical reads exceeds DB2ExpSQLLogicalReadCrit percent of the total number of reads of all statements, the check turns to Critical.

If for a particular SQL statement the amount of logical reads exceeds DB2ExpSQLLogicalReadWarn percent of the total number of reads of all statements but does not exceed DB2ExpSQLLogicalReadCrit, the check turns to Warning.

If for a particular SQL statement the amount of physical reads exceeds DB2ExpSQLPhysicalReadCrit percent of the total number of reads of all statements, the check turns to Critical.

If for a particular SQL statement the amount of physical reads exceeds DB2ExpSQLPhysicalReadWarn percent of the total number of reads of all statements but does not exceed DB2ExpSQLPhysicalReadCrit, the check turns to Warning.

If the usage of file systems where the DB2 active log directories are located exceeds the DB2FSLogActiveCrit threshold, the check status is set to Critical.

The file systems of the active logs are taken from the DB2 parameters logpath and mirrorlogpath.

You can define the threshold either in the percentage of the total size of the resource, or in KB, MB, or GB values of the remaining free space. In the first case, the parameter gets effective if the usage measured in % of the total space is higher than the defined threshold. In the second case, the parameter gets effective if the remaining free space is lower than the defined threshold.

If the usage of file systems where the DB2 active log directories are located exceeds the DB2FSLogActiveWarn threshold, the check status is set to Warning but only if the status is not Critical due to DB2FSLogActiveCrit.

The file systems of the active logs are taken from the DB2 parameters logpath and mirrorlogpath.

You can define the threshold either in the percentage of the total size of the resource, or in KB, MB, or GB values of the remaining free space. In the first case, the parameter gets effective if the usage measured in % of the total space is higher than the defined threshold. In the second case, the parameter gets effective if the remaining free space is lower than the defined threshold.

If the log archive filesystem usage exceeds the DB2FSLogArchCrit threshold the check status is set to Critical. The log archive filesystem is discovered automatically by Avantra Agent.

You can define the threshold either in the percentage of the total size of the resource, or in KB, MB, or GB values of the remaining free space. In the first case, the parameter gets effective if the usage measured in % of the total space is higher than the defined threshold. In the second case, the parameter gets effective if the remaining free space is lower than the defined threshold.

If the predicted point in time when the filesystem limit is exceeded is within the upcoming DB2FSLogArchExCrit hours, the check result of DB2_FSLOGARCH is set to Critical.

If the predicted point in time when the filesystem limit is exceeded is within the upcoming DB2FSLogArchExWarn hours, but not within the upcoming DB2FSLogArchExCrit hours, the check result of DB2_FSLOGARCH is set to Warning, unless the DB2FSLogArchExCrit threshold is exceeded.

Defines whether the forecasting algorithm is active or inactive. See Forecasting for more information.

If the log archive filesystem usage exceeds the DB2FSLogArchWarn threshold, but does not exceed the DB2FSLogArchCrit threshold, the check status is set to Warning.

You can define the threshold either in the percentage of the total size of the resource, or in KB, MB, or GB values of the remaining free space. In the first case, the parameter gets effective if the usage measured in % of the total space is higher than the defined threshold. In the second case, the parameter gets effective if the remaining free space is lower than the defined threshold.

If the predicted point in time when the log space limit is exhausted is within the upcoming DB2LogExCrit hours, the check result of DB2_LOGUSAGE is set to Critical.

If the predicted point in time when the log space limit is exhausted is within the upcoming DB2LogExWarn hours, but not within the upcoming DB2LogExCrit hours, the check result of DB2_LOGUSAGE is set to Warning.

Defines whether the forecasting algorithm is active or inactive. See Forecasting for more information.

If the log space exceeds the DB2LogUsageCrit threshold, the check status is set to Critical.

You can define the threshold either in the percentage of the total size of the resource, or in KB, MB, or GB values of the remaining free space. In the first case, the parameter gets effective if the usage measured in % of the total space is higher than the defined threshold. In the second case, the parameter gets effective if the remaining free space is lower than the defined threshold.

If the log space exceeds the DB2LogUsageWarn threshold, but does not exceed the DB2LogUsageCrit threshold, the check status is set to Warning.

You can define the threshold either in the percentage of the total size of the resource, or in KB, MB, or GB values of the remaining free space. In the first case, the parameter gets effective if the usage measured in % of the total space is higher than the defined threshold. In the second case, the parameter gets effective if the remaining free space is lower than the defined threshold.

If the number of transaction log files located in the Failover Archive Path directory is above {DB2NumFailArchLogsCrit}, the check status is set to Critical. The _Failover Archive Path directory is taken from the DB2 parameter failarchpath.

If the number of transaction log files located in the Failover Archive Path directory is above DB2NumFailArchLogsWarn but below DB2NumFailArchLogsCrit, the check status is set to Warning. The Failover Archive Path directory is taken from the DB2 parameter failarchpath.

If the predicted point in time when the tablespace limit is exceeded is within the upcoming DB2TableSpaceExCrit hours, the check result of DB2_TABLESPACES is set to Critical.

If the predicted point in time when the tablespace limit is exceeded is within the upcoming DB2TableSpaceExWarn hours, but not within the upcoming DB2TableSpaceExCrit hours, the check result of DB2_TABLESPACES is set to Warning, unless the DB2TableSpaceUsageCrit threshold is exceeded for some tablespace.

Defines whether the forecasting algorithm is active or inactive. See Forecasting for more information.

If the use of one of the database tablespaces exceeds the DB2TableSpaceUsageCrit threshold, the check status is set to Critical.

You can define the threshold either in the percentage of the total size of the resource, or in KB, MB, or GB values of the remaining free space. In the first case, the parameter gets effective if the usage measured in % of the total space is higher than the defined threshold. In the second case, the parameter gets effective if the remaining free space is lower than the defined threshold.

If the use of one of the database tablespaces exceeds the DB2TableSpaceUsageWarn threshold, but none of them exceeds the DB2TableSpaceUsageCrit threshold, the check status is set to Warning, unless the DB2TableSpaceExCrit threshold is exceeded for some tablespace.

You can define the threshold either in the percentage of the total size of the resource, or in KB, MB, or GB values of the remaining free space. In the first case, the parameter gets effective if the usage measured in % of the total space is higher than the defined threshold. In the second case, the parameter gets effective if the remaining free space is lower than the defined threshold.

Starting from DBConnectErrsCrit failed database connection attempts the check status will turn from Warning to Critical.

Usually, the <Avantra Agent automatically determines the URL to connect to the Database. In case the automatically determined URL does not work properly, you may override it using this parameter.

Available interpolations (macros):

Maximum number of rows to return from table M_ADMISSION_CONTROL_EVENTS.

Define if the check result shall be reported as Warning or Critical status.

Configure how far in the past we are looking for entries in table M_ADMISSION_CONTROL_EVENTS.

The HDB_Alerts check turns to Critical if the number of alerts with rating Error found within the timespan defined by HDBAlertsTimeSpan is equal to or above HDBAlertsErrorCountCrit.

You can exclude alerts from contributing to the check status by specifying the alert’s ID using parameter HDBAlertsExcludeIDs. Multiple entries must be separated by spaces, comma, or semicolon. HDBAlertsExcludeIDs's syntax is forgiving, i. e. leading, trailing or multiple spaces will not harm and the right alerts will still be excluded as long as numeric values are found.

The HDB_Alerts check turns to Critical if the number of alerts with rating High found within the timespan defined by HDBAlertsTimeSpan is equal to or above HDBAlertsHighCountCrit.

The HDB_Alerts check turns to Warning if the number of alerts with rating Low found within the timespan defined by HDBAlertsTimeSpan is equal to or above HDBAlertsLowCountWarn. The check status of HDB_Alerts will be Ok if no alerts with priorty above Low are found and if the number of Low priority alerts is below the threshold.

The HDB_Alerts check turns to Warning if the number of alerts with rating Medium found within the timespan defined by HDBAlertsTimeSpan is equal to or above HDBAlertsMediumCountWarn. The check status of HDB_Alerts will be Ok if no alerts with priority above Medium are found and if the number of Medium priority alerts is below HDBAlertsMediumCountWarn threshold, and the number of Low priority alerts is below HDBAlertsLowCountWarn threshold.

Restricts the watch period of the HDB_Alerts Check.

Restricts the watch period of the HDB_Backup Check.

If the backup status is “prepared” and it started less than 5 Minutes earlier, then the check is OK.

Defines the time span (in minutes) that is taken into account for the HDB_CPULoad Check.

If one of the node’s CPU load exceeds this threshold, the check status turns to Critical.

If one of the node’s CPU load exceeds this threshold, the check status turns to Warning, unless the Critical threshold HDBCPULoadCrit is exceeded for any node.

If there are more than HDBDeltaMergesNumCrit taking longer than HDBDeltaMergesTimeCrit amount of time the check status of HDB_DeltaMerges turns to Critical.

If there are more than HDBDeltaMergesNumWarn taking longer than HDBDeltaMergesTimeWarn amount of time the check status of HDB_DeltaMerges turns to Warning, unless a Critical threshold is exceeded.

If there are more than HDBDeltaMergesNumCrit taking longer than HDBDeltaMergesTimeCrit amount of time the check status of HDB_DeltaMerges turns to Critical.

If there are more than HDBDeltaMergesNumWarn taking longer than HDBDeltaMergesTimeWarn amount of time the check status of HDB_DeltaMerges turns to Warning, unless a Critical threshold is exceeded.

If the usage of the disks containing the storage device exceeds the HDBDisksUsageCrit threshold the check status is set to Critical.

If the usage of the disks containing the storage device exceeds the HDBDisksUsageWarn threshold, the check status is set to Warning, unless the HDBDisksUsageCrit threshold is exceeded.

If the predicted point in time when the SAP HANA Log Area space is exceeded lies within the upcoming HDBDisksLogExCrit hours, the check status of this HDB_DisksLog is set to Critical.

If the predicted point in time when the SAP HANA Log Area space is exceeded lies within the upcoming HDBDisksLogExWarn hours, but not within the HDBDisksLogExCrit hours, the check status of this HDB_DisksLog is set to Warning.

If the usage of the filesystems containing the log areas exceeds the HDBDisksLogUsageCrit threshold, the check status is set to Critical.

If the usage of the filesystems containing the log area exceeds the HDBDisksLogUsageWarn threshold, the check status is set to Warning, unless the HDBDisksLogUsageCrit threshold is exceeded.

If the usage of the filesystems containing the log backups exceeds the HDBDisksLogBackupUsageCrit threshold, the check status is set to Critical.

If the usage of the filesystems containing the log area exceeds the HDBDisksLogBackupUsageWarn threshold, the check status is set to Warning, unless the HDBDisksLogBackupUsageCrit threshold is exceeded.

You can exclude storage devices from contributing to the check status by specifying the storage device ID using parameter HDBExcludeStorageDeviceIDs. Multiple entries must be separated by comma or semicolon. HDBExcludeStorageDeviceIDs's syntax is forgiving, i. e. leading, trailing or multiple spaces will not harm and the right storage devices will still be excluded as long as numeric values are found.

You can exclude storage devices from contributing to the check status by specifying the storage ID using parameter HDBExcludeStorageIDs. Multiple entries must be separated by comma or semicolon. HDBExcludeStorageIDs's syntax is forgiving, i. e. leading, trailing or multiple spaces will not harm and the right storage devices will still be excluded as long as numeric values are found.

You can exclude storage devices from contributing to the check status by specifying the storage device type (e.g. Data, Log_backup) using parameter HDBExcludeStorageTypes. Multiple entries must be separated by comma or semicolon. The exclude list may contain leading and/or trailing spaces, and spaces between the items. They will be trimmed away to make sure that the right storage devices will be excluded.

Programs executing SQL statements on this list are not considered for the check result. Wildcard * is allowed. Multiple entries must be separated by , (comma). If your statement includes a comma character, please escape it with a backslash \.

If the total execution time of an SQL statement compared to the total execution time of all SQL statements exceeds HDBExpSQLTimePctCrit percent the check status of HDB_ExpSQL turns to Critical.

If the total execution time of an SQL statement compared to the total execution time of all SQL statements exceeds HDBExpSQLTimePctWarn percent the check status of HDB_ExpSQL turns to Warning, unless the Critical threshold HDBExpSQLTimePctCrit is exceeded.

You can exclude job names from contributing to the check status by specifying the job names using parameter HDBJobNameExclude. Multiple entries must be separated by comma or semicolon. The syntax of HDBJobNameExclude is forgiving, i. e. leading, trailing or multiple spaces will not harm and the right jobs will still be excluded as long as the job name matches.

You may use placeholders ? (single character) and * (any number of characters) to specify a job name pattern to be excluded.

If jobs are found running longer than HDBJobRuntimeCrit minutes the check status is set to Critical.

If jobs are found running longer than HDBJobRuntimeWarn minutes the check status is set to Warning, unless there is a job found running longer than HDBJobRuntimeCrit minutes.

Define the severity of HDB_Landscape in case of a problem.

If the license has an expiration date, the Check HDB_License turns to Critical if less than HDBLicenseExpireTimeCrit days are left until expiration.

If the license has an expiration date, the Check HDB_License turns to Warning if less than HDBLicenseExpireTimeWarn days are left until expiration, unless the Critical threshold HDBLicenseExpireTimeCrit is exceeded.

Memory relation of the used memory to the licensed memory.

Memory relation of the used memory to the licensed memory.

Defines the time span in minutes which is used to examine log backups back from the current moment.

Configures the Critical threshold of the HDB_LogFiles check; if more locked log files are found the check will raise a Critical alert.

Configures the Warning threshold of the HDB_LogFiles check; if more locked log files are found the check will raise a Warning alert.

If the Database peak memory usage compared to the allocation limit exceeds the HDBMemoryPeakUsageCrit threshold, the check status is set to Critical.

If the Database peak memory usage compared to the allocation limit exceeds the HDBMemoryPeakUsageWarn threshold, the check status is set to Warning unless the HDBMemoryPeakUsageCrit threshold is exceeded.

If a host’s physical memory usage exceeds the HDBMemoryPhysicalUsageCrit threshold, the check status is set to Critical.

If a host’s physical memory usage exceeds the HDBMemoryPhysicalUsageWarn threshold, the check status is set to Warning, unless the HDBMemoryPhysicalUsageCrit threshold is exceeded.

If a service’s memory usage exceeds HDBMemoryServicesUsageCrit percent or a service’s free memory falls below HDBMemoryServicesUsageCrit KB/MB/GB, the check status is set to Critical.

If a service’s memory usage exceeds HDBMemoryServicesUsageWarn percent or a service’s free memory falls below HDBMemoryServicesUsageWarn KB/MB/GB, the check status is set to Warning, unless the HDBMemoryServicesUsageCrit threshold is exceeded.

Configures the Critical threshold for system replication delay in seconds.

Configures the Warning threshold for system replication delay in seconds.

If system replication is not set up for a HANA database, HDB_SystemReplication will return an Ok check status by default. You can change this using the HDBSystemReplNotFoundStatus parameter and thus enforce that system replication is configured.

The relation of the total memory pools in % to the global allocation limit.

The relation of the total memory pools in % to the global allocation limit.

Value in relation to rows to the upper limit of 2 bn rows.

Define which tables have been excluded.

Define how many top tables the check monitors.

Value in relation to rows to the upper limit of 2 bn rows.

If the last successful backup of the MSSQL Master Database is older than MSSBackupAgeMasterCrit days, the check status is set to Critical.

If the last successful backup of the MSSQL Master Database is older than MSSBackupAgeMasterWarn days, but not older than MSSBackupAgeMasterCrit days, the check status is set to Warning.

If the last successful backup of the MSSQL MSDB Database is older than MSSBackupAgeMsdbCrit days, the check status is set to Critical.

If the last successful backup of the MSSQL MSDB Database is older than MSSBackupAgeMsdbWarn days, but not older than MSSBackupAgeMsdbCrit days, the check status is set to Warning.

Comma-separated list of database names that are ignored from the MSS_DBBACKUP check. By default, the MSS_DBBACKUP check includes the master and msdb database as well. If you want to exclude databases, set the names of those databases in this monitoring parameter. Use a comma to separate multiple databases.

If the predicted point in time when the DB space limit is exceeded is within the upcoming MSSDBExCrit hours, the check result of MSS_DBUSAGE is set to Critical.

If the predicted point in time when the DB space limit is exceeded is within the upcoming MSSDBExWarn hours, but not within the upcoming MSSDBExCrit hours, the check result of MSS_DBUSAGE is set to Warning, unless the MSSDBUsageCrit threshold is exceeded.

Defines whether the forecasting algorithm is active or inactive. See Forecasting for more information.

If the usage of the database exceeds the MSSDBUsageCrit threshold, the check status is set to Critical.

You can define the threshold either in the percentage of the total size of the resource, or in KB, MB, or GB values of the remaining free space. In the first case, the parameter gets effective if the usage measured in % of the total space is higher than the defined threshold. In the second case, the parameter gets effective if the remaining free space is lower than the defined threshold.

If the usage of the MSSQL database exceeds the MSSDBUsageWarn threshold but does not exceed MSSDBUsageCrit threshold, the check status is set to Warning, unless the MSSDBExCrit threshold is exceeded.

You can define the threshold either in the percentage of the total size of the resource, or in KB, MB, or GB values of the remaining free space. In the first case, the parameter gets effective if the usage measured in % of the total space is higher than the defined threshold. In the second case, the parameter gets effective if the remaining free space is lower than the defined threshold.

You can set this parameter if the monitoring Avantra Agent has no access to the filesystem holding the SQL Server installation, e.g. if you are using Agentless Monitoring.

In this case, the MSS_DBUSAGE and MSS_LOGUSAGE do not consider auto-growth database files.

SQL statements on this list are not considered for the check result. Wildcard * is allowed. Multiple entries must be separated by ; (semicolon). If your statement includes a semicolon character, please escape it with a backslash \.

Defines whether or not excluded statements, which will not contribute to the check result, are displayed.

If for a particular SQL statement the amount of logical reads exceeds MSSExpSQLLogicalReadCrit percent of the total number of reads of all statements, the check turns to Critical.

If for a particular SQL statement the amount of logical reads exceeds MSSExpSQLLogicalReadWarn percent of the total number of reads of all statements, but does not exceed MSSExpSQLLogicalReadCrit, the check turns to Warning.

Limit the number of considered SQLstatements to the topmost MSSExpSQLNumTopRecs. This is due to performance reasons.

If for a particular SQL statement the amount of physical reads exceeds MSSExpSQLPhysicalReadCrit percent of the total number of reads of all statements, the check turns to Critical.

If for a particular SQL statement the amount of physical reads exceed MSSExpSQLPhysicalReadWarn percent of the total number of reads of all statements, but does not exceed MSSExpSQLPhysicalReadCrit, the check turns to Warning.

If the transaction log for the MSSQL database is older than MSSLogBckAgeCrit minutes, the check status is set to Critical.

If the transaction log for the SAP SID database is older than MSSLogBckAgeWarn minutes, but is not older than MSSLogBckAgeCrit minutes, the check status is set to Warning, unless the MSSLogExCrit threshold is exceeded.

If the predicted point in time when the transaction log limit is exceeded is within the upcoming MSSLogExCrit hours, the check result of MSS_LOGUSAGE is set to Critical.

If the predicted point in time when the transaction log limit is exceeded is within the upcoming MSSLogExWarn hours, but not within the upcoming MSSDBExCrit hours, the check result of MSS_LOGUSAGE is set to Warning, unless the MSSDBUsageCrit threshold is exceeded.

Defines whether the forecasting algorithm is active or inactive. See Forecasting for more information.

If the usage of the transaction log of the database exceeds the MSSLogUsageCrit threshold, the check status is set to Critical.

You can define the threshold either in the percentage of the total size of the resource, or in KB, MB, or GB values of the remaining free space. In the first case, the parameter gets effective if the usage measured in % of the total space is higher than the defined threshold. In the second case, the parameter gets effective if the remaining free space is lower than the defined threshold.

If the usage of the transaction log of the database exceeds the MSSLogUsageWarn threshold, but does not exceed the MSSLogUsageCrit threshold, the check status is set to Warning, unless the MSSLogExCrit threshold is exceeded.

You can define the threshold either in the percentage of the total size of the resource, or in KB, MB, or GB values of the remaining free space. In the first case, the parameter gets effective if the usage measured in % of the total space is higher than the defined threshold. In the second case, the parameter gets effective if the remaining free space is lower than the defined threshold.

A recent version of the Microsoft SQL server might force SQL connections to use NTLMv2 security. If you experience the error message The login is from an untrusted domain and cannot be used with Windows authentication in DBCONNECT check, setting this parameter to true might fix this.

Defines a Critical threshold for the ORA_ALERTLOG check. The check status will be Critical if that many log entries considered as critical are found.

Defines a Warning threshold for the ORA_ALERTLOG check. The check status will be Warning if that many log entries considered as warning are found, unless the ORAAlertLogCountCrit critical threshold is exceeded.

Designates an entry in the Oracle alert log as critical. Readers familiar with regular expressions may note that the expression below is a Perl style regular expression which is case insensitive.

Designates an entry in the Oracle alert log as warning.

Defines the location of the Oracle alert log file (fullpath, including the file name). The macro %%SID%% is provided and will be replaced with the Real SAP SID (for SAP Systems) or the database name (for Databases). The macro %%ORACLE_HOME%% may be used as well.

Restricts the watch period of the ORA_ALERTLOG check.

If the flag is set, the ORA_BACKUP does not verify if files marked as active in RMAN do actually exist on the filesystem.

This parameter tells Avantra which backup tool is used for the backup of the Oracle Database and thus controls which checks are executed.

If the parameter is set to RMAN the check ORA_BACKUP is executed which verifies backups performed with Oracle RMAN. If the parameter is set to BRBACKUP, the checks ORA_BRBACKUPSTAT, ORA_BRBACKUP, and ORA_BRARCHIVE will be executed.

If the running time of an Oracle online backup is above ORABrbackupDelayCrit percent of the usual average runtime, the check status is set to Critical.

If the running time of an Oracle online backup is above ORABrbackupDelayCrit percent of the usual average runtime and above ORABrbackupDelayTimeCrit minutes, the check status is set to Critical.

If the running time of an Oracle online backup is above ORABrbackupDelayWarn percent of the usual average runtime and above ORABrbackupDelayTimeWarn minutes, but below ORABrbackupDelayCrit percent or ORABrbackupDelayTimeCrit minutes, the check status is set to Warning.

If the running time of an Oracle online backup is above ORABrbackupDelayWarn percent of the usual average runtime, but below ORABrbackupDelayCrit percent, the check status is set to Warning.

If the running time of an Oracle offline backup is above ORABrbackupOfflineDelayCrit percent of the usual average runtime, the check status of the DBCONNECT, RFCConnect, and J2EECONNECT are set to Critical. For stand-alone Oracle Databases, the parameter is only effective if the BR*Tools are used.

Defines the BRBACKUP function IDs considered as valid backup types when BRBACKUP is checked. The pre-configured ant aft means only full tape backups are considered as backups. If your Oracle database is backed up with backint (and thus the backup target is a file instead of a tape), you need to set the parameter to ant aft anf aff.

This parameter defines the Oracle schema where the tables for BR*Tools are located. Usually, the Avantra Agent determines the schema, and only if this fails you need to define the schema manually.

Only the latest ORABrToolsSelectRange days are searched for successful BR*Tools operations.

Controls the number of auto-extent increments to be available in an Oracle datafile filesystem before a Critical alert is raised.

Controls the number of auto-extent increments to be available in an Oracle datafile filesystem before a Warning alert is raised.

If the last successful execution of any of the checked DBA operations is older than ORADBAOperAgeCrit days, the check status turns to Critical.

If the last successful execution of any of the checked DBA operations is older than ORADBAOperAgeWarn days, but none is older than ORADBAOperAgeCrit or even unsuccessful, the check status turns to Warning.

Only the DBA operations corresponding to the function IDs defined with this parameter are considered by the ORA_DBAOPER check.

Only the latest ORADBAOperSelectRange days are searched for successful DBA operations.

You may set this parameter if the monitoring Avantra Agent has no access to the filesystem holding the Oracle installation, e.g. if you are using Agentless Monitoring.

This parameter defines the minimum number of deadlocks that must have occurred in the last ORAEnqueueTimeSpan minutes to turn the ORA_Enqueue check Critical.

By setting this parameter to -1, the deadlocks check of ORA_Enqueue is disabled.

This parameter defines the minimum number of deadlocks that must have occurred in the last ORAEnqueueTimeSpan minutes to turn the ORA_Enqueue check Warning.

If this parameter is set to a value equal to or higher than ORAEnqueueDeadLocksCrit, it has no effect.

This parameter defines the minimum ratio of timeouts to requests/conversions of the last ORAEnqueueTimeSpan minutes necessary to turn the ORA_Enqueue check Critical.

By setting this parameter to 0, the timeouts check of ORA_Enqueue is disabled.

This parameter defines the minimum ratio of timeouts to requests/conversions of the last ORAEnqueueTimeSpan minutes necessary to turn the ORA_Enqueue check Warning.

If this parameter is set to a value equal to or higher than ORAEnqueueTimeoutsCrit, it has no effect.

The ORA_Enqueue check collects enqueue statistics data up to a certain age. This parameter defines the age (in minutes) of the oldest data set to consider. If a data set gets older, it is removed from the collection.

This parameter defines the minimum ratio of wait events to requests/conversions of the last ORAEnqueueTimeSpan minutes necessary to turn the ORA_Enqueue check Critical.

By setting this parameter to 0, the wait events check part of ORA_Enqueue is disabled.

This parameter defines the minimum ratio of wait events to requests/conversions of the last ORAEnqueueTimeSpan minutes necessary to turn the ORA_Enqueue check Warning.

If this parameter is set to a value equal to or higher than ORAEnqueueWaitsCrit, it has no effect.

Statements issued from programs listed within this parameter are not considered for the check result. The list is separated by one or more white spaces. Program names containing white spaces must be enclosed in double quotes. You may use the special macro <NOPROG> to sort out statements that have no Program Name value.

Note that prior to SAP Basis Release 4.5C no program names are shown at all. In this case, the <NOPROG> macro excludes all statements.

Wildcard * is allowed.

Defines whether or not statements generated by excluded programs are shown in the check message.

If any SQL statement (not excluded by ORAExpSQLExclude) exceeds an amount of ORAExpSQLGetCrit percent of the total buffer gets, the check result turns to Critical.

If any SQL statement (not excluded by ORAExpSQLExclude) exceeds an amount of ORAExpSQLGetWarn percent of the total buffer gets, and no statement exceeds an amount of ORAExpSQLGetCrit percent of the total buffer gets or ORAExpSQLReadCrit percent of the total disk reads, the check turns to Warning.

If any SQL statement (not excluded by ORAExpSQLExclude) exceeds an amount of ORAExpSQLReadCrit percent of the total disk reads, the check result turns to Critical.

If any SQL statement (not excluded by ORAExpSQLExclude) exceeds an amount of ORAExpSQLReadWarn percent of the total disk reads, and no statement exceeds an amount of ORAExpSQLGetCrit percent of the total buffer gets or ORAExpSQLReadCrit percent of the total disk reads, the check turns to Warning.

If the number of extents allocated for an Oracle segment exceeds ORAExtentsUsageCrit percent of max_extents defined for this segment, the check status is set to Critical.

If the number of extents allocated for an Oracle segment exceeds ORAExtentsUsageCrit percent of max_extents defined for this segment, but does not exceed ORAExtentsUsageCrit percent, the check status is set to Warning

If the log arch filesystem usage exceeds the ORAFSLogArchCrit threshold, the check status is set to Critical. The log arch filesystem is discovered automatically by Avantra Agent.

You can define the threshold either in the percentage of the total size of the resource, or in KB, MB, or GB values of the remaining free space. In the first case, the parameter gets effective if the usage measured in % of the total space is higher than the defined threshold. In the second case, the parameter gets effective if the remaining free space is lower than the defined threshold.

If the predicted point in time when the filesystem limit is exceeded is within the upcoming ORAFSLogArchExCrit hours, the check result of ORA_FSLOGARCH is set to Critical.

If the predicted point in time when the filesystem limit is exceeded is within the upcoming ORAFSLogArchExWarn hours, but not within the upcoming ORAFSLogArchExCrit hours, the check result of ORA_FSLOGARCH is set to Warning, unless the ORAFSLogArchExCrit threshold is exceeded.

Defines whether the forecasting algorithm is active or inactive. See Forecasting for more information.

The ORA_FSLOGARCH check tries to read the log archive destination location from the Oracle parameters. In cases where this doesn’t work, this parameter allows you to force override / set the archive destination location. There can be multiple paths entered, separated by semicolons ( ';' ).

If the log arch filesystem usage exceeds the ORAFSLogArchWarn threshold, but does not exceed the ORAFSLogArchCrit threshold, the check status is set to Warning, unless the ORAFSLogArchExCrit threshold is exceeded.

You can define the threshold either in the percentage of the total size of the resource, or in KB, MB, or GB values of the remaining free space. In the first case, the parameter gets effective if the usage measured in % of the total space is higher than the defined threshold. In the second case, the parameter gets effective if the remaining free space is lower than the defined threshold.

Usually, the Avantra Agent determines the Oracle Home directory automatically. In case it does not you may set this parameter accordingly.

ORA_BACKUP will select RMAN data not older than defined in this parameter.

If the parameter is set, the checks ORA_DBAOPER and ORA_DBCHECKLOG will be executed.

This is the default for Database instances of an SAP System.

If you run SAPDBA or BRCONNECT with a stand-alone Database you may set this parameter as well.

This parameter defines the Oracle schema where the tables for SAPDBA or BRCONNECT are located. Usually, Avantra Agent determines the schema and only if this fails, you need to define the schema manually.

Defines the time interval between two ORA_SEGMENTS checks.

Defines the count threshold for sessions that exceed ORASessionsTimeWaitWarn or ORASessionsTimeWaitCrit time thresholds. The threshold is compared to the number of Critical sessions for a Critical Check Result or the number of Critical plus Warning sessions for a Warning Check Result.

Configures the wait classes that shall be ignored by the ORA_Sessions Check.

The values must be separated by blanks.

The check ORA_Sessions compares session wait times of matching sessions against this threshold to categorize them as Critical. All Critical sessions are counted and further compared against ORASessionsCountWait for the final Check Result.

The check ORA_Sessions compares session wait times of matching sessions against this threshold to categorize them as Warning. All Warning sessions are counted and together with the Critical session count compared against ORASessionsCountWait for the final Check Result.

If the predicted point in time when the tablespace limit is exceeded is within the upcoming ORATableSpaceExCrit hours, the check result of ORA_TABLESPACES is set to Critical.

If the predicted point in time when the tablespace limit is exceeded is within the upcoming ORATableSpaceExWarn hours, but not within the upcoming ORATableSpaceExCrit hours, the check result of ORA_TABLESPACES is set to Warning, unless the ORATableSpaceUsageCrit threshold is exceeded for some tablespace.

Defines whether the forecasting algorithm is active or inactive. See Forecasting for more information.

If one of the databases tablespaces usage exceeds the ORATableSpaceUsageCrit threshold, the check status is set to Critical.

You can define the threshold either in the percentage of the total size of the resource, or in KB, MB, or GB values of the remaining free space. In the first case, the parameter gets effective if the usage measured in % of the total space is higher than the defined threshold. In the second case, the parameter gets effective if the remaining free space is lower than the defined threshold.

If the use of one of the database tablespaces exceeds ORATableSpaceUsageWarn percent, but none of them exceeds ORATableSpaceUsageCrit percent, the check status is set to Warning, unless the ORATableSpaceExCrit threshold is exceeded for some tablespace.

You can define the threshold either in the percentage of the total size of the resource, or in KB, MB, or GB values of the remaining free space. In the first case, the parameter gets effective if the usage measured in % of the total space is higher than the defined threshold. In the second case, the parameter gets effective if the remaining free space is lower than the defined threshold.

By default, Avantra uses TNS to connect the Oracle database of an SAP System. Thus the Avantra Agent will determine the TNS admin directory (where the file tnsnames.ora is located). If this process fails, e.g. since the Oracle home directory could not be determined, you may set ORATNSAdminDir manually to work around the issue.

By default, Avantra uses TNS to connect the Oracle Database instance of an SAP System with the TNS alias being equal to the Real SAP SID. If the TNS alias is different from the Real SAP SID, you need to set this parameter to the corresponding TNS alias.

Controls whether or not Performance Data Collection is turned on for Systems. If you do not want the Avantra Agent to collect performance data you may remove the flag.

Use this monitoring parameter to configure the Predictive Analytics engine for the Database. By default the engine is configured as Balanced.

Defines a list of Daily Check details that are considered relevant for the Daily Check status, i.e. the status of which contributes to the overall status. By default the parameter is not defined, i.e. all Daily Check details contribute.

If you define an empty list no Daily Check detail will contribute. In this case, the status of the Daily Check will be Unknown always.

If set, Daily Checks will run on Saturday and Sunday as well.

SIQ_Backup looks for SIQBackupSelectRange days back to find successful backups. The default value is 60 days, so usually, there is no need to change this parameter since backups must be made far more often.

If the last successful Full Backup is older than FullBackupAgeCrit days, the check status is set to Critical. You can define override this value on a per-day level using the corresponding Monitoring Exception Parameter.

If the last successful FullBackup is older than FullBackupAgeWarn days, but not older than FullBackupAgeCrit days, the check status is set to Warning. You can define override this value on a per-day level using the corresponding Monitoring Exception Parameter.

RunJSAllowDBWrite monitoring parameters can be set to ‘Enabled’ or ‘Disabled’ (default) value. It allows SQL queries defined within custom checks and workflows to change the data in the Database.

If the dbfile usage exceeds the SIQDataFilesUsageCrit threshold the check status is set to Critical.

You can define the threshold either in the percentage of the total size of the resource, or in KB, MB, or GB values of the remaining free space. In the first case, the parameter gets effective if the usage measured in % of the total space is higher than the defined threshold. In the second case, the parameter gets effective if the remaining free space is lower than the defined threshold.

If the dbfile usage of a database exceeds the SIQDataFilesUsageWarn threshold the check status is set to Warning.

You can define the threshold either in percentage of the total size of the resource, or in KB, MB, or GB values of the remaining free space. In the first case, the parameter gets effective if the usage measured in % of the total space is higher than the defined threshold. In the second case the parameter gets effective if the remaining free space is lower than the defined threshold.

If the predicted point in time when the dataspace is exceeded is within the upcoming SIQDataSpacesExCrit hours, the check status of SIQ_DataSpaces is set to Critical.

If the predicted point in time when the data space is exceeded is within the upcoming SIQDataSpacesExWarn hours, but not within the upcoming SIQDataSpacesExCrit hours, the check status of SIQ_DataSpaces is set to Warning, unless the SIQDataSpacesExCrit threshold is exceeded.

Defines whether the forecasting algorithm is active or inactive. See Forecasting for more information.

If the usage of a dataspace exceeds the SIQDataSpacesUsageCrit threshold the check status is set to Critical.

You can define the threshold either in the percentage of the total size of the resource, or in KB, MB, or GB values of the remaining free space. In the first case, the parameter gets effective if the usage measured in % of the total space is higher than the defined threshold. In the second case, the parameter gets effective if the remaining free space is lower than the defined threshold.

If the data space usage of a database exceeds the SIQDataSpacesUsageWarn threshold, the check status is set to Warning, unless the SIQDataSpacesUsageCrit threshold is exceeded.

You can define the threshold either in the percentage of the total size of the resource, or in KB, MB, or GB values of the remaining free space. In the first case, the parameter gets effective if the usage measured in % of the total space is higher than the defined threshold. In the second case, the parameter gets effective if the remaining free space is lower than the defined threshold.

Comma-separated list of database names that are ignored from the SYB_Backup check. Spaces before or after the comma are gently ignored. Excluded databases will still appear in the SYB_Backup table display, but are marked as Excluded → Yes. Most databases that usually require no backup up are already excluded by default. However, you may add more databases since the backup of some databases is documented as optional in official SAP guide SAP Business Suite on SAP Adaptive Server Enterprise.

SYB_Backup looks for SYBBackupSelectRange days back to find successful backups. The default value is 60 days, so usually, there is no need to change this parameter since backups must be made far more often.

If the running time of a Sybase backup is above 100 percent of the usual average runtime and above SYBBackupStatDelayTimeCrit minutes, the check status is set to Critical.

If the running time of a Sybase backup is above 50 percent of the usual average runtime and above SYBBackupStatDelayTimeWarn minutes, the check status is set to Warning, unless the Critical conditions are met, see SYBBackupStatDelayTimeCrit.

Comma-separated list of database names that are ignored from the SYB_BackupStat check. Spaces before or after the comma are gently ignored. Excluded databases will still appear in the SYB_BackupStat table display, but are marked as Excluded → Yes. Most databases that usually require no backup up are already excluded by default. However, you may add more databases since the backup of some databases is documented as optional in official SAP guide SAP Business Suite on SAP Adaptive Server Enterprise.