## 9.8 Reference: Alerts
This reference section gives details of all alerts and includes links to any related SAP Notes.
All alerts include a recommended user action and for many alerts a corresponding SAP Note is available. In column 4 of the following table ('Configuration') an asterisk '*' identifies alerts which have multiple configurable severity thresholds, Info-only alerts are flagged by 'Info', and those with only a single configurable value with '1'.
## Alerts
|   ID | Name                                 | Description                                                                                                                                                          | Cfg   | User Action                                                                                                                                           | Category     | Further Infor­ mation                     |
|------|--------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|-------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|------------------------------------------|
|    0 | Internal statis­ tics server prob­ lem | Identifies internal statistics server problem.                                                                                                                       |       | Resolve the problem. For more information, see the trace files. You may need to activate tracing first.                                               | Availability | SAP Note: 1803039                        |
|    1 | Host physical memory usage           | Determines what percentage of total physical memory available on the host is used. All processes consuming memory are considered, in­ cluding non-SAP HANAproc­ esses. | *     | Investigate memory usage of processes.  Note Only relevant inHANA 1.0. Not active inHANA 2.0. See SAP Note: 2757696 Alert 1 shows wrong information  | Memory       | SAP Note: 1898317 SAP Note:1840954       |
|    2 | Disk usage                           | Determines what percentage of each disk containing data, log, and trace files is used. This includes space used by non-SAP HANAfiles.                                | *     | Investigate disk usage of processes. Increase disk space, for example by shrink­ ing volumes, deleting diagno­ sis files, or adding additional storage. | Disk         | SAP Note: 1900643                        |
|    3 | Inactive services                    | Identifies inactive services.                                                                                                                                        | 1     | Investigate why the service is inactive, for example, by checking the service's trace files.                                                          | Availability | Inactive > 600 seconds. SAP Note:1902033 |
|    4 | Restarted serv­ ices                  | Identifies services that have restarted since the last time the check was performed.                                                                                 |       | Investigate why the service had to restart or be re­ started, for example, by checking the service's trace files.                                      | Availability | SAP Note: 1909660                        |
|    5 | Host CPU Usage                       | Determines the percentage CPU idle time on the host and therefore whether or not CPU resources are running low.                                                      | *     | Investigate CPU usage.                                                                                                                                | CPU          | SAP Note: 1909670                        |
<!-- image -->
<!-- image -->
|   ID | Name                                                 | Description                                                                                                                                                                                                                                                                    | Cfg   | User Action                                                                                                                                                                          | Category       | Further Infor­ mation                                                 |
|------|------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|----------------------------------------------------------------------|
|   10 | Delta merge (mergedog) con­ figuration                | Determines whether or not the 'active' parameter in the 'mergedog' section of system configuration file(s) is 'yes'. mergedog is the system process that periodically checks column tables to de­ termine whether or not a delta merge operation needs to be executed.          |       | Change in SYSTEM layer the parameter active in sec­ tion(s) mergedog to yes                                                                                                           | Configura­ tion | SAP Note: 1909641                                                    |
|   12 | Memory usage of name server                          | Determines what percentage of allocated shared memory is being used by the name server on a host.                                                                                                                                                                              | *     | Increase the shared memory size of the name server. In the 'topology' section of the nameserver.ini file, increase the value of the 'size' param­ eter.                               | Memory         | SAP Note: 1977101                                                    |
|   16 | Lock wait time­ out configura­ tion                    | Determines whether the 'lock_wait_timeout' parame­ ter in the 'transaction' sec­ tion of the indexserver.ini file is between 100,000 and 7,200,000.                                                                                                                              |       | In the 'transaction' section of the indexserver.ini file, set the 'lock_wait_timeout' pa­ rameter to a value between 100,000 and 7,200,000 for the System layer.                      | Configura­ tion | SAP Note: 1909707                                                    |
|   17 | Record count of non-partitioned column-store ta­ bles | Determines the number of records in non-partitioned column-store tables. Current table size is not critical. Parti­ tioning need only be consid­ ered if tables are expected to grow rapidly (a non-parti­ tioned table cannot contain more than 2,147,483,648 (2 billion) rows). | Info  | Consider partitioning the ta­ ble only if you expect it to grow rapidly.                                                                                                              | Memory         | SAP HANAAd­ ministration Guide > Table Partitioning, SAP Note:1909763 |
|   20 | Table growth of non-partitioned column-store ta­ bles | Determines the growth rate of non-partitioned columns tables.                                                                                                                                                                                                                  | *     | Consider partitioning the ta­ ble. See also: Guided Answer: How to reduce the size of a table.                                                                                        | Memory         | SAP HANAAd­ ministration Guide > Table Partitioning, SAP Note:1910140 |
|   21 | Internal event                                       | Identifies internal database events.                                                                                                                                                                                                                                           | *     | Resolve the event and then mark it as resolved by exe­ cuting the SQL statement ALTER SYSTEM SET EVENT HANDLED '<host>:<port>' <id>. Note that this is not necessary for INFO events. | Availability   | SAP Note: 1977252                                                    |
Further Infor­
<!-- image -->
<!-- image -->
|   ID | Name                                            | Description                                                                                                                                                                                               | Cfg   | User Action                                                                                                                                                                                    | Category                | mation                                                               |
|------|-------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|----------------------------------------------------------------------|
|   22 | Notification of all alerts                      | Determines whether or not there have been any alerts since the last check and if so, sends a summary e-mail to specified recipients.                                                                      |       | Investigate the alerts.                                                                                                                                                                        | Availability            |                                                                      |
|   23 | Notification of medium and high priority alerts | Determines whether or not there have been any medium and high priority alerts since the last check and if so, sends a summary e-mail to specified recipients.                                             |       | Investigate the alerts.                                                                                                                                                                        | Availability            |                                                                      |
|   24 | Notification of high priority alerts            | Determines whether or not there have been any high pri­ ority alerts since the last check and if so, sends a sum­ mary e-mail to specified re­ cipients.                                                     |       | Investigate the alerts.                                                                                                                                                                        | Availability            |                                                                      |
|   25 | Open connec­ tions                               | Determines what percentage of the maximum number of permitted SQL connections are open. The maximum number of permitted con­ nections is configured in the "session" section of the in­ dexserver.ini file. | *     | Investigate why the maxi­ mumnumberof permitted open connections is being approached.                                                                                                           | Sessions/ Transac­ tions | SAP Note: 1910159                                                    |
|   26 | Unassigned vol­ umes                             | Identifies volumes that are not assigned a service.                                                                                                                                                       |       | Investigate why the volume is not assigned a service. For example, the assigned serv­ ice is not active, the removal of a host failed, or the re­ moval of a service was per­ formed incorrectly. | Configura­ tion          | SAP Note: 1910169                                                    |
|   27 | Record count of column-store ta­ ble partitions  | Determines the number of records in the partitions of column-store tables. A table partition cannot contain more than 2,000,000,000 (2 billion) rows.                                                     | *     | Consider repartitioning the table.                                                                                                                                                             | Memory                  | SAP HANAAd­ ministration Guide > Table Partitioning, SAP Note:1910188 |
|   28 | Most recent sa­ vepoint opera­ tion               | Determines how long ago the last savepoint was defined, that is, how long ago a com­ plete, consistent image of the database was persisted to disk.                                                        | *     | Investigate why there was a delay defining the last save­ point and consider triggering the operation manually by executing the SQL statement ALTER SYSTEM SAVEPOINT.                           | Disk                    | SAP Note: 1977291                                                    |
|   29 | Size of delta storage of col­ umn-store ta­ bles  | Determines the size of the delta storage of column ta­ bles.                                                                                                                                               | *     | Investigate the delta merge history in the monitoring view M_DELTA_MERGE_STA­ TISTICS. Consider merging the table delta manually.                                                               | Memory                  | SAP Note: 1977314                                                    |
<!-- image -->
|   ID | Name                           | Description                                                                                                                                                                                                          | Cfg   | User Action                                                                                                                                                                                                                                                                                                                                                                              | Category     | Further Infor­ mation                                                                               |
|------|--------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|----------------------------------------------------------------------------------------------------|
|   30 | Check internal disk full event | Determines whether or not the disks to which data and log files are written are full. A disk-full event causes your database to stop and must be resolved.                                                           | *     | Resolve the disk-full event as follows: In the Administration Editor on the Overview tab, choose the "Disk Full Events" link and mark the event as handled. Alternatively, exe­ cute the SQL statements AL­ TER SYSTEM SET EVENT ACKNOWLEDGED '<host>:<port>' <id> and AL­ TER SYSTEM SET EVENT HANDLED '<host>:<port>' <id>.                                                               | Disk         | SAP Note: 1898460                                                                                  |
|   31 | License expiry                 | Determines how many days until your license expires. Once your license expires, you can no longer use the system, except to install a new license.                                                                   | *     | Obtain a valid license and in­ stall it. For the exact expira­ tion date, see the monitoring view M_LICENSE.                                                                                                                                                                                                                                                                               | Availability | Security, Author­ ization and Li­ censing, SAP Note:1899480                                          |
|   32 | Log mode LEG­ ACY               | Determines whether or not the database is running in log mode "legacy". Log mode "legacy" does not support point-in-recovery and is not recommended for productive systems.                                          |       | If you need point-in-time re­ covery, reconfigure the log mode of your system to "nor­ mal". In the "persistence" section of the global.ini con­ figuration file, set the param­ eter "log_mode" to "normal" for the System layer. When you change the log mode, you must restart the data­ base system to activate the changes. It is also recom­ mended that you perform a full data backup. | Backup       | Configuration Parameter Is­ sues. SAP Note: 1900296                                                 |
|   33 | Log mode OVER­ WRITE            | Determines whether or not the database is running in log mode "overwrite". Log mode "overwrite" does not support point-in-recovery (only recov­ ery to a data backup) and is not recommended for pro­ ductive systems. |       | If you need point-in-time re­ covery, reconfigure the log mode of your system to "nor­ mal". In the "persistence" section of the global.ini con­ figuration file, set the param­ eter "log_mode" to "normal" for the System layer. When you change the log mode, you must restart the data­ base system to activate the changes. It is also recom­ mended that you perform a full data backup. | Backup       | SAP HANAAd­ ministration Guide > Backing up and Recover­ ing the SAP HANADatabase. SAP Note: 1900267 |
|   ID | Name                               | Description                                                                                               | Cfg   | User Action                                                                                                           | Category                | Further Infor­ mation                                                                               |
|------|------------------------------------|-----------------------------------------------------------------------------------------------------------|-------|-----------------------------------------------------------------------------------------------------------------------|-------------------------|----------------------------------------------------------------------------------------------------|
|   34 | Unavailable vol­ umes               | Determines whether or not all volumes are available.                                                      |       | Investigate why the volume is not available.                                                                          | Configura­ tion          | SAP HANAAd­ ministration Guide > Backing up and Recover­ ing the SAP HANADatabase, SAP Note: 1900682 |
|   35 | Existence of data backup           | Determines whether or not a data backup exists. Without a data backup, your database cannot be recovered. |       | Perform a data backup as soon as possible.                                                                            | Backup                  | SAP HANAAd­ ministration Guide > Backing up and Recover­ ing the SAP HANADatabase, SAP Note: 1900728 |
|   36 | Status of most recent data backup  | Determines whether or not the most recent data backup was successful.                                     |       | Investigate why the last data backup failed, resolve the problem, and perform a new data backup as soon as pos­ sible. | Backup                  | SAP HANAAd­ ministration Guide > Backing up and Recover­ ing the SAP HANADatabase, SAP Note: 1900795 |
|   37 | Age of most re­ cent data backup    | Determines the age of the most recent successful data backup.                                             | *     | Perform a data backup as soon as possible.                                                                            | Backup                  | SAP HANAAd­ ministration Guide > Backing up and Recover­ ing the SAP HANADatabase, SAP Note: 1900730 |
|   38 | Status of most recent log back­ ups | Determines whether or not the most recent log backups for services and volumes were successful.           |       | Investigate why the log backup failed and resolve the problem.                                                        | Backup                  | SAP HANAAd­ ministration Guide > Backing up and Recover­ ing the SAP HANADatabase, SAP Note: 1900788 |
|   39 | Long-running statements            | Identifies long-running SQL statements.                                                                   | *     | Investigate the statement. For more information, see the table _SYS_STATIS­ TICS.HOST_LONG_RUN­ NING_STATEMENTS.        | Sessions/ Transac­ tions | SAP Note: 1849392                                                                                  |
<!-- image -->
|   ID | Name                                                | Description                                                                                                                                                                                                      | Cfg   | User Action                                                                                                                                                                                                                            | Category                | Further Infor­ mation               |
|------|-----------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|------------------------------------|
|   40 | Total memory usage of col­ umn-store ta­ bles         | Determines what percentage of the effective allocation limit is being consumed by individual column-store ta­ bles as a whole (that is, the cumulative size of all of a ta­ ble's columns and internal structures) | *     | Consider partitioning or re­ partitioning the table.                                                                                                                                                                                    | Memory                  | SAP Note: 1977268                  |
|   41 | In-memory Da­ taStore activa­ tion                    | Determines whether or not there is a problem with the activation of an in-memory DataStore object.                                                                                                               |       | For more information, see the table _SYS_STATIS­ TICS.GLOBAL_DEC_EX­ TRACTOR_STATUS and SAP Note 1665553.                                                                                                                                | Availability            | SAP Note: 1665553 SAP Note:1977230 |
|   42 | Long-running / idling cursors.                      | Identifies long-running / idling cursors.                                                                                                                                                                        | *     | Close the cursor in the appli­ cation, or kill the connection by executing the SQL state­ ment ALTER SYSTEM DIS­ CONNECT SESSION <LOGI­ CAL_CONNECTION_ID>. For more information, see the ta­ ble HOST_LONG_IDLE_CUR­ SOR (_SYS_STATISTICS). | Sessions/ Transac­ tions | SAP Note: 1900261                  |
|   43 | Memory usage of services                            | Determines what percentage of its effective allocation limit a service is using.                                                                                                                                 | *     | Check for services that con­ sume a lot of memory.                                                                                                                                                                                      | Memory                  | SAP Note: 1900257                  |
|   44 | Licensed mem­ ory usage                              | Determines what percentage of licensed memory is used.                                                                                                                                                           | Info  | Increase licensed amount of main memory. You can see the peak memory allocation since installation in the sys­ tem view M_LICENSE (col­ umnPRODUCT_USAGE).                                                                               | Memory                  | SAP Note: 1899511                  |
|   45 | Memory usage of main storage of column-store tables | Determines what percentage of the effective allocation limit is being consumed by the main storage of individual column-store tables.                                                                            | *     | Consider partitioning or re­ partitioning the table.                                                                                                                                                                                    | Memory                  | SAP Note: 1977269                  |
|   46 | RTEdump files                                       | Identifies new runtime dump files (*rtedump*) have been generated in the trace direc­ tory of the system. These contain information about, for example, build, loaded modules, running threads, CPU, and so on.   |       | Check the contents of the dump files.                                                                                                                                                                                                  | Diagnosis Files         | SAP Note: 1977099                  |
Further Infor­
|   ID | Name                                         | Description                                                                                                                                                                                                                                     | Cfg   | User Action                                                                                                                                                                                                                                                          | Category                | mation                            |
|------|----------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-----------------------------------|
|   47 | Long-running se­ rializable trans­ actions     | Identifies long-running serial­ izable transactions.                                                                                                                                                                                             | *     | Close the serializable trans­ action in the application or kill the connection by execut­ ing the SQL statement AL­ TER SYSTEM DISCONNECT SESSION <LOGICAL_CON­ NECTION_ID>. For more in­ formation, see the table HOST_LONG_SERIALIZA­ BLE_TRANSACTION (_SYS_STATISTICS). | Sessions/ Transac­ tions | Transactional Problems            |
|   48 | Long-running uncommitted write transac­ tions | Identifies long-running un­ committed write transac­ tions.                                                                                                                                                                                       | *     | Close the uncommitted transaction in the application or kill the connection by exe­ cuting the SQL statement ALTER SYSTEM DISCON­ NECT SESSION <LOGI­ CAL_CONNECTION_ID>. For more information, see the ta­ ble HOST_UNCOMMIT­ TED_WRITE_TRANSACTION (_SYS_STATISTICS).   | Sessions/ Transac­ tions | SAP Note: 1977276                 |
|   49 | Long-running blocking situa­ tions            | Identifies long-running block­ ing situations.                                                                                                                                                                                                   | *     | Investigate the blocking and blocked transactions and if appropriate cancel one of them.                                                                                                                                                                             | Sessions/ Transac­ tions | SAP Note: 2079396                 |
|   50 | Number of diag­ nosis files                   | Determines the number of di­ agnosis files written by the system (excluding zip­files). An unusually large number of files can indicate a problem with the database (for exam­ ple, problem with trace file rotation or a high number of crashes). | 1     | Investigate the diagnosis files.                                                                                                                                                                                                                                     | Diagnosis Files         | See KBA 1977162, SAP Note:1977162 |
|   51 | Size of diagnosis files                      | Identifies large diagnosis files. Unusually large files can indicate a problem with the database.                                                                                                                                               | *     | Check the diagnosis files in the SAP HANAstudio for de­ tails.                                                                                                                                                                                                        | Diagnosis Files         | See KBA 1977208, SAP Note:1977208 |
|   52 | Crashdump files                              | Identifies new crashdump files that have been gener­ ated in the trace directory of the system.                                                                                                                                                  |       | Check the contents of the dump files.                                                                                                                                                                                                                                | Diagnosis Files         | SAP Note: 1977218                 |
|   53 | Pagedump files                               | Identifies new pagedump files that have been gener­ ated in the trace directory of the system.                                                                                                                                                   |       | Check the contents of the dump files.                                                                                                                                                                                                                                | Diagnosis Files         | SAP Note: 1977242                 |
Further Infor­
<!-- image -->
<!-- image -->
<!-- image -->
|   ID | Name                                                   | Description                                                                                                                                                                                                                         | Cfg   | User Action                                                                                              | Category                | mation                                                                                          |
|------|--------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|----------------------------------------------------------------------------------------------------------|-------------------------|-------------------------------------------------------------------------------------------------|
|   54 | Savepoint dura­ tion                                    | Identifies long-running save­ point operations.                                                                                                                                                                                      | *     | Check disk I/O performance.                                                                              | Backup                  | CPU Related Root Causes and Solutions, I/O Related Root Causes and Sol­ utions, SAP Note:1977220 |
|   55 | Columnstore un­ loads                                   | Determines how many col­ umns in columnstore tables have been unloaded from memory. This can indicate performance issues.                                                                                                            | *     | Check sizing with respect to data distribution.                                                          | Memory                  | SAP Note: 1977207                                                                               |
|   56 | Python trace ac­ tivity                                 | Determines whether or not the python trace is active and for how long. The python trace affects system per­ formance.                                                                                                                | *     | If no longer required, deacti­ vate the python trace in the relevant configuration file.                  | Diagnosis Files         | SAP Note: 1977098                                                                               |
|   57 | Instance secure store file system (SSFS) inacces­ sible | Determines if the instance secure store in the file sys­ tem (SSFS) of your SAP HANAsystem is accessible to the database.                                                                                                            |       | Check and make sure that the instance SSFS is accessi­ ble to the database.                               | Security                | SAP Note: 1977221                                                                               |
|   58 | Plan cache size                                        | Determines whether or not the plan cache is too small.                                                                                                                                                                              | Info  | Currently Alert 58 is inactive and replaced by Alert 91. Please activate Alert 91 - Plan Cache Hit Ratio | Memory                  | SAP Note: 1977253                                                                               |
|   59 | Percentage of transactions blocked                     | Determines the percentage of transactions that are blocked.                                                                                                                                                                         | *     | Investigate blocking and blocked transactions and if appropriate cancel some of them.                    | Sessions/ Transac­ tions | SAP Note: 2081856                                                                               |
|   60 | Sync/Async read ratio                                  | Identifies a bad trigger asyn­ chronous read ratio. This means that asynchronous reads are blocking and be­ have almost like synchronous reads. This might have nega­ tive impact on SAP HANAI/O performance in certain sce­ narios.    | Info  | Please refer to SAP note 1930979.                                                                        | Disk                    | I/O Related Root Causes and Sol­ utions, SAP Note:1965379                                        |
|   61 | Sync/Async write ratio                                 | Identifies a bad trigger asyn­ chronous write ratio. This means that asynchronous writes are blocking and be­ have almost like synchronous writes. This might have nega­ tive impact on SAP HANAI/O performance in certain sce­ narios. | Info  | Please refer to SAP note 1930979.                                                                        | Disk                    | I/O Related Root Causes and Sol­ utions, SAP Note:1965379                                        |
Further Infor­
<!-- image -->
<!-- image -->
<!-- image -->
|   ID | Name                                          | Description                                                                                                                                                                                                                                                                                                                                                                                                                    | Cfg   | User Action                                                                                 | Category   | mation                                          |
|------|-----------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|---------------------------------------------------------------------------------------------|------------|-------------------------------------------------|
|   62 | Expiration of da­ tabase user passwords        | Identifies database users whose password is due to ex­ pire in line with the config­ ured password policy. If the password expires, the user will be locked. If the user in question is a technical user, this may impact application availability. It is recom­ mended that you disable the password lifetime check of technical users so that their password never expires (AL­ TER USER <username> DIS­ ABLE PASSWORDLIFE­ TIME). |       | Change the password of the database user.                                                   | Security   | SAP Note: 2082406                               |
|   63 | Granting of SAP_INTER­ NAL_HANA_SU PPORT role  | Determines if the internal support role (SAP_INTER­ NAL_HANA_SUPPORT) is currently granted to any da­ tabase users.                                                                                                                                                                                                                                                                                                              | 1     | Check if the corresponding users still need the role. If not, revoke the role from them.    | Security   | SAP Note: 2081857                               |
|   64 | Total memory usage of table- based audit log  | Determines what percentage of the effective memory allo­ cation limit is being con­ sumed by the database table used for table-based audit logging. If this table grows too large, the availability of the database could be im­ pacted.                                                                                                                                                                                          | *     | Consider exporting the con­ tent of the table and then truncating the table.                 | Memory     | SAP Note: 2081869                               |
|   65 | Runtime of the log backups cur­ rently running | Determines whether or not the most recent log backup terminates in the given time.                                                                                                                                                                                                                                                                                                                                             | *     | Investigate why the log backup runs for too long, and resolve the issue.                    | Backup     | SAP HANAAd­ ministration Guide, SAP Note:2081845 |
|   66 | Storage snap­ shot is prepared                 | Determines whether or not the period, during which the database is prepared for a storage snapshot, exceeds a given threshold.                                                                                                                                                                                                                                                                                                 | *     | Investigate why the storage snapshot was not confirmed or abandoned, and resolve the issue. | Backup     | SAP HANAAd­ ministration Guide, SAP Note:2081405 |
|   67 | Table growth of rowstore tables               | Determines the growth rate of rowstore tables                                                                                                                                                                                                                                                                                                                                                                                  | *     | Try to reduce the size of row store table by removing un­ used data                          | Memory     | SAP Note: 2054411                               |
|   68 | Total memory usage of row store               | Determines the current memory size of a row store used by a service                                                                                                                                                                                                                                                                                                                                                            | *     | Investigate memory usage by row store tables and consider cleanup of unused data            | Memory     | SAP Note: 2050579                               |
<!-- image -->
|   ID | Name                                                             | Description                                                                                                                          | Cfg   | User Action                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | Category       | Further Infor­ mation                            |
|------|------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------|-------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|-------------------------------------------------|
|   69 | Enablement of automatic log backup                               | Determines whether auto­ matic log backup is enabled.                                                                                 |       | Enable automatic log backup. For more details please see SAP HANAAdministration Guide.                                                                                                                                                                                                                                                                                                                                                                                                 | Backup         | SAP HANAAd­ ministration Guide, SAP Note:2081360 |
|   70 | Consistency of internal system components af­ ter system up­ grade | Verifies the consistency of schemas and tables in inter­ nal system components (for example, the repository) af­ ter a system upgrade. |       | Contact SAP support.                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | Availability   |                                                 |
|   71 | Row store frag­ mentation                                         | Check for fragmentation of row store.                                                                                                |       | Implement SAP Note 1813245.                                                                                                                                                                                                                                                                                                                                                                                                                                                            | Memory         | SAP Note: 1813245                               |
|   72 | Number of log segments                                           | Determines the number of log segments in the log vol­ ume of each serviceCheck for number of log segments.                            | *     | Make sure that log backups are being automatically cre­ ated and that there is enough space available for them. Check whether the system has been frequently and un­ usually restarting services. If it has, then resolve the root cause of this issue and create log backups as soon as pos­ sible.                                                                                                                                                                                      | Backup         |                                                 |
|   75 | Rowstore ver­ sion space skew                                     | Determines whether the row­ store version chain is too long.                                                                          | *     | Identify the connection or transaction that is blocking version garbage collection. You can do this in the SAP HANAstudio by executing "MVCC Blocker Statement" and "MVCC Blocker Transac­ tion" available on the System Information tab of the Ad­ ministration editor. If possi­ ble, kill the blocking connec­ tion or cancel the blocking transaction. For your infor­ mation, you can find table in­ formation by using query "SELECT * FROMTABLES WHERETABLE_OID = <table object ID>". | Memory         | Transactional Problems                          |
|   76 | Discrepancy be­ tween host server times                           | Identifies discrepancies be­ tween the server times of hosts in a scale-out system.                                                   | *     | Check operating system time settings.                                                                                                                                                                                                                                                                                                                                                                                                                                                  | Configura­ tion |                                                 |
|   77 | Database disk usage                                              | Determines the total used disk space of the database. All data, logs, traces and backups are considered.                             | *     | Investigate the disk usage of the database. See system view M_DISK_USAGE for more details.                                                                                                                                                                                                                                                                                                                                                                                             | Disk           |                                                 |
|   ID | Name                                                              | Description                                                                                                                                                                                                                                                               | Cfg   | User Action                                                                                                                                                                                                                     | Category       | Further Infor­ mation          |
|------|-------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|-------------------------------|
|   78 | Connection be­ tween systems in system repli­ cation setup          | Identifies closed connections between the primary system and a secondary system. If connections are closed, the primary system is no longer being replicated.                                                                                                             |       | Investigate why connections are closed (for example, net­ work problem) and resolve the issue.                                                                                                                                   | Availability   | SAP HANAAd­ ministration Guide |
|   79 | Configuration consistency of systems in sys­ tem replication setup | Identifies configuration pa­ rameters that do not have the same value on the pri­ mary system and a secon­ dary system. Most configura­ tion parameters should have the same value on both sys­ tems because the secondary system has to take over in the event of a disaster. |       | If the identified configuration parameter(s) should have the same value in both sys­ tems, adjust the configura­ tion. If different values are acceptable, add the parame­ ter(s) as an exception in global.ini/[inifile_checker]. | Configura­ tion | SAP HANAAd­ ministration Guide |
|   80 | Availability of ta­ ble replication                                | Monitors error messages re­ lated to table replication.                                                                                                                                                                                                                    |       | Determine which tables en­ countered the table replica­ tion error using system view M_TABLE_REPLICAS, and then check the correspond­ ing indexserver alert traces.                                                                | Availability   |                               |
|   81 | Cached view size                                                  | Determines how much mem­ ory is occupied by cached view                                                                                                                                                                                                                    | *     | Increase the size of the cached view. In the "re­ sult_cache" section of the in­ dexserver.ini file, increase the value of the "total_size" pa­ rameter.                                                                           | Memory         |                               |
|   82 | Timezone con­ version                                              | Compares SAP HANAinter­ nal timezone conversion with Operating System timezone conversion.                                                                                                                                                                                 | *     | Update SAP HANAinternal timezone tables (refer to SAP note 1932132).                                                                                                                                                            | Configura­ tion | SAP Note: 1932132             |
|   83 | Table consis­ tency                                                | Identifies the number of er­ rors and affected tables de­ tected by _SYS_STATIS­ TICS.Collector_Global_Ta­ ble_Consistency.                                                                                                                                                   | *     | Contact SAP support.                                                                                                                                                                                                            | Availability   |                               |
|   84 | Insecure in­ stance SSFS en­ cryption config­ uration                | Determines whether the master key of the instance secure store in the file sys­ tem (SSFS) of your SAP HANAsystem has been changed. If the SSFS master key is not changed after in­ stallation, it cannot be guar­ anteed that the initial key is unique.                    |       | Change the instance SSFS master key as soon as possi­ ble. For more information, see the SAP HANAAdminis­ tration Guide.                                                                                                          | Security       | SAP HANAAd­ ministration Guide |
|   ID | Name                                                       | Description                                                                                                                                                                                                                                                                                                                                                         | Cfg   | User Action                                                                                                                                                                                                       | Category       | Further Infor­ mation          |
|------|------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|-------------------------------|
|   85 | Insecure sys­ temPKI SSFS encryption con­ figuration         | Determines whether the master key of the secure store in the file system (SSFS) of your system's in­ ternal public key infrastruc­ ture (system PKI) has been changed. If the SSFS master key is not changed after in­ stallation, it cannot be guar­ anteed that the initial key is unique.                                                                            |       | Change the system PKI SSFS master key as soon as possi­ ble. For more information, see the SAP HANAAdminis­ tration Guide.                                                                                          | Security       | SAP HANAAd­ ministration Guide |
|   86 | Internal commu­ nication is con­ figured too openly          | Determines whether the ports used by SAP HANAfor internal communication are securely configured. If the "listeninterface" property in the "communication" section of the global.ini file does not have the value ".local" for sin­ gle-host systems and ".all" or ".global" for multiple-host systems, internal communi­ cation channels are exter­ nally exploitable. |       | The parameter [communica­ tion] listeninterface in global.ini is not set to a se­ cure value. Please refer to SAP Note 2183363 or the section on internal host name resolution in the SAP HANAAdministration Guide. | Security       | SAP Note: 2183363             |
|   87 | Granting of SAP HANADI sup­ port privileges                 | Determines if support privi­ leges for the SAP HANADe­ ployment Infrastructure (DI) are currently granted to any database users or roles.                                                                                                                                                                                                                             |       | Check if the corresponding users still need the privileges. If not, revoke the privileges from them.                                                                                                              | Security       |                               |
|   88 | Auto merge for column-store ta­ bles                        | Determines if the delta merge of a table was exe­ cuted successfully or not.                                                                                                                                                                                                                                                                                         | *     | The delta merge was not exe­ cuted successfully for a ta­ ble. Check the error descrip­ tion in view M_DELTA_MERGE_STATIS­ TICS and also Indexserver trace.                                                           | Memory         |                               |
|   89 | Missing volume files                                       | Determines if there is any volume file missing.                                                                                                                                                                                                                                                                                                                     |       | Volume file missing, data­ base instance is broken, stop immediately all operations on this instance.                                                                                                              | Configura­ tion |                               |
|   90 | Status ofHANA platform lifecy­ cle management configuration | Determines if the system was not installed/updated with the SAP HANADatabase Lifecycle Manager (HDBLCM).                                                                                                                                                                                                                                                            |       | Install/updateSAPHANA Database Lifecycle Manager (HDBLCM). Implement SAP note 2078425                                                                                                                             | Configura­ tion | SAP Note: 2078425             |
Further Infor­
|   ID | Name                                                            | Description                                                                                                                                                                                                     | Cfg   | User Action                                                                                                                                                                                                                                      | Category       | mation                                                                                                |
|------|-----------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|-------------------------------------------------------------------------------------------------------|
|   91 | Plan cache hit ratio                                            | Determines whether or not the plan cache hit ratio is too low.                                                                                                                                                  | *     | Increase the size of the plan cache. In the "sql" section of the indexserver.ini file, in­ crease the value of the "plan_cache_size" parame­ ter.                                                                                                  | Memory         |                                                                                                       |
|   92 | Root keys of per­ sistent services are not properly synchronized | Not al services that persist data could be reached the last time the root key change of the data volume encryp­ tion service was changed. As a result, at least one service is running with an old root key.     |       | Trigger a savepoint for this service or flush the SSFS cache using hdbcons                                                                                                                                                                       | Security       |                                                                                                       |
|   93 | Streaming Li­ cense expiry                                       | Determines how many days until your streaming license expires. Once your license ex­ pires, you can no longer start streaming projects.                                                                          | *     | Obtain a valid license and in­ stall it. For the exact expira­ tion date, see the monitoring view M_LICENSES.                                                                                                                                      | Availability   |                                                                                                       |
|   94 | Log replay back­ log for system replication sec­ ondary           | System Replication secon­ dary site has a higher log re­ play backlog than expected.                                                                                                                              | *     | Investigate on secondary site, why log replay backlog is increased                                                                                                                                                                               | Availability   |                                                                                                       |
|   95 | Availability of Data Quality ref­ erence data (di­ rectory files) | Determine the Data Quality reference data expiration dates.                                                                                                                                                     | *     | Download the latest Data Quality reference data files and update the system. (For more details about updating the directories, see the In­ stallation and Configuration Guide for SAP HANASmart Data Integration and SAP HANASmart Data Quality.) | Availability   | Installation and Configuration Guide for SAP HANASmart Data Integration andSAPHANA Smart Data Quality |
|   96 | Long-running tasks                                              | Identifies all long-running tasks.                                                                                                                                                                              | *     | Investigate the long-running tasks. For more information, see the task statistics tables or views in _SYS_TASK schema and trace log.                                                                                                             |                |                                                                                                       |
|   97 | Granting of SAP HANADI con­ tainer import privileges             | Determines if the container import feature of the SAP HANADeployment Infra­ structure (DI) is enabled and if import privileges for SAP HANADI containers are cur­ rently granted to any data­ base users or roles. |       | Check if the identified users still need the privileges. If not, revoke the privileges from them and disable the SAP HANADI container im­ port feature.                                                                                           | Security       |                                                                                                       |
|   98 | LOB garbage collection activ­ ity                                | Determines whether or not the lob garbage collection is activated.                                                                                                                                              |       | Activate the LOB garbage collection using the corre­ sponding configuration pa­ rameters.                                                                                                                                                          | Configura­ tion |                                                                                                       |
|   ID | Name                                                | Description                                                                                                                                                                                                                                                      | Cfg   | User Action                                                                                                                                                                                                                                                                               | Category                | Further Infor­ mation   |
|------|-----------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|------------------------|
|   99 | Maintenance Status                                  | Checks the installed SP ver­ sion against the recom­ mended SP version.                                                                                                                                                                                            | *     | Please consider upgrading to the recommended SP ver­ sion.                                                                                                                                                                                                                                 | Configura­ tion          |                        |
|  100 | Unsupported operating sys­ tem in use                | Determines if the operating system of the SAP HANADa­ tabase hosts is supported.                                                                                                                                                                                  |       | Upgrade the operating sys­ tem to a supported version (see SAP HANAMaster Guide for more information).                                                                                                                                                                                     | Configura­ tion          |                        |
|  101 | SQL access for SAP HANADI technical users           | Determines if SQL access has been enabled for any SAP HANADI technical users. SAP HANADI techni­ cal users are either users whose names start with '_SYS_DI' or SAP HANADI container technical users (<container name>, <con­ tainer name>DI, <container name>OO). |       | Check if the identified users ('_SYS_DI*' users or SAP HANADI container technical users) still need SQL access. If not, disable SQL access for these users and deactivate the users.                                                                                                      | Security                |                        |
|  102 | Existence of sys­ tem database backup                | Determines whether or not a system database backup ex­ ists. Without a system data­ base backup, your system cannot be recovered.                                                                                                                                  |       | Perform a backup of the sys­ tem database as soon as possible.                                                                                                                                                                                                                             | Backup                  |                        |
|  103 | Usage of depre­ cated features                       | Determines if any deprecated features were used in the last interval.                                                                                                                                                                                            |       | Check the view M_FEA­ TURE_USAGE to see which features were used. Refer to SAP Note 2425002 for fur­ ther information.                                                                                                                                                                      |                         |                        |
|  104 | System replica­ tion: increased log shipping backlog | Monitors log shipping back­ log. Alert is raised when threshold value is reached (priority dependent on threshold values).                                                                                                                                        | *     | To identify the reason for the increased system replication log shipping backlog, check the status of the secondary system. Possible causes for the increased system replica­ tion log shipping backlog can be a slow network perform­ ance, connection problems, or other internal issues. |                         |                        |
|  105 | Total Open Transactions Check                       | Monitors the number of open transactions per service.                                                                                                                                                                                                            | *     | Double check if the applica­ tion is closing the connection correctly, and whether the high transaction load on the system is expected.                                                                                                                                                    | Sessions/ Transac­ tions |                        |
|  106 | ASYNC replica­ tion in-memory buffer overflow        | Checks if local in-memory buffer in ASYNC replication mode runs full.                                                                                                                                                                                            |       | Check buffer size, peak loads, network, IO on secon­ dary.                                                                                                                                                                                                                                 | Availability            |                        |
|  107 | Inconsistent fall­ back snapshot                     | Checks for inconsistent fall­ back snapshots.                                                                                                                                                                                                                     | 1     | Drop the inconsistent snap­ shot                                                                                                                                                                                                                                                           | Availability            |                        |
Further Infor­
<!-- image -->
|   ID | Name                                   | Description                                                                                                                                                                    | Cfg   | User Action                                                                                                                                                                                                                                                                                                                    | Category       | mation                                                                            |
|------|----------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|-----------------------------------------------------------------------------------|
|  108 | Old fallback snapshot                  | Checks for out of date fall­ back snapshots (older than the defined thresholds).                                                                                                | *     | Check the age and possibly drop the snapshot                                                                                                                                                                                                                                                                                   | Availability   |                                                                                   |
|  109 | Backup history broken                  | Checks if the backup history is incomplete or inconsistent (the log_mode is internally set to overwrite, it is not en­ sured that the service is fully recoverable via backup). |       | Perform a data backup as soon as possible to ensure that the service is fully recov­ erable.                                                                                                                                                                                                                                    | Backup         |                                                                                   |
|  110 | Catalog Consis­ tency                   | An alert is raised if the Cata­ log Consistency Check de­ tects errors (identifies the number of errors and af­ fected objects).                                                  | *     | Contact SAP support.                                                                                                                                                                                                                                                                                                           | Availability   |                                                                                   |
|  111 | Replication sta­ tus of replication log | Check whether the status of replication log is disabled.                                                                                                                       | *     | Truncate replication log table and enable replication log                                                                                                                                                                                                                                                                      | Availability   |                                                                                   |
|  112 | Missing STO­ NITH with shared storage   | Check whether a STONITH provider is configured in a scale-out system with shared basepaths.                                                                                    | 1     | Implement a STONITH pro­ vider.                                                                                                                                                                                                                                                                                                 | ?              | See Implement­ ing a HA/DR Provider in the SAP HANASys­ tem Administra­ tion Guide . |
|  113 | Open file count                        | Determines what percentage of total open file handles are in use. All processes are con­ sidered, including non-SAP HANAprocesses.                                              | *     | You can configure the Linux file-max parameter using the following commands: 1. Check the current maxi­ mumnumberof allowed file handles: cat /proc/sys/fs/ file­max 2. Extend maximum number of file handles in /etc/ sysctl.conf: fs.file­max = 20000000 3. Activate changes for oper­ ating system: sysctl -p /etc/ sysctl.conf | Configura­ tion |                                                                                   |
|  114 | Active async IO count                  | Determines what percentage of total asynchronous input/ output requests are in use. All processes are considered, including non-SAPHANA processes.                             | *     | You can increase the size of the Linux I/O queue ( aio- max-nr parameter) as de­ scribed in SAP Note 1868829.                                                                                                                                                                                                                   | Configura­ tion | SAP Note: 1868829                                                                 |
Further Infor­
|   ID | Name                                         | Description                                                                                                                                                                                                                                                                     | Cfg   | User Action                                                                                                                                                                                                                                                                                                                                      | Category       | mation                                                                                                               |
|------|----------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|----------------------------------------------------------------------------------------------------------------------|
|  115 | Timezone envi­ ronment varia­ ble verification | Determines if the timezone environment variable TZ can be interpreted. See M_TIME­ ZONE_ALERTS. Otherwise HANAfalls back to a system call which can cause signifi­ cant performance issues.                                                                                       | 1     | Please set the timezone envi­ ronment variable TZ to a valid value according to the POSIX documentation and restart the HANAdatabase. See also SAP Note 2100040.                                                                                                                                                                                  | Configura­ tion | SAP Note: 2100040                                                                                                    |
|  116 | Transparent huge pages sta­ tus               | Determines if Transparent Huge Pages (THP) are acti­ vated which can cause issues for the database.                                                                                                                                                                              | 1     | Deactivate THP by setting the kernel parameter to "[never]".                                                                                                                                                                                                                                                                                     |                | SAP Notes: 2031375                                                                                                   |
|  118 | Port ephemeral max count                     | Checks for free local ports by referring to following kernel parameters: net.ipv4.ip_local_p ort_range and net.ipv4.ip_local_r eserved_ports . The alert is raised if the number of free local ports is below the con­ figured minimum.                                          | 1     | Increase the local port range by setting profile parameters as described in SAP Note 401162, or free ports which do not have to be reserved. The number of free local ports and ports which should be reserved for HANAserv­ ices can be found in the sys­ tem view M_HOST_INFOR­ MATION, keys: net_port_ephemeral_ max_count and net_port_ranges . | Configura­ tion | SAP Note: 401162 . See also SAP Host Agent and Linux kernel parame­ ters in the SAP HANASystem Administration Guide . |
|  119 | Required local SAP HANAport ranges           | Checks for local ports which are required but which have not been reserved (see Alert 118). If not reserved there is a risk that these ports could be automatically assigned to other applications. The alert is raised if any ports in the local ports range are not reserved. | 1     | Reserve ports by setting pro­ file parameters as described in SAP Note 401162. Details of unreserved ports can be retrieved from the system view M_HOST_IN­ FORMATION key: net_port_unreserved _ranges .                                                                                                                                           | Configura­ tion | SAP Note: 401162 See also SAP Host Agent and Linux kernel parame­ ters in the SAP HANASystem Administration Guide .   |
|  128 | LDAP Enabled Users without SSL               | Checks for the vulnerability where users may be enabled for LDAP Authentication but SSL is not enabled.                                                                                                                                                                         |       | Configure SSL to reduce risk of man-in-the-middle attacks and privacy protection.                                                                                                                                                                                                                                                                | Security       |                                                                                                                      |
|  129 | Check trusted certificate expi­ ration date   | Determines if there are any trusted certificates that will expire soon or have already expired.                                                                                                                                                                                 | 1     | Replace the certificates that are expiring or are already ex­ pired with new ones.                                                                                                                                                                                                                                                                | Security       |                                                                                                                      |
|   ID | Name                                               | Description                                                                                                                                                                                   | Cfg   | User Action                                                                                                                           | Category       | Further Infor­ mation                                                                     |
|------|----------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|---------------------------------------------------------------------------------------------------------------------------------------|----------------|------------------------------------------------------------------------------------------|
|  130 | Check own cer­ tificate expira­ tion date            | Determines if there are any own or chained certificates that will expire soon or have already expired.                                                                                        | *     | Replace the certificates that are expiring or are already ex­ pired with new ones.                                                     | Security       |                                                                                          |
|  131 | Session re­ quests queued by admission control      | Determines the number of session requests waiting in the admission control queue. This can indicate an issue with the response time of the request.                                           | 1     | Investigate why the session requests newly queued by admission control. Refer to M_ADMISSION_CON­ TROL_EVENTS for more in­ formation.   | Availability   |                                                                                          |
|  132 | Session re­ quests rejected by admission control    | Determines the number of session requests newly re­ jected by admission control. This can indicate an issue with the availability of the da­ tabase.                                            | 1     | Investigate why the session requests newly rejected by admission control. Refer to M_ADMISSION_CON­ TROL_EVENTS for more in­ formation. | Availability   |                                                                                          |
|  135 | Checks configu­ ration for SAP HANASLDData Supplier | For system replication, virtual and physical databases must be configured to send the correct landscape data to the Landscape Management Da­ tabase via the System Land­ scape Directory (SLD). |       | ConfigureSAPHANASLD Data Supplier as docu­ mented in SAP HANASystem Administration Guide (see link in Further Information).            | Configura­ tion | Configuring SAP HANAfor Sys­ tem Replication Technical Sce­ nario in SAP Sol­ ution Manager |
|  136 | Unsupported Parameter Val­ ues Set                  | Checks if configuration pa­ rameters are set to an un­ supported value.                                                                                                                         |       | Correct the values of configu­ ration parameters as neces­ sary.                                                                        | Configura­ tion |                                                                                          |
|  137 | Restart Required for Configura­ tion Change         | Check if a restart is required for a configuration change to become effective.                                                                                                                |       | If necessary, restart the sys­ tem.                                                                                                    | Configura­ tion |                                                                                          |
|  500 | Dbspace usage                                      | Checks for the dbspace size usage.                                                                                                                                                            | *     | Investigate the usage of dbspace and increase the size.                                                                               | Disk           |                                                                                          |
|  501 | Dbspace status                                     | Determines whether or not all dbspaces are available.                                                                                                                                         |       | Investigate why the dbspace is not available.                                                                                         | Availability   |                                                                                          |
|  502 | Dbspace file sta­ tus                               | Determines whether or not all dbspace files are available.                                                                                                                                    |       | Investigate why the dbspace file is not available.                                                                                    | Availability   |                                                                                          |
|  600 | Inactive Stream­ ing applications                   | Identifies inactive Streaming applications.                                                                                                                                                   |       | Investigate why the Stream­ ing application is inactive, for example, by checking the Streaming application's trace files.             | Availability   |                                                                                          |
|  601 | Inactive Stream­ ing project man­ aged adapters      | Identifies inactive Streaming project managed adapters.                                                                                                                                       |       | Investigate why the Stream­ ing project managed adapter is inactive, for example, by checking the trace files.                         | Availability   |                                                                                          |
|   ID | Name                                                      | Description                                                                                                                         | Cfg   | User Action                                                       | Category       | Further Infor­ mation   |
|------|-----------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------|-------|-------------------------------------------------------------------|----------------|------------------------|
|  602 | Streaming project physical memory usage                   | Determines what percentage of total physical memory available on the host is used for the streaming project.                        | *     | Investigate memory usage of the streaming project.                | Memory         |                        |
|  603 | Streaming project CPU us­ age                              | Determines the percentage CPU usage for a streaming project on the host and therefore whether or not CPU resources are running out. | *     | Investigate CPU usage.                                            | CPU            |                        |
|  604 | Number of pub­ lishers of streaming project                | Identify the large publishers of streaming project. Make sure that they will not break the streaming project.                       | *     | Investigate whether these publishers are created inten­ tionally.  | Configura­ tion |                        |
|  605 | Number of sub­ scribers of streaming project               | Identify the large subscribers of streaming project. Make sure that they will not break the streaming project.                      | *     | Investigate whether these subscribers are created in­ tentionally. | Configura­ tion |                        |
|  606 | Row throughput of subscriber of streaming project         | Identify which subscriber of streaming project has low throughput measured in rows per second.                                      | 1     | Investigate why the sub­ scriber works slowly.                     | Configura­ tion |                        |
|  607 | Transaction throughput of subscriber of streaming project | Identify which subscriber of streaming project has trans­ action throughput measured in transactions per second.                     | 1     | Investigate why the sub­ scriber works slowly.                     | Configura­ tion |                        |
|  608 | Row throughput of publisher of streaming project          | Identify which publisher of streaming project has low throughput measured in rows per second.                                       | 1     | Investigate why the publisher works slowly.                       | Configura­ tion |                        |
|  609 | Transaction throughput of publisher of streaming project  | Identify which publisher of streaming project has trans­ action throughput measured in transactions per second.                      | 1     | Investigate why the publisher works slowly.                       | Configura­ tion |                        |
|  610 | Bad rows of project managed adapter                       | Identify which project man­ aged adapter has much rows with error.                                                                   | 1     | Investigate why the adapter has such much rows with er­ ror.       | Configura­ tion |                        |
|  611 | High latency of project managed adapter                   | Identify which project man­ aged adapter has high la­ tency.                                                                          | 1     | Investigate why the adapter has high latency.                     | Configura­ tion |                        |
|  612 | Large queue of stream of streaming project                | Identify which stream of streaming project has large queue.                                                                         | 1     | Investigate why the stream has large queue.                       | Configura­ tion |                        |
|   ID | Name                                       | Description                                                              | Cfg   | User Action                                                                                          | Category       | Further Infor­ mation   |
|------|--------------------------------------------|--------------------------------------------------------------------------|-------|------------------------------------------------------------------------------------------------------|----------------|------------------------|
|  613 | Large store of stream of streaming project | Identify which stream of streaming project has large store.              | 1     | Investigate why the stream has large store.                                                          | Configura­ tion |                        |
|  700 | Agent availability                         | Determines how many mi­ nutes the agent has been in­ active.               | *     | Investigate connection of agent and check if agent is up and running.                                | Availability   |                        |
|  701 | Agent memory usage                         | Determines what percentage of total available memory on agent is used.   | *     | Investigate which adapter or processes use a lot of mem­ ory.                                         | Memory         |                        |
|  710 | Remote Sub­ scription excep­ tion            | Checks for recent exceptions in remote subscriptions and remote sources. |       | Investigate the error mes­ sage and the error code and restart the remote subscrip­ tion if necessary. | 0              |                        |