Virtual Memory Errors

[Judy Fisher]

We have encounter intermittent Virtual Memory errors on our systems
running SQL Anywhere. We were told by a developer that this was a problem
with Watcom and using Stored Procedures extensively? I am wondering if this
is a true statement and if is still an issue with SQL Anywhere 5.0?

Judy Fisher
jfi...@datavantage.com

[Leo Tohill]

> We have encounter intermittent Virtual Memory errors on our systems
>running SQL Anywhere. We were told by a developer that this was a problem
>with Watcom and using Stored Procedures extensively? I am wondering if this
>is a true statement and if is still an issue with SQL Anywhere 5.0?

No, there's nothing that fits such a vague description. That's kind of like saying that my computer
crashes when I use the keyboard extensively. <g> Usually it's What I do, not how much.

What version and build are you running? What is the exact error? How much memory is on the
computer, what is the operating system, and what are the virtual memory settings?

Leo Tohill - Team Sybase
>> Please post in newsgroup, not via email <<

[Judy Fisher]

We are running version 5.5.03 build #1666 SQL Anywhere, on NT4.0, with 64 M
or Ram with the VM settings initial size at 128M and max size at 128M (we
have plenty of HD space). We interface with SQL Anywhere with Powerbuilder
5.0.3. The exact error is "Your system is running low on Virtual Memory.
Please close some applications. You can then start the System option in the
Control Panel and choose the Virtual Memory Button to create an additional
paging file or to increase the size of your paging file". We use a large
number of triggers in our layaway function of our software and have isolated
the error occurring during that process.

Leo Tohill <leot...@csi.com> wrote in message
news:38443f48...@199.93.177.77...

[Jim Egan]

It's possible that you have created or encountered memory leaks. In your
triggers and procedures make sure you are closing all cursors.

How much memory are you allocating to the database engine? It should not
be more than about 32 megabytes.
--
Jim Egan [TeamSybase]
Houston, TX

Sybase Developers Network
http://sdn.sybase.com/sdn/mec/mec_home.stm

[Leo Tohill]

Is PB running on the same machine? It would be easy for a PB app to occupy more than 32mb of vm.
Add 20 to 40 for a NT4 footprint, and then add the SA cache size + 2mb, and other running
applications... you could reach the 128mb limit pretty easily. I would increase that limit,
myself.

As Jim said, failure to close cursors or drop statements could cause a memory leak. Also, PB has
had some memory leak problems. Do you have any tool that lets you look at the memory requirements of
each task as it runs?

>We are running version 5.5.03 build #1666 SQL Anywhere, on NT4.0, with 64 M
>or Ram with the VM settings initial size at 128M and max size at 128M (we
>have plenty of HD space). We interface with SQL Anywhere with Powerbuilder
>5.0.3. The exact error is "Your system is running low on Virtual Memory.
>Please close some applications. You can then start the System option in the
>Control Panel and choose the Virtual Memory Button to create an additional
>paging file or to increase the size of your paging file". We use a large
>number of triggers in our layaway function of our software and have isolated
>the error occurring during that process.

[Judy Fisher]

Thanks, for the help. Our PB developers are going to double check that. On
one of the systems we are allocating 8M or memory and on another one we are
allocating 12M?

Jim Egan <ega...@compuserve.com> wrote in message
news:MPG.12ae53a04...@forums.sybase.com...

[Judy Fisher]

Thanks for the help. As I told Jim , my PB developers will look into the
cursor issue. We tried to use memproof to pin point the memory problem
unfortunately it only shows API applications and our software does not use
API standards. I have memsnap that I am going to try today, and another
idea we had is to try to set up a continuous loop through the triggers that
are being used and see if we can create the error that way.
Thanks again, for the ideas and help.

Leo Tohill <leot...@csi.com> wrote in message

news:3844b409...@199.93.177.77...

[Eric Teutsch]

On the NT box, open TaskManager, open the Processes tab, do View / Select
Columns... and add the Virtual Memory column. Then click on the header of
the VM Size to see which process has the biggest allocation of VM space.
Monitor this for a while, and it will tell you which process is eating up
your VM space. It could easily be something totally unrelated to your app,
or to SQLAnywhere.

Eric T.

Judy Fisher <jfi...@datavantage.com> wrote in message
news:GLpEMAAP$GA....@forums.sybase.com...