1) How big (max) can an Oracle SGA be in a 32bit platform (Windows and
Linux on ia32)?
This doesn't fully answer your question, but you may want to take
a look at this white paper.
http://otn.oracle.com/tech/linux/pdf/9iR2-on-Linux-Tech-WP-Final.PDF
Do realize that PAE (36bit kernel/physical
On Saturday 01 March 2003 01:13 pm, Craig I. Hagan wrote:
1) How big (max) can an Oracle SGA be in a 32bit platform (Windows and
Linux on ia32)?
This doesn't fully answer your question, but you may want to take
a look at this white paper.
By default, Windows imposes a 2g per process limit on all processes
including the OS itself. Oracle runs as a process with each session running
as a thread within that process so the entire Oracle process including SGA,
sessions, DLLs, executables, etc. must all fit within 2g. There is a
boot.ini
Hmmm. I should have asked that last over the phone interview for that
prospective job what hardware platform they run their databases on.
They claimed all their database is cached in memory, as in all. I
know they use Linux, but on what hardware platform. 3GB buffer cache
(less than this since
Hey, I just remembered that Oracle on Linux runs as multiple processes
, unlike Oracle on Windows which runs as one big process. Does this
mean each Oracle process on Linux can access 3GB of memory? So that in
the end the whole of Oracle can actually use greater than 3GB of memory?
--
Lyndon Tiu
That 3g limit only applies to Windows (2g w/o the boot.ini /3g switch).
Linux is a whole other bowl of wax. Having never run Oracle in Linux I'm
afraid I can't answer your question. My best guess would be the per process
limit is 4g, but on most unix platforms the SGA (which the OP was about) is
Lyndon - How about more memory than you can afford. On most Unix systems,
and I assume Linux is roughly similar, there is a kernel setting that is
effectively the per process limit. If you have 4 gig real memory, you
would set the per process limit much lower because all processes must share
that
Windows is a mess. Everything (all foreground and background processes) has
to cram inside 2Gb (default) or 3Gb (boot.ini option for certain Windows
versions). Also, by default, each database session thread allocates 1Mb for
stack space by default, and that takes away from the process's total of
