ORA-27300: OS system dependent operation:semget failed with status: 28 - 2
Database Startup Fails with ORA-27300: OS system dependent operation:semget failed with status: 28 (文件 ID 949468.1)
Oracle Database - Enterprise Edition - Version 10.1.0.2 to 11.2.0.2 [Release 10.1 to 11.2]
Information in this document applies to any platform.
SYMPTOMS
On a linux server, when an additional database instance is brought up, getting errors:
SQL> startup nomount
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
CHANGES
An additional database has been created on a linux server.
PROCESSES parameter in init.ora set to the correct value, accordingly.
Linux Kernel Parameter for Semaphore - Total 32000 semaphore are available in the system but still gets an error - ORA-27300.
$ ipcs -ls
------ Semaphore Limits --------
max number of arrays = 128
max semaphores per array = 250
max semaphores system wide = 32000
max ops per semop call = 100
semaphore max value = 32767
CAUSE
In theory, 32000 semaphores are available in the system and one semaphore identifier can accommodate a maximum of 250 semaphores with
the configuration above.
But ipcs command shows each semaphore identifier accomodates maximum of 156 semaphores by Oracle.
$ ipcs << For this case, it has around 100 semaphore identifiers being used without bringing up the additional instance.
..
------ Semaphore Arrays --------
key semid owner perms nsems
0x450e15bd 0 root 666 1
0x0000cace 32769 root 666 1
0x358b172c 327683 oracle 660 104
0x9053d038 11075588 oracle 660 156
0x9053d039 11108357 oracle 660 156
0x9053d03a 11141126 oracle 660 156
0x9053d03b 11173895 oracle 660 156
..
According to this figure, the maximum available semaphores in this server will be 156 x 128 = 19968, not 32000.
SOLUTION
SEMMNI should be increased to accomodate more semaphores.
1. Query the current semaphore values in the kernel
# /sbin/sysctl -a | grep sem
2. Modify SEMMNI value in the /etc/sysctl.conf.
From
kernel.sem = 250 32000 100 128
To
kernel.sem = 250 32000 100 200
3. # /sbin/sysctl -p
Oracle Database - Enterprise Edition - Version 10.1.0.2 to 11.2.0.2 [Release 10.1 to 11.2]
Information in this document applies to any platform.
SYMPTOMS
On a linux server, when an additional database instance is brought up, getting errors:
SQL> startup nomount
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
CHANGES
An additional database has been created on a linux server.
PROCESSES parameter in init.ora set to the correct value, accordingly.
Linux Kernel Parameter for Semaphore - Total 32000 semaphore are available in the system but still gets an error - ORA-27300.
$ ipcs -ls
------ Semaphore Limits --------
max number of arrays = 128
max semaphores per array = 250
max semaphores system wide = 32000
max ops per semop call = 100
semaphore max value = 32767
CAUSE
In theory, 32000 semaphores are available in the system and one semaphore identifier can accommodate a maximum of 250 semaphores with
the configuration above.
But ipcs command shows each semaphore identifier accomodates maximum of 156 semaphores by Oracle.
$ ipcs << For this case, it has around 100 semaphore identifiers being used without bringing up the additional instance.
..
------ Semaphore Arrays --------
key semid owner perms nsems
0x450e15bd 0 root 666 1
0x0000cace 32769 root 666 1
0x358b172c 327683 oracle 660 104
0x9053d038 11075588 oracle 660 156
0x9053d039 11108357 oracle 660 156
0x9053d03a 11141126 oracle 660 156
0x9053d03b 11173895 oracle 660 156
..
According to this figure, the maximum available semaphores in this server will be 156 x 128 = 19968, not 32000.
SOLUTION
SEMMNI should be increased to accomodate more semaphores.
1. Query the current semaphore values in the kernel
# /sbin/sysctl -a | grep sem
2. Modify SEMMNI value in the /etc/sysctl.conf.
From
kernel.sem = 250 32000 100 128
To
kernel.sem = 250 32000 100 200
3. # /sbin/sysctl -p
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/35489/viewspace-1827034/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- ORA-27300: OS system dependent operation:semget failed with status: 28 - 1AI
- ORA-27300: OS system dependent operation:fork failed with statusAI
- ORA-27300: OS system dependent operation:fork failed with status: 12AI
- ORA-27300: OS system dependent operation:fork failed with status: 11AI
- ORA-27300: OS system dependent operation: CreateThread failedthreadAI
- ORA-27300 OS system dependent operation:if_not_found 問題處理
- informix初始化的時候報: semget: errno = 28ORM
- 3.4.3 Restoring the System to Normal OperationRESTORM
- maridb Error 'Operation DROP USER failed forErrorAI
- Check failed: status == CUDNN_STATUS_SUCCESS (4 vs. 0) CUDNN_STATUS_INTERNAL_ERRORAIDNNError
- rabbitMq的status報錯Error: unable to perform an operation on node ‘rabbit……MQErrorORM
- python os.systemPython
- Failed to get D-Bus connection: Operation not permittedAIMIT
- EBS: collect2: ld returned 1 exit status, Relink of module "FEMCCE" failed.AI
- docker安裝matlab mount failed: Operation not permitted.DockerMatlabAIMIT
- SAP CRM One order裡user status和system status的mapping邏輯APP
- Checking operating system version FailedAI
- adb remount of system failed: Permission deniedREMAI
- Apache無法啟動解決 the requested operation has failedApacheAI
- ORA-00245: control file backup operation failedAI
- ORA-13516: AWR Operation failed: CATPROC not validAI
- AVADA提示red system status的解決方法
- Python os.system 和 os.popen的區別Python
- solrcloud 報 HTTP Status 503 - Server is shutting down or failed to initializeSolrCloudHTTPServerAI
- Checking operating system version Failed 續AI
- remount of /system failed: Read-only file system原因及解決REMAI
- 【ORACLE】ORA-00245: control file backup operation failedOracleAI
- 2021-2-28:呼叫 System.gc() 後究竟發生了什麼?GC
- JBAS014613: Operation ("add") failed啟動報錯AI
- python os.system、os.popen、subprocess.Popen的區別Python
- gitlab-runner之build failed with exit status 1問題分析GitlabUIAI
- RuntimeError: cuDNN error: CUDNN_STATUS_EXECUTION_FAILED解決辦法ErrorDNNAI
- struts2 status屬性
- iOS開發 Build operation failed without specifying any errors 問題fixiOSUIAIError
- svn報錯cleanup failed–previous operation has not finished; run cleanup if it was interrupte...AI
- [筆記].痛哉!!!Error: Can't access JTAG chain, Error: Operation failed筆記ErrorAI
- PHP報錯getimagesize(): SSL operation failed with code 1問題解決方案PHPAI
- Process startup failed (ORA-27300,ORA-27301,ORA-27302)AI