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. [Python3 练习] 007 简单的猜数字小游戏

    题目:简单的猜数字小游戏 (1) 描述 程序随机生成一个数字,玩家用键盘输入所猜数字,在规定次数内猜对为胜. (2) 要求 程序随机生成一个 1 到 100 的自然数 有 7 次机会去猜 机会用尽之前 ...

  2. ESP32、GPRS A9测试

    测试内容: 1.A9作为客户端,在服务器主动断开连接或异常断开的时候,使用网络连接状态查询接口,能否获得准确的网络连接状态. 结果: TCP: A9开多连接时,成功连接TCP服务器后,发送查询语句AT ...

  3. hibernate的get方法和load方法区别

    读者需注意:Hibernate版本不同,运行机制不太一样,以下是hibernate3.x作为讲解 get方法: Hibernate会确认一下该id对应的数据是否存在,首先在session缓存中查找,然 ...

  4. POJ-2352.Stats(树状数组简单应用)

    Stars Time Limit: 1000MS   Memory Limit: 65536K Total Submissions: 58255   Accepted: 24860 Descripti ...

  5. Appium+Python之元素定位和操作

    一.常用识别元素的工具 uiautomatorviewer:Android SDK自带的一个工具,在tools目录下     二.元素定位   1.格式:find_element_by_定位方式(va ...

  6. sde自动备份到文件gdb

    本方法原理是使用python(以下简称py)调用arcmap的gp,在上再用bat调用py的方式实现.优点是能应用于所有数据库类型(包括pg,oracle等)的sde库 环境:arcmap 10.4, ...

  7. Hibernate Validation与Spring整合各注解的用法Demo

    转自:https://www.aliyun.com/jiaocheng/1315650.html <dependency> <groupId>org.hibernate< ...

  8. ffmpeg的中文文档

    1. 概要 ffmpeg [global_options] {[input_file_options] -i INPUT_FILE} ... {[output_file_options] OUTPUT ...

  9. CentOS7搭建Hadoop2.8.0集群及基础操作与测试

    环境说明 示例环境 主机名 IP 角色 系统版本 数据目录 Hadoop版本 master 192.168.174.200 nameNode CentOS Linux release 7.4.1708 ...

  10. Python + logging输出到屏幕,将log日志写入到文件

    logging提供了一组便利的函数,用来做简单的日志.它们是 debug(). info(). warning(). error() 和 critical(). logging函数根据它们用来跟踪的事 ...