Ruslan Dautkhanov commented on SQOOP-3022:

Thank you [~maugli], I will definitely try and report back here.

The other performance problems we had with sqoop was related to wide dataset so 
not related to this jira (This issue is related to Oracle-side bottlenecks like 
redo log generation, direct-path insert contention etc). The issue with wide 
datasets was purely sqoop-side problem (again, not related to this issue) was 
partially fixed in SQOOP-2920 and other fixes are coming in your SQOOP-2983 - 
Thank You for your work on that.

> 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

Reply via email to