Re: drop empty dbspace & primary chunk

cc9f500 12 1 12 1 N informix testgldbs cc9eca0 12 12 0 1000000 999697 PO- /work/informix/data/testgl.dbs bbanksig{informix}/sfw/informix/shells>onspaces -d testgldbs -p /work/informix/data/testgl.dbs -o 0 WARNING: Dropping a chunk. Do you really want to continue? (y/n)y Chunk not dropped. ISAM error: Can not drop first chunk I dropped the database I was attempting to dbimport but I got the same result when trying to drop the dbspace. How can I drop "testgldbs" dbspace? I want to use another disk with raw devices for the chunks. Regards, Denmark W.

You don't have to specify the chunk if you're dropping the dbspace & primary chunk. Just do onspaces -d testgldbs Erickson In article <95rsa5$kki$1@news.xmission.com>, "Denmark B. Weatherburn" <dweatherb@btl.net> wrote: > > > cc9f500 12 1 12 1 N informix testgldbs > cc9eca0 12 12 0 1000000 999697 PO- > /work/informix/data/testgl.dbs > > bbanksig{informix}/sfw/informix/shells>onspaces -d testgldbs -p > /work/informix/data/testgl.dbs -o 0 > WARNING: Dropping a chunk. > Do you really want to continue? (y/n)y > Chunk not dropped. > ISAM error: Can not drop first chunk> > I dropped the database I was attempting to dbimport but I got the same > result when trying to drop the dbspace. > How can I drop "testgldbs" dbspace? > > I want to use another disk with raw devices for the chunks. > > Regards, > > Denmark W. > > Sent via Deja.com http://www.deja.com/

Denmark B. Weatherburn wrote in message <95rsa5$kki$1@news.xmission.com>... > If you need to drop chunks in a dbspace, you'll have to drop the end ones. The first one has critical data in it - you know, the kind that tells you it doesn't like your wallpaper. If you want to shift the data in a dbspace (or some chunks) and you have been smart enough to setup symbolic links, then you will be able to dd all chunks in a particular "device" to another device that may be rawer. What I mean is, if you've declared and defined a cooked file /work/informix/data/testgl.dbs and then you added one or more chunks into that space - ie 100Mb at offset 0, 100Mb at offset 100Mb, etc to a total of 500Mb then you will need to allocate a raw space of 500mb, dd the contents of /work/informix/data/testgl.dbs to the raw chunk and reset the symbolic link to point to the raw chunk instead of /work/informix/data/testgl.dbs. If you HAVEN'T used symbolic links, then you are lucky because you can start to do that. You need to remove the file /work/informix/data/testgl.dbs after copying it, then make a symbolic link of that same name in the same directory which points to your raw space. People who've used the names of actual raw devices have sod-all chance of replacing them with symbolic links, and they will get into trouble if a disk dies and they install a new one with unavoidably different device names. They COULD mess around and spoof the device names but that's way too ugly to contemplate, and very risky because future people have to notice and understand the mess that's been made in the /dev directory. BTW All this must be done with the engine offline! And take an archive first. And write down all the before-names of the files, because if you revert to the archive due to screwing up this process, those files had better be there.