Allow datapump to replace non-table objects

Richard Harrison .

Hi,

An often asked question on the forum (asked again today) is to let datapump replace objects other than tables.

Currently TABLE_EXISTS_ACTION=REPLACE allows tables to be dropped and recreated but all other objects (well other than indexes indirectly by tables being dropped) such as functions/procedures/packages all fail to create as the objects already exist. It would be great if there was another setting to force the replacement of other objects - this should be easy to do as all that needs to change is the adding of 'or replace' to the create command.

Cheers,

Rich

caadecarvalho

That would help a lot to deploy procedures and packages! Nice one!

bhagatsingh

Hi,

This is really great idea. Every time, i have drop procedure/sequences before doing the import. else it skips this objects.

like table_exists_action, oracle can introduce parameters like procedure_exists_action, sequence_exists_action like this.

Regards

Rajkishore

MartinKlierDBA

Very good idea, would save us several steps.

himmy

I would not agree with this idea , what if there is an unwanted change in code of trigger or functions , you could possibly not troubleshoot it without the help of developer

Gbenga Ajakaye

This would definitely save me a lot of time. Please implement ASAP. +

Andreas Huber

I would not agree with this idea , what if there is an unwanted change in code of trigger or functions , you could possibly not troubleshoot it without the help of developer

Where is the problem?

If you don't use the new option it will not be used and there will be no change to the old behaviour.

You don't have to use the table_exists_action as well.

EricKR-Oracle

+1