how to restore archive to 2 instances on same server

We have a development server with 3 instances of the engine running. 2 of the instances contain copies of the production databases from the production server. The copies are to be updated frequently. This can be done with a lenghy dbexport/dbimport but I would rather use ontape and restore a level 0 archive. This can easily be done with one of the instances as I can create device names match the production instancebut I am not sure about the other. Would it be possible to do something like the following: assume device dir is /dev/rdsk production server: rootdbs : slice1 : ln -s slice1 c0b0t0d0s1 dev instance1 rootdbs: raw1 : ln -s raw1 c0b0t0d1s1 dev instance2 rootdbs: rawa : ln -s rawa c0b0t0d1s2 but when i go to do a restore I create a link from slice1 to raw1 so I have: slice1 --> raw1 --> c0b0t0d0s1 do restore rm slice links create links pointing to instance 2 slice1 --> rawa --> c0b0t0d1s2 How do other people do this ? It its any help, it's IDS 7.30, unixware 7.0.1, database instance ~ 18 Gb

Cannot do it. You can restore that way however, only one of these instances will be able to be in memory at a time and you will have to remember to relink the links when switching. Art S. Kagel Tam McLaughlin wrote: > > We have a development server with 3 instances of the engine running. > 2 of the instances contain copies of the production databases from the > production > server. The copies are to be updated frequently. This can be done with a > lenghy > dbexport/dbimport but I would rather use ontape and restore a level 0 > archive. > This can easily be done with one of the instances as I can create device > names match > the production instancebut I am not sure about the other. Would it be > possible to do > something like the following: > > assume device dir is /dev/rdsk > > production server: > > rootdbs : slice1 : ln -s slice1 c0b0t0d0s1 > > dev instance1 > > rootdbs: raw1 : ln -s raw1 c0b0t0d1s1 > > dev instance2 > > rootdbs: rawa : ln -s rawa c0b0t0d1s2 > > but when i go to do a restore I create a link from slice1 to raw1 so I have: > > slice1 --> raw1 --> c0b0t0d0s1 > > do restore > > rm slice links > > create links pointing to instance 2 > > slice1 --> rawa --> c0b0t0d1s2 > > How do other people do this ? > It its any help, it's IDS 7.30, unixware 7.0.1, database instance ~ 18 Gb

Informix gave us a utility (we can only use it with their permission every time we want to use it) which renames the chunk pathnames in the reserved pages. We too have a need to do what you are talking about (SAP). I think it's call TBCHKSAP. Bill -- Bill Border Agilent Technologies (formerly Hewlett-Packard) bill_border@agilent.com Low-Cost UX-Based Oracle/Informix Monitor: http://dbamon/com Tam McLaughlin wrote in message <8nb9uf$163$1@neptunium.btinternet.com>... >We have a development server with 3 instances of the engine running. >2 of the instances contain copies of the production databases from the >production >server. The copies are to be updated frequently. This can be done with a >lenghy >dbexport/dbimport but I would rather use ontape and restore a level 0 >archive. >This can easily be done with one of the instances as I can create device >names match >the production instancebut I am not sure about the other. Would it be >possible to do >something like the following: > >assume device dir is /dev/rdsk > >production server: > > rootdbs : slice1 : ln -s slice1 c0b0t0d0s1 > >dev instance1 > > rootdbs: raw1 : ln -s raw1 c0b0t0d1s1 > >dev instance2 > > rootdbs: rawa : ln -s rawa c0b0t0d1s2 > >but when i go to do a restore I create a link from slice1 to raw1 so I have: > >slice1 --> raw1 --> c0b0t0d0s1 > >do restore > >rm slice links > >create links pointing to instance 2 > >slice1 --> rawa --> c0b0t0d1s2 > > >How do other people do this ? >It its any help, it's IDS 7.30, unixware 7.0.1, database instance ~ 18 Gb > >