You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sqoop.apache.org by "Kathleen Ting (Updated) (JIRA)" <ji...@apache.org> on 2012/03/11 18:16:59 UTC

[jira] [Updated] (SQOOP-461) Sqoop User Guide's troubleshooting section should include Oracle Connection Errors

     [ https://issues.apache.org/jira/browse/SQOOP-461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kathleen Ting updated SQOOP-461:
--------------------------------

    Status: Patch Available  (was: Open)
    
> 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.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