/dev/shm过小导致ORA-00845错误解决方法
2012-06-20 17:26
369 查看
The workaround, if you encounter the ORA-00845 error, is to increase the /dev/shm
mountpoint size.
For example:
# mount -t tmpfs shmfs -o size=7g /dev/shm
To make this change persistent across system restarts, add an entry in /etc/fstab
similar to the following:
shmfs /dev/shm tmpfs size=7g 0
Starting with Oracle Database 11g, the Automatic Memory Management feature
requires more shared memory (/dev/shm)and file descriptors. The size of the shared
memory must be at least the greater of the MEMORY_MAX_TARGET and MEMORY_
TARGET parameters for each Oracle instance on the computer. If the MEMORY_MAX_
TARGET parameter or the MEMORY_TARGET parameter is set to a non-zero value, and
an incorrect size is assigned to the shared memory, it results in an ORA-00845 error at
startup. On Linux systems, if the operating system /dev/shm mount size is too small
for the Oracle system global area (SGA) and program global area (PGA), it will result
in an ORA-00845 error.
The number of file descriptors for each Oracle instance must be at least
512*PROCESSES. The limit of descriptors for each process must be at least 512. If file
descriptors are not sized correctly, you will see an ORA-27123 error from various
Oracle processes and potentially Linux Error EMFILE (Too many open
files)in non-Oracle processes.
To determine the amount of shared
mountpoint size.
For example:
# mount -t tmpfs shmfs -o size=7g /dev/shm
To make this change persistent across system restarts, add an entry in /etc/fstab
similar to the following:
shmfs /dev/shm tmpfs size=7g 0
Starting with Oracle Database 11g, the Automatic Memory Management feature
requires more shared memory (/dev/shm)and file descriptors. The size of the shared
memory must be at least the greater of the MEMORY_MAX_TARGET and MEMORY_
TARGET parameters for each Oracle instance on the computer. If the MEMORY_MAX_
TARGET parameter or the MEMORY_TARGET parameter is set to a non-zero value, and
an incorrect size is assigned to the shared memory, it results in an ORA-00845 error at
startup. On Linux systems, if the operating system /dev/shm mount size is too small
for the Oracle system global area (SGA) and program global area (PGA), it will result
in an ORA-00845 error.
The number of file descriptors for each Oracle instance must be at least
512*PROCESSES. The limit of descriptors for each process must be at least 512. If file
descriptors are not sized correctly, you will see an ORA-27123 error from various
Oracle processes and potentially Linux Error EMFILE (Too many open
files)in non-Oracle processes.
To determine the amount of shared
相关文章推荐
- 数据库启动时报ORA-00845错误解决方法
- 【问题记录】数据库打不开 报ORA-00845错误 /dev/shm设置过小
- CentOS 下修改/dev/shm 大小解决ORA-00845
- ORA-00845: MEMORY_TARGET not supported on this system 错误解决方法!
- 权限问题导致Nginx 403 Forbidden错误的解决方法
- ORA-04091错误原因与解决方法
- oracle连接中出现错误ORA-12541,ORA-12514,ORA-01017的解决方法
- ORA-01078: 和 LRM-00109 :错误 解决方法
- 临时表应用中出现的ora-14450错误的简单解决方法
- 错误:ORA-28002: the password will expire within 7 days 解决方法
- ArcSDE复制数据时出现ORA-00955名称已由现有对象使用错误的解决方法
- 使用EhCache时,用户按住F5刷新页面,导致socket write error错误的解决方法
- Oracle 11.2.0.3 ORA-12012 ORA-29280 ORA-06512 错误 解决方法
- Oracle ORA-12541:TNS:no listener错误解决方法 (转)
- 物理删除oracle数据文件(DBF文件)导致数据库ORA-01033的解决方法
- 高级复制添加主体站点的时候碰到ORA-23375错误的解决方法
- ORA-00911无效字符错误解决方法
- 常见oracle错误代码ORA-xxxxx及其解决方法(持续更行中)
- nginx反向代理tomcat应用,struts2网站程序redirect时导致请求地址错误的解决方法
- RMAN ORA-19504、ORA-27038错误解决方法