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. 剑指offer--day09

    1.1 题目:栈的压入.弹出序列:输入两个整数序列,第一个序列表示栈的压入顺序,请判断第二个序列是否可能为该栈的弹出顺序.假设压入栈的所有数字均不相等.例如序列1,2,3,4,5是某栈的压入顺序,序列 ...

  2. 应用安全 - PHPCMS - Joomla漏洞汇总

    Joomla 反序列化(版本低于3.4.5) CVE-2015-8562 RCE Date:October, 2019原理:https://blog.hacktivesecurity.com/inde ...

  3. char数组初始化

    初始化 char str[10]="Hello"; char str[10]={'H','e','l','l','o','\0'}; char str[10]={'H'}; cha ...

  4. gitee.ZC_blog快速方案

    1. 1.1.改 hexo的配置文件中 gitee的路径 复制URL,到hexo的配置文件_config.yml …… deploy: type: git # type为git repo: https ...

  5. Navicat Premium 12.1.20.0安装与激活

    一.Navicat Premium 12下载 链接: https://pan.baidu.com/s/1GgNbCPGahN-Z91f4dnQkBQ 提取码: 3q8f 复制这段内容后打开百度网盘手机 ...

  6. [BZOJ2588]Count on a tree(LCA+主席树)

    题面 给定一棵N个节点的树,每个点有一个权值,对于M个询问(u,v,k),你需要回答u xor lastans和v这两个节点间第K小的点权.其中lastans是上一个询问的答案,初始为0,即第一个询问 ...

  7. ES6判断当前页面是否微信浏览器中打开

    1.使用jq判断是否用微信浏览器打开页面 var is_weixin = (function(){return navigator.userAgent.toLowerCase().indexOf('m ...

  8. python学习第五十天shutil模块的用法

    什么shutil模块,就是对高级的文件,文件夹,压缩包进行处理的模块,下面简单讲述其用法. 文件和文件夹的操作 拷贝文件内容 import shutil shutil.copyfileobj(open ...

  9. ReactiveObjC(RAC)的使用汇总

    RAC 指的就是 RactiveCocoa ,是 Github 的一个开源框架,能够帮我们提供大量方便的事件处理方案,让我们更简单粗暴地去处理事件,现在分为 ReactiveObjC 和 Reacti ...

  10. 读取FTP上的excel文件,并写入数据库

    今天遇到一些问题,需要从ftp上读取一些excel文件,并需要将excel中的数据写入到数据库,这样就可以通过管理页面查看这些数据. 我将相关工作分为三步,1.从ftp上读取相关文件,并将excel文 ...