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

DB2 ver 7.1 Processing was cancelled due to an interrupt

P: 8
Hi,

I feel I am going nuts trying to figure out something and get into other problems.
I have a DB2 UDB Enterprise Edition version 7.1. I recently upgraded to FixPack 14.
I try to update a column for a table, but it doesn't happen anything.
I used the following command in the Command Center:
UPDATE USER.T2 SET TEST = 'A'

And sometimes the result says:
------------------------------ Command Entered ------------------
UPDATE USER.T2 SET TEST = 'A'
-----------------------------------------------------------------------------
and nothing else.
When I try to see the content of the table, I type a simple command:
SELECT * FROM USER.T2
and the table shows the column TEST with the old values. Nothing changed.

Sometimes for either the UPDATE or the SELECT command, I get this error:

DB21034E The command was processed as an SQL statement because it was not a valid Command Line Processor command. During SQL processing it returned:
SQL0952N Processing was cancelled due to an interrupt. SQLSTATE=57014
SQL0952N Processing was cancelled due to an interrupt.

(For example when I have this error for the SELECT command, and I try to press CTRL + ENTER the second time to execute the command, it will show the results. But still the UPDATE command doesn't change anything)

Does it mean that it is something wrong with my DB2 installation?

Best Regards,
Steven
Jul 17 '07 #1
Share this Question
Share on Google+
3 Replies


P: 10
Jal
Looks like you are using DB2 Command editor. Instead try using db2clp.
To Invoke db2clp type db2cmd in the Run window or on the command line.
Aug 17 '07 #2

P: 8
Hi,

Is it better to use the db2clp? In the Command Editor is easier to change the commands. Editing is more user friendly. Is it not supposed to have the same result?

Steven
Aug 21 '07 #3

P: 10
Jal
I trust db2clp more. GUI features from IBM are not worth talking about. They are painfully slow.
I know why people dont like the command line. An easier way out is to use the option db2 -t to get into the db2 environment (This enables ; as sql command terminator, so you can write multiline sql queries. Remember to end yr queries with a ; semicolon).
Write and edit you queries in a notepad, copy and paste to the db2clp to run the command.
Its definitely better than 'Command Editor'.

Jalaj
Aug 21 '07 #4

Post your reply

Sign in to post your reply or Sign up for a free account.