http://blog.itpub.net/23135684/viewspace-1203447/

Mon Sep 11 08:56:10 2017
Errors in file /oracle/db/diag/rdbms/orcl/orcl1/trace/orcl1_o000_39574.trc (incident=24529):
ORA-04031: unable to allocate 12312 bytes of shared memory ("shared pool","unknown object","KKSSP^2543","kglseshtTable")
Incident details in: /oracle/db/diag/rdbms/orcl/orcl1/incident/incdir_24529/orcl1_o000_39574_i24529.trc
Mon Sep 11 08:56:11 2017
Dumping diagnostic data in directory=[cdmp_20170911085611], requested by (instance=1, osid=39574 (O000)), summary=[incident=24529].
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Mon Sep 11 08:56:11 2017
Thread 1 advanced to log sequence 3235 (LGWR switch)
Current log# 1 seq# 3235 mem# 0: +DATA03/orcl/onlinelog/group_1.275.932424707
Current log# 1 seq# 3235 mem# 1: +FR03/orcl/onlinelog/group_1.1125.932424707
Mon Sep 11 08:56:12 2017
Sweep [inc][24529]: completed
Sweep [inc2][24529]: completed
Mon Sep 11 08:56:12 2017
Errors in file /oracle/db/diag/rdbms/orcl/orcl1/trace/orcl1_arc2_107446.trc (incident=24457):
ORA-04031: unable to allocate 12312 bytes of shared memory ("shared pool","unknown object","KKSSP^2605","kglseshtTable")
Incident details in: /oracle/db/diag/rdbms/orcl/orcl1/incident/incdir_24457/orcl1_arc2_107446_i24457.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
WARNING: ASM communication error: op 0 state 0x0 (15055)
ERROR: direct connection failure with ASM
Dumping diagnostic data in directory=[cdmp_20170911085613], requested by (instance=1, osid=107446 (ARC2)), summary=[incident=24457].
Mon Sep 11 08:56:16 2017
Errors in file /oracle/db/diag/rdbms/orcl/orcl1/trace/orcl1_o000_39601.trc (incident=24530):
ORA-04031: unable to allocate 12312 bytes of shared memory ("shared pool","unknown object","KKSSP^2543","kglseshtTable")
Incident details in: /oracle/db/diag/rdbms/orcl/orcl1/incident/incdir_24530/orcl1_o000_39601_i24530.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Dumping diagnostic data in directory=[cdmp_20170911085617], requested by (instance=1, osid=39601 (O000)), summary=[incident=24530].
Errors in file /oracle/db/diag/rdbms/orcl/orcl1/trace/orcl1_arc2_107446.trc (incident=24458):
ORA-04031: unable to allocate 12312 bytes of shared memory ("shared pool","unknown object","KKSSP^2605","kglseshtTable")
ORA-15055: SM ʵORA-04031: unable to allocate 12312 bytes of shared memory ("shared pool","unknown object","KKSSP^2605","kglseshtTable")
Incident details in: /oracle/db/diag/rdbms/orcl/orcl1/incident/incdir_24458/orcl1_arc2_107446_i24458.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
WARNING: ASM communication error: op 0 state 0x0 (15055)
ERROR: direct connection failure with ASM
NOTE: Deferred communication with ASM instance
Errors in file /oracle/db/diag/rdbms/orcl/orcl1/trace/orcl1_arc2_107446.trc:
ORA-15055: SM ʵORA-04031: unable to allocate 12312 bytes of shared memory ("shared pool","unknown object","KKSSP^2605","kglseshtTable")
ORA-15055: SM ʵORA-04031: unable to allocate 12312 bytes of shared memory ("shared pool","unknown object","KKSSP^2605","kglseshtTable")
NOTE: deferred map free for map id 8074
Dumping diagnostic data in directory=[cdmp_20170911085619], requested by (instance=1, osid=107446 (ARC2)), summary=[incident=24458].
Mon Sep 11 08:56:23 2017
Errors in file /oracle/db/diag/rdbms/orcl/orcl1/trace/orcl1_arc3_107448.trc (incident=24465):
ORA-04031: unable to allocate 12312 bytes of shared memory ("shared pool","unknown object","KKSSP^2543","kglseshtTable")
Incident details in: /oracle/db/diag/rdbms/orcl/orcl1/incident/incdir_24465/orcl1_arc3_107448_i24465.trc
Mon Sep 11 08:56:23 2017
Dumping diagnostic data in directory=[cdmp_20170911085623], requested by (instance=1, osid=107448 (ARC3)), summary=[incident=24465].
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
WARNING: ASM communication error: op 0 state 0x0 (15055)
ERROR: direct connection failure with ASM
Mon Sep 11 08:56:24 2017
Errors in file /oracle/db/diag/rdbms/orcl/orcl1/trace/orcl1_arc2_107446.trc (incident=24459):
ORA-04031: unable to allocate 12312 bytes of shared memory ("shared pool","unknown object","KKSSP^2605","kglseshtTable")
ORA-00312: 2 1: '+DATA03/orcl/onlinelog/group_2.276.932424709'
ORA-17503: ksfdopn: 2 δDATA03/orcl/onlinelog/group_2.276.932424709
ORA-15055: SM ʵORA-04031: unable to allocate 12312 bytes of shared memory ("shared pool","unknown object","KKSSP^2605","kglseshtTable")
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
WARNING: ASM communication error: op 0 state 0x0 (15055)
ERROR: direct connection failure with ASM
Mon Sep 11 08:56:28 2017
WARNING: ASM communication error: op 17 state 0x40 (4031)
ERROR: slave communication error with ASM
Errors in file /oracle/db/diag/rdbms/orcl/orcl1/trace/orcl1_arc0_107442.trc (incident=24441):
ORA-04031: unable to allocate 12312 bytes of shared memory ("shared pool","unknown object","KKSSP^2667","kglseshtTable")
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Errors in file /oracle/db/diag/rdbms/orcl/orcl1/trace/orcl1_arc3_107448.trc (incident=24466):
ORA-04031: unable to allocate 12312 bytes of shared memory ("shared pool","unknown object","KKSSP^2543","kglseshtTable")
ORA-15055: SM ʵORA-04031: unable to allocate 12312 bytes of shared memory ("shared pool","unknown object","KKSSP^2543","kglseshtTable")
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
WARNING: ASM communication error: op 0 state 0x0 (15055)
ERROR: direct connection failure with ASM
NOTE: Deferred communication with ASM instance
Errors in file /oracle/db/diag/rdbms/orcl/orcl1/trace/orcl1_arc3_107448.trc:
ORA-15055: SM ʵORA-04031: unable to allocate 12312 bytes of shared memory ("shared pool","unknown object","KKSSP^2543","kglseshtTable")
ORA-15055: SM ʵORA-04031: unable to allocate 12312 bytes of shared memory ("shared pool","unknown object","KKSSP^2543","kglseshtTable")
NOTE: deferred map free for map id 8075

