Database Tutorials MSSQL, Oracle, PostgreSQL, MySQL, MariaDB, DB2, Sybase, Teradata, Big Data, NOSQL, MongoDB, Couchbase, Cassandra, Windows, Linux 
With the disable_archive_logging parameter, which is a feature introduced with Oracle 12c, we are able to import without producing redo in a database in archivelog mode. In this way, the risk of filling the archive log directory in large import operations will be eliminated and you will be able to process faster.
If the log_mode of the database is not force_logging, you can use this parameter. You can check the log_mode of a database as follows.
1 2 3 4 5 | SQL> select log_mode,force_logging from v$database; LOG_MODE FORCE_LOGGING ------------ --------------------------------------- ARCHIVELOG NO |
In the following example, the import operation of a table was performed using disable_archive_logging.
1 | [oracle@orcldb ~]$ impdp system/manager directory=DUMPDIR tables=USER.TABLE transform=disable_archive_logging:y |
