how to check chuncknumber 2 page 346207

Posted in 2006

Topics: Versions, Editions & End-of-Life

Danny De Koster — Wed, 13 Sep 2006 16:27:48 +0200 — source: Usenet: comp.databases.informix

Hi all, I have a problem with a table. Doing an oncheck -cDI dabasename:tablename gives a problem in 2:346207. How can I check and repair that place and solve the problem? IDS 9.40.UC2 Linux SuSe 8.2 thanks for any tips. Danny

↪ replying to Danny De Koster

RoB via DBMonster.com — Wed, 13 Sep 2006 14:52:05 GMT — source: Usenet: comp.databases.informix

Re-run the oncheck -cDI and if the problem is still there then oncheck couldn't fix the it. What is the output from oncheck -cDI? Does the engine Assert Fail (AF) when accessing the rows on that tblspace? Is this tblspace for a table or index? If it's an index then just try dropping and recreating the index. Otherwise you might have to unload around the bad rows (all rows on that page) in the table if the engine AFs each time you access those rows. Try unloading all rows in the table to see what happens? If it finishes successfully without any AFs then you could just recreate the table and then load it again. Your interim version (xC2) is very old so this problem might have been caused by a bug in that release. Interim version 9.40.xC7 (or perhaps higher) is available. Personally I would NEVER NEVER NEVER NEVER EVER use any IDS interim below .xC4 in a production environment unless you REALLY LOVE dealing with product defects (speaking as an ex-advanced tech-support engineer). -- Message posted via http://www.dbmonster.com

↪ replying to RoB via DBMonster.com

ddk24 — Wed, 13 Sep 2006 15:46:30 GMT — source: Usenet: comp.databases.informix

Hi Rob, Since I'm rather new, can you help me to unload around the bad rows?? Thanks, Danny RoB wrote: >Re-run the oncheck -cDI and if the problem is still there then oncheck >couldn't fix the it. > >What is the output from oncheck -cDI? >Does the engine Assert Fail (AF) when accessing the rows on that tblspace? > >Is this tblspace for a table or index? If it's an index then just try >dropping and recreating the index. > >Otherwise you might have to unload around the bad rows (all rows on that page) >in the table if the engine AFs each time you access those rows. Try unloading >all rows in the table to see what happens? If it finishes successfully >without any AFs then you could just recreate the table and then load it again. > >Your interim version (xC2) is very old so this problem might have been caused >by a bug in that release. Interim version 9.40.xC7 (or perhaps higher) is >available. Personally I would NEVER NEVER NEVER NEVER EVER use any IDS >interim below .xC4 in a production environment unless you REALLY LOVE dealing >with product defects (speaking as an ex-advanced tech-support engineer).