We use redirected restore to refresh test from prod on different AIX 5.2
servers. The databases have the same number, size and names of cooked
containers. The only difference is the fully qualified path contains a
different "SID": eg. "/db2/PRD/data1/..." versus "/db2/TST/data1/...".
(Please note as an SAP installation I cannot change this layout).
We use "set tablespace container" statements to redefine the fully
qualified container names. During the restore the existing containers are
dropped and new containers are created. This process takes a long time.
My question is, can we somehow avoid re-creating these containers. For
example, what would happen if we just created a symbolic link PRD->TST so
that the restore would find the existing containers? (I've done this
successfully using Informix raw devices.)
Or, do the containers need to be re-created for a valid restore?
Thanks,
Chris
--
Message posted via http://www.dbmonster.com