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. C++[Tarjan求点双连通分量，割点][HNOI2012]矿场搭建

    最近在学图论相关的内容,阅读这篇博客的前提是你已经基本了解了Tarjan求点双. 由割点的定义(删去这个点就可使这个图不连通)我们可以知道,坍塌的挖煤点只有在割点上才会使这个图不连通,而除了割点的其他 ...

  2. pandas 入门（2）

    from pandas import Series, DataFrame, Index import numpy as np from numpy import nan as NA obj = Ser ...

  3. CentOS7 redhat7 linux系统1分钟安装Zabbix web 监控 服务器

    一．准备工作OS:centos7.4Zabbix version:3.4.6(2018/1/15日上线的新版本)Database:MariaDB关闭防火墙:systemctl stop firewal ...

  4. JAVA Error:The project was not built since its build path is incomplete. Cannot find the class file for java.util.Map$Entry.....

    今天,学习Netty框架时遇到error:Description Resource Path Location Type:The project was not built since its bui ...

  5. HDFS-HA高可用工作机制

    1.HDFS-HA概述 1)所谓HA(high available),即高可用(7*24小时不中断服务). 2)实现高可用最关键的策略是消除单点故障.HA严格来说应该分成各个组件的HA机制:HDFS的 ...

  6. SQL查询结果增加序列号

    SQL查询记录中增加序列号 根据学生成绩在查询结果中增加排名字段: 1.SELECT ROW_NUMBER() OVER (ORDER BY SCORE ASC) AS RANK,NAME,SCORE ...

  7. [2019CCPC网络赛][hdu6704]K-th occurrence(后缀数组&&主席树)

    题目链接:http://acm.hdu.edu.cn/showproblem.php?pid=6704 题意为查询子串s[l...r]第k次出现的位置. 写完博客后5分钟的更新 写完博客才发现这份代码 ...

  8. centos解决Could not find a version that satisfies the requirement pip3 (from versions: none)及No matching distribution found for pip3问题

    python环境:python 3.8 报错信息: WARNING: pip is configured with locations that require TLS/SSL, however th ...

  9. (一)WebPack4.0 从零开始

    一:WebPack基础知识 (1):webpack的定义 webpack官网给出的定义是:webpack 是一个现代 JavaScript 应用程序的静态模块打包器(module bundler). ...

  10. 利用docker创建包含需要python包的python镜像

    一.拉取python镜像 需要先安装docker,这里读者自行搜索docker的安装过程,下面我们拉取python镜像:以3.7.4为例 docker pull python:3.7.4 二.进入容器 ...