Printable View
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 source database is production which I can not possibly make read only during christmas holiday season.
So this is a partition that is still subject to data changing, or is it just sharing a TS with other data that might change?
What's your version?
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.
Do you (or the developers) really need 22GB partition in development env? I don't think so.Quote:
Originally Posted by newbie5
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.
Tamil
The development says it is working on a sev1 ticket and for whatever reason needs the entire 22Gigs of data.
I am doing an exp/imp. I heard of fast reader. What is it? Is it any faster really?
why should an export/import be better then a copy over a DB link?Quote:
Originally Posted by newbie5
Wouldnt the exp/imp need a huge UNDO segment for a table of size 22GB? How long does the whole export operation of the table take.
Thanks.
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.
A 22gig direct export of a table partition is taking 10 hours. Surprisingly the dmp file size is 32GB. How so? When I gzipped it it shrunk to 3GB.
your system is slow
I have exported several +200 gb size database under 5 hours and the i/o system werent 100% optimized
Production database is 6.5T. 18CPU. Memory 56G. Oracle 9.2.0.5. We are not there on 10g - hence can not use data pump. There are users the batch jobs while export is going on.
I did not use data pump neither
how long does a insert parallel via db link take?