SAP HANA FAQ – Most Frequently Asked Questions for SAP HANA provides a quick reference:   SAP Note 2057595 – FAQ: SAP HANA High Availability SAP Note 2073112 – FAQ: SAP HANA Studio SAP Note 2081591 – FAQ: SAP HANA Table Distribution SAP Note 2082286 – FAQ: SAP HANA Graph SAP Note 2100009 – FAQ: SAP HANA Savepoints SAP Note 2100040 – FAQ: SAP HANA CPU SAP Note 2101244 – FAQ: SAP HANA Multitenant Database Containers (MDC) SAP Note 2112604 – FAQ: SAP HANA Compression SAP Note 2114710 – FAQ: SAP HANA Threads and Thread Samples SAP Note 2115815 FAQ: SAP …... The post SAP HANA Frequently A ..read more

HANA System Replication is one of the important topic in SAP HANA. Being used in the context of high availability and disaster recovery scenario, It is really important to learn how to setup HANA System Replication in multi-tier replication scenario.   In this scenario we are enabling HANA System Replication – In Multi-tier scenario.   There are 3 HANA nodes: A, B and C, named SiteA, SiteB and SiteC Site A : Primary Database Node Site B: Secondary Database Node / HA Node Site C: DR node Replication Mode: From Site A –> Site B : SYNC From Site B …... The post Set Up SAP HANA System ..read more

Here i am explaining different replication Modes between Sites in the HANA Replication setup. Synchronous (SYNC) : The secondary system sends an acknowledgment back to the primary system as soon as the data is received and persisted to the log volumes on disk. Asynchronous (ASYNC): Asynchronous replication, the primary does not wait until the secondary sends an acknowledgement. Synchronous in-memory (SYNCMEM):The secondary system sends an acknowledgment back to the primary system as soon as the data is received in memory. The disk I/O speed on the secondary system doesn’t influence the pr ..read more

Parameter : statement_memory_limit Key Highlights :   statement_memory_limit parameter is used to control memory limit for single query execution. Sometime it happens if we don’t set any limit on query level then single execution of query takes complete HANA memory and result to the HANA crash . So it is really improvement to set proper value of statement_memory_limit   Description in detail: Sets a statement memory limit on HANA node  in GB (0 or not set = disabled) The limit defines the maximum memory that can be temporarily used for the execution of a statement on o ..read more

Parameter : allocationlimit  Key Highlights : This parameter is very useful in the Multi-tenant database container (MDC) system to set memory limit on each tenant system. Example : If we have 4 tenant systems in the landscape then we can set on indexsever.ini file –> allocationlimit for each tenant system to the accepted memory limit for each tenant system. Parameter: allocationlimit Description: Sets an upper limit of memory usable by individual processes in megabytes. When set to 0 or missing, the SAP HANA system implicitly calculates a default value based on global_al ..read more

HANA System Replication is one of the important topic in SAP HANA. Being used in the context of high availability and disaster recovery scenario, It is really important to learn how to setup HANA System Replication in multi-tier replication scenario.   In this scenario we are enabling HANA System Replication – In Multi-tier scenario.   There are 3 HANA nodes: A, B and C, named SiteA, SiteB and SiteC Site A : Primary Database Node Site B: Secondary Database Node / HA Node Site C: DR node Replication Mode: From Site A –> Site B : SYNC From Site B …... The post Set Up SAP HANA System ..read more

Here i am explaining different replication Modes between Sites in the HANA Replication setup. Synchronous (SYNC) : The secondary system sends an acknowledgment back to the primary system as soon as the data is received and persisted to the log volumes on disk. Asynchronous (ASYNC): Asynchronous replication, the primary does not wait until the secondary sends an acknowledgement. Synchronous in-memory (SYNCMEM):The secondary system sends an acknowledgment back to the primary system as soon as the data is received in memory. The disk I/O speed on the secondary system doesn’t influence the primary ..read more

Parameter : statement_memory_limit Key Highlights :   statement_memory_limit parameter is used to control memory limit for single query execution. Sometime it happens if we don’t set any limit on query level then single execution of query takes complete HANA memory and result to the HANA crash . So it is really improvement to set proper value of statement_memory_limit   Description in detail: Sets a statement memory limit on HANA node  in GB (0 or not set = disabled) The limit defines the maximum memory that can be temporarily used for the execution of a statement on one node. When a statement ..read more

Parameter : allocationlimit  Key Highlights : This parameter is very useful in the Multi-tenant database container (MDC) system to set memory limit on each tenant system. Example : If we have 4 tenant systems in the landscape then we can set on indexsever.ini file –> allocationlimit for each tenant system to the accepted memory limit for each tenant system. Parameter: allocationlimit Description: Sets an upper limit of memory usable by individual processes in megabytes. When set to 0 or missing, the SAP HANA system implicitly calculates a default value based on global_allocation_limit. Mult ..read more

Parameter: interval   Description: Sets a time interval in seconds between two checks for differences of ini file parameters between primary and secondary systems in a system replication scenario. To disable/enable those checks, set the parameter [inifile_checker] enable. Value: Positive integer   Default: 3600 (seconds = 1 hour)   Restart required: No     Ref: SAP HANA Admin Guide and Frequently Used Configuration Parameters in SAP HANA The post inifile_checker –> Parameter : interval appeared first on SAP BASIS-1 SOLUTION ..read more