Don, I'm afraid that you cannot generate a new db2 instance with 'one shot' with the BMC tools.
I think that the shortest way is restoring the backup objects with another alias, changing the VCAT related informations in BSDS, regenerating the dsnzparm for the new subsystem and creating new storage groups with the new VCAT for the user objects.
- Stop DB2
- Backup of db2 subsystem and user data
- Restore with new name (if needed)
- DSNJU003 to change the names of vcat and active logs
- Update of procs in proclib
- Insert new application environments in wlm
- Creation of new storage groups with new VCAT and new volumes
- Drop and create of DSDB07 temporary tablespaces with the new names
Of course i suggest to do some tests before creating the "gold" test subsystem.
Just a note... migrating to version 9, the VCAT handling is much more easier
Sorry, I have a dumb question? Are your steps describing a BMC or conventional restore?
Our database contains over 700 tables with a few tables containing several million rows. I need to convince management that a restore is much easier and quicker than recontructing a test database using all its production tables. So is it possible to give me a rough estimate of time the restore would take?
First of all thank you for the information you have provided me.
Since I'm not a DBA, is there anyway I can explain in layman's terms, what I propose to do (which is your suggestions) to management. Our currect process for building a test sytem is unloading and loading each of the 700 plus tables from prod to test. It's taken a month to clean up the errors on our second test build. It seems to me to be resource extensive and kind of ludicrous