Powell, Mark D wrote:
> Michael, I could easily be wrong but I think you are getting 04030
> errors because you have allocated too much of your total available
> memory to the SGA and do not have enough left to be allocated to the
> PGA's of your user sessions.

Essentially, the DB Creation Asst was only going to use 40%, which we
thought was quite low, of it's possible 2GB so we decided on 80% since
all this server does is this 1 instance. So it came up with 1.2GB for
sga and 400MB for pga.

> Have your tried reducing your SGA_TARGET
> to say 800M or 1G and seeing if this eliminates the 04030 errors while
> still allowing the database to perform well enough?

That is the only thing support has suggested (other than the 3gb switch)
but they haven't given me a practical way to do it yet. You can only
reduce sga_target by the difference in your current amount and the min
sizes of the parameters that sga_target controls. sga_target is 1200MB,
the sum of min sizes is 1188MB so I can only reduce it in 12MB steps it
seems. Now perhaps this is really what I need to do (can't do it all at
once), but support has never responded back if there's a more
appropriate way to do it (after several updates of my SR asking for
clarification).

> Why can't you use the -3G or better yet /PAE switch to make more than 2G
> available?

It isn't supported by MS in a production environment on Standard Edition
unless the app vendor (Oracle) has tested it. Oracle hasn't responded
about that either.

--

Sincerely,
Michael Ray
Topshot Systems LLC
--
http://www.freelists.org/webpage/oracle-l