SAP Knowledge Base Article - Preview

3246986 - HANA parameter doesn't take effect due to empty value in a different configuration level

Symptom

You have configured a parameter. However, you noticed that the parameter doesn't take effect. 

For example, you've run following SQL to configure the allocation limit for your tenant DB in HANA 2.0 DB. 
ALTER SYSTEM ALTER CONFIGURATION ('global.ini', 'DATABASE', '<Tenant_SID>') SET ('memorymanager', 'allocationlimit') = '102400' WITH RECONFIGURE;

However, when you run following SQL to check the allocation limit, a value different from configured value would be returned.
SELECT DATABASE_NAME, HOST, PORT, SERVICE_NAME, ALLOCATION_LIMIT/1024/1024 "ALLOCATION_LIMIT in MB" FROM "SYS_DATABASES"."M_SERVICE_MEMORY" where DATABASE_NAME = '<Tenant_SID>'

DATABASE_NAME HOST PORT SERVICE_NAME ALLOCATION_LIMIT in MB
<Tenant_SID> <host name><port number>indexserver204,800


Read more...

Environment

  • HANA 1.0
  • HANA 2.0

Product

SAP HANA 1.0, platform edition ; SAP HANA, platform edition 2.0

Keywords

dummy, wrong, incorrect, HANA studio, memory_tracking, resource_tracking, host level, system level, tenant DB level , KBA , HAN-DB , SAP HANA Database , How To

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.