Re: Informix database reorganization

Joe Lumbley <jlumbley@netcom.com> wrote: : There's one very troubling point about your situation. You are demanding : 100% uptime and your development is "still in progress". Surely you have : separate development and production environments on different machines? : If not, you'll be like a dog chasing its tail. : Good luck.....btw the alter fragment is a good approach. Can ALTER FRAGMENT...INIT IN dbspace be done within the same dbspace? Does this work forever or at some point do you have to do a total re-org? If we move to a new server with different disk layout, what is the best scenario? Do we try to set it up as a secondary instance with a layout like the primary, restore from a backup, organize it like we want it, and try to replicate the changes, then go live? Or does replication require both instances to have the same exact layout? What tricks does replication allow you to get away with? Since we're using BaaN, is it necessary to use the BaaN tools to export and import data into Informix (this = slow) or is it going to be okay to use the Informix export and import utilities? Is the replication thing a waste of time for what we're thinking of doing? What happens if your Informix server dies (like someone takes an axe to the machine, or a flood, hurricane, etc) and you have to try to restore from backups? How similar do the configurations have to be? Can you create the same number of dbspaces with the same names as before, but just large enough to hold your current data? No one has been able to answer this very well for us to get a warm fuzzy on it and we thought this would be an essential part of a disaster recovery plan for our Informix database. Thanks to all who responded to my previous post and didn't laugh too loud! *runs off to chase tail* Jon Freeland<*> eclypse@millerind.com