[
https://issues.apache.org/jira/browse/SQOOP-351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13116029#comment-13116029
]
[email protected] commented on SQOOP-351:
-----------------------------------------------------
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/2031/
-----------------------------------------------------------
(Updated 2011-09-28 00:23:21.440410)
Review request for Sqoop and Arvind Prabhakar.
Changes
-------
Reformatted so that no line exceeds 80 characters unless it's code. Removed
trailing white spaces.
Summary
-------
Updated documentation.
This addresses bug SQOOP-351.
https://issues.apache.org/jira/browse/SQOOP-351
Diffs (updated)
-----
src/docs/user/troubleshooting.txt b2eb5ee
Diff: https://reviews.apache.org/r/2031/diff
Testing
-------
Built docs and verified.
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
> Attachments: 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
