Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

OAS 4.0.7 on NT4 and Virtual Memory Errors

1 view
Skip to first unread message

SteveMc...@bigfoot.com

unread,
Feb 22, 1999, 3:00:00 AM2/22/99
to
I am running OAS 4.0.7 under NT 4.0/SP3. I have 128MB RAM and I am _only_
runni g OAS. I have Oracle 8 on a seperate machine.

I have been getting alot of these errors in my NT Event Viewer.
Any Idea what the problem might be???

The description for Event ID ( 0 ) in Source ( OracleWRBService ) could not
be found.
It contains the following insertion string(s):
02-21-1999 17:41:11 0 server-bonehead `Broker` 283 1
0x10fff `OWS-04770: Host ord-srv-trex is running out of
Virtual Memory(at 4 MB) and disabled temporarily for
Cartridge Bone_Head/Mofoi instance creation.

Steve McAllister


-----------== Posted via Deja News, The Discussion Network ==----------
http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own

Joe Kazimierczyk

unread,
Feb 22, 1999, 3:00:00 AM2/22/99
to SteveMc...@bigfoot.com
I am getting similar '...running out of Virtual Memory(at 4 MB) and disabled
temporarily for...' errors with OAS 4.0.7 under Solaris 2.6. The solaris box
is only running OAS, has 256 Mb mem, 512 Mb swap. Swap space is usually
about 95% free when I see this error. So far, Oracle Support has not been
helpful. I'd also be interested in solutions / comments about this problem.

Joe Kazimierczyk
kazi...@bms.com

Bogdan Stepien

unread,
Feb 24, 1999, 3:00:00 AM2/24/99
to
When I was running 4.0.5 on NT4/SP3 with 192MB RAM, I had similar problems.
Increasing virtual pagefile size to 256MB helped, but it still worked very
slow.
Another problem which can cause such behaviour is large amount of session
enabled cartirdges (of any type), occupying memory (decreasing session
expiration
time should help).

Now I am running OWAS 4.0.6 and Oracle 8.0.4 on Solaris with 192MB RAM,
and have no problems (till now ;).

--
Bogdan Stepien
mailto:ste...@tpg.pl

SteveMc...@BigFoot.com wrote in article
<7arq4j$2o3$1...@nnrp1.dejanews.com>...

Super Kev

unread,
Feb 25, 1999, 3:00:00 AM2/25/99
to
Can we try to keep this thread open until some one can get an answer from
Oracle.

We recently installed OAS 4.0.7 ( previously ran OAS 3.xx with no problems )

The pl/sql cartridges kept crashing around our ears very frequently. After
reading the log files it seemed that the major problem ( but I stress that
this was not the only cause of failure ) was due to lack of virtual memory
on the server.

I doubled the virtual mem on the server and the problem has lessened ( there
are occasional crashed though !!! )

We are only in a dev environment with only three or four of us requesting
via OAS.

The question to be raised then is just how much virtual memory will OAS 4
require when a high user system is in place ???

We are so worried now that at the minute our safest option is to return to
using OAS 3 !!!

Any responses will be greatly appreciated

Cheers

Steve Bright


SteveMc...@BigFoot.com wrote in message

Andrew Tacchi

unread,
Feb 25, 1999, 3:00:00 AM2/25/99
to
Dear Super,

I'm also having this problem ( PLSQL cartridge seems to hang, the listener
is still running fine ), I will tell you what results I get when I get
something worth tellng.

The problem seems to be reduced with an increase to the virtual memory on
our server.

We currently have a Pentium Pro 200 with 256MB with a 256MB swap file.

It has OWS 4.0.7 and 4 Oracle instances that are small developement areas
SGA 10MB ) with very little data.


Super Kev wrote in message <7b3bf9$tjf$1...@hagen.cloud9.co.uk>...


>Can we try to keep this thread open until some one can get an answer from
>Oracle.
>
>We recently installed OAS 4.0.7 ( previously ran OAS 3.xx with no
problems )
>
>The pl/sql cartridges kept crashing around our ears very frequently. After
>reading the log files it seemed that the major problem ( but I stress that
>this was not the only cause of failure ) was due to lack of virtual memory
>on the server.
>
>I doubled the virtual mem on the server and the problem has lessened

Jay Walters

unread,
Mar 5, 1999, 3:00:00 AM3/5/99
to
I've also seen the same problem, it stems from the fact that OAS won't
create new cartridge instances if there isn't enough virtual memory. I
found to run a stable Oracle8 + OAS 4.0.7 w/1 Java cartridge +
JDeveloper I needed at least 320 MB of virtual memory (physical +
pagefile). This total virtual number was independent of the physical
memory, as I ran with both 96 MB and 192 MB. Moving from 256MB to 320MB
made a world of difference for me, but of course your mileage will vary
depending on the type and size of your cartridges.

Cheers

0 new messages