[
https://issues.apache.org/jira/browse/SQOOP-461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13227739#comment-13227739
]
[email protected] commented on SQOOP-461:
-----------------------------------------------------
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/4287/
-----------------------------------------------------------
(Updated 2012-03-12 18:18:58.435413)
Review request for Sqoop and Arvind Prabhakar.
Changes
-------
Thanks Arvind for your feedback, which I've incorporated.
Summary
-------
Updated Documentation.
This addresses bug SQOOP-461.
https://issues.apache.org/jira/browse/SQOOP-461
Diffs (updated)
-----
./src/docs/user/troubleshooting.txt 1299737
Diff: https://reviews.apache.org/r/4287/diff
Testing
-------
Built docs and verified.
Thanks,
Kathleen
> Sqoop User Guide's troubleshooting section should include Oracle Connection
> Errors
> ----------------------------------------------------------------------------------
>
> Key: SQOOP-461
> URL: https://issues.apache.org/jira/browse/SQOOP-461
> Project: Sqoop
> Issue Type: Improvement
> Components: docs
> Affects Versions: 1.4.1-incubating
> Reporter: Kathleen Ting
> Assignee: Kathleen Ting
> Attachments: SQOOP-461-1.patch, SQOOP-461.patch
>
>
> While working with Oracle you may encounter the below problem when the Sqoop
> command explicitly specifies the --driver oracle.jdbc.driver.OracleDriver
> option. When the driver option is included in the Sqoop command, the built-in
> connection manager selection defaults to the generic connection manager,
> which is not the intended Oracle driver. This is because if the driver option
> is not specified, the built-in Oracle connection manager will chose the very
> driver that is being passed in. It would be helpful if this was documented in
> the troubleshooting section of the Sqoop User Guide.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
