Scribd
Upload
320 views

Oracle 12c Disabling LOGGING On Data Pump Import

This document discusses a new feature in Oracle 12c that allows disabling logging during Data Pump imports. This can speed up large data loads by not writing redo log information to disk or archiving it. The feature is enabled using the DISABLE_ARCHIVE_LOGGING metadata transform parameter, which can be specified on the impdp command line or with DBMS_DATAPUMP. It will not disable logging of CREATE/ALTER statements or master table operations, and will be ignored if the database is in FORCE LOGGING mode. An example impdp command using this parameter is provided.

Uploaded by

doyenblog
Copyright
© © All Rights Reserved
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
320 views

Oracle 12c Disabling LOGGING On Data Pump Import

This document discusses a new feature in Oracle 12c that allows disabling logging during Data Pump imports. This can speed up large data loads by not writing redo log information to disk or archiving it. The feature is enabled using the DISABLE_ARCHIVE_LOGGING metadata transform parameter, which can be specified on the impdp command line or with DBMS_DATAPUMP. It will not disable logging of CREATE/ALTER statements or master table operations, and will be ignored if the database is in FORCE LOGGING mode. An example impdp command using this parameter is provided.

Uploaded by

doyenblog
Copyright
© © All Rights Reserved
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 1

Disabling LOGGING on Data Pump Import

A new feature of Data Pump introduced with Oracle 12c has the possibility to disable
logging generation during an import operation, allowing us to have faster imports due
that the redo log information is not written to the disk or even archived. This is
particularly useful for large data loads such as database migrations.
Note: When making use of a NOLOGGING option, always perform a full RMAN
backup after the NOLOGGING operation is completed.
This new feature is now possible due to the introduction of a new metadata
TRANSFORM parameter called DISABLE_ARCHIVE_LOGGING; It can be used on the
impdp command line or even when using the
DBMS_DATAPUMP.METADATA_TRANSFORM PL/SQL procedure.
Not all operations are logged when using DISABLE_ARCHIVE_LOGGING, the
following operations during an import process will still be logged:
The CREATE and ALTER statements (the only exception is the CREATE INDEX
statement)
All operations against the master table that is being used by Data Pump to coordinate
its activities
Note: If the database is in the FORCE LOGGING mode, logging will not be disabled
during an import operation that is making use of the DISABLE_ARCHIVE_LOGGING
metadata TRANSFORM parameter.
Here is one example of how this new feature can be used:
$ impdp test/test TABLES=test.test1 DIRECTORY=datapump
DUMPFILE=test_test1.dmp TRANSFORM=DISABLE_ARCHIVE_LOGGING:Y

You might also like