sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ruslan Dautkhanov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SQOOP-3022) sqoop export for Oracle generates tremendous amounts of redo logs
Date Thu, 06 Oct 2016 20:56:21 GMT

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

Ruslan Dautkhanov commented on SQOOP-3022:

Thank you Attila for your prompt response.

APPEND_VALUES is *not* a valid Oracle hint. Never saw it is used. Just looked at non-public
Oracle articles in support.oracle.com and don't see it is there too. 'APPEND' is the only
correct hint that I am aware of that controls logging. 

I searched sqoop source for 'APPEND_VALUES' at https://github.com/apache/sqoop/search?utf8=%E2%9C%93&q=APPEND_VALUES+
and see many times it is mentioned in comments, but never actually injected into an INSERT
statement? I don't see it is used.

Actually, I have sqoop export to Oracle running right now and there are no hints used in INSERT
statements. Is it enabled through some sort of optional sqoop export argument?

Since Oracle hints are coming in a comment-like syntax, any invalid hints are not only ignored,
but any other hints after first invalid Oracle hint are ignored (not parsed) as well. So if
you see APPEND_VALUES is actually used in code, it has to be changed to APPEND.

Thank you for reference and work on SQOOP-2983 - that would be great to see it commited.

> 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

View raw message