Doug, you can select on syscat.constdep where constname=' SQL021007103120890' The cols will identify for you which table(table_x) and also btype identides which object(ie, I for index) and bname, the object name. I suspect most likely you may be encuntering a unique viloation on a PK or something of the sort. HTH, Pierre. ----- Original Message ----- From: "Doug Carter" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, February 20, 2003 1:46 PM Subject: [DB2EUG] integrity violation
> > Hi all, > > When attempting to set integrity, I occasionally get a strange error: > > SQL3603N Check data processing through the SET INTEGRITY statement has found > integrity violation involving a constraint with name > "FOO.TABLE_X.SQL021007103120890". SQLSTATE=23514 > > I'm running the command: > > db2 SET INTEGRITY FOR FOO.TABLE_X IMMEDIATE CHECKED > > I know this is not a lot of info to go on, but is there something > easy (obvious) to correct this problem? > > TIA, > > Doug Carter > WebCriteria > > > > - > ::: When replying to the list, please use 'Reply-All' and make sure > ::: a copy goes to the list ([EMAIL PROTECTED]). > *** To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED] > *** For more information, check http://www.db2eug.uni.cc - ::: When replying to the list, please use 'Reply-All' and make sure ::: a copy goes to the list ([EMAIL PROTECTED]). *** To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED] *** For more information, check http://www.db2eug.uni.cc
