節(jié)點(diǎn)1：

Wed Feb 13 16:08:06 2019

Errors in file /u01/app/oracle/diag/rdbms/testdb/testdb1/trace/testdb1_dia0_9267.trc (incident=1248083):

ORA-32701: Possible hangs up to hang ID=4 detected

Incident details in: /u01/app/oracle/diag/rdbms/testdb/testdb1/incident/incdir_1248083/testdb1_dia0_9267_i1248083.trc

DIA0 requesting termination of session sid:5190 with serial # 42237 (ospid:180727) on instance 2

due to a GLOBAL, HIGH confidence hang with ID=4.

Hang Resolution Reason: Although the number of affected sessions did not

justify automatic hang resolution initially, this previously ignored

hang was automatically resolved.

DIA0: Examine the alert log on instance 2 for session termination status of hang with ID=4.

Wed Feb 13 16:08:08 2019

Sweep [inc][1248083]: completed

Sweep [inc2][1248083]: completed

Wed Feb 13 16:09:41 2019

Errors in file /u01/app/oracle/diag/rdbms/testdb/testdb1/trace/testdb1_dia0_9267.trc (incident=1248084):

ORA-32701: Possible hangs up to hang ID=4 detected

Incident details in: /u01/app/oracle/diag/rdbms/testdb/testdb1/incident/incdir_1248084/testdb1_dia0_9267_i1248084.trc

DIA0 requesting termination of process sid:5190 with serial # 42237 (ospid:180727) on instance 2

due to a GLOBAL, HIGH confidence hang with ID=4.

Previous SESSION termination failed.

Hang Resolution Reason: Although the number of affected sessions did not

justify automatic hang resolution initially, this previously ignored

hang was automatically resolved.

DIA0: Examine the alert log on instance 2 for process termination status of hang with ID=4.

[oracle@testdb1 trace]$ more /u01/app/oracle/diag/rdbms/testdb/testdb1/trace/testdb1_dia0_9267.trc

Trace file /u01/app/oracle/diag/rdbms/testdb/testdb1/trace/testdb1_dia0_9267.trc

*** TRACE FILE RECREATED AFTER BEING REMOVED ***

Incident 1248083 created, dump file: /u01/app/oracle/diag/rdbms/testdb/testdb1/incident/incdir_1248083/testdb1_dia0_9267_i1248083.trc

ORA-32701: Possible hangs up to hang ID=4 detected

Incident 1248084 created, dump file: /u01/app/oracle/diag/rdbms/testdb/testdb1/incident/incdir_1248084/testdb1_dia0_9267_i1248084.trc

ORA-32701: Possible hangs up to hang ID=4 detected

節(jié)點(diǎn)2：

Wed Feb 13 16:09:41 2019

Errors in file /u01/app/oracle/diag/rdbms/testdb/testdb2/trace/testdb2_dia0_7404.trc (incident=1008107):

ORA-32701: Possible hangs up to hang ID=4 detected

Incident details in: /u01/app/oracle/diag/rdbms/testdb/testdb2/incident/incdir_1008107/testdb2_dia0_7404_i1008107.trc

