Reference: Database Checks

ADA_BACKUP

Verify MaxDB Backup

Description

Checks the end date / time of the most recent backup required for complete recovery of the Database.

If it is older than a configured period of time, a Warning or a Critical message is generated.

The maximum allowed age can be defined generally by using parameters BackupAgeCrit and BackupAgeWarn and the corresponding Monitoring Exception Parameters.

Additionally the check displays an overview of all backups required for the most recent complete Database recovery.

ADA_DATAAREA

Verify data area usage

Description

An alarm is raised if the data area usage exceeds some configurable threshold, or if the predicted data area exhaustion is within a configurable period of time.

ADA_LOGAREA

Verify log area usage

Description

An alarm is raised if the log area usage exceeds some configurable threshold, or if the predicted log area exhaustion is within a configurable time period.

ANY_Backup

Verify SAP SQL Anywhere Database backup

Description

Checks for backup maintenance plans and verifies if they were successfully executed.

If no backup maintenance plan for full backup is found, the check status will be Critical and there will be no further check evaluation.

If there is a full backup maintenance plan, the reports of this plan will be evaluated. ANY_Backup collector will select reports of the last ANYBackupSelectRange days. For the backup check to be Ok, a successful report must be found, and the finished time of the last full backup must be below thresholds ANYBackupFullWarnAge and ANYBackupFullCritAge.

Additionally the age of the last successful backup must be below BackupAgeWarn and BackupAgeCrit, but it is not required that the last successful backup is a full backup. If the latest backup was unsuccessful, the check status will be Warning unless Critical thresholds are exceeded.

ANY_Connections

Verifies number of SAP SQL Anywhere database connections

Description

An alert is raised if the number of database connections exceeds some configurable threshold. In case the number defined in Avantra threshold ANYConnectionsNumCrit is above the number of connections allowed (SAP SQL Anywhere database option max_connections), the defined thresholds ANYConnectionsNumCrit and ANYConnectionsNumWarn will be automatically adapted to 95 % and 80 % of the max_connections value.

The table showing the connections details shows a selection out of hundreds of connection properties. If you would like to see other properties displayed as well, please contact support and we might add this information in a future release.

ANY_DBSpaces

Verify SAP SQL Anywhere dbspaces usage

Description

An alert is raised if dbspace usage exceeds some configurable threshold, or if the predicted dbspace exhaustion is within a configurable period of time. Exceptions to the general Warning and Critical thresholds may be defined on a per dbspace level.

ANY_Messages

Queries and verifies SAP SQL Anywhere database server messages

Description

The check queries for server messages within the last day. If Monitoring Parameter RunDailyCheckOnWE is false, the check queries for server messages for the last 3 days on Mondays, to make sure you do not miss any entries.

The check status is Ok if only INFO messages are found or the number of ERR and WARN messages is below ANYMessagesNumWarn. If the number of both, ERR and WARN messages is above ANYMessagesNumWarn the check status is Warning, unless the number of ERR messages is exceeding ANYMessagesNumCrit which will result as Critical check status.

If only INFO messages are found, the latest 100 INFO messages will be displayed. If ERR or WARN messages are found, INFO messages will not be displayed. The maximum number of ERR or WARN messages displayed is limited to a total number of 500 messages.

It is possible to exclude messages from being counted as WARN or ERR message. To do so, please use Monitoring Parameter ANYMessagesExclude, see the parameterʼs documentation for the syntax details.

ANY_MessagesStat

Queries and verifies SAP SQL Anywhere database server messages for RealTime Monitoring

Description

ANY_MessagesStat does the same as ANY_Messages — monitoring the SAP SQL Anywhere server messages, but queries it for entries within last ANYMessagesStatTimespan minutes only and reports to RealTime Monitoring.

ANY_TransLog

Verify SAP SQL Anywhere transaction log usage

Description

Determines the databaseʼs transaction and possible mirror transaction log and checks the usage of the same. An alert is raised if log usage exceeds some configurable threshold, or if the predicted transaction log exhaustion is within a configurable period of time.

DB2_BACKUP

Verify Database backup

Description

Checks the last full database backup and shows its start-, end- and runtime.

If it was not successful a Warning or Critical status is reported, depending on the exit state of the latest backup command.

Additionally the age of the last successful backup is checked. If the last successful backup is too old a Warning is reported. The maximum age can be defined using the Monitoring Parameters BackupAgeCrit and BackupAgeWarn. There is also the option to define a Monitoring Exception Parameter.

The backup granularity (i.e. tablespace or database) is not considered. Tablespace backups are therefore considered in the same way as full database backups. If you use tablespace backups you need to take care for an appropriate backup strategy. However, the granularity is displayed with the Check Result for your information.

DB2_BACKUPSTAT

Verify DB2 Database backup (RealTime Monitoring)

Description

The return code of the latest backup is evaluated.

If the return code is 0, the check status will be Ok, in case the value is 1, the status will be Warning. Otherwise the status is set to Critical.

This check reports to the RealTime Monitoring, The Monitoring Parameter BackupResetRTMTime can be used to reset the check status back to Ok automatically after a certain period of time.

DB2_CBO_STATS

Verify table and index statistics' age

Description

Counts the number of tables / indexes with statistics not older than DB2CBOMaxAge days.

If the number of tables / indexes with up-to-date statistics is below threshold DB2CBONumEntriesUpdCrit or DB2CBONumEntriesUpdWarn the check will return a Critical or a Warning message.

See Monitoring Parameter ABAPDBSchema if you need to override the schema name for this Check.

DB2_DIAGLOG

