By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
443,795 Members | 1,660 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 443,795 IT Pros & Developers. It's quick & easy.

IX lock not released

P: n/a
i am using type 4 driver with fp3 on windows 64bit server, auto commit
is true, cursor is CS type.

i have a sensitive , updatable cursor open and bring back a one row
resultset, i get this locklist

Lock Name = 0x020027011C0000000000000052
Lock Attributes = 0x00000000
Release Flags = 0x00000002
Lock Count = 1
Hold Count = 0
Lock Object Name = 28
Object Type = Row
Tablespace Name = USERSPACE1
Table Schema = xx
Table Name = xx
Mode = U

Lock Name = 0x02002701000000000000000054
Lock Attributes = 0x00000000
Release Flags = 0x00000003
Lock Count = 2
Hold Count = 2
Lock Object Name = 295
Object Type = Table
Tablespace Name = USERSPACE1
Table Schema = xx
Table Name = xx
Mode = IX

after that i will do update on this row, once the update statement
execute. statement.execute(sql), i still have a table IX lock there,
why the commit part not working? i have tried to explicitly call
conn.commit() still not help. but this will cause us problem since we
don't want to have IX lock stay after commit. Does this is the way
work on DB2?

Lock Name = 0x02002701000000000000000054
Lock Attributes = 0x00000000
Release Flags = 0x00000003
Lock Count = 2
Hold Count = 2
Lock Object Name = 295
Object Type = Table
Tablespace Name = USERSPACE1
Table Schema = xx
Table Name = xxx
Mode = IX
Nov 12 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
I don't use JDBC 2 feature.
Where can I find the definition of a sensitive cursor? Is it a scroll
cursor?
AFAIK, when using updatable cursor, you need turn off the autocommit,
otherwise you may lose the cursor handle.
xixi wrote:
i am using type 4 driver with fp3 on windows 64bit server, auto commit
is true, cursor is CS type.

i have a sensitive , updatable cursor open and bring back a one row
resultset, i get this locklist

Lock Name = 0x020027011C0000000000000052
Lock Attributes = 0x00000000
Release Flags = 0x00000002
Lock Count = 1
Hold Count = 0
Lock Object Name = 28
Object Type = Row
Tablespace Name = USERSPACE1
Table Schema = xx
Table Name = xx
Mode = U

Lock Name = 0x02002701000000000000000054
Lock Attributes = 0x00000000
Release Flags = 0x00000003
Lock Count = 2
Hold Count = 2
Lock Object Name = 295
Object Type = Table
Tablespace Name = USERSPACE1
Table Schema = xx
Table Name = xx
Mode = IX

after that i will do update on this row, once the update statement
execute. statement.execute(sql), i still have a table IX lock there,
why the commit part not working? i have tried to explicitly call
conn.commit() still not help. but this will cause us problem since we
don't want to have IX lock stay after commit. Does this is the way
work on DB2?

Lock Name = 0x02002701000000000000000054
Lock Attributes = 0x00000000
Release Flags = 0x00000003
Lock Count = 2
Hold Count = 2
Lock Object Name = 295
Object Type = Table
Tablespace Name = USERSPACE1
Table Schema = xx
Table Name = xxx
Mode = IX


Nov 12 '05 #2

P: n/a
WITH HOLD... WITH HOLD... WITH HOLD...

xixi wrote:
i am using type 4 driver with fp3 on windows 64bit server, auto commit
is true, cursor is CS type.

i have a sensitive , updatable cursor open and bring back a one row
resultset, i get this locklist

Lock Name = 0x020027011C0000000000000052
Lock Attributes = 0x00000000
Release Flags = 0x00000002
Lock Count = 1
Hold Count = 0
Lock Object Name = 28
Object Type = Row
Tablespace Name = USERSPACE1
Table Schema = xx
Table Name = xx
Mode = U

Lock Name = 0x02002701000000000000000054
Lock Attributes = 0x00000000
Release Flags = 0x00000003
Lock Count = 2
Hold Count = 2
Lock Object Name = 295
Object Type = Table
Tablespace Name = USERSPACE1
Table Schema = xx
Table Name = xx
Mode = IX

after that i will do update on this row, once the update statement
execute. statement.execute(sql), i still have a table IX lock there,
why the commit part not working? i have tried to explicitly call
conn.commit() still not help. but this will cause us problem since we
don't want to have IX lock stay after commit. Does this is the way
work on DB2?

Lock Name = 0x02002701000000000000000054
Lock Attributes = 0x00000000
Release Flags = 0x00000003
Lock Count = 2
Hold Count = 2
Lock Object Name = 295
Object Type = Table
Tablespace Name = USERSPACE1
Table Schema = xx
Table Name = xxx
Mode = IX


Nov 12 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.