AW: Re: AW: datapump and deferred_segment_creation

source and target databases are the same. I did the test ln both<http://11.2.0.4> and<http://12.1.0.2> , and observed the same.

The deferred_segment_creation is set to the default value TRUE.

Even in oracle documentation the system parameter and the datapump parameter have contradictory default values. So I'm interested to know whether this is an error from oracle side, or there is a real reason for this?
Please note that changing explicitly the segment_creation solved my problem, I'm just little bit curious.

Thanks
Ahmed

• Original-Nachricht --- Von: Andy Klock Betreff: Re: AW: datapump and deferred_segment_creation Datum: 14. Mai 2021, 19:01 An: ahmed.fikri_at_t-online.de, list, oracle

Hi Ahmed,

"ahmed.fikri_at_t-online.de <mailto:ahmed.fikri_at_t-online.de> " < ahmed.fikri_at_t-online.de <mailto:ahmed.fikri_at_t-online.de> > writes:

> 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)

You still haven't provided any details as to how and what you are really doing. Things like database versions and details of the source and target expdp/impdp may matter.

For example:

Deferred_segment_creation Behavior When Importing in 11g a Dump Created in 10g (Doc ID 1637985.1)

or, was deferred_segment_creation = true set on the database during the expdp?

Thanks,

Andy K

--
<http://www.freelists.org/webpage/oracle-l>




--
http://www.freelists.org/webpage/oracle-l