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:
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
Answer should be D.
As the database not in Force Logging mode and DISABLE_ARCHIVE_LOGGING=y, none of the operations will be logged.
Correct Answer is: A
Oracle offers disable_archive_logging in Data Pump to simply disable the writing on archived redo logs, and thereby speeding-up export operations.
It is definitely not [A] since FORCE_LOGGING=NO (look at the picture!) and TRANSFORM=DISABLE_ARCHIVE_LOGGING:Y.
[D] is also wrong, because the master table is ALWAYS logged. Hence [B] and [C] must also be wrong!
So, no correct answer!
Of course it’s may be stupid but:
Using a value “Y” reduces the logging associated with tables and indexes during the import by setting their logging attribute to NOLOGGING before the data is imported and resetting it to LOGGING once the operation is complete.
Only table or index:
TRANSFORM=DISABLE_ARCHIVE_LOGGING:Y:TABLE
TRANSFORM=DISABLE_ARCHIVE_LOGGING:Y:INDEX
May be logging means here logging info into impdp logfile not writing on archived redo logs? ) So A and hello to jrd )
Shawn, please if you want to comment something, please be sure to read and figure out more about Oracle.
C
“… figure out more about Oracle ?”
there is still redo logging for all CREATE and ALTER statements, except CREATE INDEX, and all operations against the master table
D is the correct answere, Here is the Oracle document for the same:
DISABLE_ARCHIVE_LOGGING:
If set to Y, then the logging attributes for the specified object types (TABLE and/or INDEX) are disabled before the data is imported.
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.
Answer is definitely D.
Check the link – http://db12c.blogspot.com/2013/06/using-new-oracle-database-12c-feature.html
It shows a live example
Correct Answer is “C”!!!
“The new TRANSFORM option, DISABLE_ARCHIVE_LOGGING, to the impdp command line causes Oracle Data Pump to disable redo logging when loading data into tables and when creating indexes. It also adds the same option as part of the PL/SQL DBMS_DATAPUMP package. With redo logging disabled, the disk space required for redo logs during an Oracle Data Pump import is 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.”
http://docs.oracle.com/database/121/NEWFT/chapter12101.htm#NEWFT253
C
Oracle Data Pump No Logging Option for Import
The new TRANSFORM option, DISABLE_ARCHIVE_LOGGING, to the impdp command line causes Oracle Data Pump to disable redo logging when loading data into tables and when creating indexes. It also adds the same option as part of the PL/SQL DBMS_DATAPUMP package. With redo logging disabled, the disk space required for redo logs during an Oracle Data Pump import is 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.
The answer is C!!
C seems to be the best answer.
Agree, the answer is ‘C’
C see the link and explanation from Eder Couto
https://docs.oracle.com/database/121/NEWFT/chapter12101.htm#NEWFT401
2.4.4.6 Oracle Data Pump No Logging Option for Import
The new TRANSFORM option, DISABLE_ARCHIVE_LOGGING, to the impdp command line causes Oracle Data Pump to disable redo logging when loading data into tables and when creating indexes. It also adds the same option as part of the PL/SQL DBMS_DATAPUMP package. With redo logging disabled, the disk space required for redo logs during an Oracle Data Pump import is 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.
D
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.
Parts of alert.log
2016-02-16 13:05:32.699000 +08:00
DM00 started with pid=46, OS id=3071, job SYSTEM.SYS_IMPORT_SCHEMA_01
2016-02-16 13:05:34.034000 +08:00
DW00 started with pid=45, OS id=3073, wid=1, job SYSTEM.SYS_IMPORT_SCHEMA_01
Import log
[oracle@db12c ~]$ more import.log
;;;
Import: Release 12.1.0.2.0 – Production on Tue Feb 16 13:05:29 2016
Copyright (c) 1982, 2014, Oracle and/or its affiliates. All rights reserved.
;;;
Connected to: Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 – 64bit Production
With the Partitioning, OLAP, Advanced Analytics, Real Application Testing
and Unified Auditing options
Master table “SYSTEM”.”SYS_IMPORT_SCHEMA_01″ successfully loaded/unloaded
Starting “SYSTEM”.”SYS_IMPORT_SCHEMA_01″: system/********@mydb directory=home dumpfile=picoman.dmp schemas=picoman transform=DI
SABLE_ARCHIVE_LOGGING:Y
Processing object type SCHEMA_EXPORT/USER
Processing object type SCHEMA_EXPORT/DEFAULT_ROLE
Processing object type SCHEMA_EXPORT/TABLESPACE_QUOTA
Processing object type SCHEMA_EXPORT/PRE_SCHEMA/PROCACT_SCHEMA
Job “SYSTEM”.”SYS_IMPORT_SCHEMA_01″ successfully completed at Tue Feb 16 13:05:36 2016 elapsed 0 00:00:04
In fact, there is nothing to record in both alert and import.log.
I must thank you for the efforts you’ve put in writing this site. I am hoping to view the same high-grade content by you later on as well. In fact, your creative writing abilities has motivated me to get my own, personal site now ;)|
C – Correct Answer
C-
C