The potential blocker again.

admin管理员组

文章数量:1530517

From alert log: 

 Current log# 2 seq# 3744 mem# 1: /oraredo2/RPTS/redo12_2.log
Thu Feb 10 19:13:20 2011
GES: Potential blocker (pid=22180) on resource TX-00260029-003FCA69;
 enqueue info in file /opt/app/oracle/admin/RPTS/bdump/rpts1_lmd0_12113.trc and DIAG trace file
Thu Feb 10 20:37:53 2011
GES: Potential blocker (pid=14397) on resource TX-003F002C-002AF21C;
 enqueue info in file /opt/app/oracle/admin/RPTS/udump/rpts1_ora_14399.trc and DIAG trace file
Thu Feb 10 20:37:56 2011
GES: Potential blocker (pid=25233) on resource TX-00440002-002BF3D2;
 enqueue info in file /opt/app/oracle/admin/RPTS/udump/rpts1_ora_2266.trc and DIAG trace file
Thu Feb 10 20:38:00 2011
GES: Potential blocker (pid=22180) on resource TX-00260029-003FCA69;
 enqueue info in file /opt/app/oracle/admin/RPTS/bdump/rpts1_lmd0_12113.trc and DIAG trace file

From trace file:

*** 2010-11-09 21:00:55.461
*** SERVICE NAME:() 2010-11-09 21:00:55.460
*** SESSION ID:(1101.1) 2010-11-09 21:00:55.460
 syncr inc 129 lvl 1 from 2 rcvd (my inc,lvl: 0, 0) (129/4.0.0)
 syncr inc 129 lvl 1 from 1 rcvd (my inc,lvl: 129, 1) (129/5.0.0)
 s2m domain info received from 1 (129.6)
* s2m: domain 0 valid according to instance 1
 s2m domain info received from 2 (129.6)
 ftd received from node 2 (129/7.0.0)
 first hvmap received from 1 for domain 0 (129.7)
* kjxhvmaph: domain 0 valid = 1 according to instance 1
 last hvmap received from 1, (129.7)
 first hvmap received from 1 for enqueue mappings (129.7)
 last hvmap received from 1, (129.7)
 ptmap received from node 1 (129.7)
 ftd received from node 1 (129/7.0.0)
 all ftds received
 syncr inc 129 lvl 2 from 1 rcvd (my inc,lvl: 129, 1) (129/7.0.0)
 syncr inc 129 lvl 2 from 2 rcvd (my inc,lvl: 129, 2) (129/7.0.0)
 ftd received from node 2 (129/13.0.0)
 ftd received from node 1 (129/13.0.0)
 all ftds received
 syncr inc 129 lvl 3 from 1 rcvd (my inc,lvl: 129, 2) (129/13.0.0)
 syncr inc 129 lvl 3 from 2 rcvd (my inc,lvl: 129, 3) (129/13.0.0)
 ftd received from node 2 (129/15.0.0)
 syncr inc 129 lvl 4 from 2 rcvd (my inc,lvl: 129, 3) (129/15.0.0)
 ftd received from node 1 (129/15.0.0)
 all ftds received
 syncr inc 129 lvl 4 from 1 rcvd (my inc,lvl: 129, 4) (129/15.0.0)
 ftd received from node 2 (129/17.0.0)
 ftd received from node 1 (129/18.0.0)
 all ftds received
 syncr inc 129 lvl 5 from 2 rcvd (my inc,lvl: 129, 4) (129/18.0.0)
 syncr inc 129 lvl 5 from 1 rcvd (my inc,lvl: 129, 5) (129/18.0.0)
 ftd received from node 2 (129/20.0.0)
 ftd received from node 1 (129/20.0.0)
 all ftds received
 syncr inc 129 lvl 6 from 1 rcvd (my inc,lvl: 129, 5) (129/20.0.0)
It is said that it is a bug :

Ref:

Bug 5898210 - Hang from concurrent MV refresh and library cache invalidation in RAC [ID 5898210.8]

本文标签： potentialBlocker