DIA0 terminating blocker (ospid: 180727 sid: 5190 ser#: 42237) of hang with ID = 4

[oracle@testdb2 trace]$ more /u01/app/oracle/diag/rdbms/testdb/testdb2/trace/testdb2_dia0_7404.trc

Trace file /u01/app/oracle/diag/rdbms/testdb/testdb2/trace/testdb2_dia0_7404.trc

*** TRACE FILE RECREATED AFTER BEING REMOVED ***

Incident 1008106 created, dump file: /u01/app/oracle/diag/rdbms/testdb/testdb2/incident/incdir_1008106/testdb2_dia0_7404_i1008106.trc

ORA-32701: Possible hangs up to hang ID=4 detected

Incident 1008107 created, dump file: /u01/app/oracle/diag/rdbms/testdb/testdb2/incident/incdir_1008107/testdb2_dia0_7404_i1008107.trc

ORA-32701: Possible hangs up to hang ID=4 detected

等待事件

inst# SessId Ser# OSPID PrcNm Event

----- ------ ----- --------- ----- -----

1 6746 23425 37352 M000 enq: WF - contention

2 5190 42237 180727 M000 not in wait

inst# SessId Ser# OSPID PrcNm Event

----- ------ ----- --------- ----- -----

1 6746 23425 37352 M000 enq: WF - contention

2 5190 42237 180727 M000 not in wait

---解決辦法

-----MOS 上文章 2226216.1

1. Collect statistics on following fixed table:

SQL> exec dbms_stats.gather_table_stats('SYS', 'X$KEWRATTRNEW');

PL/SQL procedure successfully completed.

SQL> exec dbms_stats.gather_table_stats('SYS', 'X$KEWRSQLIDTAB');

PL/SQL procedure successfully completed.

Or

2. Restarting the database will release of X$KQLFBC table data

Or

3. Flush shared_pool on a regular basis

*** 2019-02-14 06:25:08.352

current sql: insert into wrh$_sql_bind_metadata (snap_id, dbid, sql_id, name, position, dup_position, datatype, datatype_string, characte

r_sid, precision, scale, max_length) SELECT /*+ ordered use_nl(bnd) index(bnd sql_id) */ :lah_snap_id, :dbid, bnd.sql_id, name, position,

dup_position, datatype, dataty

---處理方法

exec dbms_stats.gather_table_stats('SYS', 'X$KEWRATTRNEW');

exec dbms_stats.gather_table_stats('SYS', 'X$KEWRSQLIDTAB');

--立馬生效

exec?dbms_stats.gather_table_stats(ownname?=>?'SYS',tabname?=>?'X$KEWRATTRNEW',no_invalidate?=>?FALSE);

exec?dbms_stats.gather_table_stats(ownname?=>?'SYS',tabname?=>?'X$KEWRSQLIDTAB',no_invalidate?=>?FALSE);

---定時(shí)任務(wù)

# flush shared_pool 每個(gè)月執(zhí)行一次

33 02 15 * * /bin/sh /home/oracle/flush_shared_pool/flush_shared_pool.sh &> /dev/null

[oracle@testdb2 ~]$ cat /home/oracle/flush_shared_pool/flush_shared_pool.sh

#!/bin/bash

source /home/oracle/.bash_profile

sqlplus / as sysdba >> /home/oracle/flush_shared_pool/exec_shared_pool.log <

set timing on;

@/home/oracle/flush_shared_pool/flush_shared_pool.sql

EOF

[oracle@testdb2 ~]$ cat /home/oracle/flush_shared_pool/flush_shared_pool.sql

alter system flush shared_pool;

---還有可能是死鎖引起的故障

1.業(yè)務(wù)查詢程序死鎖問題

2.執(zhí)行刷新shared_pool--兩個(gè)節(jié)點(diǎn)都需要執(zhí)行

EXEC DBMS_STATS.GATHER_FIXED_OBJECTS_STATS;

EXEC DBMS_STATS.GATHER_SCHEMA_STATS ('SYS');

alter system flush shared_pool;

--查詢2個(gè)節(jié)點(diǎn)基表信息

select count(*) from x$ksmsp;

exec?dbms_stats.gather_table_stats(ownname?=>?'SYS',tabname?=>?'X$KEWRATTRNEW',no_invalidate?=>?FALSE);

exec?dbms_stats.gather_table_stats(ownname?=>?'SYS',tabname?=>?'X$KEWRSQLIDTAB',no_invalidate?=>?FALSE);

--絕招

alter system set "_awr_disabled_flush_tables" = 'wrh$_sql_bind_metadata';

標(biāo)簽：testdb1,11G,testdb2,stats,RAC,32701,oracle,shared,pool

來源： https://www.cnblogs.com/daizhengyang/p/13396709.html

總結(jié)

以上是生活随笔為你收集整理的oracle 11203 ora32701,11G RAC ORA-32701 参考学习的全部內(nèi)容，希望文章能夠幫你解決所遇到的問題。

如果覺得生活随笔網(wǎng)站內(nèi)容還不錯(cuò)，歡迎將生活随笔推薦給好友。