Mailing-List: contact dev-help@sqoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@sqoop.apache.org
Date: Wed, 12 Oct 2016 00:04:20 +0000 (UTC)
From: "Ruslan Dautkhanov (JIRA)" <jira@apache.org>
To: dev@sqoop.apache.org
Message-ID: <JIRA.13010271.1475785780000.799452.1476230660595@Atlassian.JIRA>
In-Reply-To: <JIRA.13010271.1475785780000@Atlassian.JIRA>
References: <JIRA.13010271.1475785780000@Atlassian.JIRA> <JIRA.13010271.1475785780614@arcas>
Subject: [jira] [Commented] (SQOOP-3022) sqoop export for Oracle generates
 tremendous amounts of redo logs
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 12 Oct 2016 00:04:22 -0000


    [ https://issues.apache.org/jira/browse/SQOOP-3022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15567026#comment-15567026 ] 

Ruslan Dautkhanov commented on SQOOP-3022:
------------------------------------------

Hi [~maugli],

Thank you for pointing to addBatch() and executeBatch() - I totally agree if sqoop is using them, there is no much value in supporting a separate INSERT ALL syntax. It probably would be around the same performance then.


Thanks again,
Ruslan

> 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.3, 1.4.4, 1.4.5, 1.4.6
>            Reporter: Ruslan Dautkhanov
>              Labels: export, oracle
>
> 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)