No, it won't. But you have to do a redirected restore.
Originally Posted by oracle10gsingh
Tagging or untagging is not the issue. The problem is that a container is already in use - as SQL0294 says. When you back up a database, the backup image contains the absolute path to the various containers of the tablespaces. During RESTORE, DB2 tries to place the containers into the exact same location. But since the original database still exist (and you probably didn't restore into the existing database), DB2 cannot create files with the same name for the new (restored) database. So you get the error.
2.when i am restoring it gives me a error SQL0294N to untag the containers ..now the containers in reference here are of the source database or the target database ? since i am creating a database while restoring only .its shouldnt give me such a error so does it mean its accessing the source database or within a backup image containers need to be untag ?
What you have to do is to specify different locations for the containers of the restored database. For that, you have to apply a restored with the REDIRECT option. You start the restore with this option, the restore stops in the middle, you specify new locations for the containers, then you continue the restore and the containers will be created in the new locations. Thus, you won't get any collisions with containers from other databases.
IBM DB2 Analytics Accelerator
IBM Germany Research & Development