AW: datapump and deferred_segment_creation
Date: Wed, 12 May 2021 17:02:53 +0200 (CEST)
Message-ID: <1620831773304.1884851.3a98be200ad96b5bfd8a20b7beb1b2799e30d46d_at_spica.telekom.de>
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
-----Original-Nachricht-----
Hi Ahmed,
Take a look at the TRANSFORM parameter with the option for
SEGMENT_CREATION:
<https://docs.oracle.com/en/database/oracle/oracle-database/19/sutil/datapump-import-utility.html#GUID-64FB67BD-EB67-4F50-A4D2-5D34518E6BDB>
Andy K
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Wednesday, May 12, 2021 10:42 AM, ahmed.fikri_at_t-online.de
<ahmed.fikri_at_t-online.de> wrote:
Hi all,
When importing partitioned tables using the datapump, segments are
allocated for empty table and index partitions (1MB each).
The parameter deferred_segment_creation is set to TRUE.
Is there any way to prevent oracle allocation 1M space for empty
Ahmed
Betreff: Re: datapump and deferred_segment_creation
Datum: 2021-05-12T16:52:29+0200
Von: "Andy Klock" <andy_at_klockmail.com>
An: "ahmed.fikri_at_t-online.de" <ahmed.fikri_at_t-online.de>
> Is there any way to prevent oracle allocation 1M space for empty
partitions while using datapump.
Best regards
Ahmed
-- http://www.freelists.org/webpage/oracle-lReceived on Wed May 12 2021 - 17:02:53 CEST