BAD BLOB PAGE

Posted in 2006

Topics: Storage & Space Management, Migration, Import/Export & Data Conversion

Habichtsberg, Reinhard — Mon, 25 Sep 2006 15:21:53 +0200 — source: Usenet: comp.databases.informix

INFORMIX-OnLine Version 7.24.UC3 ReliantUNIX-N 5.45 We have a problem with a table of a SAP database. It's impossible to unload the table. The error is that a blob data cannot be found. The result of oncheck -cd database:table: TBLspace data check for database:table BAD PAGE 5f303f7: pg_addr 5f303c5 != bp->bf_pagenum 5f303f7 What could be done to repair the table? Any help is appreciated. Reinhard.

↪ replying to Habichtsberg, Reinhard

scottishpoet — 25 Sep 2006 06:44:56 -0700 — source: Usenet: comp.databases.informix

install a previous archive that did not contain the corruption and roll forward the logs alternatively youwould need to unload around the corruption, drop the tabel and reload without the abd rows Habichtsberg, Reinhard wrote: > INFORMIX-OnLine Version 7.24.UC3 > ReliantUNIX-N 5.45 > > We have a problem with a table of a SAP database. It's impossible to unload > the table. > The error is that a blob data cannot be found. > > The result of oncheck -cd database:table: > TBLspace data check for database:table > > BAD PAGE 5f303f7: pg_addr 5f303c5 != bp->bf_pagenum 5f303f7 > > What could be done to repair the table? > > Any help is appreciated. > Reinhard.

↪ replying to Habichtsberg, Reinhard

scottishpoet — 25 Sep 2006 06:45:02 -0700 — source: Usenet: comp.databases.informix

install a previous archive that did not contain the corruption and roll forward the logs alternatively youwould need to unload around the corruption, drop the tabel and reload without the bad rows Habichtsberg, Reinhard wrote: > INFORMIX-OnLine Version 7.24.UC3 > ReliantUNIX-N 5.45 > > We have a problem with a table of a SAP database. It's impossible to unload > the table. > The error is that a blob data cannot be found. > > The result of oncheck -cd database:table: > TBLspace data check for database:table > > BAD PAGE 5f303f7: pg_addr 5f303c5 != bp->bf_pagenum 5f303f7 > > What could be done to repair the table? > > Any help is appreciated. > Reinhard.