according to sun best practices doc for oracle --
The ISM is enabled by default by both Oracle and Sun. So you don't need to
set it explicitly. However to make sure that the Prod instance locks its SGA
in shared memory, you should start it first before starting test instances..
The LOCK_SGA paramater is useful only for HP.
HTH
santysharma
Oracle certified DBA
Sun Certified System Admin
"Raf LaPietra" <raf_at_u10.telocity.com> wrote in message
news:W2vj7.5263$S5.3221931_at_newsrump.sjc.telocity.net...
> I am not sure, but I beleive you have to enable intimate shared memory for
> this to work and set use_ism=true
>
> -Raf
>
> In article <20010830.17082600_at_its.charlestoncounty.org>,
> Peter Shankey <shankeyp_at_its.charlestoncounty.org> wrote:
> >Oracle has an parameter called LOCK_SGA which will lock the memory the=20
> >SGA uses into physical memory. I saw a tech note on metalink.oracle.com =
> >
> >but it applied to HPUX. The error I get on Solaris is:
> > =20
> >Connected to:
> >Oracle8i Enterprise Edition Release 8.1.7.0.0 - Production
> >With the Partitioning option
> >JServer Release 8.1.7.0.0 - Production
> >
> >SQL> shutdown immediate
> >Database closed.
> >Database dismounted.
> >ORACLE instance shut down.
> >SQL> startup
> >ORA-27126: unable to lock shared memory segment in core
> >SVR4 Error: 1: Not owner
> >SQL>=20
> >
> >My question is how do or can I configure the OS to do this, and has=20
> >anyone had bad experiences doing this?
> >
> >My situation is I have a couple of test Oracle instances and a couple of=
> >=20
> >product one. I want the production instances to get the memory.=20
> >Unfortunately I am maxed on memory.
> >
> >Pete =20
>
>
Received on Thu Aug 30 2001 - 16:06:41 CDT
