ORA-609:疑似MEMORY_TARGET设置过大导致的宕机
来源:互联网 发布:淘宝购物返利微信群 编辑:程序博客网 时间:2024/05/18 03:00
ORA-609:疑似MEMORY_TARGET设置过大导致的宕机
现象:
客户的数据库最近发生好几次忽然宕机事件,查看alert日志:
Thu Oct 10 10:47:50 2013
ORA-609 : opiodr aborting process unknown ospid (834_47932399713424)
Thu Oct 10 10:47:50 2013
ORA-609 : opiodr aborting process unknown ospid (740_47613956914320)
Thu Oct 10 10:47:53 2013
ORA-609 : opiodr aborting process unknown ospid (755_47556191542416)
Thu Oct 10 10:47:53 2013
ORA-609 : opiodr aborting process unknown ospid (761_47545590688912)
Thu Oct 10 10:47:54 2013
ORA-609 : opiodr aborting process unknown ospid (859_47653507185808)
Thu Oct 10 10:47:58 2013
ORA-609 : opiodr aborting process unknown ospid (904_47121713061008)
Thu Oct 10 10:48:08 2013
ORA-609 : opiodr aborting process unknown ospid (918_47924605709456)
Thu Oct 10 10:48:16 2013
ORA-609 : opiodr aborting process unknown ospid (965_46996288695440)
Thu Oct 10 10:48:16 2013
ORA-609 : opiodr aborting process unknown ospid (984_47202090368144)
Thu Oct 10 10:49:06 2013
ORA-609 : opiodr aborting process unknown ospid (1103_47027913133200)
Thu Oct 10 10:49:08 2013
Thu Oct 10 10:49:08 2013
ORA-609 : opiodr aborting process unknown ospid (1064_47991325715600)
ORA-609 : opiodr aborting process unknown ospid (1150_47885260754064)
Thu Oct 10 10:50:02 2013
Process W000 died, see its trace file
Thu Oct 10 10:50:17 2013
Process W001 died, see its trace file
Thu Oct 10 10:54:19 2013
Process W000 died, see its trace file
Process W000 died, see its trace file
Process W000 died, see its trace file
Thu Oct 10 10:54:31 2013
Process W000 died, see its trace file
Process W000 died, see its trace file
Process W000 died, see its trace file
Thu Oct 10 10:54:43 2013
Process W000 died, see its trace file
Process W000 died, see its trace file
Process W000 died, see its trace file
Thu Oct 10 10:54:55 2013
Process W000 died, see its trace file
Process W000 died, see its trace file
Process W000 died, see its trace file
Thu Oct 10 10:55:07 2013
Process W000 died, see its trace file
Process W000 died, see its trace file
Process W000 died, see its trace file
Thu Oct 10 10:55:19 2013
Process W000 died, see its trace file
Process W000 died, see its trace file
Process W000 died, see its trace file
Thu Oct 10 10:55:31 2013
Process W000 died, see its trace file
Process W000 died, see its trace file
Process W000 died, see its trace file
Thu Oct 10 11:02:06 2013
Thread 2 advanced to log sequence 18269
Current log# 15 seq# 18269 mem# 0: +UNIDG/uni/onlinelog/group_15.295.796513629
Thu Oct 10 11:02:08 2013
SUCCESS: diskgroup UNIDG was mounted
Thu Oct 10 11:02:18 2013
SUCCESS: diskgroup UNIDG was dismounted
Thu Oct 10 11:03:40 2013
Process m001 died, see its trace file
Thu Oct 10 11:04:23 2013
Process m001 died, see its trace file
分析:
查看启动时的参数设置,发现客户的系统启用了自动内存管理:
memory_target = 21G <-------------Automatic Memory Management feature is used.
free -g查看内存为23G
怀疑主机资源耗尽导致系统宕机,建议客户memory_target设置为16-18G。
调小memort_target之后,之前的自动宕机现象消失。
附:分析了如下日志。
$CRS_HOME/log/<nodename>/*.log
$CRS_HOME/log/<nodename>/crsd/*.log
$CRS_HOME/log/<nodename>/cssd/*.log
/etc/oracle/oprocd/*.log.* or /var/opt/oracle/oprocd/*.log.*
现象:
客户的数据库最近发生好几次忽然宕机事件,查看alert日志:
Thu Oct 10 10:47:50 2013
ORA-609 : opiodr aborting process unknown ospid (834_47932399713424)
Thu Oct 10 10:47:50 2013
ORA-609 : opiodr aborting process unknown ospid (740_47613956914320)
Thu Oct 10 10:47:53 2013
ORA-609 : opiodr aborting process unknown ospid (755_47556191542416)
Thu Oct 10 10:47:53 2013
ORA-609 : opiodr aborting process unknown ospid (761_47545590688912)
Thu Oct 10 10:47:54 2013
ORA-609 : opiodr aborting process unknown ospid (859_47653507185808)
Thu Oct 10 10:47:58 2013
ORA-609 : opiodr aborting process unknown ospid (904_47121713061008)
Thu Oct 10 10:48:08 2013
ORA-609 : opiodr aborting process unknown ospid (918_47924605709456)
Thu Oct 10 10:48:16 2013
ORA-609 : opiodr aborting process unknown ospid (965_46996288695440)
Thu Oct 10 10:48:16 2013
ORA-609 : opiodr aborting process unknown ospid (984_47202090368144)
Thu Oct 10 10:49:06 2013
ORA-609 : opiodr aborting process unknown ospid (1103_47027913133200)
Thu Oct 10 10:49:08 2013
Thu Oct 10 10:49:08 2013
ORA-609 : opiodr aborting process unknown ospid (1064_47991325715600)
ORA-609 : opiodr aborting process unknown ospid (1150_47885260754064)
Thu Oct 10 10:50:02 2013
Process W000 died, see its trace file
Thu Oct 10 10:50:17 2013
Process W001 died, see its trace file
Thu Oct 10 10:54:19 2013
Process W000 died, see its trace file
Process W000 died, see its trace file
Process W000 died, see its trace file
Thu Oct 10 10:54:31 2013
Process W000 died, see its trace file
Process W000 died, see its trace file
Process W000 died, see its trace file
Thu Oct 10 10:54:43 2013
Process W000 died, see its trace file
Process W000 died, see its trace file
Process W000 died, see its trace file
Thu Oct 10 10:54:55 2013
Process W000 died, see its trace file
Process W000 died, see its trace file
Process W000 died, see its trace file
Thu Oct 10 10:55:07 2013
Process W000 died, see its trace file
Process W000 died, see its trace file
Process W000 died, see its trace file
Thu Oct 10 10:55:19 2013
Process W000 died, see its trace file
Process W000 died, see its trace file
Process W000 died, see its trace file
Thu Oct 10 10:55:31 2013
Process W000 died, see its trace file
Process W000 died, see its trace file
Process W000 died, see its trace file
Thu Oct 10 11:02:06 2013
Thread 2 advanced to log sequence 18269
Current log# 15 seq# 18269 mem# 0: +UNIDG/uni/onlinelog/group_15.295.796513629
Thu Oct 10 11:02:08 2013
SUCCESS: diskgroup UNIDG was mounted
Thu Oct 10 11:02:18 2013
SUCCESS: diskgroup UNIDG was dismounted
Thu Oct 10 11:03:40 2013
Process m001 died, see its trace file
Thu Oct 10 11:04:23 2013
Process m001 died, see its trace file
分析:
查看启动时的参数设置,发现客户的系统启用了自动内存管理:
memory_target = 21G <-------------Automatic Memory Management feature is used.
free -g查看内存为23G
怀疑主机资源耗尽导致系统宕机,建议客户memory_target设置为16-18G。
调小memort_target之后,之前的自动宕机现象消失。
附:分析了如下日志。
$CRS_HOME/log/<nodename>/*.log
$CRS_HOME/log/<nodename>/crsd/*.log
$CRS_HOME/log/<nodename>/cssd/*.log
/etc/oracle/oprocd/*.log.* or /var/opt/oracle/oprocd/*.log.*
1 0
- ORA-609:疑似MEMORY_TARGET设置过大导致的宕机
- sga_max_size设置过大导致ORALCE无法启动ORA-27100解决办法
- 解决内存设置过大导致实例无法启动ORA-27100
- memory_target 设置太小,导致无法启动实例的解决办法
- ORA-00845 memory_target比shmfs大导致数据库起不来
- TCP连接数过大导致down机的原因分析
- AIX系统的非计算内存最大值设置过大导致Oracle数据库有些不能连接上
- Oracle11g新引入的memory_target以及ORA-00845: MEMORY_TARGET not supported on this system的产生
- ORA-00845: MEMORY_TARGET not supported on thi s system导致rac安装失败
- ora-00845 MEMORY_TARGET not supported on this system 的问题
- ORA-00845 MEMORY_TARGET not supported on this system 的解决
- OracleParameter设置空值时,导致ORA-01008错误的解决
- oracle数据量过大导致死掉的解决方法
- elasticsearch字段过大导致的内存问题
- ORA-27300,ORA-27301,ORA-27302,ORA-27303导致实例宕的问题分析
- oracle连接数设置过大,导致oracle启动不了
- Oracle 最大连接数设置过大导致服务无法启动
- ORA-00604和ORA-04031导致数据库实例宕机
- hdu1054 二分图水题
- 汇编实现的 memcpy memset strstr
- kmp和扩展kmp原理
- effective C++: 8.定制new和delete
- [web前端笔试] AJAX笔试面试题汇总
- ORA-609:疑似MEMORY_TARGET设置过大导致的宕机
- Metapost—Hello World
- 复杂的表单服务器端验证
- 未定义行为
- jQuery对Ajax的封装:load(),get(),post()
- 数论基本理论的整理
- UFLDL Tutorial_Linear Decoders with Autoencoders
- 手游团队的六个死因 取舍Unity技术引争议
- jQuery三级联动