Copying a 22Gig partition from Production to Development
I need to copy a 22G partition from our production to development database.
What is the best way to do this with minimum time spent on resources. I am under the impression that transportable tablespaces feature needs the datafiles in read only mode which I can not do in production. Is it true?
if you want the minimum resource usage on production then TT would be the way to go ... readonly is a requirement of the source database, not the target one, no?
The easiest way would probably be to just copy it via DB link.
One way which would use no ressources on the Prod Server would be to restore your Prod backup on the Dev server and then copy your data from this new DB into your Dev DB.
I need to copy a 22G partition from our production to development database.
What is the best way to do this with minimum time spent on resources. I am under the impression that transportable tablespaces feature needs the datafiles in read only mode which I can not do in production. Is it true?
Do you (or the developers) really need 22GB partition in development env? I don't think so.
What you should do is create a partition and insert sample data (may be around 100,000 rows) and update the statistics manually to several million rows. This can be easily achieved through exp/imp with minimum overhead on prod server.
Do the prod and developer databases use the same os? Do you backup your database? Have you tested your restore procedures lately? Why don't you just restore from the backup? If it is a question of disk space, you can always remap the drives as raid 0 while you are doing your testing.
Bookmarks