Re: Solaris 8: out of memory

In article <3B4B1FDA.DCCB808D_at_attws.com>, "Daniel says...
>
>Przemek B±k wrote:
>
>> New install of Solaris 8, Oracle 8.1.7. We want to create new database.
>> In /etc/system we have:
>> * Shared memory
>> set shmsys:shminfo_shmmax = 4294967295
>> set shmsys:shminfo_shmmin = 1
>> set shmsys:shminfo_shmmni = 300
>> set shmsys:shminfo_shmseg = 30
>> * Semaphores
>> set semsys:seminfo_semmns = 15000
>> set semsys:seminfo_semmni = 100
>> set semsys:seminfo_semmnu = 100
>> set semsys:seminfo_semmsl = 150
>> set semsys:seminfo_semmap = 60
>>
>> /u01/app/oracle/product/8.1.7>uname -a
>> SunOS bravo 5.8 Generic_108528-08 sun4u sparc SUNW,Ultra-4
>> /u01/app/oracle/product/8.1.7>id -a
>> uid=102(oracle) gid=100(dba) groups=100(dba)
>> /u01/app/oracle/product/8.1.7>echo $ORACLE_SID
>> PGFWAR
>> /u01/app/oracle/product/8.1.7>svrmgrl
>>
>> Oracle Server Manager Release 3.1.7.0.0 - Production
>>
>> Copyright (c) 1997, 1999, Oracle Corporation. All Rights Reserved.
>>
>> Oracle8i Release 8.1.7.0.0 - Production
>> JServer Release 8.1.7.0.0 - Production
>>
>> SVRMGR> connect internal
>> Password:
>> Connected.
>> SVRMGR> startup nomount
>> ORA-27102: out of memory
>> SVR4 Error: 22: Invalid argument
>> SVRMGR>
>>
>> Two questions:
>> 1. Why the server is asking for password ?
>> 2. Why is "out of memory" ?
>>
>> przemol
>
>Either the kernel parameters for shared memory are set too low or the
>syntax is incorrect for the shared memory facility in the "/etc/system"
>file.
>
>To verify the current settings:
>
> % /etc/sysdef
>
> *
> * IPC Shared Memory
> *
> 1048576 max shared memory segment size (SHMMAX)
> 1 min shared memory segment size (SHMMIN)
> 400 shared memory identifiers (SHMMNI)
> 50 max attached shm segments per process (SHMSEG)
>
> If the value for SHMMAX is "1048576" either the syntax is incorrect or the
>
> parameter is not set at all in the "/etc/system" file.
>
> Proper syntax is:
>
> set shmsys: shminfo_shmmax = 4294967295
>
> Be sure the syntax is correct for all of your kernel parameters. An
>example would be:
>
> set shmsys: shminfo_shmmni = 400
> set shmsys: shminfo_shmseg = 50
> set semsys: seminfo_semmns = 14000
> set semsys: seminfo_semmni = 1024
> set semsys: seminfo_semmsl = 1024
> set shmsys: shminfo_shmmax = 4294967295
>
> A value higher than "1048576" means your syntax is correct but you need to
>
> increase the value of SHMMAX. Setting SHMMAX to "4294967295" is the
>maximum
> for the 32bit version of the Solaris operating system. Setting SHMMAX to
> this value is safe and is the suggested setting by Oracle Support.
>
> Explanation:
> ============
>
> If the "shmget" call fails to grab to enough shared memory to accommodate
>the
> variable portion of the SGA the ORA-27102 is signaled.
>
>Daniel A. Morgan
>

In keeping with the "teach em to fish" philosophy....

It should be noted that a search on http://metalink.oracle.com for

ora-27102 SVR4 Error: 22: Invalid argument

turns up the Oracle Support note Daniel quoted verbaitim above....

Doc ID: Note:1049169.6
Subject: SOLARIS: ORA-27102 AT STARTUP NOMOUNT AFTER INSTALL OF 8.0.X Type: PROBLEM
Status: PUBLISHED
Content Type: TEXT/PLAIN
Creation Date: 23-APR-1998
Last Revision Date: 25-SEP-2000  

--
Thomas Kyte (tkyte@us.oracle.com)             http://asktom.oracle.com/ 
Expert one on one Oracle, programming techniques and solutions for Oracle.
http://www.amazon.com/exec/obidos/ASIN/1861004826/  
Opinions are mine and do not necessarily reflect those of Oracle Corp