Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Usenet -> c.d.o.server -> Re: svrmgrl problem
"Alexey Ovchinnikov" <alexiss_at_svl.ru> wrote in message
news:9u7qps$9pg$1_at_octopus.co.ru...
> "Sybrand Bakker" <postbus_at_sybrandb.demon.nl> wrote in message
> news:u0ekri54pcm341_at_corp.supernews.com...
> >
> > "Alexey Ovchinnikov" <alexiss_at_svl.ru> wrote in message
> > news:9u7hq6$7kh$1_at_octopus.co.ru...
> >
> > 1 Check the alert<SID>.log in the bdump directory. It will contain
> pertinent
> > error messages
> > 2 This error is usually being caused by the fact the SHM* settings in
Unix
> > don't match the settings for the SGA, in that case Oracle will fail to
> > create the SGA, and as Oracle locally communicates by means of the SGA
you
> > will get 3113.
> >
> > Hth
> >
> > --
> > Sybrand Bakker
> > Senior Oracle DBA
> >
> > to reply remove '-verwijderdit' from my e-mail address
> >
> >
> >
>
> where can i find SGA settings? are you mean SHMMAX value under SHM* ? So,
I
> set up SHMMAX to 0x800000 (128 Mb) - it's my RAM size, recompile kernel,
> restart computer and get same problem
>
> thanks
> Alexey Ovchinnikov
>
>
>
>
The SGA settings are in init<SID>.ora in $ORACLE_HOME/dbs
The main settings affecting memory are
db_block_buffers (multiply by db_block_size to get the number of bytes used)
shared_pool_size (in bytes)
large_pool_size (in bytes)
java_pool_size (in bytes)
log_buffer
You didn't check alert<SID>.log, did you? Please do so.
Hth
-- Sybrand Bakker Senior Oracle DBA to reply remove '-verwijderdit' from my e-mail addressReceived on Fri Nov 30 2001 - 05:51:43 CST