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
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.
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.
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
