How to configure alerts in HANA for memory consumption ?

● Host physical memory usage (Alert 1)
● Memory usage of name server (Alert 12)
● Total memory usage of Column Store tables (Alert 40)
● Memory usage of services (Alert 43)
● Memory usage of main storage of Column Store tables (Alert 45)
● Runtime dump files (Alert 46)

AlertDescriptionUser ActionFurther Information
Alert 1: Physical MemoryCheck for free physical memoryCheck for processes that consume a lot of memoryMemory Problems
Alert 2: Disk UsageCheck for sufficient disk spaceCheck for processes that consume a lot of disk space or add additional disk spaceDisk Related
Alert 3: Inactive name servers, index servers, preprocessorsCheck whether services are inactiveCheck the reason, why services are inactive 
Alert 4: Restarted ServicesCheck whether services have been restartedCheck the reason why services have been restarted 
Alert 5: Host CPU UsageDetermines the percentage CPU idle time on the host and therefore whether or not CPU resources are running low.Investigate CPU usageCPU Related
Alert 10: Delta merge (mergdog) configurationCheck whether in DEFAULT or SYSTEM layer the parameter active in section(s) mergedog is yesChange in SYSTEM layer the parameter active in section(s) mergedog to yesDelta Merge
Alert 12: Check shared memory used size for category TOPOLOGYCheck the nameserver shared memory size on the affected hostIncrease shared memory size for the nameserverMemory Problems
Alert 16: Param lock_waittimeoutCheck whether in DEFAULT or SYSTEM layer the parameter lock_waittimeout in indexserver.ini section ptime is between 100.000 and 7.200.000Change in DEFAULT or SYSTEM layer the parameter lock_waittimeout in indexserver.ini section ptime to value between 100.000 and 7.200.000Transactional Problems
Alert 17: Record count of not partitioned column-store tablesCheck record count of not partitioned column tableCheck record count of not partitioned column table and consider to split itMemory Problems, SAP HANA Administration Guide > Table Partitioning
Alert 19: Record count of delta storage of column-store tablesDetermines the number of records in delta storage of column-store tables.Investigate the delta merge history in M_DELTA_MERGE_STATISTICS. Consider merging the table manuallyDelta Merge
Alert 20: Table growth of non-partitioned column-store tableCheck table growth of not partitioned column tableCheck significant table growth of not partitioned column table and consider to split itMemory Problems, SAP HANA Administration Guide > Table Partitioning
Alert 21: Internal EventCheck for internal eventCheck for internal event. If resolved execute ALTER SYSTEM SET EVENT HANDLED <:event>. 
Alert 25: Check number of connectionsChecks if number of connections reached thresholdCheck why the number of connections reached threshold 
Alert 26: Check for not assigned volumesCheck if there are not assigned volumesCheck why there are not assigned volumes 
Alert 27: Check record count of column table partitionCheck for record count of column table partitionCheck for record count of column table partitionMemory Problems, SAP HANA Administration Guide > Table Partitioning
Alert 28: Check last savepoint timeCheck for the last savepoint timeCheck why last savepoint was delayed. Consider triggering savepoint manually. 
Alert 29: Check size of delta memoryCheck size of delta memoryCheck if mergedog worksDelta Merge
Alert 30: Internal disk full eventsCheck for internal disk full eventCheck for internal disk full event. Resolve the disk full situation. If resolved execute ALTER SYSTEM SET EVENT HANDLED <:event>.Internal Disk Full Event (Alert 30)
Alert 31: License expiringCheck license expirationGet a valid license and install it Alert Text "Your license will expire in " + DAYS_BEFORE_LICENSE_EXPIRATION + " days."Security, Authorization and Licensing
Alert 32: Check whether the database is running in log mode OVERWRITELog mode OVERWRITE does not support point-in-recovery (only recovery to a data backup) and is not recommended for productive systemsCheck whether you need point-in-time recovery and if required reconfigure your system to the log mode NORMAL.Configuration Parameter Issues
Alert 33: Check database supports point-in-time recoveryLog mode legacy is not recommended for productive systems. If a point-in-time recoverable system is needed the database has to run in log mode normal.Refer to the SAP HANA Administration Guide for details about the required reconfiguration.SAP HANA Administration Guide > Backing up and Recovering the SAP HANA Database
Alert 34: Check availability of volumes for backupCheck whether all volumes are available to execute a backupCheck the reason, why the volume is not availableSAP HANA Administration Guide > Backing up and Recovering the SAP HANA Database
Alert 35: Check whether a data backup existsCheck whether at least one data backup existsTo make your database recoverable execute a data backup as soon as possibleSAP HANA Administration Guide > Backing up and Recovering the SAP HANA Database
Alert 36: Check last data backupCheck whether the last data backup was successfulCheck the reason, why the last data backup was not successful, resolve the problem and execute a new data backup as soon as possibleSAP HANA Administration Guide > Backing up and Recovering the SAP HANA Database
Alert 37: Check the age of the last data backupCheck the age of the last successfull data backupTo reduce your downtime in case of recovery execute a data backup as soon as possible.SAP HANA Administration Guide > Backing up and Recovering the SAP HANA Database
Alert 38: Check last log backupsCheck whether the last log backups were successfulCheck the reason, why the a log backup was not successful and resolve the problemSAP HANA Administration Guide > Backing up and Recovering the SAP HANA Database
Alert 39: Check long running statementsCheck if there is a long running statement.Check table "_SYS_STATISTICS"."HOST_LONG_RUNNING_STATEMENTS" for detailed information.Transactional Problems
Alert 40: Check column table size with respect to memory allocation limitCheck size of column table with respect to memory allocation limitUser Action: Consider to (re) split the tableMemory Problems
Alert 41: Check the In-Memory DataStore Object activationCheck if there is a problem with the In-Memory DataStore Object activation ?Check table "_SYS_STATISTICS"."GLOBAL_DEC_EXTRACTOR_STATUS" for detailed information. See SAP note 1665553 
Alert 42: Check long idle cursorCheck if there is a long lived cursorClose the cursor in the application, or kill the connection by executing the SQL statement ALTER SYSTEM DISCONNECT SESSION <LOGICAL_CONNECTION_ID>. For more information, see the table HOST_LONG_IDLE_CURSOR (_SYS_STATISTICS).Transactional Problems
Alert 43: Check used memory against allocation limitCheck utilization of memory against allocation limit of serviceCheck for services that consume a lot of memoryMemory Problems
Alert 44: Check currently utilized percentage of main memoryCheck if the utilized amount of main memory exceeds the licensed amount of main memory. Check the system view M_LICENSE (column PRODUCT_USAGE) for the exact utilized amount of main memoryIncrease licensed amount of main memoryMemory Problems
Alert 45: Check column table size with respect to main memory allocation limitCheck size of column table with respect to main memory allocation limitConsider to (re) split the tableMemory Problems
Alert 46: Check for new rte dump filesCheck if new rte dump files are generated in the trace directory of the system.Check contents of new rte dump files. 
Alert 47: Check for long lived serializable transactionCheck if there is a long serializable transaction.Close the serializable transaction in the application or kill the connection by executing the SQL statement ALTER SYSTEM DISCONNECT SESSION <LOGICAL_CONNECTION_ID>. For more information, see the table HOST_LONG_SERIALIZABLE_TRANSACTION (_SYS_STATISTICS).Transactional Problems
Alert 48: Check an uncommitted write transactionCheck if there is an uncommitted write transaction.Close the uncommitted transaction in the application or kill the connection by executing the SQL statement ALTER SYSTEM DISCONNECT SESSION <LOGICAL_CONNECTION_ID>. For more information, see the table HOST_UNCOMMITTED_WRITE_TRANSACTION (_SYS_STATISTICS).Transactional Problems
Alert 49: Check blocked transactionsCheck if there is a blocked transaction.Review blocking and blocked transaction and cancel one of them if appropriate.Transactional Problems
Alert 50: Check number of diagnosis filesCheck of there are too many diagnosis files. The existence of many such files might indicate a problem.Check the diagnosis files.See KBA 1977162
Alert 51: Check number of diagnosis filesIdentifies large diagnosis files. An unusually large file size can indicate a problem with the database.Check the diagnosis files in the SAP HANA studio for details.See KBA 1977208
Alert 52: Check for new crash dump filesIdentifies new crash dump files have been generated in the trace directory of the system.Check the contents of the dump files. 
Alert 53: Check for new page dump filesIdentifies new pagedump files have been generated in the trace directory of the system.Check the contents of the dump files.
Alert 54: Long Savepoint durationIdentifies long-running savepoint operations.Check disk I/O performance.CPU Related Root Causes and Solutions, I/O Related Root Causes and Solutions
Alert 55: Column-store unloadsDetermines how many columns in columnstore tables have been unloaded from memory. This can indicate performance issues.Check sizing with respect to data distribution.Memory Problems
Alert 56: Python 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. 
Alert 57: Secure store file system (SSFS) availabilityDetermines if the secure storage file system (SSFS) is accessible to the databaseCheck and make sure that the secure storage file system (SSFS) is accessible to the database. 
Alert 58: Plan cache sizeDetermines whether or not the plan cache is too small.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. 
Alert 59: Percentage of transactions blockedDetermines the percentage of transactions that are blocked.Investigate blocking and blocked transactions and if appropriate cancel some of them.Transactional Problems
Alert 60: Sync/Async read ratioIdentifies a bad trigger asynchronous read ratioPlease refer to SAP Note 1965379.I/O Related Root Causes and Solutions
Alert 61: Sync/Async write ratioIdentifies a bad trigger asynchronous write ratio.Please refer to SAP Note 1965379I/O Related Root Causes and Solutions
Alert 65: Runtime 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.SAP HANA Administration Guide
Alert 66: Storage 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.SAP HANA Administration Guide
Alert 67: Table growth of rowstore tablesDetermines the growth rate of rowstore tablesTry to reduce the size of row store table by removing unused data 
Alert 68: Total 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 
Alert 69: Enablement of automatic log backupDetermines whether automatic log backup is enabled.Enable automatic log backup. For more details please see SAP HANA Administration Guide.SAP HANA Administration Guide
Alert 70: Consistency 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. 
Alert 71: Row store fragmentationCheck for fragmentation of row store.Implement SAP Note 181324 
Alert 72: Number 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. 
Alert 73: Overflow of rowstore version spaceDetermines the overflow ratio of the rowstore version space.Identify the connection or transaction that is blocking version garbage collection. You can do this in the SAP HANA studio by executing the "MVCC Blocker Connection" and "MVCC Blocker Transaction" statements available on the System Information tab of the Administration editor. If possible, kill the blocking connection or transaction.Transactional Problems
Alert 74: Overflow of metadata version spaceDetermines the overflow ratio of the metadata version space.Identify the connection or transaction that is blocking version garbage collection. You can do this in the SAP HANA studio by executing the "MVCC Blocker Connection" and "MVCC Blocker Transaction" statements available on the System Information tab of the Administration editor. If possible, kill the blocking connection or transaction.Transactional Problems
Alert 75: Rowstore 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 the "MVCC Blocker Connection" and "MVCC Blocker Transaction" statements available on the System Information tab of the Administration editor. If possible, kill the blocking connection or transaction.Transactional Problems
Alert 76: Discrepancy between host server timesIdentifies discrepancies between the server times of hosts in a scale-out system.Check operating system time settings. 
Alert 77: Database 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. 
Alert 78: System Replication Connection ClosedIdentifies 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.SAP HANA Administration Guide
Alert 79: System Replication Configuration Parameter MismatchIdentifies 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].SAP HANA Administration Guide
Alert 80: Availability of asynchronous table replicationMonitors error messages related to asynchronous table replication.Determine which tables encountered the table replication error using system view M_ASYNCHRONOUS_TABLE_REPLICAS, and then check the corresponding indexserver alert traces. 









Tags: How to configure alerts in HANA for memory consumption, SAP HANA Memory management, 
Share this article :

Post a Comment

 
Copyright © 2011. SAP HANA TUTORIALS FREE - S/4 HANA - All Rights Reserved