MDM.exe and oracle.exe ....memory leak.. not releasing Nonpaged memory

[Former Member]

We are facing Memory leak in oue MDM server. Our environment details

are as follows;

MDM 5.5 SP5 ( Build 5.5.41.70)

Oracle 10.2 patch 2

windows server 2003 SP1

XI 7.0 SP 9

If server is running continuously 3-4 days then Nonpaged memory is

getting exausted and server does not respond. Now we have to retart the

windows server manually.

If we see the task manager it is shows more than 200,000 handles for

oracle.exe and more than 100,000 handles for mds.exe.

1: Oracle.exe -- more than 200000 handles ( Approx >5000 is problem)

2: Mds.exe -- more than 100000 handles ( Approx >5000 is problem)

Since these applications are not releasing the handles properly so all

nonpaged memory gets exausted and server stops responding.

If we restart the mdm server, database and OracleserviceMDMD, then

nonpaged memory is released. But some times even if we restart these

services, we do not get nonpaged memory released. So we have to restart

the windows server.

please help me if anyone else have faced the same problem.

regards

Saurabh

[Former Member]

.

[former_member278106]

Hi Saurabh,

Are you running MDM 5.5, Oracle 10.2, MSSQL and XI 7.0 on one physical machine?

Regards,

Lev

[Former Member]

Hi Saurabh,

We had similar Issue with workflow in SP04 as memory was not released and we had to restart server after 2-3 days. SAP claimed that they fixed it in SP05,not sure if this got solved that in SP05.

Please suggest if you are facing this problem with workflow also.

- An

[Former Member]

Hi,

Many thanks to all of you for valuable inputs.

We have upgraded MDM to the currecnt patch level MDM 5.5 sp5 patch2 hotfix 4.

But still we are facing the same issue.

We are using import server, syndicator and publisher and workflow.

Since all activities are going on... we are not sure about the activity which causing it.

Still struggling for solution...

regards

Saurabh

[Former Member]

Hi Saurabh,

What I suggest you to open an OSS message.

However in parallel , try to simulate all these three process one by one. You can really see the difference that which process adding memory.

Hope it will solve your problems,

- An

[Former Member]

SAP has suggested us to migrate the win2003 32 Bit to 64 Bit machine.

So planning for migration. Reason is that win 32 Bit m/c can have max 3 GB of memory. if we use PAE for memory extention on win 32 bit m/c then MDM does not understand how to address that memory. So even if we use more than 3 GB memory, for MDM effectively it is only 3 GB.

regards

Saurabh

[Former Member]

Hello Saurabh,

SAP developers have discovered a connection leak that is probably

what you are seeing and the leak should be either gone or vastly

reduced for MDM 5.5 SP6.

If you could can describe what activities caused the leak you noticed

(as Cleopatra discussed) we will use that as a basis to test for any

leaks that remain.

Thank you for your report,

Dave

[Former Member]

Hi Saurabh,

What operations are you performing on the server? We investigated and found a few operations that are not correctly releasing the handles to the database, but you would have to be continuously, repeatedly executing these operations to see such a spike in the handles. Are you using Import or Syndicator? Any help you can provide is really appreciated; it seems like you may have found a real problem with the software.

Thanks!

Cleopatra