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

SET integrity fails despite of for exception...

P: n/a
I was runing load and then set integrity with for exception clause,
still the statement failed , there are some reecords in the exception
table but the actual table is still in check pending state...what s
causeing this?? i was under impression that if i use for exception the
set integrity statemtn should never fail, since it inserts all vilating
rows into exception table....
any help appreicated

the set intergrity st used is...

SET INTEGRITY FOR schema.table IMMEDIATE CHECKED FOR EXCEPTION IN
schema.table USE schema.except_table

Apr 19 '06 #1
Share this Question
Share on Google+
3 Replies


P: n/a
technocrat wrote:
I was runing load and then set integrity with for exception clause,
still the statement failed , there are some reecords in the exception
table but the actual table is still in check pending state...what s
causeing this?? i was under impression that if i use for exception the
set integrity statemtn should never fail, since it inserts all vilating
rows into exception table....
any help appreicated

the set intergrity st used is...

SET INTEGRITY FOR schema.table IMMEDIATE CHECKED FOR EXCEPTION IN
schema.table USE schema.except_table


What's the error message that you got?

--
Knut Stolze
DB2 Information Integration Development
IBM Germany
Apr 19 '06 #2

P: n/a
Unfortunately I did not print stack....but the following execute
statemtnts like loading the next table didnt work. ...the error while
loading the next table was...

COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver][DB2/6000] SQL20139N
SQL statem ents may not be issued in routine
"CONTROL.INIT" (specific name "SQL060413135154
100") because of a previous statement failed or was interrupted.
SQLSTATE=51038
Also today morning I checked the state of the table which and for some
unknown weird reason the table was in normal state and accessible...

Any one has any idea whats going on?

Apr 19 '06 #3

P: n/a
I know now that the table was in normal state in the morning becuase i
had run set integrity command (while i got disc while executing and
assumed that ,that session would be disconnected)
But I have no idea till now why the set integrity failed the frst time.

Apr 19 '06 #4

This discussion thread is closed

Replies have been disabled for this discussion.