Re: response> andrew shaw

From me: >>>What we would like to do, therefore, is somehow back up the data, drop >>>the rootdbs and its chunks, allocate the chunks to 2 different dbspaces, >>>and then restore the data. >>> >>>It seems clear that we cannot use tbunload/tbload for the backups, but >>>even if we use dbunload, how on earth do we drop the rootdbs (or at >>>least deallocate the second two chunks)? >>> >>>Any pointers would be most appreciated. >>> From article <1sr9o3INNrjn@emory.mathcs.emory.edu>, by bmacwill@letterkenn-emh2.army.mil ("B.T. MacWilliams"): > > To the best of my knowledge, you should be able to use dbexport to > output all the data to flat ascii files and it creates an sql file that > will allow you to recreate your database. Pay close attention to the > extent sizes and locking levels because it will not be retained in the > output from dbexport. > > Once this is done and the sql file has been modified to recreate > your database exactly, you can bring Online offline. Go into tbmonitor and > reconfigure your system to look at the new partition for the rootdbs area. > Bring Online up and add your other chuncks. At this point you should be > ready to dbimport the database. Hopefully someone out there will confirm > my recommendations. Good Luck. > Many thanks to you and all who responded via email. I now understand that I can/should 1. Use tb*load since the chunk-preserving store is the archive/restore mechanism. 2. Reinitialize the database via tbinit -i. 3. Not perhaps worry about VTOC on disk. 4. Allocate more than 1 page for the VTOC if present. Andrew Shaw AT&T Bell Labs andrew.shaw@att.com