[
https://issues.apache.org/jira/browse/SQOOP-3022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15589895#comment-15589895
]
Markus Kemper edited comment on SQOOP-3022 at 10/19/16 9:25 PM:
----------------------------------------------------------------
Additional Clarification:
With OraOop and CDH <5.3.0 you need to manually install OraOop, meaning:
If you do not create the Driver Manager for OraOop in /var/lib/sqoop/managers.d
you need to specify
(-Dsqoop.connection.factories=org.apache.sqoop.manager.oracle.OraOopManagerFactory).
Also to enable/disable OraOop using (-Doraoop.disabled=true|false).
With OraOop and CDH >=5.3.0 the OraOop classes are included in the CDH Sqoop
jar, meaning:
All references (e.g. managers.d, oraoop.jar) of a previous manual install
should be removed and the only required option to enable OraOop is to use the
--direct option. We do however recommend also deploying the Sqoop1 Client
Gateway on any host where the Sqoop1 CLI command is executed. Any global
OraOop configurations can also be set in the Gateway's sqoop-site.xml safety
valve.
In the end we resolved [~Tagar]'s issue by doing the following
1. Confirmed Sqoop1 Client Gateway was deployed
2. Confirmed OraOop managers.d file was not present
3. Confirmed that oraoop.jar was not present
4. Removed options:
4.1.
-Dsqoop.connection.factories=org.apache.sqoop.manager.oracle.OraOopManagerFactory
4.2. -Doraoop.disabled=false
5. Added options:
5.1. --direct
Hope this helps.
[[email protected]]
was (Author: [email protected]):
Additional Clarification:
With OraOop and CDH <5.3.0 you need to manually install OraOop, meaning:
If you do not create the Driver Manager for OraOop in /var/lib/sqoop/managers.d
you need to specify
(-Dsqoop.connection.factories=org.apache.sqoop.manager.oracle.OraOopManagerFactory).
Also to enable/disable OraOop using (-Doraoop.disabled=true|false).
With OraOop and CDH >=5.3.0 the OraOop classes are included in the CDH Sqoop
jar, meaning:
All references (e.g. managers.d, oraoop.jar) of a previous manual install
should be removed and the only required option to enable OraOop is to use the
--direct option. We do however recommend also deploying the Sqoop1 Client
Gateway on any host where the Sqoop1 CLI command is executed. Any global
OraOop configurations can also be set in the Gateway's sqoop-site.xml safety
valve.
Hope this helps.
[[email protected]]
> 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)
