logging mode of table has effective in performance of impdp utility.
test scenario:
table test has rows 480W .
1, expdp scott/tiger directory=diskc dumpfile=outp1.dmp tables=test
--470MB
2, expdp scott/tiger directory=diskc dumpfile=outp2.dmp tables=test compression=all
--160MB, use compression to reduce I/O with same or less time.
1, table with logging .
impdp scott/tiger directory=diskc dumpfile=outp1.dmp tables=test
time costs: 108s, and there are many archived log produced.
2, table with nologging .
impdp scott/tiger directory=diskc dumpfile=outp1.dmp tables=test
impdp scott/tiger directory=diskc dumpfile=outp2.dmp tables=test
whether dumpfile compressed or not , time costs are nearly same: 38s,there is not archived log produced.
3, use parameter table_exists_action=append , to load data into table which is exists in the dest schema. The definition of dest table is not changed (including logging mode is not change by impdp).
--------the table logging mode characteristic is similar in every scenario.Such as impdp, sqlldr, insert /*+append */ ...
[@more@]
来自 “ ITPUB博客 ” ,链接:http://blog.itpub.net/350519/viewspace-1042142/,如需转载,请注明出处,否则将追究法律责任。
转载于:http://blog.itpub.net/350519/viewspace-1042142/