Verify the DB2 diagnostics log file

Description

An alert is raised if a certain number of entries with a Warning, Error, or Severe value in the Level property are found during a configurable period of time.

The DB2_DIAGLOG check can be configured in a very flexible way. The log parsing engine allows you to access any field of a DB2 diagnostics log entry, and you have the option to define virtually any Boolean expression in order to consider certain entries as Warning or Critical.

The check evaluation rule is: If there are more than DB2DiagLogCountCrit entries found during the past DB2DiagLogTimeSpan minutes matching the expression DB2DiagLogExprCrit, the check status will be Critical. Otherwise, if there are more than DB2DiagLogCountWarn entries during the same time span matching the expression DB2DiagLogExprWarn, the check status will be Warning. Otherwise, it will be Ok.

The location of the DB2 diagnostics log file is determined by the diagpath DB2 Database parameter. In case diagpath is not set the check returns a Warning.

The DB2_DIAGLOG check is not supported for systems using a remote database (i.e. if DB2DBRemote is set to 1)!

DB2_ExpSQL

Watch for expensive SQL statements

Description

Reports expensive SQL statements considering the I/O of all statements in query cache.

An SQL statement is considered expensive, if the amount of logical and/or physical reads for the particular statement exceeds a certain amount of all logical and physical reads.

Warning and Critical thresholds can be defined for the logical and physical reads, and statements can be excluded from the check.

DB2_FSLOGARCH

Verify DB2 transaction log filesystems

Description

The check execution depends on the configuration of your DB2 UDB Database.

The DB2_FSLOGARCH check is not supported for systems using a remote database (i.e. DB2DBRemote is set to 1).

DB2_LOGUSAGE

Watch DB2 log space usage

Description

An alert is raised if the log space of the DB2 UDB Database exceeds some configurable threshold, or if the predicted log space exhaustion is within a configurable period of time.

Reference Data
Managed Object

DB2 Database. For Java-only SAP Systems only if kernel version ≥ 6.40

Check Cycle

Basic

Depends on

DBCONNECT

Monitoring Parameters

DB2LogUsageCrit, DB2LogUsageWarn, DB2LogExCrit, DB2LogExWarn, DB2LogForecast

DB2_TABLESPACES

Verify DB2 tablespaces usage

Description

An alert is raised if tablespace usage exceeds some configurable threshold, or if the predicted tablespace exhaustion is within a configurable period of time. Exceptions to the general Warning and Critical thresholds may be defined on a per tablespace level.

Auto-resize tablespaces are supported as well. The check considers the space available assuming that the tablespace can be resized to its limit regardless of any underlying file system limitations. If the tablespace is configured with "unlimited" maxium size (i.e. tablespace_max_size is -1), the architectural size limit of the tablespace is considered (see also DB2 LUW SQL and XML Limits).

You can distinguish auto-resized tablespaces from other ones in the Check Result. If an tablespace is configured using auto-resize, you will get the following result in case of a Warning or Critical check status:

'PSAPBTABD' is used by 96.6 % (17.51 GB free, 17.51 GB auto-resize free)

Since — in the example above — the amount of actual free space in the tablespace is identical to the maximum available auto-resize free space the tablespace will not extend any further and it might be time to reorganize or to upgrade to large tablespaces.

The following example shows the situation where a tablespace still can be auto-resized:

'PA3#ODSI' is used by 9.7 % (25.61 GB free, 231.27 GB auto-resize free)

The Avantra Agent does not check if there is enough space on the filesystem to actually resize a tablespace. You need to monitor the file systems as well using the FILESYSTEMS check.

Reference Data
Managed Object

SAP System (for Java-only systems only if kernel version ≥ 6.40) and Database Type DB2

Check Cycle

Basic

Depends on

DBCONNECT

Monitoring Parameters

DB2TableSpaceUsageCrit, DB2TableSpaceUsageWarn, DB2TableSpaceExCrit, DB2TableSpaceExWarn, DB2TableSpaceForecast

DBCONNECT

Verifies connectivity to a Database.

Description

Verifies the connection to a Database. If the Database connection has been established successfully, the check will provide some additional information in its result.

If the Database connection fails, the Check Result will be Warning and after DBConnectErrsCrit subsequent connection attempts without success, the result will be Critical.

Additionally the check serves as a master check for all other checks executed on a Database, so if the connection fails, all the other dependent checks will return Unknown.

The DBCONNECT check therefore is the most important check for a Database.

SAP Systems with Oracle Database only: The Avantra Agent by default tries to connect the Oracle database using`TNS`lookup with the SAP System's Real SAP SID as`TNS`alias.

If this fails (for example because the`TNS`admin directory could not be determined) you can make use of the Parameter Set ORATNSAdminDir and ORATNSAlias.

Oracle Databases in conjunction with SAP BR*Tools only: If there is a running off-line backup, the check will return a Warning. If the elapsed time (since backup start) is ORABrbackupOfflineDelayCrit percent longer than the average total backup runtime of the last 5 full backups, a Critical alert is raised. If there are less than 2 full backups available a backup time of 4 hours is assumed.

FULLCHECK

Per-Database summary of Daily Checks

Description

Returns the overall status of all Checks executed during the Daily Check on a particular SAP Instance or Database.

For instance, if the connection attempt (to the SAP Instance or Database) failed, this check type returns a Critical message. If this check fails, all other dependent checks will have status Unknown.

In Ok status the check explains which checks have been executed on the particular SAP Instance or Database, which profiles have been collected, etc.

You may want to skip the execution of Daily Checks on the weekend using Monitoring Parameter RunDailyCheckOnWE.

