import utility

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

db2group88 - 21 Apr 2006 22:02 GMT

hi, we are using db2 v8.2 Express on Windows, I try to import the rows
into a table which is being used ( maybe being read or write), and it
was kicked out because there is lock waiting. As our appliction design,
the lock should be a row lock, so whoever use the table should just
create a row lock, but insert to this tables still be prevented, why is
that ? is there anyway to allow import while in production? thanks

Reply to this Message

tuarek - 23 Apr 2006 02:25 GMT

Hi,

If you see the same problem with your other processes, your db2
client's "Isolation level" may be the cause of problem. Make sure that
they are not using "Repeatable Read". You can find this setting in
your db2cli.ini file.

Regards,

Mehmet

Reply to this Message

db2group88 - 24 Apr 2006 22:26 GMT

hi, i have checked the db2cli.ini under D:\IBM\SQLLIB
but don't find anything setting related "repeatable read", please
advice

; Comment lines start with a semi-colon.

[tstcli1x]
uid=userid
pwd=password
autocommit=0
TableType="'TABLE','VIEW','SYSTEM TABLE'"

[tstcli2x]
; Assuming dbalias2 is a database in DB2 for MVS.
SchemaList="'OWNER1','OWNER2',CURRENT SQLID"

[MyVeryLongDBALIASName]
dbalias=dbalias3
SysSchema=MYSCHEMA

Reply to this Message

tuarek - 25 Apr 2006 05:04 GMT

db2cli's isolation level parameter is defined by TXNISOLATION = ...
Nevertheless it is not in your db2cli.ini Nevermind.

Do you think that the OTHER db2 clients / applications might be helding
a TABLE LEVEL lock?

Do they issue "Lock table ..." command ever and terminate without
issuing "COMMIT"?

You better take a snapshot: "get snapshot for locks on yourdbname"
and do a reverse engineering to figure out what is happening in the
other applications/clients.

It is really difficult for me to say anything further without knowing
what else is going on.

regards,

Mehmet

Reply to this Message

db2group88 - 23 May 2006 23:06 GMT

i do get snapshot and find out the table only with IS lock but still
prevent import. our application only allow row lock and with auto
commit on. Please advise

Lock Name = 0x02009701000000000000000054

Lock Attributes = 0x00000000

Release Flags = 0x40000000

Lock Count = 2

Hold Count = 2

Lock Object Name = 407

Object Type = Table

Tablespace Name = USERSPACE1

Table Schema = ML101PD

Table Name = OETBLP

Mode = IS

Reply to this Message