千家信息网

升级psu引发的新bugORACLE ORA-07445

发表于:2025-02-01 作者:千家信息网编辑
千家信息网最后更新 2025年02月01日,最近客户在打10.2.0.5.19 PSU补丁,运行@catbundle.sql psuapply,报ORA-07445:exception encountered: core dump[joet_c
千家信息网最后更新 2025年02月01日升级psu引发的新bugORACLE ORA-07445

最近客户在打10.2.0.5.19 PSU补丁,运行@catbundle.sql psuapply,报ORA-07445:exception encountered: core dump[joet_create_root_thread_group()+140] [SIGSEGV] [Address not mapped to object] [0x000000008][] []错误。导致升级无法进行下去。

查看相关文档,只显示如下信息:

没有其他方案,只能备份数据库,来尝试上边的方案,但是在逻辑备份时同样遇到上边的错误。无奈只能使用rman进行备份。

根据1940340.1这个文档上的说可能是在应用PSU是导致的oracle buf。

按照步骤如下:

Create pfile='/home/oracle/pfie.ora' fromspfile ;\

SQL> alter system set java_jit_enabled =FALSE; ---10g 不需要

SQL> alter system set"_system_trig_enabled"=FALSE;---

SQL> alter system setJOB_QUEUE_PROCESSES=0;

SQL> startup restrict

SQL> @catbundle.sql psu apply -跑完还原参数
 

SQL> alter system set"_system_trig_enabled"=TRUE;

SQL> alter system setJOB_QUEUE_PROCESSES=10;

重启数据库。

以上方案直供参考。

参考1940340.1文档

文档信息如下:

In this Document


Symptoms

Changes

Cause

Solution

References

APPLIES TO:

Oracle Database - Enterprise Edition - Version 11.2.0.3 to 11.2.0.3 [Release 11.2]
Information in this document applies to any platform.

SYMPTOMS

ORA-07445: exception encountered: core dump [joet_create_root_thread_group()+145] is seen at startup.

The issue happens in CDC environments and the following statement is seen in the alert log:

----- Current SQL Statement for this session (sql_id=f03bykh7st1m5) -----
BEGIN
/* NOP UNLESS A TABLE OBJECT */
IF dictionary_obj_type = 'TABLE'
THEN
sys.dbms_cdc_ipublish.change_table_trigger(dictionary_obj_owner,dictionary_obj_name,sysevent);
END IF;
END;
----- PL/SQL Stack -----
----- PL/SQL Call Stack -----
object line object
handle number name
0xa7dd71c0 12 package body SYS.DBMS_CDC_IPUBLISH

The error can also be seen from MMON_SLAVE with an action of : JAVAVM JIT slave action without any SQL statement referenced.

The call stack is:

joet_create_root_th <- read_group <- joet_aux_thread_mai
<- seoa_note_stack_out <- side <- joet_thread_main <- sjontlo_initialize <- joe_enter_vm
<- ioei_execute <- ioesub_EXECUTE <- seoa_note_stack_out <- side <- ioe_execute
<- side <- jox_ioe_execute <- joxgrovel_jitsomeme <- thods <- joxgroveldrv
<- thods <- joxjitexe <- joxrdp_ <- joxrdp <- kebm_slave_main
<- ksvrdp <- opirip <- opidrv <- sou2o <- opimai_real
<- ssthrdmain <- main <- libc_start_main <- start

joet_create_root_thread_group <- joet_aux_thread_main
<- seoa_note_stack_outside <- joet_thread_main <- sjontlo_initialize <- joe_enter_vm

CHANGES

Apply Patch 19791427 : COMBO OF OJVM COMPONENT 11.2.0.3.1 DB PSU + DB PSU 11.2.0.3.12 (OCT2014)

OR

Patch 19282015: ORACLE JAVAVM COMPONENT 11.2.0.3.1 DATABASE PSU (OCT2014) +
Patch 19121548: DATABASE PATCH SET UPDATE 11.2.0.3.12 (INCLUDES CPUOCT2014)

OR ONLY

Patch 19282015 "ORACLE JAVAVM COMPONENT 11.2.0.3.1 DATABASE PSU (OCT2014)

CAUSE

The cause is a problem within the Patch and it is investigated by Development in active bugs:

BUG 19904315 - RECEIVE ORA-07445[JOET_CREATE_ROOT_THREAD_GROUP()] AFTER APPLYING PATCH 19791427

Bug 19838078 - ORA-7445 [JOET_CREATE_ROOT_THREAD_GROUP()+136] ON SMON CACHE RECOVERY

SOLUTION

To workaround this issue perform the next steps:

1/ Apply patch 19791427 or Patch 19282015 till the end of Installation steps and 3.3.1.

2/ Before running Postinstallation step (3.3.2), set the following init parameters so that JIT and job process do not start.

If spfile is used:

SQL> alter system set java_jit_enabled = FALSE;
SQL> alter system set "_system_trig_enabled"=FALSE;
SQL> alter system set JOB_QUEUE_PROCESSES=0;

3/ Startup instance in restricted mode and run postinstallation step.

SQL> startup restrict

4/ Run Postinstallation steps (3.3.2)

5/ Reset modified init parameters
SQL> alter system set java_jit_enabled = true;
SQL> alter system set "_system_trig_enabled"=TRUE;
SQL> alter system set JOB_QUEUE_PROCESSES=10;
-- or original JOB_QUEUE_PROCESSES value

5/ Restart instance as normal

REFERENCES

BUG:19904315 - ORA-7445 [JOET_CREATE_ROOT_THREAD_GROUP+145] AFTER APPLYING PATCH 19791427

0