[ https://issues.apache.org/jira/browse/SQOOP-3022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15587504#comment-15587504 ]
Ruslan Dautkhanov commented on SQOOP-3022: ------------------------------------------ Was able to test now. Mid-run on one of the mappers, Oracle session statistics had: - 'bytes received via SQL*Net from client' ~ 8G - both 'redo size' and 'redo size for direct writes' ~ 1.3G which shows that direct path is being used. (we also have both sqoop staging tablespace and table created with NOLOGGING which also contributes to small redo log generation). Thank you. > 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)