We are running Baan V5.0c over an Oracle 8.0.5 database. One session in Baan is consuming excessive amounts of memory: cprrp0520m000 - Time Phased Planning Overview. A normal bshell consumes 10-20 megabytes of swap space on our AIX system. Users running cprrp0520m000 consume 100-300 megabytes of memory.

We are about to expand our user capacity from ~50 to 150. This is a manageable problem with 50 users but will become a system stopper at 150 when >100% of our swap space could be consumed.

Baan Support says no other customer has reported this problem and, at the moment, is considering this a defect in Oracle.

Has anyone else seen this and if so how did you handle it?

This may be totally unrelated, but on Windows 2000, we have seen bshells grow to over 100MB in memory, which I find quite scarey.

Can't remember exactly which sessions at the moment tough.

Phil

Hi.

I work mainly on Windows environments and I've seen sometimes users consuming 200MB or so.

I noticed this happens mainly on big batch sessions.
For example, finalizing batches in finance. If you have a big batch - 5000 lines or so - I noticed the memory consumption growing and growing...

The problem (I think) is that after closing the session in cause, the memory remains allocated until you fully close your baan client...

Fred

One of my customers had something similiar, after some investigation it turned out that someone had changed performance parameter in cpcom0100s000 ‘Multiplier 2-D Array’s’. Due to that parameter sessions used more than 150Mb instead of the normal 20Mb.

So be aware that some parameters can have these kind of effects.

Rgrds,
Han

What are the settings involved? Right now our 2-D setting is 365 but I have no idea what that means or what the proper setting should be. The system came setup that way and no one has suggested changing it.

I think I've found them. I made some adjustments to the parameter and the results look good so far. I'll be monitoring the memory usage to see if it holds steady at its now lower value.

Normal setting: number of workingperiods per day * number of days to plan divided by 365. Round up a little.

Rgrds,
Han