Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
Database Servers
DB2InformixIngresMS SQLOraclePervasive.SQLPostgreSQLProgressSybase
Desktop Databases
FileMakerFoxProMS AccessParadox
General
General DB TopicsDatabase Theory
Related Topics
Java Development.NET DevelopmentVB DevelopmentMore Topics ...

Database Forum / DB2 Topics / April 2006

Tip: Looking for answers? Try searching our database.

SET integrity fails despite of for exception...

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
technocrat - 19 Apr 2006 04:37 GMT
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
Knut Stolze - 19 Apr 2006 09:35 GMT
> I was runing  load and then set integrity with for exception clause,
> still the statement failed , there are some reecords in the exception
[quoted text clipped - 8 lines]
> SET INTEGRITY FOR schema.table IMMEDIATE CHECKED FOR EXCEPTION IN
> schema.table USE schema.except_table

What's the error message that you got?

Signature

Knut Stolze
DB2 Information Integration Development
IBM Germany

technocrat - 19 Apr 2006 14:26 GMT
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?
technocrat - 19 Apr 2006 14:49 GMT
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.
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.