Migrate from UAT database to Production database

Question

Hi all,
I need to set up my production database based on the UAT database.I would like to re-generate all my objects script and grant scripts from UAT so that there will not be any discripency. I can't go for full db export due to some apps constraints.I'm planing to generate grant scripts from dba_tab_privs for each role and generate public synonym script from dba_objects for each user.Object inventory can be taken from dba_objects for each user. FK and PK constraints are another worry.
Am I on a right path?? My worry is that, I may miss out something. Can anyone guide me?

Answer 1

I think Bhandari's advice is good as long your UAT and PRODUCTION on the same OSWhat about the data? UAT is going to full of rubbish data that nobody would want in a production system. But you wouldn't want to zap it from UAT because you'll need it for the next release (patch, enhancement, whatever). So you copy it all over into Production and then remove everything that's not supposed to be there? Starting a release by trashing the data in production doesn't sound very clever to me. Furthermore it's a complete non-starter for managing an incremental release.
Using Import/Export isn't much better. Neither is generating scripts from the UAT data dictionary. Forget about Release 1.0! Think about how you're going to manage 1.1!
The simplest, the least effort, the most robust approach is to create Production from the scripts that were used to build UAT. Anything else is more complicated, more work, less reliable. The only reasons why anybody might need to take some other approach are because they didn't build UAT entirely with scripts or because they didn't subject those scripts to source control. And that's what I mean by bad processes.
LALEAGTFOTP!
Cheers, APC