打开APP
userphoto
未登录

开通VIP,畅享免费电子书等14项超值服

开通VIP
ORA-600(5351)错误

ORA-600(5351)错误

在告警日志中发现了ORA-600(5351)错误,同时出现大量的There are 3 memory allocation errors for object-level stat错误。
详细的错误信息为:

Tue Jun 22 12:00:09 2010Thread 1 advanced TO log SEQUENCE 1522CURRENT log# 3 seq# 1522 mem# 0: /dev/rredo03There are 6 memory allocation errors FOR object-level statIN the LAST 15 minutesThere are 4 memory allocation errors FOR object-level statIN the LAST 15 minutesThere are 3 memory allocation errors FOR object-level statIN the LAST 15 minutesThere are 26 memory allocation errors FOR object-level statIN the LAST 15 minutesThere are 9 memory allocation errors FOR object-level statIN the LAST 15 minutesThere are 3 memory allocation errors FOR object-level statIN the LAST 15 minutesThere are 2 memory allocation errors FOR object-level statIN the LAST 15 minutesThere are 3 memory allocation errors FOR object-level statIN the LAST 15 minutesThere are 3 memory allocation errors FOR object-level statIN the LAST 15 minutesTue Jun 22 16:14:21 2010Errors IN file /oracle/admin/ruledb/udump/ruledb_ora_233726.trc:ORA-00600: internal error code, arguments: [5351], [4365070], [57664], [], [], [], [], []Tue Jun 22 16:14:44 2010Doing block recovery FOR file 201 block 170765No block recovery was neededThere are 658 memory allocation errors FOR object-level statIN the LAST 15 minutesThere are 362 memory allocation errors FOR object-level statIN the LAST 15 minutesThere are 16 memory allocation errors FOR object-level statIN the LAST 15 minutesThere are 4 memory allocation errors FOR object-level statIN the LAST 15 minutesTue Jun 22 17:43:01 2010ALTER SYSTEM SET db_cache_size='2100M' SCOPE=BOTH;Tue Jun 22 17:43:17 2010ALTER SYSTEM SET shared_pool_size='712M' SCOPE=BOTH;

在MOS中查询了一下ORA-600(5351),只差到一篇文章,基本上和当前的问题没有什么关系。不过除了这个明显的ORA-600错误外,大量的memory allocation errors for object-level错误信息也值得关注,查询发现问题和数据库共享池使用有关,如果频繁出现这个错误,最终可能导致ORA-4031错误。
Oracle在文档Memory Allocation Errors For Object-Level Stat Appearing in the Alert Log File [ID 757895.1]中描述了这个问题,而给出的解决方法是增大共享池或者设置隐含参数_OBJECT_STATISTICS=FALSE。
当前的数据库shared_pool的设置是500M左右,调整到712M后,无论是memory allocation errors还是ORA-600(5351)错误,都没有再重现。

本站仅提供存储服务,所有内容均由用户发布,如发现有害或侵权内容,请点击举报
打开APP,阅读全文并永久保存 查看更多类似文章
猜你喜欢
类似文章
ORA
案例:ORA-04031 12.1.0.2 on exadata x7
ORACLE 事件代码
DLL的灾难
high
Building your own memory manager for C/C++ projects – IBM Developer
更多类似文章 >>
生活服务
热点新闻
分享 收藏 导长图 关注 下载文章
绑定账号成功
后续可登录账号畅享VIP特权!
如果VIP功能使用有故障,
可点击这里联系客服!

联系客服