HDB_Alerts

Verify the last hour’s SAP HANA Alerts

Description

Monitors the alerts generated by the statistics server. The alerts are counted according to their priority: Error, High, Medium, and Low.

The check status is set to Warning if at least one alert with priority Error or High is found within the timespan defined by HDBAlertsTimeSpan. If the number of Error alerts is above HDBAlertsErrorCountCrit or the number of High alerts is above HDBAlertsHighCountCrit the check status is set to Critical.

Since the default values for HDBAlertsErrorCountCrit and HDBAlertsHighCountCrit are both configured to 1, by default the check status is Critical starting from one Error or High alert.

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, or 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 priority above Medium are found and if number of Medium priority alerts is below HDBAlertsMediumCountWarn threshold, and number of Low priority alerts is below HDBAlertsLowCountWarn threshold.

Finally, 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' 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.

Excluded alerts will still be reported in the check result’s overview table. They will be marked with string (Excluded) in the Alert ID column and will not be colored.

HDB_Backup

Verify SAP HANA Database backups

Description

If the latest complete backup was not successful a Warning check status is generated.

If the latest successful complete backup is older than BackupAgeCrit a Critical check status is generated, if it is older than BackupAgeWarn the check status will be Warning.

If no complete backups are found in the time range defined by HDBBackupCompleteSelectRange the check status will be Critical.

HDB_CPULoad

Verify CPU usage of SAP HANA server nodes

Description

This Check corresponds to the CPU counters retrieved from the SAP HANA statistic views. The last HDBCPULoadAverageTime minutes are taken into account.

HDB_DeltaMerges

Verify Runtime of SAP HANA Delta Merges

Description

This Check monitors the duration of Delta Merges. The check status turns to Warning or Critical if there is a certain number of delta merges exceeding the corresponding runtime thresholds.

HDB_Disks

Verify SAP HANA Disk Usage

Description

This Check verifies the usage of the filesystems (disks) used to store the HANA Database data (i.e. storage devices). You may exclude storage devices by using the exclude parameters listed below. For example, log backup storage devices might be repored with zero size since they are backed up by a 3rd party backup solution.

HDB_DisksLog

Verify SAP HANA Log Area Usage

Description

A special case of the HDB_Disks Check for the SAP HANA Log Areas with more restrictive thresholds.

HDB_DisksLogBackup

Verify SAP HANA Log Backup Usage

Description

A special case of the HDB_Disks Check for the SAP HANA Log Backups with more restrictive thresholds.

If you use a third party tool to backup your log segments this Check can be disabled.

HDB_ExpSQL

Report Expensive SQL Statements

Description

An SQL statement is considered expensive if its total execution time compared to the total execution time of all SQL statements exceeds a given threshold.

If you need to reset the SAP HANA internal statistics which this Check is based on, you can do so by executing the following SQL statement:

ALTER SYSTEM RESET MONITORING VIEW SYS.M_SQL_PLAN_CACHE_RESET

HDB_JobRuntime

Verify the runtime of SAP HANA Jobs

Description

This checks monitors the duration of jobs running on SAP HANA. If jobs are found which are running longer than HDBJobRuntimeCrit minutes, the status of the check will be Critical. If jobs are found, which are running longer than HDBJobRuntimeWarn but still not longer than HDBJobRuntimeCrit minutes, the status will be Warning.

You may exclude jobs from being verified by using HDBJobNameExclude. Per default jobs with name Backup are excluded.

HDB_Landscape

Verify the integrity of a SAP HANA Landscape

Description

This Check monitors the status of the different SAP HANA hosts. It is specially useful in scale out environments to detect switchover situations to the standby host.

The Check Result is Ok as long as all hosts are active and all host’s status is either OK or IGNORE. Otherwise the Check will turn to the check status defined in HDBLandscapeSeverity.

HDB_License

Verify SAP HANA License

Description

Verifies if the SAP HANA license will expire soon. If no valid license found the Check turns to Critical. If a valid license is found the expiration date is verified unless the license is unlimited.

HDB_LogBackup

Checks the number of successful log backups in the past hour or a configurable time span.

Description

Checks for successful / failed log backups in the past hour or a time span configurable by HDBLogBackupTimeSpan. The check will become Critical when there are only failed backups found during the time span, otherwise it will be Warning. If there are at least one successful and no failed backups found during the time span, the check will be Ok.

HDB_LogFiles

Checks the number of locked log files.

Description

Various reasons may cause a HANA log file to be locked. This check verifies the number of locked log files and raises an alert if there are too many locked log files.

HDB_MemoryPeak

Verify Peak Memory Usage

Description

Compares the database peak memory usage (since last reset) to the allocation limit.

If you need to reset the SAP HANA internal statistics which this Check is based on, you can do so by executing the following SQL statement:

ALTER SYSTEM RESET MONITORING VIEW SYS.M_HEAP_MEMORY_RESET

HDB_MemoryPhysical

Verify SAP HANA hosts Physical Memory Usage

Description

Monitors the physical memory ( ) usage on each host.

HDB_MemoryServices

Verify SAP HANA Services Memory Usage

Description

Monitors the service memory usage. Compares the memory used against the effective allocation limit.

HDB_Services

Verify if SAP HANA Services are active

Description

Verifies the SAP HANA operational status i.e. if all services are started.

The check status is Ok if all services are active.

The check turns to Critical if no services are found or if at least one service is not active.

Reference Data
Managed Object

SAP HANA Database

Check Cycle

Basic

Depends on

DBCONNECT

Monitoring Parameters

None

HDB_SystemReplDelay

