<<Back to Oracle Main Page
ORA-00845 Raised While Starting the DB Instance
DB AlertLog ExtractFollowings is recorded in the database Alertlog
WARNING: You are trying to use the MEMORY_TARGET feature. This feature requires the /dev/shm file system to be mounted for at least 2147483648 bytes. /dev/shm is either not mounted or is mounted with available space less than this size. Please fix this so that MEMORY_TARGET can work as expected. Current available is 2090700800 and used is 1694498816 bytes. Ensure that the mount point is /dev/shm for this directory.
memory_target needs larger /dev/shm
Cause
The new Automatic Memory Management functionality uses /dev/shm on Linux for SGA and PGA management. The errors occur if either MEMORY_TARGET or MEMORY_MAX_TARGET is configured larger than the configured /dev/shm size, or if /dev/shm is mounted incorrectly.
Investigation
Checked if /dev/shm is mounted
#/cd dev/shm
#df -h .
Filesystem Size Used Avail Use% Mounted on
tmpfs 3.6G 1.6G 2.0G 45% /dev/shm
Yes its mounted correctly and allocated space to it is 3.5G
Checked MEMORY_TARGET or MEMORY_MAX_TARGET value
<initParam name="memory_max_target" value="2048" unit="MB" />
<initParam name="memory_target" value="1280" unit="MB" />
I am starting the instance with 2G of memory_max_target and it is still not starting.
Shitttttttttt...
I have one more database already running on this server. Looking to it I see 2GB is already allocated to it
To start the Instance I need minimum 4GM /dev/shm and currently I have only 3.5G.
Note: /dev/shm must be configured large enough to hold all the instances on the server
size of /dev/shm=sum of (MEMORY_MAX_TARGET of all instances)
Solutions
Solution1
Adjust the size of /dev/shm then only start the DB instance
#mount -t tmpfs shmfs -o size=4g /dev/shm
Modify the /etc/fstab to make the chages persistent across the reboot
Solution2
Disable AMM
Note:Check out the best practices at oracle.com to disable the AMM
Comments
Post a Comment