Which statement is true?

Examine the following query output:

You issue the following command to import tables into the hr schema:
$ > impdp hr/hr directory = dumpdir dumpfile = hr_new.dmp schemas=hr
TRANSFORM=DISABLE_ARCHIVE_LOGGING: Y
Which statement is true?

Examine the following query output:

You issue the following command to import tables into the hr schema:
$ > impdp hr/hr directory = dumpdir dumpfile = hr_new.dmp schemas=hr
TRANSFORM=DISABLE_ARCHIVE_LOGGING: Y
Which statement is true?

A.
All database operations performed by the impdp command are logged.

B.
Only CREATE INDEX and CREATE TABLE statements generated by the import are logged.

C.
Only CREATE TABLE and ALTER TABLE statements generated by the import are logged.

D.
None of the operations against the master table used by Oracle Data Pump to coordinate its
activities are logged.

Explanation:
* From the exhibit we see that FORCE_LOGGING is set to NO.

* Datapump Import impdp in 12c includes a new parameter to disable logging during data import.
This option could improve performance of import tremendously during large data loads.
The TRANSFORM=DISABLE_ARCHIVE_LOGGING is used to disable logging. The value can be
Y or N. Y to disable logging and N to enable logging.
However, if the database is running with FORCE LOGGING enabled, data pump ignores disable
logging request.
Note:
* When the primary database is in FORCE LOGGING mode, all database data changes are
logged. FORCE LOGGING mode ensures that the standby database remains consistent with the
primary database.
* force_logging V$database
A tablespace or the entire database is either in force logging or no force logging mode. To see
which it is, run:
SQL> SELECT force_logging FROM v$database;
FOR
—NO

Show Hint

← Previous question

Next question →

Leave a Reply 16

Ravi

Even with this parameter specified, there is still redo logging for other operations of Oracle Data Pump. This includes all CREATE and ALTER statements, except CREATE INDEX, and all operations against the master table used by Oracle Data Pump during the import.

praveen

B& C is incorrect because it says ONLY …Infact It logs operations against the master table.

D is incorrect based above statement

A should be correct answer.

Ranjit

Domingo

C. Ravi is right.
http://docs.oracle.com/database/121/NEWFT/chapter12101.htm#NEWFT259

2.4.4.6 Oracle Data Pump No Logging Option for Import

Ranjit

Yes C is right

bbk

Alessandro

rsv1999

A test was done by Javier.
Before the import, there were zero archive logs
During the import, we see that there is no archivelog being generated since there is no redo generation.
After import was completed, we can see that no new archivelog were generated.

Notes from Oracle Documentation:
With redo logging disabled, the disk space required for redo logs during an Oracle Data Pump import will be smaller. However, to ensure recovery from media failure, the DBA should do an RMAN backup after the import completes.
Even with this parameter specified, there is still redo logging for other operations of Oracle Data Pump. This includes all CREATE and ALTER statements, except CREATE INDEX, and all operations against the master table used by Oracle Data Pump during the import.
This feature reduces the required maintenance of redo logs by DBAs.
Hence the correct answer is C.

sugar

http://www.oracle.com/technetwork/database/enterprise-edition/oow2013-data-pump-2044029.pdf
p.37-

No logging for options for import
This includes all CREATE and ALTER statements, except CREATE INDEX

Peter

The transform_name specifies the name of the transform. The possible options are as follows, in alphabetical order:

DISABLE_ARCHIVE_LOGGING:[Y | N]

If set to Y, then the logging attributes for the specified object types (TABLE and/or INDEX) are disabled before the data is imported. If set to N (the default), then archive logging is not disabled during import. After the data has been loaded, the logging attributes for the objects are restored to their original settings. If no object type is specified, then the DISABLE_ARCHIVE_LOGGING behavior is applied to both TABLE and INDEX object types. This transform works for both file mode imports and network mode imports. It does not apply to transportable tablespace imports.

Note:
If the database is in FORCE LOGGING mode, then the DISABLE_ARCHIVE_LOGGING option will not disable logging when indexes and tables are created.