您好,登錄后才能下訂單哦!
最近客戶在打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 |
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.
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
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)
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
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
BUG:19904315 - ORA-7445 [JOET_CREATE_ROOT_THREAD_GROUP+145] AFTER APPLYING PATCH 19791427
免責聲明:本站發布的內容(圖片、視頻和文字)以原創、轉載和分享為主,文章觀點不代表本網站立場,如果涉及侵權請聯系站長郵箱:is@yisu.com進行舉報,并提供相關證據,一經查實,將立刻刪除涉嫌侵權內容。