Why Memory_size_per_connection value is -1?

[gabriela_urqua]

Hello Everybody,

We just upgrade our Hana Platform from SPS82 to SPS96.

For monitoring the memory usage, we usually use the SYS.M_CONNECTIONS view. With the SPS82 in the M_CONNECTIONS view, we got different values in the parameter memory_size_per_connection that represents the allocate memory for the connections. Those values were always positive values.

But now in the SPS96 when we review the memory_size_per_connection parameter, we are getting the value -1 for all the connections. What does it means? Why we got this value?

I'll appreciate your help.

Best regards,

Gaby

[oliver_sviszt]

Hello Everyone,

In our case the situation is the same: the column displays -1, althought both parameters are set. Could you find any fix to this problem?

[gabriela_urqua]

Hello!!

I reviewed and we have memory_tracking switching to on, also we verified and we have the statement:memory_limit set to 128, but we still have the same issue

Regards,

Gaby

[Former Member]

Can you run SQL: "HANA_Configuration_Parameters" (SAP Note 1969700) and attach the result?

[gabriela_urqua]

Hi Martin

This is the result

FILE_NAME	SECTION	PARAMETER_NAME	RECOMMENDED_VALUE	SAP_NOTE	DEFAULT_VALUE	CONFIGURED_VALUE	REC_HOST	DEFAULT_HOST	CONFIGURED_HOST
EVALUATION TIME:	25/06/2015 14:42
HANA VERSION:	1.00.096.00.1432206182
SPS:	9
SCALE-OUT:	No
REPLICATION:	No
STAT. SERVER:	Embedded
global.ini	auditing configuration	global_auditing_state	true	863362 (security)	-- HANA internal --	-- not set --	-- HANA internal --	-- not set --
global.ini	expensive_statement	enable	true	2000000 (analysis improvements)	false	-- not set --	-- not set --
global.ini	memorymanager	statement_memory_limit	-- individual value --	1999997 (memory consumption)	128
global.ini	persistence	log_backup_timeout_s	300 to 3600	1645183	900	86400
global.ini	persistence	log_mode	normal	1645183	normal	overwrite
global.ini	resource_tracking	enable_tracking	on	1999997 (analysis improvements)	off
global.ini	resource_tracking	memory_tracking	on	1999997 (analysis improvements)	off
global.ini	resource_tracking	service_thread_sampling_monitor_thread_detail_enabled	true	2114710 (analysis improvements)	false	-- not set --	-- not set --
indexserver.ini	sqlscript	enable_select_into_scalar_udf	true	2160814 (terminations)	-- HANA internal --	-- not set --	-- HANA internal --	-- not set --
indexserver.ini	transaction	transaction_history_record_limit	-- individual value --	1910610 (wrong results)	1000000	-- not set --	-- not set --
indexserver.ini	transaction	transaction_history_size_limit	-- individual value --	1910610 (wrong results)	10240	-- not set --	-- not set --
xsengine.ini	persistence	log_segment_size_mb	64 to 1024	2062080 (backup overhead)	8	-- not set --	-- not set --
indexserver.ini	row_engine	consistency_check_at_startup	-- no recommendation --	n/a    (erroneous SAP delivery)	-- HANA internal --	page, index	-- no recommendation --	-- HANA internal --	saphana-prod
nameserver.ini	statisticsserver	active	-- no recommendation --	1917938 (monitoring)	true	true	-- no recommendation --

HANA_CONFIGURATION_PARAMETERS.txt.zip

[Former Member]

This output indicates that both parameters in question are set to a blank / NULL value. You have to set them to 'on' and a limit value as mentioned above.

[gabriela_urqua]

Hi Martin,

Sorry we had to restart our HANA and so that we turn off the parameters. We forgot to turn on before running the script. Now we turned on and the result is

FILE_NAME	SECTION	PARAMETER_NAME	RECOMMENDED_VALUE	SAP_NOTE	DEFAULT_VALUE	CONFIGURED_VALUE	REC_HOST	DEFAULT_HOST	CONFIGURED_HOST
EVALUATION TIME:	25/06/2015 15:25
HANA VERSION:	1.00.096.00.1432206182
SPS:	9
SCALE-OUT:	No
REPLICATION:	No
STAT. SERVER:	Embedded
global.ini	auditing configuration	global_auditing_state	true	863362 (security)	-- HANA internal --	-- not set --	-- HANA internal --	-- not set --
global.ini	expensive_statement	enable	true	2000000 (analysis improvements)	false	-- not set --	-- not set --
global.ini	memorymanager	statement_memory_limit	-- individual value --	1999997 (memory consumption)	128
global.ini	persistence	log_backup_timeout_s	300 to 3600	1645183	900	86400
global.ini	persistence	log_mode	normal	1645183	normal	overwrite
global.ini	resource_tracking	service_thread_sampling_monitor_thread_detail_enabled	true	2114710 (analysis improvements)	false	-- not set --	-- not set --
indexserver.ini	sqlscript	enable_select_into_scalar_udf	true	2160814 (terminations)	-- HANA internal --	-- not set --	-- HANA internal --	-- not set --
indexserver.ini	transaction	transaction_history_record_limit	-- individual value --	1910610 (wrong results)	1000000	-- not set --	-- not set --
indexserver.ini	transaction	transaction_history_size_limit	-- individual value --	1910610 (wrong results)	10240	-- not set --	-- not set --
xsengine.ini	persistence	log_segment_size_mb	64 to 1024	2062080 (backup overhead)	8	-- not set --	-- not set --
indexserver.ini	row_engine	consistency_check_at_startup	-- no recommendation --	n/a     (erroneous SAP delivery)	-- HANA internal --	page, index	-- no recommendation --	-- HANA internal --	saphana-prod
nameserver.ini	statisticsserver	active	-- no recommendation --	1917938 (monitoring)	true	true	-- no recommendation --

Thanks for your help

HANA_CONFIGURATION_PARAMETERS2.txt.zip

[Former Member]

For me statement_memory_limit still appears to be empty. What is the result of:

select * from m_inifile_contents where key = 'statement_memory_limit'

[Former Member]

You said you disabled parameters before the restart - is it necessary for each restart or was there a specific reason?

(sorry, I am new to HANA)

[Former Member]

No, you can keep them set.

[gabriela_urqua]

Hi Martin

Sorry for the delay but I don´t have connection all the time for this HANA system. The result of the selec is:

FILE_NAME	LAYER_NAME	TENANT_NAME	HOST	SECTION	KEY	VALUE
global.ini	DEFAULT	memorymanager	statement_memory_limit
global.ini	SYSTEM	memorymanager	statement_memory_limit	128

[Former Member]

This is completely shuffled: The section is in the tenant column, the parameter name is in the host column and the parameter value is in the section column. So something went completely wrong when setting the parameter. Can you tell me how you did it? Do you use MDC (multi-tenant database containers)?

[gabriela_urqua]

Thank you Lars and Martin, I am reviewing both notes, I appreciate your help!

Regards,

Gaby

[Former Member]

If you have already set memory_tracking, you should additionally set statement_memory_limit due to the bug described in SAP Note 2164844.

[lbreddemann]

Is memory_tracking switched to ON on this SPS 9 system?

If not, you might want to change that setting.

Also see

1999997

FAQ: SAP HANA Memory

- Lars