Skip to Main Content

Oracle Database Discussions

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Bitmap causing deadlock

rishwingerDec 23 2013 — edited Dec 23 2013

Hi Experts

I understand the basic problem why deadlocks can happen with bitmap indexes in concurrent environments.

Thanks to TOM http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:582867200346727043

But, could anyone please explain what exactly is happening in the following case?


Deadlock graph:

  ---------Blocker(s)-------- ---------Waiter(s)---------

Resource Name process session holds waits process session holds waits

TX-001a000a-000a9be5 146 393 X 149 947 S

TX-000b0020-007c4e3e 149 947 X 146 393 S

session 393: DID 0001-0092-000070C6 session 947: DID 0001-0095-0000457B

session 947: DID 0001-0095-0000457B session 393: DID 0001-0092-000070C6

Rows waited on:

  Session 393: obj - rowid = 00087875 - AACHh1AAAAAAAAAAAA

  (dictionary objn - 555125, file - 0, block - 0, slot - 0)

  Session 947: obj - rowid = 0008785C - AACHhcAAAAAAAAAAAA

  (dictionary objn - 555100, file - 0, block - 0, slot - 0)

----- Information for the OTHER waiting sessions -----

Session 947:

  sid: 947 ser: 7443 audsid: 80871604 user: 267/xxxxxx

  flags: (0x41) USR/- flags_idl: (0x1) BSY/-/-/-/-/-

  flags2: (0x40009) -/-/INC

  pid: 149 O/S info: user: grid, term: UNKNOWN, ospid: 25682

  image: oracle@kkkkkkkk

  client details:

  O/S info: user: ggggg, term: unknown, ospid: 1234

  machine: ffffff program: JDBC Thin Client

  application name: JDBC Thin Client, hash value=2546894660

  current SQL:

 

  INSERT INTO child table

----- End of information for the OTHER waiting sessions -----

Information for THIS session:

----- Current SQL Statement for this session (sql_id=b936wq8mpp6y7) -----

  

  UPDATE parent table

  SET fk = :1 ,

  WHERE 

  PK=:4

  

  

===================================================

Session 393: obj - rowid = 00087875 - AACHh1AAAAAAAAAAAA

(dictionary objn - 555125, file - 0, block - 0, slot - 0)

Session 947: obj - rowid = 0008785C - AACHhcAAAAAAAAAAAA

(dictionary objn - 555100, file - 0, block - 0, slot - 0)

555125,555100 data_object_id correspond to Bitamp index on parent ,child table respectively

The point which confuses is

STEP-1 is an Insert in child table

STEP-2 is update on parent table

Different bitmap keys are being updated by above steps then why there is a deadlock ?

Thanks

Rishwinger

Comments

702619
这个需要在portal administration中设置,好像是最右边的菜单下
702619
sorry!我没有这方面的材料。你提的这个很简单,在我说的那个地方通过下拉框,把你自己设置的ldap加进来即可,默认只有bea自带的那个ldap
702619
就是这个地方,不可以?!
我用的是RDBMS模式,没有问题的;我觉得别的模式都应该是同样的原理。
另外你看看建立TDSAuthentication时,设置的控制标志是什么
702619
终于搞定了,都是眼泪啊。。。。55555555
702619
重新配置provider的顺序,把你的ldap放到最上面。
702619
恭喜!能否将出错原因和最终解决方法写出来。
以方便后来者,谢谢
702619
配置基本是参考http://dev2dev.bea.com.cn/bbs/thread.jspa?forumID=101&threadID=26607&tstart=0 这个帖子里面的配置方法,配好以后,我调整了其他的东西没有重启portal server,每次做一个修改都需要重启才可以生效
702619
很简单,你这种情况,将原来缺省的授权的控制选项改为OPTIONAL , 就OK了!
1 - 8
Locked Post
New comments cannot be posted to this locked post.

Post Details

Locked on Jan 20 2014
Added on Dec 23 2013
3 comments
2,895 views