cancel
Showing results for 
Search instead for 
Did you mean: 

SAP MDM memory consumption reaches 100% and crashes

Former Member
0 Kudos

Hi all,

We are encountering issue with MDM system where memory consumption only increases after restart and finally reaches 95+% resulting in system becoming non-responsive/crash.

MDS_Logs don't show any errors which can lead to RCA explaining this behavior. We have Portal & PI systems connected to MDM.

Observation is that memory consumption never reduces.

I can provide logs but they are not of much use. As of now we restart MDM at regular interval to release memory.

Appreciate if any inputs can be provided.

Environment :

MDM Version :- 7.1.12.129

Oracle version :- 11.2.0.3.0


Regards,

Pragyesh

Accepted Solutions (1)

Accepted Solutions (1)

former_member201266
Contributor
0 Kudos

Hi,

Just check if there are scheduled bulk import or export ports which is causing this.

Try and disable syndication ports (Or suspend Syn server), also see if there are bulk imports which are in place and last check MDM workflow if there are getting triggered.

And most importantly close portal connection via code after user is inactive after a period of time (say 5 mins) or else the active session's also can cause the issue.

The above can be some causes for the abnormal behavior.

Regards,

Sai Charan.

Former Member
0 Kudos

Hello all,

Thanks for your checks and inputs.

Most relevant log that was found was tcp connections log where we can see orphan TCP connection.

Issue is not resolved as of now since now it is API/custom code corrections that should resolve the issue.

Relevant SAP notes : 1409330 - API sessions are never been closed

1508762 - Sessions management at Java API custom app

1407733 - How to destroy the event dispatcher connection?

Former Member
0 Kudos

As an alternative for the diagnose process, you may check if the server space is used up...if yes, then check if the distribution folders are getting extreamly large. If that's the case, it means you are having auto-syndication on-going. You need to find the syndication mapping and change the config in MDM syndicator.

Anqi

Answers (3)

Answers (3)

gabor_molnar
Advisor
Advisor
0 Kudos

While having high memory usage, run the MDS Clix Monitor in order to get to know what MDM process taking long (Note 1358503). Then you can focus on optimizing this process/solve the issue with them.

One typical reason might be for the high memory usage is the too many completed workflows in the repository: Note 1240587 But this is just one guess, if it didnt help, use MDM Clix Monitor to go on.

Regards,

Gábor

Former Member
0 Kudos

To be honest I've never used Clix before...I'll definitely try it out.

Thanks so much for the notes!!

Former Member
0 Kudos

Hi.

You don't say which processes are consuming the memory but ....


We saw something similar with MDM on Wintel.
mds.exe memory consumption was into the Gbs and growing.
The server had 24Gb of memory of which mds.ini was using or claiming 22.

We were able to increase the server memory to 36Gb.
We saw mds.ini settle down at 26Gb memory usage.

I believe it is because the mds server process caches repository contents in its own memory space as much as possible. We saw it does this on a restart of MDM. We may have been using the option to have the repository indexes rebuilt at start which may have forced the caching of repository content.

It begs the question that if mds does cache repository content, does your Oracle buffer cache need to be of any particular size!

Regards
Ken.

Former Member
0 Kudos

Thanks Ken for your valuable inputs!!

For us also it is indeed mds process that consumes memory steadily.

After restart of MDM we see that there is only 1 trend steady increase....

How can we understand from logs that it is indeed because of caching that memory use only increases and anyway to find optimal value that will be occupied by mds process cache.

Appreciate if you can share some SAP document related to this caching behaviour of mds.

fyi : our OS is Linux

Regards,

Pragyesh

Former Member
0 Kudos

In addition SAP MDM is able to run for approx. 2 weeks before memory consumption reaches almost 100%

So increment in mds memory utilization is very slow.

mukeshkumawat
Explorer
0 Kudos

Hi Pragyesh,

Did you see the Oracle DB logs to understand from which operation it's occupying such a large space.Also if you have automatic Import and Syndication Port configuration Please do have a Check on file generation.

Thanks,

Mukesh