I just installed Oracle 11g today, and encountered the following error when starting the database after configuration.
SQL> startup
ORA-27154: post/wait create failed
ORA-27300: OS system dependent operation:semget failed with status: 28
ORA-27301: OS failure message: No space left on device
ORA-27302: failure occurred at: sskgpcreates
After looking at the documentation, ORA-2715 explains.
ORA-27154: post/wait create failed
Cause: internal error, multiple post/wait creates attempted simultaneously
Action: check errno and contact Oracle Support
Adjusted /etc/sysctl.conf and changed kernel.sem to
kernel.sem =5010 641280 5010 128
Make it work
#sysctl -p
====================================================
APPLIES TO:
Oracle Database – Enterprise Edition – Version 9.2.0.1 to 10.2.0.5 [Release 9.2 to 10.2]
Oracle Database – Enterprise Edition – Version 11.2.0.4 to 11.2.0.4 [Release 11.2]
Oracle Solaris on SPARC (64-bit)
Solaris Operating System (SPARC 64-bit)
SYMPTOMS
Attempting to startup instance, fails with error
ORA-27154: post/wait create failed
ORA-27300: OS system dependent operation:semget failed with status: 28
ORA-27301: OS failure message: No space left on device
ORA-27302: failure occured at: sskgpcreates
CHANGES
CAUSE
SEMMNS is set to 230 against 1024(Minimum Recommended).
The low value of SEMMNS is preventing to start the instance.
The SEMMNS parameter should be set to the sum of the PROCESSES parameter for each Oracle database, adding the largest one twice, and then adding an additional 10 for each database.
SEMMSL is set to 60 against 256 (Minimum Recommended).
This is recommended in both the Oracle 9.2 and 10.2 installation guides
SOLUTION
To implement the solution, please execute the following steps:
1. Set the kernel parameter as recommended in
Oracle 9.2 Installation Guide:
SEMMNS 1024
SEMMSL 256
Oracle 10.2 Installation Guide (for Solaris 8 and 9):
semsys:seminfo_semmns 1024
semsys:seminfo_semmsl 256
(refer to 10.2 Installation Guide for specific recommendations on Solaris 10 parameter settings)
Or
2. Reduce the Processes in Init.ora file to small value.
(This is useful when you don’t want to reboot the Unix server as a change of kernel setting requires a reboot for changes to be reflected)
NOTE:
1. If you have previously changed your kernel for another program to levels equal to or higher than the levels recommended in the Installation Guide, then do not change the settings. If the levels are too low, change them to levels at least as high as those in the table.
2. If you change the kernel settings, save the /etc/system file and restart the system to reflect the change
Similar Posts:
- How to Solve Rac ORA-01102 error: cannot mount database in EXCLUSIVE mode
- Oracle: db_12.2.0.1.0_Linux-x86-64: dbca Customized mode:ORA-07202: sltln: invalid parameter to sltln.
- [Solved] Linux Start database Error: could not open parameter file init**.ora
- The problem of “bad PBR sig” in the installation of Solaris10
- [Solved] ORA-12162: TNS:net service name is incorrectly spe
- [Solved] Oracle Error: SGA_MAX_SIZE cannot be set to more than MEMORY_TARGET
- Database “C:/Users/com/test” not found, either pre-create it or allow remote database creation (not recommended in secure environments) [90149-200] 90149/90149
- apr_socket_recv: Connection reset by peer (104)
- MYSQL Developer Error:Unable to find a Java Virtual Machine
- SQL Developer:Unable to find a Java Virtual Machine [Solved]