Re: How to drop an inconsistant chunk?

David Williams (djw@smooth1.demon.co.uk) wrote: : In article <338e95fc.8326392@PersonalNews.Germany.EU.net>, Lutz : Wiggershaus <wiggershaus@bdv2.un.eunet.de> writes : >After restoring a chunk from a level 0 archive without restoring the : >logs the chunk remains inconsistant. We are not able work with this : >chunk any more. Even dropping it is impossible. (onspaces -d <dbspace> : >leads to "Dbspace is not empty", onspaces -d -p <device> -o offset : >leads to "cannot drop first chunk") : >There are only two solutions of this problem: : >1. oninit -isy : >2. Calling Informix Tech Support. They log on to the machine and drop : >the chunk. : >Does anyone know, what they are doing or is there any other possible : >solution to this problem? : >We are using Online 7.20 on SCO ODT 5.0. : > : >Thank in advance. : > : >Lutz Wiggershaus : Run onspaces -- , there is an option to mark a dbspace as up or down. Probably won't work but worth a try. Informix "cannot drop first chunk" so he thinks there's some sort of data there that he wants to get rid of first before dropping the chunk...you can't get there from here. One of the techniques that Informix Tech Support uses is going into the rootdbs and twiddling bits in order to change a flag that makes OnLine think that it's a blobspace. Supposedly, that's easier for them to drop. Anybody with more specific info? Joe -- : David Williams -- --------------------------------------------------------------------------- Joe Lumbley(jlumbley@netcom.com) ---------------------------------------------------------------------------