Hi,
in my case setting the datapump's parameter segement_creation to the
non-default value 0 (this value prevents the creation of segments for empty
objects) saved me Terabytes of space and many hours of processing (creating
segments of millions of empty partitions is time consuming).
So the question, is there any reason or other use case behind the choice of
the default value of this parameter, or maybe the default values are
generally chosen haphazardly?
And why oracle introduces this parameter in datapump, which overrides the
system parameter deferred_segment_creation, even the last one can be
changed at session level? (one can use loggon trigger for datapump outside
pl/sql)
Best regards
Ahmed
-----Original-Nachricht-----
Betreff: AW: datapump and deferred_segment_creation
Datum: 2021-05-13T10:04:41+0200
Von: "ahmed.fikri@xxxxxxxxxxx" <ahmed.fikri@xxxxxxxxxxx>
An: "ahmed.fikri@xxxxxxxxxxx" <ahmed.fikri@xxxxxxxxxxx>,
"andy@xxxxxxxxxxxxx" <andy@xxxxxxxxxxxxx>
thanks Andy and Dimitre!
the parameter SEGMENT_CREATION is working.
Best regards
Ahmed
-----Original-Nachricht-----
Betreff: AW: datapump and deferred_segment_creation
Datum: 2021-05-12T17:03:12+0200
Von: "ahmed.fikri@xxxxxxxxxxx" <ahmed.fikri@xxxxxxxxxxx>
An: "andy@xxxxxxxxxxxxx" <andy@xxxxxxxxxxxxx>
Thanks Andy.
I'll check if it is working for Table and Index partitions.
However, I wonder the default value of the parameter SEGMENT_CREATION is
set to Y, whereas deferred_segment_creation is set to true.
Best regards
Ahmed
-----Original-Nachricht-----
Betreff: Re: datapump and deferred_segment_creation
Datum: 2021-05-12T16:52:29+0200
Von: "Andy Klock" <andy@xxxxxxxxxxxxx>
An: "ahmed.fikri@xxxxxxxxxxx" <ahmed.fikri@xxxxxxxxxxx>
Hi Ahmed,
Is there any way to prevent oracle allocation 1M space for emptypartitions while using datapump.