I didn't see any "create a database in staging server" in your original post; you added it after I pointed your strategy wouldn't do it.
Duplicating a database from datafiles/archivelogs/controlfiles/... works all the time; I will love to see you working out your exp/imp strategy in a medium size database... lets say as small as 500Gig in size.
If you want to suggest a solution that has a size constraint, better to ask OP for the size of the database, then, if applies, suggest it. Simple isn't
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.
Just a couple of minor changes... in the blue color
Originally Posted by bhattnirav
Will it be work with 24*7 DB?
Put production database in backup mode
Force checkpoint
Copy datafiles to staging server.
Create controlfile script from production database.
Take production database out of backup mode
Transfer archive logs to staging server.
Rename database by creating controlfile. The script is created from production database like
CREATE CONTROLFILE REUSE SET DATABASE "STGDB" RESETLOGS ARCHIVELOG
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.
Bookmarks