Ruslan Dautkhanov commented on SQOOP-3022:

Thanks a lot [~david.robson].

Yes, "oraoop.partitioned" set to "TRUE" and  
"oraoop.oracle.append.values.hint.usage" to "ON" combined do look it might be 
the solution for the excesive redo log generation on Oracle side. Didn't know 
those options exist. Would it be possible to wait closing this issue some time 
before I would run some sqoop export to Oracle tests?

> 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