根据Oracle的推荐,在11g中使用MEMORY_TARGET参数的话,那么MEMORY_TARGET至少应该分配256M以上,而且随着DISK GROUP的容量的增长,SHARED_POOL所需要的空间也随着增加。因此对于磁盘组空间比较大的ASM实例而言,采用默认参数作为MEMORY_TARGET显然是不够的。

对于当前环境,只需要简单的调整ASM实例的MEMORY_TARGET参数,将其扩大到500M以上,就可以避免该错误的产生。

ora4031的更多相关文章

  1. Gathering Initial Troubleshooting Information for Analysis of ORA-4031 Errors on the Shared Pool

    In this Document   Purpose   Troubleshooting Steps   References APPLIES TO: Oracle Database - Enterp ...

  2. ORA-4031 错误故障排除与诊断[视频] (Doc ID 2016002.1)

    Copyright (c) 2019, Oracle. All rights reserved. Oracle Confidential.     ORA-4031 错误故障排除与诊断[视频] (Do ...

  3. ORA-4031 During Startup Nomount using RMAN without parameter file (PFILE) (Doc ID 1176443.1)

    ORA-4031 During Startup Nomount using RMAN without parameter file (PFILE) (Doc ID 1176443.1) APPLIES ...

  4. ora-4031错误

    SQL语句共享的不好,即没有使用绑定变量 来一个SQL语句,在Shared Pool中分配一块内存……再来一个,再分配... 最后共享内存分配完了,有可能都在5k-8K 之间,如果突然又来一个SQL语 ...

  5. ORA-4031错误 解决方法

    遇到ORA-4031错误时.你的心里会不会发怵?ORA-4031非常easy导致数据库出现异常崩溃,当Oracle的核心进程无法获得共享池内存时.它们会把数据库异常宕掉.当然,ORA-4031就像黄灯 ...

  6. 【ORA】ORA-4031错误分析和解决办法

    1. ORA-4031错误的原因,一般是大量的hard parse导致了shared pool中的free list中产生大量的内存小碎片,当一个需要很大内存来进行hard parse的sql语句到来 ...

  7. ORA-4031诊断分析

    1.Environment11.2.0.4 RAC 2.Symptomsrac的一节点alert日志一直刷ORA-4031报错,提示shared pool不足,二节点并没有此报错 Sat Oct 09 ...

  8. [转载】——故障排除:Shared Pool优化和Library Cache Latch冲突优化 (文档 ID 1523934.1)

    原文链接:https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrlstate=23w4l35u5_4&id=152393 ...

  9. oracle内存粒度

    一,什么是内存粒度? When a database instance starts up, the amount of memory allocated is determined by the a ...

随机推荐

  1. 转 jvisualvm 工具使用 https://www.cnblogs.com/kongzhongqijing/articles/3625340.html

    VisualVM 是Netbeans的profile子项目,已在JDK6.0 update 7 中自带(java启动时不需要特定参数,监控工具在bin/jvisualvm.exe). https:// ...

  2. Vue.js状态管理模式 Vuex

    vuex 是一个专为 Vue.js 应用程序开发的状态管理模式.它采用集中式存储管理应用的所有组件的状态,并以相应的规则保证状态以一种可预测的方式发生变化. 安装.使用 vuex 首先我们在 vue. ...

  3. 【CF321E】+【bzoj5311】

    决策单调性 + WQS二分 贴个代码先... //by Judge #pragma GCC optimize("Ofast") #include<bits/stdc++.h& ...

  4. git把本地代码上传(更新)到github上

    # 初始化目录为本地仓库 git init # 添加所有文件到暂存去 git add . # 提交所有文件 git commit -m "init" # 添加远程仓库地址 git ...

  5. Log4Net 之将日志记录到数据库的后台实现 (二)

    原文:Log4Net 之将日志记录到数据库的后台实现 (二) 大家下午好,昨天讲了配置,今天我们讲讲后台实现,在完成了后台实现后,我们才能真正意义上的解决把自定义属性字段值录入到数据库中. 在开写之前 ...

  6. svn登录问题

    转载自: https://www.cnblogs.com/WQX-work24/p/9790260.html 版权归该作者所有.

  7. 2018-8-10-xaml-添加-region

    title author date CreateTime categories xaml 添加 region lindexi 2018-08-10 19:16:51 +0800 2018-03-15 ...

  8. centos下通过conda安装pytorch

    一.安装anaconda anaconda安装简单,只要确定自己的系统即可,具体安装请参考这里 二.确定自己的系统版本 我的是centos cat /etc/redhat-release 查看linu ...

  9. 二、搭建Swagger

    1.新建.netCore webapi项目 2.安装swagger ,通过 Package Manager 控制台:Install-Package Swashbuckle.AspNetCore 3.修 ...

  10. MYSQL学习笔记——常用语句

    1.检索数据 1.1.检索单个列:SELECT prod_name FROM products; 1.2.检索多个列:SELECT prod_id, prod_name, prod_price FRO ...