Something is odd about this. You may have several problems.

1) if shmsys:shminfo_shmmax=314572800
how did you start an instance with Total System Global Area 1987780592
bytes?

2) Now you say you have shmsys:shminfo_shmmax=1305280512,
but that is still less than the size of the SGA! That is probably why it
doesn't start.
The error you are receiving seems to indicate that.

3) There is a limit on the SGA size in Solaris 2.6 of just over 1.7 GB
without
doing something special. That is less than your SGA size also! Is this
Solaris 2.6?
If so, see: metalink Note:15566.1 and/or see:
http://www.ixora.com.au/q+a/0102/09144710.htm

-OraSaurus (Not associated with ixora except as a grateful user!)

----- Original Message -----
From: "Tamara Coleman" <[Email Address Removed] "LazyDBA.com Discussion" <[Email Address Removed] Thursday, May 31, 2001 12:09 PM
Subject: Shared Memory problem on Solaris 7


> We have a Enterprise 450 with 4 gb memory (which the system recognizes).
This
> database server shares this box with a Sybase database as well. A few
weeks ago,
> 2 gb was added to this machine (bringing to 4gb) because it was not able
to
> handle the 2 databases and QA at the same time. The SGA was pruned down
> considerably to allow the database to come up with these settings. Before
the 2
> gb was added the system file shmmax was set to this.
> shmsys:shminfo_shmmax=314572800
>
> Way smaller than recommended in Oracle installation, but this was the
number in
> which we where able to get Oracle to attach to shared memory. The SGA when
the
> database started was:
>
> Total System Global Area 1987780592 bytes
> Fixed Size 69616 bytes
> Variable Size 304730112 bytes
> Database Buffers 1677721600 bytes
> Redo Buffers 5259264 bytes
>
> So with the new memory I wanted to increase the SGA and thus increase the
> shmmax. When I set the shmmax to just what Oracle recommends and rebooted
the
> machine, starting Oracle got this error.
>
> SVRMGR> startup
> ORA-27123: unable to attach to shared memory segment
> SVR4 Error: 22: Invalid argument
>
> I never touched the init.ora file, I rebooted (so no lagging shared memory
> segments, but just the same checked for them with ipcrm), just increased
the
> shmmax variable. To get the database up the best I could do for that
setting was
> :
>
> shmsys:shminfo_shmmax=1305280512
>
> Here's the kicker! I have another 450, same configuration that has always
had 4
> gb memory and the typical settings in the system file, and a much larger
SGA and
> it has always worked.
>
> Please, any help would be appreciated!
>
> Tamara L Coleman
> Database Engineer
>
>
>
> --------
> Oracle documentation is here:
http://tahiti.oracle.com/pls/tahiti/tahiti.homepage
> To unsubscribe: send a blank email to oracledba-[Email Address Removed] To subscribe: send a blank email to oracledba-[Email Address Removed] Visit the list archive: http://www.LAZYDBA.com/odbareadmail.pl
> Tell yer mates about http://www.farAwayJobs.com
> By using this list you agree to these
terms:http://www.lazydba.com/legal.html
>
>

Oracle LazyDBA home page