cancel
Showing results for 
Search instead for 
Did you mean: 

Work process/memory problems on SAP/Windows/SQL Server

Former Member
0 Kudos

We have a BW instance, it's a BW 3.5 running in Windows 2000 SP4 and SQL Server 2000. The database size is about 250GB and about 40 concurrent users daily.

We often found out that we have problems like

1. Memory leak -- when a user launch a big report, it get error like "memeory go to priv" and user get shortdump.

2. Sometime either a user work process or a background process stop working and just hanging there. And it can not be killed by SM50 or task manager. The only way to kill it is to reboot the system. These hanging work processes even keep instance be started without reboot the server.

We had worked with SAP and tune some profile parameters but did not help. And pretty much the standard answer from SAP is to update kernel and ask us upgrade to Windows 2003 also.

My question to the group is that do you guys have the similar problems in Windows/SQL Server platform? If you do, what do you do to fix or reduce these problems? Upgrade to Windows 2003 will help?

Thanks,

Yujun Ran

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

1. running to a processes virtual limit does not indicate a memory leak. many adminstrators did not understand that on 32 Bit platforms increasing caches (e.g. sizes of shared memory segments) will simultaniously decrease the amount of available memory remaining to an application.

2. this behaviour is documented in note <a href="http://service.sap.com/sap/support/notes/530871">530871</a>. This is a known problem on Windows 2000. In this case 3 GB option is active and the remaining 1 GB for kernel address space is not enough for the operating system in this situation.

Windows 2003 is more robust in this situation and gives you additionally the option to shorten the 3 GB address space for the applications virtual address space to something less, giving the Windows kernel more address space.

Nevertheless you are hitting the architectural limits of 32 Bit. The best option is to go for 64 Bit. Of corse 32 Bit will run, but you have to do a lot of optimization which you don't have to do on 64 Bit.

regards

Peter

Former Member
0 Kudos

Peter,

Thanks for your response. We are aware of the note 530871 and that's basically the reason we are thinking to upgrade Win 2003. Some questions we are debating like:

1. What extra work we have to do beside just upgrade server? Note 690432 listed other things we have to do. However, we upgraded our sandbox to Win 2003 and found out we don't have to do anything of these. We upgraded and then it seems fine. However, we don't know the fully impact of the upgrade since not many users are using sandbox.

2. In our production system, we have DB server and a app server. Should we just upgrade app server first? Does this architecture (DB in Win2K, AP in Win2003) work? Anyone is currently running this architecture or any related experiences can be shared?

3. Go for 64 bit, is a total new installation or some easy migration path?

Thanks,

Yujun Ran

PS. I have rewarded you the points with helpful answer

Former Member
0 Kudos

> Peter,

>

> Thanks for your response. We are aware of the note

> 530871 and that's basically the reason we are

> thinking to upgrade Win 2003. Some questions we are

> debating like:

you should contact Microsoft as described in this note. as far as I heard customers having this problem may get a free upgrade to the Windows 2003 server license, because microsoft can not fix the problem in d windows 2000.

>

> 1. What extra work we have to do beside just upgrade

> server? Note 690432 listed other things we have to

> do. However, we upgraded our sandbox to Win 2003 and

> found out we don't have to do anything of these. We

> upgraded and then it seems fine. However, we don't

> know the fully impact of the upgrade since not many

> users are using sandbox.

the problems and additional actions normaly did affect old SAP Systems not originally supporting Windows 2003 and additionally used 3rd party products (like backup interfaces, Anti Virus Software etc).

> 2. In our production system, we have DB server and a

> app server. Should we just upgrade app server first?

> Does this architecture (DB in Win2K, AP in Win2003)

> work? Anyone is currently running this architecture

> or any related experiences can be shared?

yes, this is possible. You can easily mix Windows 2000 and Windows 2003 systems.

> 3. Go for 64 bit, is a total new installation or some

> easy migration path?

you can even start with adding single 64 bit app-servers to your existing 32 Bit server landscape.

The migration path of the database and CI is called homogenious system copy and described in the homogenious system copy guide (see netweaver 04 documentation suite).

regards

Peter

Former Member
0 Kudos

Thanks very much, Peter. You confirmed several questions in our discussion. I rewarded you with the very helpful answer.

Answers (0)