[
https://issues.apache.org/jira/browse/SQOOP-3022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15553116#comment-15553116
]
Attila Szabo commented on SQOOP-3022:
-------------------------------------
Hi [~Tagar],
I'd like to kindly ask a bit more input from you here:
Is +APPEND and +APPEND_VALUES are totally unrelated? Is +APPEND is only good
for reducing the redo logs?
The reason why I'm asking is that OraOop feature of Sqoop right now has an
option which uses the +APPEND_VALUES hint for inserting data.
So if it is not unrelated maybe that code path would be also good for you
(sadly I was not able to find out from the official Oracle docs, if
+APPEND_VALUES also reduce the redo log size (I do understand it's working on
the direct path insert too).
One plus information here:
On SQOOP-2983 right now we're working on fixing the insert performance of
OraOop so if that solution would be good for you it would make sense first
waiting for that JIRA ticket to be closed.
Thanks for your answer in advance!
[~maugli]
> 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)
