sqoop-dev mailing list archives

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

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

David Robson commented on SQOOP-3022:
-------------------------------------

I haven't tested all the various scenarios in a while but basically if you use partitioning
by setting "oraoop.partitioned" to "TRUE" it should create a table per mapper and do direct
path inserts. http://sqoop.apache.org/docs/1.4.6/SqoopUserGuide.html#_partitioning

If you don't want to use partitioning but want to disable redo logs then you can set "oraoop.oracle.append.values.hint.usage"
to "ON" which will use the APPEND_VALUES hint for the insert statements into the target table.
http://sqoop.apache.org/docs/1.4.6/SqoopUserGuide.html#_oraoop_oracle_append_values_hint_usage

So I think it already does what you require so we should be able to close this issue?

> 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)

Mime
View raw message