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

SET CURRENT LOCK TIMEOUT has no effect

P: n/a
DB2 8.1 FP7a on AIX 5.2.

$ db2 SET CURRENT LOCK TIMEOUT NOT WAIT
DB20000I The SQL command completed successfully.
$ db2 values current lock timeout

1
-----------
0

1 record(s) selected.

$ db2 REORG INDEXES ALL FOR TABLE TAB1 ALLOW WRITE ACCESS ...hangs in
Lock-wait
I read that "The CURRENT LOCK TIMEOUT special register specifies the
number of seconds to wait for a lock before returning an error
indicating that a lock cannot be obtained." I want to force an error if
the REORG has to wait at all.
Does anyone know what I am missing? Thank you for your help.

May 3 '06 #1
Share this Question
Share on Google+
1 Reply


P: n/a
pike wrote:
DB2 8.1 FP7a on AIX 5.2.

$ db2 SET CURRENT LOCK TIMEOUT NOT WAIT
DB20000I The SQL command completed successfully.
$ db2 values current lock timeout

1
-----------
0

1 record(s) selected.

$ db2 REORG INDEXES ALL FOR TABLE TAB1 ALLOW WRITE ACCESS ...hangs in
Lock-wait
I read that "The CURRENT LOCK TIMEOUT special register specifies the
number of seconds to wait for a lock before returning an error
indicating that a lock cannot be obtained." I want to force an error if
the REORG has to wait at all.
Does anyone know what I am missing? Thank you for your help.

I take a guess here and postulate that the register is only relevant to
SQL statements.
Whether that's conscious design or not, I don't know.
Maybe worth a PMR...

Cheers
Serge

--
Serge Rielau
DB2 Solutions Development
IBM Toronto Lab
May 3 '06 #2

This discussion thread is closed

Replies have been disabled for this discussion.