[
https://issues.apache.org/jira/browse/SQOOP-351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arvind Prabhakar updated SQOOP-351:
-----------------------------------
Resolution: Fixed
Fix Version/s: 1.4.0
Status: Resolved (was: Patch Available)
Patch committed. Thanks Kate!
> Sqoop User Guide's troubleshooting section should include Case-Sensitive
> Catalog Query Errors
> ---------------------------------------------------------------------------------------------
>
> Key: SQOOP-351
> URL: https://issues.apache.org/jira/browse/SQOOP-351
> Project: Sqoop
> Issue Type: Improvement
> Components: docs
> Reporter: Kate Ting
> Assignee: Kate Ting
> Fix For: 1.4.0
>
> Attachments: sqoop-351-1.patch, sqoop-351.patch
>
>
> While working with Oracle, a common problem is that Sqoop can not figure out
> column names. This happens because the catalog queries that Sqoop uses for
> Oracle expect the correct case to be specified for the user name and table
> name. 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
