19c RAC 告警日志报错 ORA 7445 [pevm_icd_call_common()+225]
问题现象:
在一套2节点的19c RAC 环境下,节点2 alert告警 ORA 7445,且频度固定为每分钟报一次;期间有重启实例,但故障依旧:
===========================================================
2023-02-07T12:51:04.359849+08:00
PL/SQL package SYS.DBMS_RCVMAN version 19.16.00.00 is too new
Oracle must be upgraded to version 08.00.04.00 to work with this package
2023-02-07T12:51:05.274685+08:00
Exception [type: SIGSEGV, SI_KERNEL(general_protection)] [ADDR:0x0] [PC:0x1289FCA1, pevm_icd_call_common()+225] [flags: 0x0, count: 1]
2023-02-07T12:51:05.325530+08:00
PL/SQL package SYS.DBMS_RCVMAN version 19.16.00.00 is too new
Oracle must be upgraded to version 08.00.04.00 to work with this package
Errors in file /u01/app/oracle/diag/rdbms/demorac/jydb2/trace/jydb2_m002_3146.trc (incident=185342) (PDBNAME=CDB$ROOT):
ORA-07445: exception encountered: core dump [pevm_icd_call_common()+225] [SIGSEGV] [ADDR:0x0] [PC:0x1289FCA1] [SI_KERNEL(general_protection)] []
Incident details in: /u01/app/oracle/diag/rdbms/demorac/jydb2/incident/incdir_185342/jydb2_m002_3146_i185342.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
2023-02-07T12:51:06.167145+08:00
db_recovery_file_dest_size of 15360 MB is 0.13% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
2023-02-07T12:51:08.737355+08:00
Dumping diagnostic data in directory=[cdmp_20230207125108], requested by (instance=2, osid=3146 (M002)), summary=[incident=185342].
直接通过ORA 7445后面的参数来定位,并未找到匹配的问题,进一步分析对应的trc文件:
[oracle@db01rac2 trace]$ vi /u01/app/oracle/diag/rdbms/demorac/jydb2/incident/incdir_185342/jydb2_m002_3146_i185342.trc
[oracle@db01rac2 trace]$
61 ----- Current SQL Statement for this session (sql_id=fhf8upax5cxsz) -----
62 BEGIN sys.dbms_auto_report_internal.i_save_report (:rep_ref, :snap_id, :pr_class, :rep_id, :suc); END;
发现在62行的位置可以看到对应的Current SQL,这是一个关键信息,通过这个sys.dbms_auto_report_internal.i_save_report(:rep_ref, :snap_id, :pr_class,:rep_id, :suc); END;
关键信息进一步匹配MOS:
- ORA-7445[PEVM_ICD_CALL_COMMON()] While Patching With a 19c DBRU (Doc ID 2779237.1)
可以认定是同类问题,是bug,但是目前尚未解决,但可以通过隐藏参数_report_capture_cycle_time
来禁用 Automatic Report Flush 这个特性:
Disable the Automatic Report Flush by setting the following hidden parameter:
SQL> alter system set "_report_capture_cycle_time"=0; /* Default is 60 seconds */
Note: There is no negative impact in setting the above parameter as this setting only disables the automatic report capturing feature introduced in 12c. It does not disable the original SQL monitoring framework. SQL monitoring can be used without any issues with this setting enabled.
这是个比较冷门的特性,可以放心禁用,禁用该特性并不会影响SQL Monitor本身。
禁用之后再去观察alert告警,发现在设置参数之后,alert已经不再每分钟抛出相关ORA 7445的错误:
2023-02-07T13:00:23.099438+08:00
Exception [type: SIGSEGV, SI_KERNEL(general_protection)] [ADDR:0x0] [PC:0x1289FCA1, pevm_icd_call_common()+225] [flags: 0x0, count: 1]
Errors in file /u01/app/oracle/diag/rdbms/demorac/jydb2/trace/jydb2_m001_4635.trc (incident=185214) (PDBNAME=CDB$ROOT):
ORA-07445: exception encountered: core dump [pevm_icd_call_common()+225] [SIGSEGV] [ADDR:0x0] [PC:0x1289FCA1] [SI_KERNEL(general_protection)] []
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
2023-02-07T13:01:23.525368+08:00
Exception [type: SIGSEGV, SI_KERNEL(general_protection)] [ADDR:0x0] [PC:0x1289FCA1, pevm_icd_call_common()+225] [flags: 0x0, count: 1]
Errors in file /u01/app/oracle/diag/rdbms/demorac/jydb2/trace/jydb2_m002_4361.trc (incident=185015) (PDBNAME=CDB$ROOT):
ORA-07445: exception encountered: core dump [pevm_icd_call_common()+225] [SIGSEGV] [ADDR:0x0] [PC:0x1289FCA1] [SI_KERNEL(general_protection)] []
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
2023-02-07T13:01:31.332246+08:00
ALTER SYSTEM SET _report_capture_cycle_time=0 SCOPE=BOTH;
2023-02-07T13:05:19.188451+08:00
PL/SQL package SYS.DBMS_RCVMAN version 19.16.00.00 is too new
Oracle must be upgraded to version 08.00.04.00 to work with this package
总结来说,针对ORA 7445类错误,肯定需要跟踪对应的trc查看详细信息。且很多时候Current SQL Statement要比Call Stack更有用。
19c RAC 告警日志报错 ORA 7445 [pevm_icd_call_common()+225]的更多相关文章
- 【故障处理】告警日志报“ORA-01565 Unable To open Spfile”
[故障处理]告警日志报"ORA-01565 Unable To open Spfile" 1.1 BLOG文档结构图 1.2 故障分析及解决过程 1.2.1 故障环境介绍 项 ...
- 11gR2数据库日志报错:Fatal NI connect error 12170、
11gR2数据库日志报错:Fatal NI connect error 12170.TNS-12535.TNS-00505 [问题点数:100分,结帖人MarkIII] 不显示 ...
- zabbix客户端日志报错no active checks on server [192.168.3.108:10051]: host [192.168.3.108] not found
zabbix客户端日志报错: 45647:20160808:220507.717 no active checks on server [192.168.3.108:10051]: host [192 ...
- 记一次rsync日志报错directory has vanished
中午两点的时候邮件告知rsync同部svn源库失败,看rsync日志报错显示如上,当时还在上课,没在公司,怀疑是不是有人动了svn的版本库,后来询问同事并通过vpn登录服务器上查看版本库是正常的,也没 ...
- 【docker】【redis】2.docker上设置redis集群---Redis Cluster部署【集群服务】【解决在docker中redis启动后,状态为Restarting,日志报错:Configured to not listen anywhere, exiting.问题】【Waiting for the cluster to join...问题】
参考地址:https://www.cnblogs.com/zhoujinyi/p/6477133.html https://www.cnblogs.com/cxbhakim/p/9151720.htm ...
- 【zabbix监控问题】记录zabbix控制面板报错及日志报错的解决方法
问题1: 上图是我已经解决了的截图.在百度查询的资料中,说是把zabbix_agentd.conf文件中server监听的主机127.0.0.1去掉,但是我去掉之后问题仍然没有解决,最后在这篇博客上发 ...
- AppiumLibrary库倒入后显示红色,日志报错:ImportError: cannot import name 'InvalidArgumentException'
AppiumLibrary安装后,robotframe worke 倒入后一直显示红色,查看日志报错:ImportError: cannot import name 'InvalidArgumentE ...
- gazebo仿真踩坑--rviz中设定机器人的目标位置,move_base后台日志报错
启动仿真环境及各种节点(amcl,move_base,map_server)后,在rviz中设定机器人的目标位置,后台日志报错 [ INFO] [1571974242.864525935, 40.51 ...
- alert日志报错:ERROR: failed to establish dependency between database RACDB and diskgroup resource ora.DATA.dg
一.打开数据库alert日志,发现有报错 ERROR: failed to establish dependency between database RACDB and diskgroup reso ...
- oracle 19c dataguard aws ORA-03186报错
环境说明 在亚马逊云AWS上面安装了一套oracle 19c dataguard,linux centos 7.7的操作系统,开始时同步正常,实时应用redolog,一会儿之后就不行了.报错如下: o ...
随机推荐
- Python数据可视化-地图可视化
Python数据可视化-地图可视化 一.基础地图使用 基础地图演示 二.疫情地图-国内疫情地图 具体代码如下 """ 演示全国疫情可视化地图开发 "" ...
- 万字血书Vue-Vue进阶
Vue进阶 生命周期 组件运行的过程 组件的生命周期是:组件从创建->运行(渲染)->销毁的整个过程,是一个时间段 如何监听组件的不同时刻 vue框架为组件内置了不同时刻的生命周期函数,是 ...
- Dubbo入门2:Springboot+Dubbo2.6.0+ZooKeeper3.4.8整合
整合Springboot+Dubbo2.6.0+ZooKeeper3.4.8 本文主要目的:记录整合以上3个框架的配置文件的写法 此文只在<Dubbo入门1>的基础上略作修改,仅记录修改的 ...
- mybatis plus 获取新增实体的主键
转载请注明出处: mybatis plus 新增实体对象调用的是 IService 接口中的 save 方法: default boolean save(T entity) { return SqlH ...
- 【lvgl-micropython】官方源码之ports/unix 编译报错
lv_micropython/ports/unix make 报错 编译环境如下 这是缺少SDL2库导致的 sudo apt-get install libsdl2-2.0 sudo apt-get ...
- 代码使我头疼之React初学习
前言 开始了,去年(2020)说要学的React,到现在2021年的12月底了,才来实施--(年底警告!年末总结还没开始写!) 不过前端为啥要学React呢?Vue不是很好用吗?Vue确实很好用,并且 ...
- [转帖]ubuntu下配置iptables、ufw端口转发
iptables 端口转发(CentOS) 注意:一来一去 在中转服务器操作 iptables -t nat -A PREROUTING -p tcp --dport [端口号] -j DNAT -- ...
- Nginx拆分配置文件的办法
Nginx拆分配置文件的办法 摘要 最近公司使用Nginx进行微服务的路由处理 但是发现随着业务发展, 配置文件越来越复杂. 修改起来也很容易出现错误. 基于此. 想通过拆分配置文件的方式来提高修改效 ...
- Nginx的Keepalive的简单学习
摘要 最近发现某项目的Nginx负载服务器上面有很多Time_wait的TCP连接 可以使用命令 netstat -n |awk '/^tcp/ {++S[$NF]} END{for (a in S) ...
- 基于eBPF的微服务网络安全(Cilium 1)
基于eBPF的微服务网络安全 翻译自:Network security for microservices with eBPF 一些开源的kubernetes工具已经开始使用eBPF,这些工具大多数与 ...