Verifies replication delay between primary and secondary side

Description

In a HANA replication scenario, this check checks the replication delay between primary and secondary side.

The check will not be present on HANA systems without a replication scenario.

HDB_SystemReplication

Verify SAP HANA system replication status

Description

Verifies, if the HANA database has replicated services and if yes, checks if all secondary services are active, fully recoverable, and the replication status is active.

If the HANA database is not configured for system replication, status of HDB_SystemReplication is Ok per default. You can change this behaviour by using HDBSystemReplNotFoundStatus, which allows you to define another status if system replication is not found.

If there are replicated services found, the check status is Ok if all the following conditions are met:

  • All secondary services must report YES as active status.

  • All secondary services must be fully recoverable, i.e. must report TRUE in column 2nd Fully Recoverable.

  • The replication status of all services must be report ACTIVE.

The check turns to Critical if one of the upper condition is not met. In this case please observe possible detail information in column Repl. Status Details.

MSS_DBBACKUP

Verify the backup

Description

Checks the latest backup date / time of the SAP SID, master and msdb Database.

If the latest backup is older than a configured period of time, a Warning message is generated. For the SAP SID Database this period of time can be configured separately for each weekday.

MSS_DBUSAGE

Verify Database usage

Description

Calculates the amount of used space in the managed Database. An alert is raised if the used space exceeds some configurable threshold, or if the predicted space exhaustion is within a configurable period of time.

MSS_EXPSQL

Watch for expensive SQL statements

Description

Reports expensive SQL statements considering the I/O of all statements in query cache.

An SQL statement is considered expensive, if the amount of logical and/or physical reads for the particular statement exceeds a certain amount of all logical and physical reads.

Warning and Critical thresholds can be defined for the logical and physical reads, and statements can be excluded from the check.

MSS_LOGBACKUP

Verify transaction log backup

Description

Determines the last transaction log backup of the managed Database.

If it is older than the configurable Warning or Critical thresholds an alert is raised respectively.

If you are using the simple recovery model you may want to disable this Check.

MSS_LOGUSAGE

Verify transaction log usage

Description

Determines the usage of the transaction log for the manged Database. An alert is raised if the transaction log usage exceeds some configurable threshold, or if the predicted exhaustion is within a configurable period of time.

ORA_ALERTLOG

Verify the Oracle alert log file.

Description

Verifies the Oracle alert log file.

A Critical alert is raised if a certain number of the following entries is found during a configurable period of time:

  • Oracle Database Error Messages: ORA-00255, ORA-00257, ORA-00270, ORA-00272, ORA-00376, ORA-00447, ORA-00470, ORA-00471, ORA-00472, ORA-00473, ORA-00474, ORA-00600, ORA-00603, ORA-01113, ORA-01114, ORA-01115, ORA-01122, ORA-01135, ORA-01578, ORA-01628, ORA-01629, ORA-01630, ORA-01631, ORA-01632, ORA-01650, ORA-01651, ORA-01652, ORA-01653, ORA-01654, ORA-01655, ORA-01656, ORA-01680, ORA-01681, ORA-01683, ORA-01684, ORA-01685, ORA-01688, ORA-01691, ORA-01692, ORA-01693, ORA-01694, ORA-03113, ORA-07445, ORA-16014, ORA-16038, ORA-19502, ORA-19504, ORA-19510, ORA-27044, ORA-27063, ORA-27072, ORA-30036

  • Messages containing Corrupt block

A Warning alert is raised if a certain number of the following entries is found:

The ORA_ALERTLOG check can be configured in a very flexible way. The log parsing engine allows you to access any field of a Oracle alert log entry, and you have the option to define virtually any Boolean expression in order to flag certain entries as Warning or Critical.

The check evaluation rule is: If there are more than ORAAlertLogCountCrit entries found during the past ORAAlertLogTimeSpan minutes matching the expression ORAAlertLogExprCrit, the check status will be Critical. Otherwise, if there are more than ORAAlertLogCountWarn entries during the same time span matching the expression ORAAlertLogExprWarn, the check status will be Warning. Otherwise, it will be Ok.

The location of the Oracle alert log file is determined by the server Monitoring Parameter ORAAlertLogLocation. If this parameter is not set, the value from the DIAGNOSTIC_DEST (for Oracle 11g and newer) or BACKGROUND_DUMP_DEST (Oracle 10g and older) parameter is considered.

A Warning Check Result will be returned if the location cannot be determined.

The ORA_ALERTLOG check is not supported for systems using a remote database (i.e. ORADBRemote is set to 1)!

ORA_BACKUP

Verify RMAN backups

Description

This check verifies the availability and consistency of the latest backup performed with the Oracle Recovery Manager (RMAN).

The check is only executed if parameter ORABackupTool is set to RMAN which is the default for stand-alone Databases.

