RE: Fragmented dbspaces

As well as John's reply .. 1. Plan the placement you would ideally like. You cannot change rootdbs, and your logical logs may be hard to change. 2. Reserve these spaces. 3. Create your logical structure based upon your old system to perform the restore - from the disk available. 4. After the restore add new dbspaces to hold your tables. 5. As time permits alter your next size, and move tables with Alter Fragment statement. 6. When all tables are moved, drop the old empty dbspaces. MW -----Original Message----- From: owner-informix-list@iiug.iiug.org [mailto:owner-informix-list@iiug.iiug.org]On Behalf Of malc_p@my-deja.com Sent: Thursday, December 07, 2000 12:49 AM To: informix-list@iiug.org Subject: Fragmented dbspaces Yup, dbspaces *not* fragmented tables. Our system holds about 75Gb on a mixture of 4.3Gb & 9Gb disks, raw chunks, HP-UX 10.20, IDS7.31. When it was built we ran some predictions re. growth and so on based on the figures given to us by the business analysis group, upon which we based our data distribution strategy; the upshot being that we settled on a dozen or so dbspaces, some holding tables that were fragmented by example. Anyway, over the last three years the data has grown at a different rate from that envisaged, and we have had to extend some dbspaces by adding new chunks when necessary. Unfortunately, due to financial restrictions and a blinkered IT management structure, the extra chunks added to some of the dbspaces has meant that some have got several chunks on several disks. So a 15Gb space may have a 10Gb initial chunk and 5 1Gb chunks, all on separate disks. This is obviously not optimal. We are just about to move disk technology and therefore shortly we are to move the data from the old disks to the new. The business cannot cope with a protracted downtime (24 hours max), so we HAVE to accomplish this by using a Level-0 archive from the old system and restore this (using ontape) to the new system. In order for ontape archive/restore to work, the target structure has to be identical. What I'd like is to consolidate the dbspaces chunks into a single chunk per dbspace. Any clues as to how we can do this - I've got a feeling someone will say 'use HPL to export all the tables, build a new instance and reload the tables'. That will take about 5 days, so not an option. Can we restore our L0 ontape to a structure with the same dbspaces (with the same total sizes) but only one chunk each? Probably not. Malc Sent via Deja.com http://www.deja.com/ Before you buy.