I worked with Tech Support on this one for several days once. In my DBA Guide (for Unix, Ingres release 6.4--we're running on an SGI with the 5.2 OS), it said I would actually have to *reinstall* INGRES from tape, which I definitely did not want to do. I was able to simplify things somewhat, but I still had to unload and reload every database. Here are the steps: 1) unload all databases 2) destroy all databases 3) rerun iibuild, supplying new locations 4) reload all databases Note: Destroying all databases includes getting rid of the iidbdb, mainly by deleting all the files under $II_SYSTEM/ingres/data/default/iidbdb. Remember to unload the database first, just in case. When iibuild runs, it looks for the existence of the iidbdb, and if it doesn't find it, it creates it. But you have to get rid of it before you can assign a new checkpoint location during the iibuild. Once you're through with the build, recreate the databases and reload them. Sorry it is still going to be time consuming for you. But at least you don't have to reinstall! And I should think it would be a bit safer than creating a symbolic link. Good Luck. --- Karen Robinson Database Administrator Member-at-Large, Colorado INGRES Users Association University of Colorado at Boulder 303 492 1504 robinson@shiver.colorado.edu Jim Athertonwrites: >Running Ingres 6.4/04 (on a Sequent Unix box) is it posible to simply >change the checkpoint location without having to go to the trouble of: >1) unloading the database >2) destroying the database >3) (re)creating the database (with different checkpoint location) >4) reloading the database >For a large database this is somewhat time-consuming, to >put it mildly! >There seems no flexibility with this whereas with the actual data >more than one location can be employed with the prospects of moving >data "on the fly" using modify xxxxxx to reorganize/relocate, etc. >Any ideas anyone. >Cheers, >Jim Atherton
© William Yuan 2000
Email William