[
https://issues.apache.org/jira/browse/SQOOP-3022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15571371#comment-15571371
]
Attila Szabo commented on SQOOP-3022:
-------------------------------------
Hi [~Tagar],
I would strongly encourage you to do an exhaustive testing on your side, before
closing this ticket.
Functionality wise I do think OraOop is feature complete, and you could achieve
your goals with it (as I've referred to it before, and as [~david.robson]
confirmed that too).
Although as partitioned/non partitioned versions of the import are very much
different from performance POV, and as there is an ongoing performance related
change ( [SQOOP-2983] which might be interesting for you ), I think it would
make sense to evaluate if the current solution+performance is satisfying for
you (from the past I do remember you had serious performance related
constraints in your system/pipline).
> 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)
