SAP Hana Alert and Resolution

SAP Hana Alert and User action Please find below table for Hana alert and user action. Please find respective Hana Alert Description and User Action below:

Your can use search functionality.

Alert IDAlert NameDescriptionUser Action
0Internal statistics server problemIdentifies internal statistics server problem.Resolve the problem. For more information, see the trace files. You may need to activate tracing first.
1Host physical memory usageDetermines what percentage of total physical memory available on the host is used. All processes consuming memory are considered, including non-SAP HANA processes.Investigate memory usage of processes.
2Disk usageDetermines what percentage of each disk containing data, log, and trace files is used. This includes space used by non-SAP HANA files.Investigate disk usage of processes. Increase disk space, for example by shrinking volumes, deleting diagnosis files, or adding additional storage.
3Inactive servicesIdentifies inactive services.Investigate why the service is inactive, for example, by checking the service's trace files.
4Restarted servicesIdentifies services that have restarted since the last time the check was performed.Investigate why the service had to restart or be restarted, for example, by checking the service's trace files.
5Host CPU UsageDetermines the percentage CPU idle time on the host and therefore whether or not CPU resources are running low.Investigate CPU usage.
6Address space usageDetermines the address space consumptionPrepare to restart HANA.
7Timer fallbackNotifies about the usage of the system timer fallback. The system timer is slower than native HANA timer.Use HANA on a system configuration with Time Stamp Counter invariant set. See SAP Note 2753418.
10Delta merge (mergedog) configurationDetermines 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 determine whether or not a delta merge operation needs to be executed.Change in SYSTEM layer the parameter active in section(s) mergedog to yes
12Memory usage of name serverDetermines 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' parameter.
16Lock wait timeout configurationDetermines whether the 'lock_wait_timeout' parameter in the 'transaction' section 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' parameter to a value between 100,000 and 7,200,000 for the System layer.
17Record count of non-partitioned column-store tablesDetermines the number of records in non-partitioned column-store tables. Current table size may not be critical. Partitioning need only be considered if tables are expected to grow rapidly (a non-partitioned table cannot contain more than 2,147,483,648 (2 billion) rows).Consider partitioning the table only if you expect it to grow rapidly.
20Table growth of non-partitioned column-store tablesDetermines the growth rate of non-partitioned columns tables.Consider partitioning the table.
21Internal eventIdentifies internal database events.Resolve the event and then mark it as resolved by executing the SQL statement ALTER SYSTEM SET EVENT HANDLED ':' . Note that this is not necessary for INFO events.
22Notification of all alertsDetermines 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.
23Notification of medium and high priority alertsDetermines 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.
24Notification of high priority alertsDetermines whether or not there have been any high priority alerts since the last check and if so, sends a summary e-mail to specified recipients.Investigate the alerts.
25Open connectionsDetermines what percentage of the maximum number of permitted SQL connections are open. The maximum number of permitted connections is configured in the "session" section of the indexserver.ini file.Investigate why the maximum number of permitted open connections is being approached.
26Unassigned volumesIdentifies volumes that are not assigned a service.Investigate why the volume is not assigned a service. For example, the assigned service is not active, the removal of a host failed, or the removal of a service was performed incorrectly.
27Record count of column-store table partitionsDetermines the number of records in the partitions of column-store tables. A table partition cannot contain more than 2,147,483,648 (2 billion) rows.Consider repartitioning the table.
28Most recent savepoint operationDetermines how long ago the last savepoint was defined, that is, how long ago a complete, consistent image of the database was persisted to disk.Investigate why there was a delay defining the last savepoint and consider triggering the operation manually by executing the SQL statement ALTER SYSTEM SAVEPOINT.
29Size of delta storage of column-store tablesDetermines exceptionally large delta storages of column tables.See SAP Knowledge Base Note 1977314. Investigate the delta merge history in the monitoring view M_DELTA_MERGE_STATISTICS. Consider merging the table delta manually.
30Check internal disk full eventDetermines 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, execute the SQL statements ALTER SYSTEM SET EVENT ACKNOWLEDGED ':' and ALTER SYSTEM SET EVENT HANDLED ':' .
31License expiryDetermines 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 install it. For the exact expiration date, see the monitoring view M_LICENSE.
33Log mode OVERWRITEDetermines whether or not the database is running in log mode "overwrite". Log mode "overwrite" does not support point-in-recovery (only recovery to a data backup) and is not recommended for productive systems.If you need point-in-time recovery, reconfigure the log mode of your system to "normal". In the "persistence" section of the global.ini configuration file, set the parameter "log_mode" to "normal" for the System layer. When you change the log mode, you must restart the database system to activate the changes. It is also recommended that you perform a full data backup.
34Unavailable volumesDetermines whether or not all volumes are available.Investigate why the volume is not available.
35Existence of data backupDetermines whether or not a data backup exists. Without a data backup, your database cannot be recovered.Perform a data backup as soon as possible.
36Status of most recent data backupDetermines 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 possible.
37Age of most recent data backupDetermines the age of the most recent successful data backup.Perform a data backup as soon as possible.
38Status of most recent log backupsDetermines whether or not the most recent log backups for services and volumes were successful.Investigate why the log backup failed and resolve the problem.
39Long-running statementsIdentifies long-running SQL statements.Investigate the statement. For more information, see the table _SYS_STATISTICS.HOST_LONG_RUNNING_STATEMENTS.
40Total memory usage of column-store tablesDetermines what percentage of the effective allocation limit is being consumed by individual column-store tables as a whole (that is, the cumulative size of all of a table's columns and internal structures)Consider partitioning or repartitioning the table.
41In-memory DataStore activationDetermines whether or not there is a problem with the activation of an in-memory DataStore object.For more information, see the table _SYS_STATISTICS.GLOBAL_DEC_EXTRACTOR_STATUS and SAP Note 1665553.
42Long running/idling cursorsIdentifies long running/idling cursors. The threshold is based on M_INIFILE_CONTENTS.VALUE where KEY = "idle_cursor_lifetime".Close the cursor in the application, or kill the connection by executing the SQL statement ALTER SYSTEM DISCONNECT SESSION .For more information, see the table HOST_LONG_IDLE_CURSOR (_SYS_STATISTICS).
43Memory usage of servicesDetermines what percentage of its effective allocation limit a service is using.Check for services that consume a lot of memory.
44Licensed memory usageDetermines what percentage of licensed memory is used.Increase licensed amount of main memory. You can see the peak memory allocation since installation in the system view M_LICENSE (column PRODUCT_USAGE).
45Memory usage of main storage of column-store tablesDetermines what percentage of the effective allocation limit is being consumed by the main storage of individual column-store tables.Consider partitioning or repartitioning the table.
46RTEdump filesIdentifies new runtime dump files (*rtedump*) have been generated in the trace directory 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.
47Long-running serializable transactionsIdentifies long-running serializable transactions.Close the serializable transaction in the application or kill the connection by executing the SQL statement ALTER SYSTEM DISCONNECT SESSION . For more information, see the table HOST_LONG_SERIALIZABLE_TRANSACTION (_SYS_STATISTICS).
48Long-running uncommitted write transactionsIdentifies long-running uncommitted write transactions.Close the uncommitted transaction in the application or kill the connection by executing the SQL statement ALTER SYSTEM DISCONNECT SESSION . For more information, see the table HOST_UNCOMMITTED_WRITE_TRANSACTION (_SYS_STATISTICS).
49Long-running blocking situationsIdentifies long-running blocking situations.Investigate the blocking and blocked transactions and if appropriate cancel one of them.
50Number of diagnosis filesDetermines the number of diagnosis files written by the system (excluding zip-files). An unusually large number of files can indicate a problem with the database (for example, problem with trace file rotation or a high number of crashes).Investigate the diagnosis files.
51Size of diagnosis filesIdentifies large diagnosis files. Unusually large files can indicate a problem with the database.Check the diagnosis files in the SAP HANA studio for details.
52Crashdump filesIdentifies new crashdump files that have been generated in the trace directory of the system.Check the contents of the dump files.
53Pagedump filesIdentifies new pagedump files that have been generated in the trace directory of the system.Check the contents of the dump files.
54Savepoint durationIdentifies long-running savepoint operations.Check disk I/O performance.
55Columnstore unloadsDetermines how many columns in columnstore tables have been unloaded from memory. This can indicate performance issues.Check sizing with respect to data distribution.
56Python trace activityDetermines whether or not the python trace is active and for how long. The python trace affects system performance.If no longer required, deactivate the python trace in the relevant configuration file.
57Instance secure store file system (SSFS) inaccessibleDetermines if the instance secure store in the file system (SSFS) of your SAP HANA system is accessible to the database.Check and make sure that the instance SSFS is accessible to the database.
58Plan cache sizeDetermines whether or not the plan cache is too small.Currently Alert 58 is inactive and replaced by Alert 91. Please activate Alert 91 - Plan Cache Hit Ratio
59Percentage of transactions blockedDetermines the percentage of transactions that are blocked.Investigate blocking and blocked transactions and if appropriate cancel some of them.
60Sync/Async read ratioIdentifies a bad trigger asynchronous read ratio. This means that asynchronous reads are blocking and behave almost like synchronous reads. This might have negative impact on SAP HANA I/O performance in certain scenarios.Please refer to SAP note 1930979.
61Sync/Async write ratioIdentifies a bad trigger asynchronous write ratio. This means that asynchronous writes are blocking and behave almost like synchronous writes. This might have negative impact on SAP HANA I/O performance in certain scenarios.Please refer to SAP note 1930979.
62Expiration of database user passwordsIdentifies database users whose password is due to expire in line with the configured 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 recommended that you disable the password lifetime check of technical users so that their password never expires (ALTER USER DISABLE PASSWORD LIFETIME).Change the password of the database user.
63Granting of SAP_INTERNAL_HANA_SUPPORT roleDetermines if the internal support role (SAP_INTERNAL_HANA_SUPPORT) is currently granted to any database users.Check if the corresponding users still need the role. If not, revoke the role from them.
64Total memory usage of table-based audit logDetermines what percentage of the effective memory allocation limit is being consumed by the database table used for table-based audit logging. If this table grows too large, the availability of the database could be impacted.Consider exporting the content of the table and then truncating the table.
65Runtime of the log backups currently runningDetermines 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.
66Storage snapshot is preparedDetermines 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.
67Table growth of rowstore tablesDetermines the growth rate of rowstore tablesTry to reduce the size of row store table by removing unused data
68Total memory usage of row storeDetermines the current memory size of a row store used by a serviceInvestigate memory usage by row store tables and consider cleanup of unused data
69Enablement of automatic log backupDetermines whether automatic log backup is enabled.Enable automatic log backup. For more details please see SAP HANA Administration Guide.
70Consistency of internal system components after system upgradeVerifies the consistency of schemas and tables in internal system components (for example, the repository) after a system upgrade.Contact SAP support.
71Row store fragmentationCheck for fragmentation of row store.Implement SAP Note 1813245.
72Number of log segmentsDetermines the number of log segments in the log volume of each serviceCheck for number of log segments.Make sure that log backups are being automatically created and that there is enough space available for them. Check whether the system has been frequently and unusually restarting services. If it has, then resolve the root cause of this issue and create log backups as soon as possible.
73Overflow of rowstore version spaceDetermines the overflow ratio of the rowstore version space.This alert is deprecated. Please refer to alert 75 "Rowstore version space skew" for indication of rowstore version accumulation
74Overflow of metadata version spaceDetermines the overflow ratio of the metadata version space.This alert is deprecated. Please refer to alert 75 "Rowstore version space skew" for indication of rowstore version accumulation
75Rowstore version space skewDetermines whether the rowstore version chain is too long.Identify the connection or transaction that is blocking version garbage collection. You can do this in the SAP HANA studio by executing "MVCC Blocker Statement" and "MVCC Blocker Transaction" available on the System Information tab of the Administration editor. If possible, kill the blocking connection or cancel the blocking transaction. For your information, you can find table information by using query "SELECT * FROM TABLES WHERE TABLE_OID = ".
76Discrepancy between host server timesIdentifies discrepancies between the server times of hosts in a scale-out system.Check operating system time settings.
77Database disk usageDetermines 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.
78Connection between systems in system replication setupIdentifies 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, network problem) and resolve the issue.
79Configuration consistency of systems in system replication setupIdentifies configuration parameters that do not have the same value on the primary system and a secondary system. Most configuration parameters should have the same value on both systems 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 systems, adjust the configuration. If different values are acceptable, add the parameter(s) as an exception in global.ini/[inifile_checker].
80Availability of table replicationMonitors error messages related to table replication.Determine which tables encountered the table replication error using system view M_TABLE_REPLICAS, and then check the corresponding indexserver alert traces.
81Cached view sizeDetermines how much memory is occupied by cached viewIncrease the size of the cached view. In the "result_cache" section of the indexserver.ini file, increase the value of the "total_size" parameter.
82Timezone conversionCompares SAP HANA internal timezone conversion with Operating System timezone conversion.Update SAP HANA internal timezone tables (refer to SAP note 1932132).
83Table consistencyIdentifies the number of errors and affected tables detected by _SYS_STATISTICS.Collector_Global_Table_Consistency.Contact SAP support.
84Insecure instance SSFS encryption configurationDetermines whether the master key of the instance secure store in the file system (SSFS) of your SAP HANA system has been changed. If the SSFS master key is not changed after installation, it cannot be guaranteed that the initial key is unique.Change the instance SSFS master key as soon as possible. For more information, see the SAP HANA Administration Guide.
85Insecure systemPKI SSFS encryption configurationDetermines whether the master key of the secure store in the file system (SSFS) of your system's internal public key infrastructure (system PKI) has been changed. If the SSFS master key is not changed after installation, it cannot be guaranteed that the initial key is unique.Change the system PKI SSFS master key as soon as possible. For more information, see the SAP HANA Administration Guide.
86Internal communication is configured too openlyDetermines whether the ports used by SAP HANA for 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 single-host systems and ".all" or ".global" for multiple-host systems, internal communication channels are externally exploitable.The parameter [communication] listeninterface in global.ini is not set to a secure value. Please refer to SAP Note 2183363 or the section on internal host name resolution in the SAP HANA Master Guide.
87Granting of SAP HANA DI support privilegesDetermines if support privileges for the SAP HANA Deployment 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.
88Auto merge for column-store tablesDetermines if the delta merge of a table was executed successfully or not.The delta merge was not executed successfully for a table. Check the error description in view M_DELTA_MERGE_STATISTICS and also Indexserver trace.
89Missing volume filesDetermines if there is any volume file missing.Volume file missing, database instance is broken, stop immediately all operations on this instance.
91Plan cache hit ratioDetermines 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, increase the value of the "plan_cache_size" parameter.
92Root keys of persistent services are not properly synchronizedNot all services that persist data could be reached the last time the root key change of the data volume encryption 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
93Streaming License expiryDetermines how many days until your streaming license expires. Once your license expires, you can no longer start streaming projects.Obtain a valid license and install it. For the exact expiration date, see the monitoring view M_LICENSES.
94Log replay backlog for system replication secondarySystem Replication secondary site has a higher log replay backlog than expected.Investigate on secondary site, why log replay backlog is increased
95Availability of Data Quality reference data (directory 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 Installation and Configuration Guide for SAP HANA Smart Data Integration and SAP HANA Smart Data Quality.)
96Long-running tasksIdentifies 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.
97Granting of SAP HANA DI container import privilegesDetermines if the container import feature of the SAP HANA Deployment Infrastructure (DI) is enabled and if import privileges for SAP HANA DI containers are currently granted to any database users or roles.Check if the identified users still need the privileges. If not, revoke the privileges from them and disable the SAP HANA DI container import feature.
98LOB garbage collection activityDetermines whether or not the lob garbage collection is activated.Activate the LOB garbage collection using the corresponding configuration parameters.
99HANA versionChecks the installed HANA version.Please check if your SAP HANA system can be upgraded to a newer version.
101SQL access for SAP HANA DI technical usersDetermines if SQL access has been enabled for any SAP HANA DI technical users. SAP HANA DI technical users are either users whose names start with '_SYS_DI' or SAP HANA DI container technical users (, #DI, #OO).Check if the identified users ('_SYS_DI*' users or SAP HANA DI container technical users) still need SQL access. If not, disable SQL access for these users and deactivate the users.
102Existence of system database backupDetermines whether or not a system database backup exists. Without a system database backup, your system cannot be recovered.Perform a backup of the system database as soon as possible.
103Usage of deprecated featuresDetermines if any deprecated features were used in the last interval.Check the view M_FEATURE_USAGE to see which features were used. Refer to SAP Note 2425002 for further information.
104Log shipping backlog for system replication secondarySystem Replication secondary site has a higher log shipping backlog than expected.Investigate on primary and secondary site, why log shipping backlog is increased
105Total Open Transactions CheckThe check monitors the number of open transactions per serviceDouble check if the application is closing the connection correctly, and whether the high transaction load on the system is expected.
106ASYNC replication in-memory buffer overflowChecks if local in-memory buffer in ASYNC replication mode runs fullCheck buffer size, peak loads, network, IO on secondary
109Backup history brokenIf the backup history is broken, the log_mode is internally set to overwrite, it is not ensured that the service is fully recoverable via backup.Perform a data backup as soon as possible to ensure that the service is fully recoverable.
110Catalog ConsistencyIdentifies the number of errors and affected objects detected by _SYS_STATISTICS.Collector_Global_Catalog_Consistency.Contact SAP support.
111Replication status of Replication LogCheck whether the status of replication log is disabled.Truncate replication log table and enable replication log.
113Host open file countDetermines what percentage of total open file handles are in use. All processes are considered, including non-SAP HANA processes.
Compare M_HOST_RESOURCE_UTILIZATION.OPEN_FILE_COUNT with M_HOST_INFORMATION.VALUE of M_HOST_INFORMATION.KEY open_file_limit.
This is normal behavior and neither a SAP HANA nor a Linux issue.
1. Check the current maximum number of 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 operating system: sysctl -p /etc/sysctl.conf
114Host active async io countDetermines what percentage of total asynchronous input/output requests are in use. All processes are considered, including non-SAP HANA processes.
Compare M_HOST_RESOURCE_UTILIZATION.ACTIVE_ASYNC_IO_COUNT with M_HOST_INFORMATION.VALUE of M_HOST_INFORMATION.KEY async_io_limit.
See SAP Notes 1868829.
115Timezone environment variable verificationDetermines if the timezone environment variable TZ can be interpreted. See M_TIMEZONE_ALERTS.
Otherwise HANA falls back to a system call which can cause significant performance issues.
Please set the timezone environment variable TZ to a valid value according to the POSIX documentation and restart the HANA database. See also SAP Note 2100040.
117Record count of non-partitioned column-store tables (include)Determines the number of records in non-partitioned column-store tables (only include tables are checked). Current table size may not be critical. Partitioning need only be considered if tables are expected to grow rapidly (a non-partitioned table cannot contain more than 2,147,483,648 (2 billion) rows).Consider partitioning the table only if you expect it to grow rapidly.
127Record count of column-store table partitions (include)Determines the number of records in the partitions of column-store tables (only include tables are checked). A table partition cannot contain more than 2,147,483,648 (2 billion) rows.Consider repartitioning the table.
128LDAP Enabled Users without SSLChecks if any user is enabled for LDAP Authentication and SSL is off.Configure SSL to reduce risk of man-in-the-middle attacks and privacy protection.
129Check trusted certificate expiration dateDetermines if there are any trusted certificates that will expire soon or have already expired.Replace the certificates.
130Check own certificate expiration dateDetermines if there are any own or chain certificates that will expire soon or have already expired.Replace the certificates.
131Session requests queued by admission controlDetermines the number of session requests waiting in the admission control queue. This can indicate an issue with the response time of the request.Investigate why the session requests newly queued by admission control. Refer to M_ADMISSION_CONTROL_EVENTS for more information.
132Session requests rejected by admission controlDetermines the number of session requests newly rejected by admission control. This can indicate an issue with the availability of the database.Investigate why the session requests newly rejected by admission control. Refer to M_ADMISSION_CONTROL_EVENTS for more information.
133Check out-of-buffers event for a buffer cacheChecks whether a buffer cache is sufficiently configured. An out-of-buffers event indicates that the affected buffer cache is insufficiently configured for the current workload. It should be resolved, otherwise queries may fail.Resolve the out-of-buffers event by increasing the max_size parameter of the affected buffer cache.
134Administration of SAP HANA DI user groups by user administratorsDetermines if any SAP HANA DI user groups can be managed by a user with the USER ADMIN system privilege. SAP HANA DI user groups are user groups whose names start with '_SYS_DI#'.Verify that the identified user groups still need to be able to be managed by users with the USER ADMIN system privilege. If they don't, disable USER ADMIN administration for these user groups (ALTER USERGROUP DISABLE USER ADMIN).
136Unsupported configuration parameter valuesChecks if configuration parameters are set to unsupported valuesCheck if system is running in a supported state
137Restart required after configuration changeChecks if services require a restart after a configuration was changedRestart services (see M_CONFIGURATION_PARAMETER_VALUES) to allow the changed configuration to become active.
500Dbspace usageChecks for the dbspace size usage.Investigate the usage of dbspace and increase the size.
501Dbspace statusDetermines whether or not all dbspaces are available.Investigate why the dbspace is not available.
502Dbspace file statusDetermines whether or not all dbspace files are available.Investigate why the dbspace file is not available.
504DT Version mismatchChecks that dynamic tiering and SAP HANA versions match.Check the reason for the mismatch, and correct the problem. See SAP Note 2637835.
505ES backup history brokenIf the backup history is broken, the service is not fully recoverable via backup.Perform a data backup as soon as possible to ensure that the service is fully recoverable.
600Inactive Streaming applicationsIdentifies inactive Streaming applications.Investigate why the Streaming application is inactive, for example, by checking the Streaming application's trace files.
601Inactive Streaming project managed adaptersIdentifies inactive Streaming project managed adapters.Investigate why the Streaming project managed adapter is inactive, for example, by checking the trace files.
602Streaming project physical memory usageDetermines what percentage of total physical memory available on the host is used for the streaming project.Investigate memory usage of the streaming project.
603Streaming project CPU usageDetermines the percentage CPU usage for a streaming project on the host and therefore whether or not CPU resources are running out.Investigate CPU usage.
604Number of publishers of streaming projectIdentify the large publishers of streaming project. Make sure that they will not break the streaming project.Investigate whether these publishers are created intentionally.
605Number of subscribers of streaming projectIdentify the large subscribers of streaming project. Make sure that they will not break the streaming project.Investigate whether these subscribers are created intentionally.
606Row throughput of subscriber of streaming projectIdentify which subscriber of streaming project has low throughput measured in rows per second.Investigate why the subscriber works slowly.
607Transaction throughput of subscriber of streaming projectIdentify which subscriber of streaming project has transaction throughput measured in transactions per second.Investigate why the subscriber works slowly.
608Row throughput of publisher of streaming projectIdentify which publisher of streaming project has low throughput measured in rows per second.Investigate why the publisher works slowly.
609Transaction throughput of publisher of streaming projectIdentify which publisher of streaming project has transaction throughput measured in transactions per second.Investigate why the publisher works slowly.
610Bad rows of project managed adapterIdentify which project managed adapter has much rows with error.Investigate why the adapter has such much rows with error.
611High latency of project managed adapterIdentify which project managed adapter has high latency.Investigate why the adapter has high latency.
612Large queue of stream of streaming projectIdentify which stream of streaming project has large queue.Investigate why the stream has large queue.
613Large store of stream of streaming projectIdentify which stream of streaming project has large store.Investigate why the stream has large store.
700Agent availabilityDetermines how many minutes the agent has been inactive.Investigate connection of agent and check if agent is up and running.
701Agent memory usageDetermines what percentage of total memory available to agent is used.Investigate which adapter or processes use a lot of memory.
710Remote Subscription exceptionChecks for recent exceptions in remote subscriptions and remote sources.Investigate the error message and the error code and restart the remote subscription if necessary.

You may also like...

Leave a Reply

Your email address will not be published.