MBIND: CANNOT ALLOCATE MEMORY ON STARTUP [ID 578536.1]

		修改时间 02-APR-2009 类型 PROBLEM 状态 PUBLISHED

In this Document
Symptoms
Changes
Cause
Solution
References

Applies to:

Oracle Server - Enterprise Edition - Version: 10.2.0.4
Linux x86-64
Oracle Server Enterprise Edition - Version: 10.2.0.4

Symptoms

Seeing memory errors upon starting the database after applying 10.2.0.4 patchset.

Typical symptoms can be

SQL> startup
mbind: Cannot allocate memory
mbind: Cannot allocate memory
mbind: Cannot allocate memory
ORACLE instance started.

Total System Global Area 1.5032E+10 bytes
Fixed Size                  2306640 bytes
Variable Size            1959054768 bytes
Database Buffers         1.3069E+10 bytes
Redo Buffers                1572864 bytes
Database mounted.
ORA-01034: ORACLE not available
ORA-27102: out of memory
Linux-x86_64 Error: 12: Cannot allocate memory
Additional information: 1
Additional information: 566886

ORA-27102: out of memory
Linux-x86_64 Error: 28: No space left on device

Changes

Installation of 10.2.0.4 patchset

Cause

New enhancements that have been added in 10.2.0.4 requires that /dev/shm be mounted with the correct size if it is used. Per the new code logic, when _db_block_cache_protect is enabled /dev/shm memory mapped file will be used instead of shm segments.

Solution

If one does not wish to disable the _db_block_cache_protect parameter, then an increase to the size of /dev/shm will be required.

References

BUG:7016155 - ORA-27102 AFTER UPGRADE FROM 10.2.0.3 TO 10.2.0.4
BUG:7019967 - MBIND: CANNOT ALLOCATE MEMORY ON STARTUP