If your database is backed up with SAP BR*Tools, you should set ORABackupTool to BRBACKUP (default for SAP System. In this case this check is automatically deleted.

If you neither use RMAN nor the BR*Tools to backup your Oracle Database you are encouraged to disable this check.

Basically, a backup is considered available and consistent if it can be recovered by`RMAN`. So the check verifies if the control file, spfile, datafiles, and archive log files backups are consistent, and if the point in time they can be recovered to is not older than defined in the Monitoring Parameters BackupAgeWarn or BackupAgeCrit. Otherwise the check will report a corresponding Warning or Critical Check Result.

The consistency check of the backups comprises the verification of consistent`SCN`(System Change Numbers, Transaction Numbers) chains contained in valid incremental backups starting with a valid full backup.

The latest SCN of the newest complete incremental backup chains of the datafiles are searched for in the Redo Log Backup Sets, and starting from the oldest set, the Redo Log Backup _SCN_s are checked for consistency up to the last entry.

For further information on Backup Sets and SCNs, see the Oracle RMAN documentation.

If backups are written to disk, the check also verifies if the files are available on disk, unless parameter ORABackupSkipFilesCheck is set, or the database is monitored remotely (indicated by parameter ORADBRemote). The Avantra Agent needs the appropriate permissions on the file system to verify the existence of the files. Set the ORABackupSkipFilesCheck otherwise.

The check will return Critical also if no backup is found within the period defined by ORARMANSelectRange.

If you manipulate files already backed up (e.g. remove or rename them) using other tools than`RMAN`,`RMAN`may not know about these changes. Neither does the Avantra Agent. You should run a crosscheck within`RMAN`in this case.

The check is always related to the latest backup. It does not check if your Database can be restored using any backup before the latest one. It does, however, check if the redo logs required to restore the latest backup are all backed up, too.

ORA_BRARCHIVE

Verify BrArchive runs

Description

An overview of all BrArchive runs of during the last Full Check Cycle is listed in the Check Result.

If there are unsuccessful runs the check will result in a {Warning}. The check is only executed if parameter ORABackupTool is set to BRBACKUP which is the default for SAP System. If your database is not backed up with SAP BR*Tools, but with _RMAN, you should set ORABackupTool to RMAN (default for stand-alone Databases). In this case this check is automatically deleted.

If you neither use RMAN nor the BR*Tools to backup your Oracle Database you are encouraged to disable this check.

ORA_BRBACKUP

Verify Database backups performed with SAP BR*Tools

Description

This check type comprises two different sub-checks:

  • The return code of the latest backup is evaluated. If the return code is 0, the check status will be Ok, in case the value is 1, the status will be Warning.

    Otherwise the status is set to Critical.

  • If the latest successful backup (i.e. one with a return code 0 or 1) is older than a configured period of time, a Warning or Critical message is generated.

The check is only executed if parameter {ORABackupTool} is set to BRBACKUP which is the default for SAP System. If your database is not backed up with SAP BR*Tools, but with _RMAN, you should set ORABackupTool to RMAN(default for stand-alone Databases). In this case this check is automatically deleted.

If you neither use RMAN nor the BR*Tools to backup your Oracle Database you are encouraged to disable this check.

ORA_BRBACKUPSTAT

Verify Database backup performed with BR*Tools (RealTime Monitoring)

Description

This check type comprises two different sub-checks:

  • The return code of the latest backup is evaluated. If the return code is 0, the check status will be Ok, in case the value is 1, the status will be Warning. Otherwise the status is set to Critical. (This is exactly the same as the first sub-check of the ORA_BRBACKUP check.)

  • The runtime of the backup is verified. The runtime is compared with the average runtime of the previous 2 to 5 (if available) backups, and additionally it is compared against a static time threshold. This shall help to reduce false alerts especially if average backup times are small. If the current runtime takes more than ORABrbackupDelayWarn percent longer than the average and is above ORABrbackupDelayTimeWarn minutes, the check status is set to Warning. If it takes more than ORABrbackupDelayCrit percent longer and is above ORABrbackupDelayTimeCrit minutes, the check status is set to Critical.

    If we cannot compute an average, a value of 4 hours is assumed.

The check is only executed if parameter {ORABackupTool} is set to BRBACKUP which is the default for SAP System. If your database is not backed up with SAP BR*Tools, but with _RMAN, you should set ORABackupTool to`RMAN`(default for stand-alone Databases). In this case this check is automatically deleted.

If you neither use RMAN nor the BR*Tools to backup your Oracle Database you are encouraged to disable this check.

This check reports to the RealTime Monitoring. The parameter BackupResetRTMTime can be used to reset the check status back to Ok automatically after a certain period of time.

ORA_DATAFILES

Verify datafiles status and auto-extension

Description

This check comprises two sub-checks:

  • The status of each datafile is checked and a Critical alert is raised unless it is either ONLINE or SYSTEM.

  • The check calculates how many auto extent increments will fit into the filesystem where the datafile is located.

    If the number of increments is below ORADataFileIncrementsCrit, a Critical alert is reported, if it is below ORADataFileIncrementsWarn but not below ORADataFileIncrementsCrit, a Warning is raised.

    Please note that the check verifies for each datafile if there is enough space in its filesystem. It will not check if all datafiles located in the same filesystem can be auto-extended at the same time!

    The second part of the check is not available for remote databases (i.e. if ORADBRemote is set to 1).

ORA_DBAOPER

Verify Oracle DBA operations

Description

This check verifies certain Oracle DBA operations that are executed with BR*Tools.

The operations can be selected by defining their Function IDs (e.g. as listed in transaction DB14) in ORADBAOperFunctionIDs.

The check is only executed if the Monitoring Parameter ORASAPToolsEnable is set to 1, which is the default for SAP Systems. For stand-alone Databasesthis check is by default disabled, i.e. ORASAPToolsEnable is set to 0. If you enable the check you probably have to set the Monitoring Parameter ORASAPToolsSchema as well.

The check consists of two sub-checks: * The return code of the latest finished DBA operation is checked. If the return code is 0, the check status will be Ok, if it is 1, the check status will be Warning, otherwise the check status will be Critical. Running operations with RC=9999 are ignored. * It is verified if the latest successful DBA operation is not older than defined in the ORADBAOperAgeCrit or ORADBAOperAgeWarn thresholds. Otherwise the check status will be set accordingly.

By default, the following operations are checked: * Collect Optimizer Statistics * Database verification with DBVERIFY * Check Optimizer Statistics

See also the description of the Monitoring Parameter ORADBAOperFunctionIDs.

Reference Data
Managed Object

Oracle Database in conjunction with BR*Tools. In case of Java-only SAP Systems you need a kernel version ≥ 6.40

Check Cycle

Daily

Depends on

FULLCHECK

Monitoring Parameters

ORADBAOperFunctionIDs, ORADBAOperAgeCrit, ORADBAOperAgeWarn, ORADBAOperSelectRange, ORASAPToolsEnable, ORASAPToolsSchema, ORAHomeDir

ORA_DBCHECKLOG

Verify results of SAPDBA or BrConnect check runs

Description

The result of the latest sapdba -check or brconnect -f check run is parsed. If the last run is older than 24 hours, a Warning message is raised. Data is only searched for in the time span defined by ORABrToolsSelectRange.

Otherwise the result is not too old, it is analyzed as follows: If the result contains messages with W level the check returns a Warning, if the result contains messages with E level the check returns Critical.

The check is only executed if the Monitoring Parameter ORASAPToolsEnable is set to 1, which is the default for SAP Systems. For stand-alone Databasesthis check is by default disabled, i.e. ORASAPToolsEnable is set to 0. If you enable the check you probably have to set the Monitoring Parameter ORASAPToolsSchema as well.

ORA_Enqueue

Checks for enqueue deadlocks, timeouts, and waits.

Description

This Check collects enqueue statistics on timeouts, waits, and deadlocks. The statistics are temporarily stored with a timestamp. The Check then verifies if the statistics values exceed one of the defined thresholds in a certain time span.

For deadlocks, absolute numbers are collected and verified. As Oracle recommends to examine each deadlock, the default Critical threshold for deadlocks is set to 1.

Timeouts and waits are calculated as ratio to the total number of enqueue requests and conversions. This allows the Check to scale on huge Databases, where more enqueue requests will occur, resulting in more timeouts and wait events.

All thresholds can be configured by means of Monitoring Parameters. For each statistics value there are two separate thresholds for Warning and Critical check status available. By default, the Warning thresholds are disabled, i.e. they have the same default value as their corresponding Critical threshold. The threshold parameters are: ORAEnqueueDeadLocksCrit/ORAEnqueueDeadLocksWarn, ORAEnqueueTimeoutsCrit/ORAEnqueueTimeoutsWarn, ORAEnqueueWaitsCrit/ORAEnqueueWaitsWarn.

By setting a Critical threshold to 0 (or < 0), the associated statistics check is turned off; e.g. setting ORAEnqueueTimeoutsCrit to 0 disables the timeouts part of the check.

The time span by which the statistics are collected and verified can be configured using the ORAEnqueueTimeSpan Monitoring Parameter.

ORA_EXPSQL

Report expensive SQL statements

Description

An SQL statement is considered expensive if the amount of buffer-gets and disk-reads for the particular statement exceeds a certain amount of all buffer-gets and disk-reads. Warning and Critical thresholds can be defined for the gets and reads, and programs executing the statements can be excluded from the check.

ORA_FSLOGARCH

Verify ORAARCH filesystems

Description

A special case of the FILESYSTEMS check for ORAARCH filesystems with separate thresholds.

The ORAARCH filesystems are detected automatically. This check is not supported for remote databases (i.e. ORADBRemote is set to 1).

ORA_LOG_MODE

Verify if the database runs in archive log mode

Description

This check verifies if the Database runs in archive log mode and returns Critical if not.

ORA_SEGMENTS

Watch extent management

Description

The check analyzes the Oracle segments (e.g. tables and indexes) of tablespaces with dictionary extent management and permanent storage in two ways:

  • If the number of allocated extents exceeds a configurable threshold of the segment’s maximum number of extents (as defined by the table or index storage parameter max_extents) a corresponding Warning or Critical alert is issued.

  • A Critical alert is issued if the continuous space in a tablespace is not large enough to allocate another extent (known as table or index storage parameter next_extent) for a segment.

For databases with locally managed tablespaces only, the Check Result simply displays a message:

Database does not contain tablespaces with dictionary extent management
and permanent content.

If the check status is Ok, and if the database contains dictionary extent management tablespaces, the check will display the covered tablespaces:

Segments are checked in tablespaces with dictionary extent management and
permanent content: PSAPC11DB, SYSTEM
All segments can allocate another extent.
All segments' number of extents are below threshold.

Due to resource consumption, this check is by default configured to run only every 60 minutes (see ORASegsChkWaitTime) in RealTime Monitoring. This check also runs in the Daily Check

ORA_Sessions

Verify number of waiting sessions and wait time.

Description

This Check counts the number of waiting sessions, considering wait time, wait class, and wait status of each session.

For each session waiting and holding a matching wait class (at time of Check execution), the wait time is compared against a Warning and a Critical wait time threshold (Monitoring Parameters ORASessionsTimeWaitWarn and ORASessionsTimeWaitCrit). All Warning and Critical sessions are counted, and the counter is compared against a count threshold (Monitoring Parameter ORASessionsCountWait). If the count threshold is exceeded by the Critical sessions, the check will be Critical otherwise if the count threshold is exceeded by the Critical and Warning sessions, the check will be Warning.

The wait class of a session is considered to filter out sessions not accounting for the check status. The wait class filter can be configured by means of the ORASessionsIgnoreWaitClass Monitoring Parameter.

ORA_TABLESPACES

Verify tablespace usage

Description

An alert is raised if the tablespace usage exceeds some configurable threshold, or if the predicted tablespace exhaustion is within a configurable period of time.

Exceptions to the general Warning and Critical thresholds may be defined on a per tablespace level.

For tablespaces with auto-extent enabled, the maximum allocatable space (in the check message labeled`auto-extent free`) is considered as free space for usage and remaining free space calculations, and not the real free space (labeled`free`) considering the currently allocated tablespace size.

The value of auto-extent free is not limited by the effective free space of the filesystems holding the tablespace’s datafiles. The ORA_DATAFILES check, however, verifies if auto-extensible datafiles can be extended within their filesystems.

SIQ_Backup

Verifies backups done with Sybase IQ “BACKUP DATABASE” command

Description

The check verifies if the last backup for each database was successful. If the last backup has failed, the check result will be Warning.

Then the check looks for the last successful backup of the database. If there is none at all (at least none in SIQBackupSelectRange days) or if the time since the last dump is above threshold BackupAgeCrit, the check result will be Critical.

If there is a successful backup and the time since the last backup is below BackupAgeCrit but above SIQBackupAgeWarn the check result will be Warning.

SIQ_DataFiles

Verifies the usage of all datafiles

Description

The check verifies if enough free space is available in all datafiles. If the usage or the amount of remaining free space is exceeding/falling below SIQDataFilesUsageCrit the check status will be Critical. If the usage or the amount of remaining free space is exceeding/falling below SIQDataFilesUsageWarn but is still below/above SIQDataFilesUsageCrit, the status will be warning.

The total check status is the worst of all sub-status of all datafiles. You can see the sub-result for each datafile in the table provided. This checks features Monitoring Exception Parameters so you may define individual thresholds for certain databases.

SIQ_Connections

Alarm is triggered when there are too few connections available

Description

The check retrieves a current database connection figures and evaluates a number of free connections, that is, the number of connections the database can accept additionally. The more available connections, the better.

If the evaluated figure falls below or equals SIQ_ConnectionsWarn, but is more than SIQConnectionsCrit, the check result is WARNING. If the evaluated figure is less than or equals SIQConnectionsCrit, the check result is CRITICAL.

Reference Data
Managed Object

Sybase IQ Database

Check Cycle

Basic

Depends on

DBCONNECT

Monitoring Parameters

SIQConnectionsCrit and SIQConnectionsWarn

SIQ_Cache

Monitors/alerts on high IQ Caches consumption

Description

The check queries the database to get information on Main, Temp and Catalog Cache sizes, usage and hit ratio. There is one sub-check per cache. Each check is comparing a cache usage with the thresholds and returns a corresponding result.

The less cache is used, the better. If the cache usage goes above or equals SIQ<cache_name>CacheUsageWarn parameter value, but not reaches SIQ<cache_name>CacheCrit parameter value, the sub-check result is WARNING. If the cache usage goes above or equals SIQ<cache_name>CacheCrit parameter value, the sub-check result is CRITICAL.

SIQ_LongTransactions

Evaluates a number of the transactions running longer than specified period of time.

Description

The check retrieves all the transactions currently running and counts ones running longer than time specified with SIQTransactionRuntime. The less long-running transactions are there, the better

If the evaluated figure exceeds or equals SIQLongTransactionsWarn, but is less than SIQLongTransactionsCrit, the check result is WARNING. If the evaluated figure is more than or equals SIQLongTransactionsCrit, the check result is CRITICAL.

SIQ_OperationsWaiting

Alarm is triggered if there are too many active transactions running longer, than defined runtime threshold

Description

During the check, a number of operations waiting for the resource governor is evaluated. The less operations are in the queue, the better

If the evaluated figure exceeds or equals SIQOperationsWaitingWarn, but is less than SIQOperationsWaitingCrit, the check result is WARNING. If the evaluated figure is more than or equals SIQOperationsWaitingCrit, the check result is CRITICAL.

SIQ_Threads

The check is evaluating a number of server threads available for serving tasks. Alarm is issued, in case there are too few threads available

Description

The check retrieves a current amount of database server threads available for use. The more threads available, the better.

If the evaluated figure falls below or equals SIQThreadsWarn, but is still more than SIQThreadsCrit, the check result is WARNING. If the evaluated figure is less than or equals SIQThreadsCrit, the check result is CRITICAL.

Reference Data
Managed Object

Sybase IQ Database

Check Cycle

Basic

Depends on

DBCONNECT

Monitoring Parameters

SIQThreadsWarn and SIQThreadsCrit

SIQ_DataSpaces

Verifies the free space of all dataspaces

Description

The check verifies if enough free space is available in all dataspaces. If the usage or the amount of remaining free space is exceeding/falling below SIQDataSpacesUsageCrit the check status will be Critical. If the usage or the amount of remaining free space is exceeding/falling below SIQDataSpacesUsageWarn but is still below/above SIQDataSpacesUsageCrit, the status will be warning.

The total check status is the worst of all sub-status of all dataspaces. You can see the sub-result for each dataspace in the table provided. This checks features Monitoring Exception Parameters so you may define individual thresholds for certain dataspaces.

SYB_Backup

Verifies backups done with Sybase DUMP DATABASE command

Description

The check verifies if the last dump for each database was successful. If the last dump has failed, the check result will be Warning.

Then the check looks for the last successful dump for each database. If there is none at all (at least none in SYBBackupSelectRange days) or if the time since the last dump is above threshold BackupAgeCrit, the check result will be Critical.

If there is a successful dump and the time since the last dump is below BackupAgeCrit but above BackupAgeWarn the check result will be Warning.

The total check status is the worst of all sub-status of all databases. You can see the sub-result for each database in the table provided. Please note that the size of backup dump files can only be displayed if the file still exists on the file system. You may exclude databases which are not backed up using parameter SYBBackupExclude. Most databases which 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_BackupStat

Verifies last finished or runtime of currently processing backup done with Sybase DUMP DATABASE command

Description

The check complements the Daily Check SYB_Backup by a RealTime Monitoring check, which immediately displays a Warning or Critical status when the last backup has failed. The status displayed after a backup has failed can be configured with monitoring parameter SYBBackupStatFailedStatus. SYBBackupStatFailedDisplayTime minutes after the failed backup has been detected, the check result status is reset to Ok.

If a backup is currently being processed, the check verifies the current runtime since backup start and compares it against the average backup time of the last 5 successful backups, and additionally it is compared against a static time threshold. This shall help to reduce false alerts especially if average backup times are small. If the current runtime takes more than 50 percent longer than the average and is above SYBBackupStatDelayTimeWarn minutes the check status is set to Warning. If it takes more than 100 percent longer and is above SYBBackupStatDelayTimeCrit minutes the check status is set to Critical.

If no 5 successful backup are found the check takes the average runtime of as many backups as possible. If none is found at all, the average runtime is initialized to 2 hours.

Please note that this check does not check the age of the last successful backup. This is done by Daily Check SYB_Backup.

SYB_DataBases

Verifies the durability status of databases and if databases with suspect pages are found

Description

The check verifies the durability status of all databases found and checks if it is set to full. Temporary databases have durability status no_recovery and are automatically excluded. If a database with a durability status not equal to full or at_shutdown is found, the check result will be Warning.

More important, the check verifies if suspect pages are reported for a database. If yes, the check status will be Critical. If a database is marked as suspect, you should find the reason for this. Usually there are entries in the error log. Please refer to Sybase/SAP documentation on how to proceed and how to reset the suspect status.

The check’s table includes many information for your reference and overview. The same data is checked elsewhere, e.g. in checks SYB_DataSpaces and SYB_LogSpaces.

Reference Data
Managed Object

Sybase ASE Database

Check Cycle

Basic

Depends on

DBCONNECT

Monitoring Parameters

n/a

SYB_DataSpaces

Verifies data space of all databases

Description

The check verifies if enough data space is available in all databases. If the usage or the amount of remaining free space is exceeding/falling below SYBDBUsageCrit the check status will be Critical. If the usage or the amount of remaining free space is exceeding/falling below SYBDBUsageWarn but is still below/above SYBDBUsageCrit, the status will be warning.

The total check status is the worst of all sub-status of all databases. You can see the sub-result for each database in the table provided. This checks features Monitoring Exception Parameters so you may define individual thresholds for certain databases.

SYB_ErrorLog

Queries and verifies the Sybase error log

Description

The check queries the Sybase error log for entries within the last day. If Monitoring Parameter RunDailyCheckOnWE is false, the check queries the error log for the last 2 days on Sundays, and for the last 3 days on Mondays, to make sure you do not miss any entries.

The check status is Ok, if no entries at all or only entries with severity level 0 or 10 are found. If any entries with severity level >=11 and ⇐16 are found, the check status is Warning. If entries with severity level 17 or above are found, the check result will be critical.

Severity level 17 means Insufficient Resources, for example space allocation fails du to missing free extents in a data segment.

Severity level 21 and above means, that SAP ASE need to be restarted or is damaged and must be repaired.

Please check the SAP Sybase ASE guide System Administration Guide: Volume 1 for information on severity levels and how to proceed in case you encounter severe error log entries.

Monitoring Parameter SYBErrorLogExcludeErrNums may be used to exclude certain error numbers from being checked.

Enter a comma or blank separated list of numbers to specify multiple values.

SYB_ErrorLogStat

Queries and verifies the Sybase error log for RealTime Monitoring.

Description

SYB_ErrorLogStat does the same as SYB_ErrorLog — monitoring the ASE error log, but queries it for entries within last SYBErrorLogTimeSpan minutes only and reports to RealTime Monitoring.

SYB_LogBackup

Monitors the transaction log backup age.

Description

SYB_LogBackup monitors, if the last transaction log backup is recent enough. This is important to ensure recoverability of your databases.

If the last transaction log dump is above SYBLogBackupAgeWarn minutes ago, but below SYBLogBackupAgeCrit minutes, the check status is Warning. If the last transaction log dump is above SYBLogBackupAgeCrit minutes ago, the check result is Critical. If a database reports a full transaction log, the check result is reported Critical. Please note that a full transaction log should usually not happen, since exhausting log space should be reported in advance by the SYB_LogSpaces check.

You may exclude databases from being checked by adding the name of the database to the comma separated list defined by Monitoring Parameter SYBLogBackupExclude. By default, many system databases are already excluded by default. However, databases are still checked for full transaction log, no matter if excluded or not.

SYB_LogSpaces

Verifies log space of all databases

Description

This check corresponds to the SYB_DataSpaces check but verifies if enough log space is available in all databases. If the usage or the amount of remaining free space is exceeding/falling below SYBLogUsageCrit, the check status will be Critical. If the usage or the amount of remaining free space is exceeding/falling below SYBLogUsageWarn but is still below/above SYBLogUsageCrit, the status will be warning.

The total check status is the worst of all sub-status of all databases. You can see the sub-result for each database in the table provided. In contrast to SYB_DataSpaces, this Check does not feature Monitoring Exception Parameters.