Jonas,
In addition to Dick's comments about a real Os ( with which I concur ) you
need to do that math. You are running 170 sessions on the database.
You can count on each session eating up 5 meg of RAM with 7.3. If you
go to 8i, you can at least double that figure. This is all dependant
You should consider running MTS or buying more RAM (if you want to run MTS you
probably need to get to 8.1.7.2 first -- I don't remember its status as of 7.3.4
but in the 8.0 and 8.1.pre-7 series it appears to be unreliable).
Your problem is probably this: of the 1.7G RAM you really only have
Actually, I would just try and shrink the sga a little bit and make sure
that your swap file is on it's own platter. I have run into a lot of
problems with swap file crap on NT, even thought the machine has a gig of
ram. Try to keep it just a little below that 1.7 threshold. Also, I read
Jonas,
We were using Oracle7 on NT for awhile until the major problems just became
too unbearable. We would get ORA-600s and corruption constantly. I moved
the database over to OpenVMS (I still miss it...) and never had another
problem.
Good luck! You'll need it!
Rich Jesse
There are several Oracle tech notes that discuss NT and Windows 2000
Server Memory/Process architecture issues and limitations. I'll look
around and post anything I can find quick without having to go back
to Metalink.
If I recall correctly, Windows 2000 Advanced Server for RAM=4G
requires
http://www.oreview.com/9805harr.htm
---excerpt---
...
On NT, the Oracle instance is implemented as a single NT process.
This process includes threads that implement each of the tasks
required for the instance. Therefore, there is a thread for each of
the background and server tasks plus a
