I working on developing a test plan for a fallback procedure for the migration of UDB ESE 8.1 in test environment.

After a successful migration to version 8.1, I dropped the instance and created Version 7.2 instance, with a plan to restore the database with replace. That didn't work, it gave an error SQL0294N container already in use.

Any body has any clue on this, if any body has gone through this excerise I appreciate if you can share your experiences
Krishna

You would need to keep the old 7.2 instance, create a new 8.1 instance and move the data over with db2look (or similar method). Then point the applications to the new instance. For fallback, re-point applications to the old instance.

This will not work on a DB2 for Windows database server, since you can only have one version of DB2 running under Windows (not sure if this has changed in 8.2).

Thanks Marcus_A for your reply. We are on AIX box,

For fall back, this is what I would do..never tried it though

drop the database
Stop all UDB and DAS instances
logon as root, and drop the UDB instance
/usr/opt/db2_08_01/instance/db2idrop database-alias
Drop the DAS instance
/usr/opt/db2_08_01/instance/dasidrop das-instance

follow either 1 or 2
1) Create the V7 instance
logon as root, and create the UDB instance
/usr/lpp/db2_07_01/db2icrt -ufencedid instancename
Create the Das instance -
/usr/lpp/db2_07_01/instance//dasicrt instancename
go to 3

2) Restore V7 instance
Go to the home directory of the UDB instance. Remember that the directory that was rename DURING THE v8 migration is SQLLIB_v7. Change the directory back to SQLLIB. For example
mv sqllib_v7 sqllib


3)db2start command
Run db2level command to ensure that you are running UDBv7
Restore database from the backup taken before migration