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

"WITH RS USE AND KEEP UPDATE LOCKS" An unexpected token

P: n/a
I am trying to run this select statment against my DB2 database and it
is throwing the following error, is there a setting in my db2 database
to allow for this call "USE AND KEEP UPDATE LOCKS"?

SELECT * FROM user.tableA WHERE FIRST_NAME ='Billy' WITH RS USE AND
KEEP UPDATE LOCKS
SQL0104N An unexpected token "USE AND KEEP UPDATE LOCKS" was
found following "Billy' WITH RS". Expected tokens may
include: "<space ".

If I just run SELECT * FROM user.tableA WHERE FIRST_NAME ='Billy'
WITH RS it works just fine.

My DB2 info:

================================================== ==========
About DB2 Administration Tools Environment
================================================== ==========
DB2 administration tools level:
Product identifier SQL08010
Level identifier 01010106
Level DB2 v8.1.0.36
Build level s021023
PTF
================================================== ==========
Java development kit (JDK):
Level IBM Corporation 1.3.1
================================================== ==========

Nov 7 '08 #1
Share this Question
Share on Google+
3 Replies


P: n/a
I just read this somewhere, it may be the problem:

"As I know, the lock request clause was introduced with DB2 v8.1 FP7
which matches the first release of v8.2."
Nov 7 '08 #2

P: n/a
On Nov 7, 9:39*am, flea2k <jeremyt...@gmail.comwrote:
I just read this somewhere, it may be the problem:

"As I know, the lock request clause was introduced with DB2 v8.1 FP7
which matches the first release of v8.2."
I updated to fixpack 17 and the problem went away so it was a version
issue.
Nov 7 '08 #3

P: n/a
"flea2k" <je********@gmail.comwrote in message
news:fc**********************************@e38g2000 prn.googlegroups.com...
On Nov 7, 9:39 am, flea2k <jeremyt...@gmail.comwrote:
I updated to fixpack 17 and the problem went away so it was a version
issue.
Since you were previously running FP 0 (8,1 GA code) before upgrading to FP
17, and there are on average over 300 APARs fixed in each fixpack (usually
more), you have also resolved at least 5,099 other problems.
Nov 7 '08 #4

This discussion thread is closed

Replies have been disabled for this discussion.