SMD parameters - "Max memory size limit is too low"

[nthsol]

Hi experts,

I am having the case that when I start the SMD on a server I get the Warning message:

!!! WARNING !!!

Max memory size limit is too low, unbegrenzt is lower than 256000 [Recommended Value]

!!! WARNING !!!

Now I wanted to set the max memory value to the recommended 256000 but I am not quite sure where to set it.

I had a look at:

• /usr/sap/SMD/J98/SMDAgent/configuration/runtime.properties
• /usr/sap/SMD/J98/profile/smd.properties
• /usr/sap/SMD/SYS/profile/START_J98_<host>
• /usr/sap/SMD/SYS/profile/SMD_J98_<host>
• /usr/sap/SMD/SYS/profile/DEFAULT.PFL

I couldn't find any place where to put the value. Could you please assist?

Kind Regards,

Niklas

Full log output while starting SMD:

bash-3.2$ smdstart.sh SMD 98

_________________________________________________________________________

SAP Solution Manager - Diagnostics Agent  - Copyright (c) 2007 SAP AG
_________________________________________________________________________

[-] Prerequisites
-----------------

Max open files limit .. OK

!!! WARNING !!!
Max memory size limit is too low, unbegrenzt is lower than 256000 [Recommended Value]
!!! WARNING !!!

[-] Starting agent SMD / 98 on host with user smdadm ..

      SAPOSCOL version  COLL 20.95 701 - V3.72 64Bit, 64 bit, single threaded, Non-Unicode
      compiled at   Feb 24 2009
      systemid      370 (Solaris on SPARCV9 CPU)
      relno         7010
      patch text    COLL 20.95 701 - V3.72 64Bit
      patchno       32
      intno         20020600
      running on    <host> SunOS 5.10 Generic_147440-11 sun4u
      PATCHES
      DATE     CHANGELIST           PLATFORM             PATCHTEXT
      20081211 1032251              ALL                  Option -w support. Removed SizeOfRecord warning rt 130.
      20090114 1036522              UNIX                 Log file permissions: 664.
      20090203 1041526              UNIX                 Add. single instance check.
      20090210 1042962              ALL                  Continue after EWA HW XML generation failure.

[-] Launching SAP SERVICE for Diagnostics Instance ...
--------------------------------------------------
ok.

[-] Launching Diagnostics Agent Instance ...
---------------------------------------

SAP-R/3-Startup Program Rel 701 V1.8 (2003/04/24)
-------------------------------------------------

Starting at 2014/05/30 09:22:24
Startup Profile: "/usr/sap/SMD/SYS/profile/START_J98_<host>"

Starting Programs
-----------------

30.05.2014 09:22:24
ShmDetach
FAIL: NIECONN_REFUSED (Connection refused), NiRawConnect failed in plugin_fopen()
(21793) Starting: local /usr/sap/SMD/J98/../exe/jcontrol pf=/usr/sap/SMD/J98/../SYS/profile/SMD_J98_<host>
(21790) Waiting for Child Processes to terminate.
exit code 0 returned.

[Former Member]

More likely it's about shell limits. Check it with ulimit/limit command (depends on shell).

[Former Member]

Dear Niklas,

could you please to see note http://service.sap.com/sap/support/notes/1901400

With best regards,

Alexander

[nthsol]

Hi Alexander,

as per SAP Note 1901400 I changed in file /usr/sap/SMD/J98/profile/smd.properties the line from

smdagent.javaParameters=-DP4ClassLoad=P4Connection -Xmx256m -Xms256m -XX:MaxPermSize=128m

to

smdagent.javaParameters=-DP4ClassLoad=P4Connection -Xmx512m -Xms512m -XX:MaxPermSize=256m

But unfortunately this did not help.

Do you have any other ideas?

[Former Member]

Dear Niklas,

It's OK.

With best regards,

Alexander

[madasamy_arunachalam]

Hi Niklas

Check this KBA, it has slightly different value.

Ensure you restart completely to new parameter to activate, After stopping smdagent, check for any smd related process & kill this if any .

1674114 - java.lang.OutOfMemoryError occurs on the managing agent during large data collection

regards

Swami

[Former Member]

Hello,

I would search profile files in this sequence - SMD_J98 (= instance profile), DEFAULT.

The process of reading profiles is the system reads always DEFAULT profile and then Instance profile. Values set in both profiles are rewritten by value specified in Instance profile (since it is used later). The Start profile should not be used anymore, but it depends on version you have.

The name of parameter should something like max_memory_limit or something similar.

Kind regards

[nthsol]

Hi Kamil,

do you have an SMD/DAA configured that works smoothly?

Could you post the values of your profile files so that I can adopt and test with them?

Regards,

Niklas

[Former Member]

Dear Niklas,

my agent has standard values:

smdagent.javaParameters=-DP4ClassLoad=P4Connection -Xmx256m -Xms256m

-XX:MaxPermSize=128m

With best regards,

Alexander