[
https://issues.apache.org/jira/browse/SQOOP-461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13227794#comment-13227794
]
Hudson commented on SQOOP-461:
------------------------------
Integrated in Sqoop-ant-jdk-1.6 #96 (See
[https://builds.apache.org/job/Sqoop-ant-jdk-1.6/96/])
SQOOP-461. Adding Oracle error to troubleshooting section of user guide.
(Kathleen Ting via Arvind Prabhakar) (Revision 1299784)
Result = SUCCESS
arvind : http://svn.apache.org/viewvc/?view=rev&rev=1299784
Files :
* /incubator/sqoop/trunk/src/docs/user/troubleshooting.txt
> 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
> Fix For: 1.4.2-incubating
>
> 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
