This content has been marked as final. Show 6 replies
Data Pump can use 3 different methods for loading data. It can use 'direct path', 'external table', and 'conventional mode'. I don't have a great understanding of all of these, but I would think that the last 2 would use more redo log than direct path. What you are proposing to get around the logging would be the way I would attempt it. You could try this on a small scale to see if it accomplishes what you need it to. (Try it without disabling logging and then with disabling logging and then compare the difference.) From what I have been told, you will see a lot less redo that way.
also, if you want to force direct path you can do:
By forcing direct path, some data may not be able to be loaded. Direct path does not support all object types.
Hope this helps.
You can do what you want to do in one step.
Set your tablespace(s) to nologging and then add this clause to the impdp command
the logging clause is then removed from the create table statement and it makes the whole process much easier.
Then you set everything back to logging afterwards.
Just for my curiosity, may i ask why this whole worry about redo generation?
like i said, just curiosity.
Edited by: rjamya on Jan 10, 2013 7:35 AM
I am trying to reclaim space in the DB which involves moving objects around. The DB is setup with a Data Guard replication to a DR site. I wanted to avoid excessive redo log generation as we have consistent problems with our bandwidth between the sites, causing log shipping to slow down or fail.
This is very helpful. I have setup a VM to test this. I will revert back with my findings but I think I have found what I was after. Thank you.
Oh actually. The database is in force logging mode, due to the use od Data Guard. This will overturn the no logging setting on the TBS level right?