问题现象:

在一套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]的更多相关文章

  1. 【故障处理】告警日志报“ORA-01565 Unable To open Spfile”

    [故障处理]告警日志报"ORA-01565 Unable To open Spfile" 1.1  BLOG文档结构图 1.2  故障分析及解决过程 1.2.1  故障环境介绍 项 ...

  2. 11gR2数据库日志报错:Fatal NI connect error 12170、

    11gR2数据库日志报错:Fatal NI connect error 12170.TNS-12535.TNS-00505 [问题点数:100分,结帖人MarkIII]             不显示 ...

  3. 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 ...

  4. 记一次rsync日志报错directory has vanished

    中午两点的时候邮件告知rsync同部svn源库失败,看rsync日志报错显示如上,当时还在上课,没在公司,怀疑是不是有人动了svn的版本库,后来询问同事并通过vpn登录服务器上查看版本库是正常的,也没 ...

  5. 【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 ...

  6. 【zabbix监控问题】记录zabbix控制面板报错及日志报错的解决方法

    问题1: 上图是我已经解决了的截图.在百度查询的资料中,说是把zabbix_agentd.conf文件中server监听的主机127.0.0.1去掉,但是我去掉之后问题仍然没有解决,最后在这篇博客上发 ...

  7. AppiumLibrary库倒入后显示红色,日志报错:ImportError: cannot import name 'InvalidArgumentException'

    AppiumLibrary安装后,robotframe worke 倒入后一直显示红色,查看日志报错:ImportError: cannot import name 'InvalidArgumentE ...

  8. gazebo仿真踩坑--rviz中设定机器人的目标位置,move_base后台日志报错

    启动仿真环境及各种节点(amcl,move_base,map_server)后,在rviz中设定机器人的目标位置,后台日志报错 [ INFO] [1571974242.864525935, 40.51 ...

  9. 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 ...

  10. oracle 19c dataguard aws ORA-03186报错

    环境说明 在亚马逊云AWS上面安装了一套oracle 19c dataguard,linux centos 7.7的操作系统,开始时同步正常,实时应用redolog,一会儿之后就不行了.报错如下: o ...

随机推荐

  1. S3C2440移植uboot之编译烧写uboot

    目录 移植环境 获取uboot 更新交叉编译工具 配置环境变量 移植环境 主 机:VMWare--ubuntu16.04 开发板:S3C2440 编译器:arm-linux-gcc-4.3.2.tgz ...

  2. 【FreeRTOS】内核查找最高优先级就绪任务

    查找最高优先级就绪任务 FreeRTOS\Source\tasks.c #if ( configUSE_PORT_OPTIMISED_TASK_SELECTION == 0 ) /* If confi ...

  3. js - 使用 scroll属性手撸轮播图 —— 无缝连接,更丝滑

    上效果图: 上代码: <!DOCTYPE html> <html lang="en"> <head>     <meta charset= ...

  4. Vue-自定义icon实现

    在项目中引入了element-ui之后,发现其内置的icon有限,无法满足项目的需求,因此需自定义icon来实现需求. 在vue项目的components下新建SvgIcon目录,在SvgIcon目录 ...

  5. Mygin实现简单的路由

    本文是Mygin第二篇 目的: 实现路由映射 提供了用户注册静态路由方法(GET.POST方法) 基于上一篇 Mygin 实现简单Http 且参照Gin 我使用了map数组实现简单路由的映射关系 不同 ...

  6. [转帖]下载 SQL Server Management Studio (SSMS)

    https://learn.microsoft.com/zh-CN/sql/ssms/download-sql-server-management-studio-ssms?view=sql-serve ...

  7. [转帖]Prometheus系列之Grafana 版本9.0.0 设置Email邮件报警实战

    目录 1. 配置文件conf/defaults.ini修改 2. Grafana Web页面配置报警邮箱接收者 3. 创建Dashboard 4. 创建Alert的文件夹 5. 设置Notificat ...

  8. [转帖]datax安装+配置+使用文档

    1 DataX离线同步工具DataX3.0介绍 DataX 是阿里巴巴集团内被广泛使用的离线数据同步工具/平台,实现包括 MySQL.Oracle.SqlServer.Postgre.HDFS.Hiv ...

  9. [转帖]MinIO系列7 - Minio性能压测

    https://www.zhihu.com/people/keen-wang 前言 声明:此文为本人历史笔记的整理,文章实际撰写时间为2021年2月份,所以本中所使用的相关组件版本较老.此文是通过压力 ...

  10. [转帖]使用s3(minio)为kubernetes提供pv存储

    http://www.lishuai.fun/2021/12/31/k8s-pv-s3/#/%E8%A6%81%E6%B1%82 我们可以通过csi使用s3为kubernetes提供pv存储,当我们申 ...