Hi,

We are running SQL 2K SP3a on a W2K3 machine. We use OLAP Services to
create cubes and serve as Datamart. Once in a few days, OLAP services
shutsdown or restarts by itself giving out "out of memory" error. Mostly it
occurs while processing the cubes, but at times during the day as well. We
have to restart Analysis services after which the cubes gets processed.

I have run Perfmon. There is plenty of available memory. The error occurs
when "virtual Bytes" of MSMDSRV.EXE becomes > 2G. We have enabled /3G
switch, increased "memory threshold", and have also applied the hotfix
Q887596.

Perfmon shows the Virtual Bytes of MSMDSRV.EXE is ever increasing during
online access. It shoots to maximum while cube processing, but drops down,
though not to the previous level.

Any solutions please ?

Thanks,
Rukmani

I have experienced the same problems.

It seems that SQL 2K SP3a has a memory leak and doesn't release memory
after processing cubes.
I suggest you get the new SP4 for AS and the AWE HotFix.

Rukmani wrote:

Hi Seiko,

This is issue is not specific to SP3a. We are struggling with this problem
for a year now, since SQL2000 and no SP. One of the solutions was to setup
move to W2K Enterprise edition and /3G switch to help increase Virtual Byte
limit to 3G. This does not work, as we still get error at 2G.

I also saw post here reporting similar problems with SP4.
I see memory increase mostly during online access. Actually, there is
memory usage increase/decrease during and after cube processing, but only
increase during online access.

Has Microsoft confirmed this problem is fixed in SP4 ? The patch Q887596
did not help.

Thanks,
Rukmani

"Seiko Pod" wrote:

Using SP4 with then AWE Hotfix has worked for us, however you might
want to consider setting MSConfig Boot.ini to release 3GB to AS and 1GB
to the OS.
This is offcourse only if yor server has a minimum of 4GB RAM.

Hi, Rukmani

What is the Memory conservation threshold value on your AS2K?
Try to set the Memory conservation threshold 200-300 Mb fewer as it is now.
The AS2K halts self not in the boundary and it follows to out of memory
error.

Vladimir Chtepa


"Rukmani" <Rukmani (AT) discussions (DOT) microsoft.com> schrieb im Newsbeitrag
news:FFC31720-40E7-4157-95B1-37EDCF061A63 (AT) microsoft (DOT) com...

Another possibility is that the out-of-memory is being caused because of a
shortage of pagefile space. Increase the pagefile and/or add a secondary
page file.
This is talked about in the AS Operations Guide
http://www.microsoft.com/technet/pro.../anservog.mspx

--
Dave Wickert [MSFT]
dwickert (AT) online (DOT) microsoft.com
Program Manager
BI Systems Team
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.


"Rukmani" <Rukmani (AT) discussions (DOT) microsoft.com> wrote

Hi Vladimir,

Our Server has 6G RAM. Memory conservation threshold is set to 3G. But I
get out of memory as soon as the Virtual bytes of MSMDSRV reaches 2G.

Thanks,
Rukmani.

"Vladimir Chtepa" wrote:

Hi Dave,
Our server has 6G RAM, and the pagefile is 4G. At the time of error,
%Usage of the pagefile is 1%, where as it has gone to 1.2% at other times.
%UsagePeak of pagefile is 1.4%.

Thanks,
Rukmani
"Dave Wickert [MSFT]" wrote:

Set Memory conservation threshold to 1,7 Gb.

"Rukmani" <Rukmani (AT) discussions (DOT) microsoft.com> schrieb im Newsbeitrag
news:FCCA0F7F-CA70-4382-AD8D-1A278957F7BF (AT) microsoft (DOT) com...

I'd still try adding pagefile. There isn't anything in the application
settings that's going to effect the available RAM to AS -- AS is
large-addressable aware -- that's compiled into the EXE. Also, triple check
your boot.ini file to make the switch is for the right config, is spelled
/3GB, not /3G, etc. Also, try putting the AS memory under a microscope with
more perfmon process counters and/or system memory counters and see if you
can determine what's going on there.

Something's preventing AS from getting the full 3GB of memory. You can tweak
the registry setting for AS to try to prevent it from running out of memory,
most notably the processing memory setting, as this is usually when AS runs
out of memory, particularly if you're processing anything in parallel, but
those won't have any effect on the actual memory (2GB vs. 3GB) that's made
available by the OS to the server.

BTW, AS doesn't use AWE -- that's a relational SQL buffer thing. AS uses
minimal buffers during data reads, and tweaking that setting has little
effect on AS performance overall.

--RJ

"Rukmani" <Rukmani (AT) discussions (DOT) microsoft.com> wrote