19c RAC 告警日志报错 ORA 7445 [pevm_icd_call_common()+225]

19c,rac,告警,日志,报错,ora,pevm,icd,call,common · 浏览次数 : 181

小编点评

## Summary of the ORA 7445 Error This document summarizes the cause of the ORA 7445 error and provides troubleshooting steps. **Problem:** * Node 2 in a 19c RAC environment received an alert for ORA 7445. * The frequency of alerts was fixed at every minute. * During a restart, the error persisted despite the restart. **Details:** * The error message indicates an invalid version of Oracle database (19.16.00.00). * The package `SYS.DBMS_RCVMAN` requires Oracle database version 08.00.04.00 or higher. **Possible causes:** * The environment might not be upgraded to the required Oracle database version. * The alert frequency might be configured too frequently. **Troubleshooting steps:** 1. **Check Oracle database version:** * Use the `DBMS_VERSION` and `SYS.DBMS_PATCH` system views to verify the installed Oracle database version. * Check if the database has been upgraded to 08.00.04.00 or higher. 2. **Verify alert frequency:** * Review the alert configuration and ensure it's set to run only once per minute. * If it's set to a different frequency, adjust it to 1 minute or higher. 3. **Upgrade Oracle database if necessary:** * If the database version is outdated, upgrade it to version 08.00.04.00 or higher. * Use the `DBMS_UPGRADE` system view to perform the upgrade. 4. **Restart the node:** * Restart the node to apply any pending database updates and ensure the new version is loaded. 5. **Re-check the alert:** * Once the node is restarted, re-run the alert check. * If the error persists, contact Oracle support for further assistance. **Additional notes:** * This error often requires monitoring of the error trace (`jydb2_m001_4635.trc` and `jydb2_m002_4361.trc`) for more details. * The `_report_capture_cycle_time` hidden parameter can be disabled to avoid automatic report flushing. * It's recommended to investigate the cause of the ORA 7445 error and take appropriate steps to prevent similar occurrences.

正文

问题现象:

在一套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]相似的内容:

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

Oracle 19c RAC 自动应用RU补丁简明版

环境:Oracle RAC(GI 19.3 + DB 19.3) 本文应用补丁信息, 19.16 RU: p34130714_190000_Linux-x86-64.zip 本文主要演示使用opatchauto apply自动应用补丁的过程。 1.更新OPatch版本 2.使用opatchauto应

在QEMU-KVM环境下部署Oracle 19.16 RAC

KVM环境和其他虚拟化或真实生产最大差异主要就是在实施前期准备工作上: 具体在 DB节点 和存储环境 的准备工作上有差异,本文会详细说明。 而剩余基本软件安装和补丁应用部分无差异,若不清楚可以直接参考之前文章: Linux平台 Oracle 19c RAC安装Part1:准备工作 Linux平台 O

19c ADG Switchover 切换测试

背景: 环境未配置DG Broker,手工切换ADG,19c也要比11g时代的切换更简单。 使用自己的测试环境,具体可参见: 单实例Primary快速搭建Standby RAC参考手册(19.16 ADG) 1.主库demo切换到RAC环境demorac: 在主库demo执行命令: SQL> alt

验证ADG的坏块检测和自动修复

环境: Oracle 19c ADG(主库:单实例;备库:RAC) 1.主库新建测试文件 2.主库创建测试表 3.查询表对应数据文件信息 4.模拟数据文件物理坏块 5.查询对应测试表 6.进一步查询日志信息 7.确认当前参数设置 1.主库新建测试文件 主库在AWR的PDB中做测试,为了不影响其他测试

部署19c ADG过程中的问题处理

回忆起来也是有些年没亲自动手搭建ADG了,今天正好有个机会重温,客户环境是19.16,恍惚记得上一次搭ADG还是在11.2.0.4的时代,时光荏苒啊。 正好看下19c的ADG和11g的ADG在部署方面有啥不同? 主备库都是RAC架构,数据库是CDB架构,包含有4个PDB,整个搭建过程还是遇到很多小问

[转帖]从生命周期的角度来谈谈Oracle 软件的版本(12c/18c/19c/20c/21c)问题

2022-04-21 20:3720050原创Oracle 19c 本文链接:https://www.cndba.cn/dave/article/107944 在2017年之前,Oracle 的版本路线是非常清晰的,我接触过的几个版本有:9i、10g、11g、12c。 但是到了2018年之后,Ora

[转帖]uos服务器系统rpm安装oracle 19c

https://blog.csdn.net/u013317172/article/details/126122220 文章目录 一、依赖二、数据库RPM包下载地址三、安装openjdk四、安装oracle-database-preinstall1)compat-libcap1错误

[FATAL] [DBT-06103] 端口 (1,521) 已在使用

今天参考之前文章 Oracle 19c快速安装部署 在一个新的环境进行安装时,发现配置数据库时报错1521端口被占用: [root@OEL7 media]# /etc/init.d/oracledb_ORCLCDB-19c configure Configuring Oracle Database

OpenEuler2203使用rpm方式安装Oracle19c的过程

OpenEuler2203使用rpm方式安装Oracle19c的过程 安装介质 oracle-database-preinstall-19c-1.0-1.el7.x86_64.rpm oracle-database-ee-19c-1.0-1.x86_64.rpm compat-libstdc++-3