rootdbs offset change
Posted in 1999
Topics: Storage & Space Management
Need to change the primary chunk rootdbs offset from 0 to 5. We were going to mirror the chunk and have the mirror have the new offset then drop the primary and then copy back from the mirror. Informix will not let us delete the primary chunk even if it is mirrored (this is only for the root chunk - dbspace. Any suggestions? Anyone out there gone through this procedure or one that works? Regards Walter Walls 201.352.6007 wwalls@erols.com Sent via Deja.com http://www.deja.com/ Before you buy.
Idue to the inflexibility of Informix, and its demand that chunk names and offsets remain consistent, I think you're stuffed. The mirroring feature you refer to is common to all dbspaces. I think your best bet is to take a level 0 archive, then use an OS tool to reposition your primary chunk to where you want it. then you can restore. If you're brave, you can achieve the same with dd. Neil Truby Londis Stores Hampton Hill, UK wwalls@erols.com wrote in message <81uhsb$u5t$1@nnrp1.deja.com>... >Need to change the primary chunk rootdbs offset from 0 to 5. We were >going to mirror the chunk and have the mirror have the new offset then >drop the primary and then copy back from the mirror. Informix will not >let us delete the primary chunk even if it is mirrored (this is only for >the root chunk - dbspace. Any suggestions? Anyone out there gone >through this procedure or one that works? > >Regards > >Walter Walls >201.352.6007 >wwalls@erols.com > > >Sent via Deja.com http://www.deja.com/ >Before you buy.
In article <81uhsb$u5t$1@nnrp1.deja.com>, wwalls@erols.com wrote: > Need to change the primary chunk rootdbs offset from 0 to 5. We were > going to mirror the chunk and have the mirror have the new offset then > drop the primary and then copy back from the mirror. Informix will not > let us delete the primary chunk even if it is mirrored (this is only for > the root chunk - dbspace. Any suggestions? Anyone out there gone > through this procedure or one that works? Why add the offset? Are you running on a Sun or AIX using native partitions? How about mark the primary down, repartition so the first cylinder of the drive is NOT part of the first partition, now bring the chunk back online. At least on Solaris only the first partition of each drive has the offset requirement. BTW if you are using soft links, as you should, then you can bring the engine down, copy the primary chunk's data to a new partition without the vtoc problem with dd, change the soft link to point to the new partition device, restart the engine. Informix will never know anything happened at all. Art S. Kagel Sent via Deja.com http://www.deja.com/ Before you buy.