You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sqoop.apache.org by "Ruslan Dautkhanov (JIRA)" <ji...@apache.org> on 2016/10/06 20:30:20 UTC

[jira] [Created] (SQOOP-3022) sqoop export for Oracle generates tremendous amounts of redo logs

Ruslan Dautkhanov created SQOOP-3022:
----------------------------------------

             Summary: sqoop export for Oracle generates tremendous amounts of redo logs
                 Key: SQOOP-3022
                 URL: https://issues.apache.org/jira/browse/SQOOP-3022
             Project: Sqoop
          Issue Type: Bug
          Components: codegen, connectors, connectors/oracle
    Affects Versions: 1.4.6, 1.4.5, 1.4.4, 1.4.3
            Reporter: Ruslan Dautkhanov


Sqoop export for Oracle generates tremendous amounts of redo logs (comparable to export size or more).

We have put target tables in nologgin mode, but Oracle will still generate redo logs unless +APPEND Oracle insert hint is used.
See https://oracle-base.com/articles/misc/append-hint for examples.

Please add an option for sqoop to generate insert statements in Oracle with APPEND statement. Our databases are swamped with redo/archived logs whenever we sqoop data to them. This is easily avoidable. And from business prospective sqooping to staging tables in nologgin mode is totally fine.

Thank you.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)