[
https://issues.apache.org/jira/browse/SQOOP-415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13172933#comment-13172933
]
Arvind Prabhakar commented on SQOOP-415:
----------------------------------------
Eric, the OracleManager uses catalog queries for looking up metadata which
requires case sensitive sepcification of user name and table name. If the
user/table name was not quoted at the time of creation, Oracle by default
converts them to upper case and hence you see this problem. It is also
documented in the troubleshooting guide [1].
One way to alleviate this problem is to do modify Sqoop behavior so as to mimic
Oracle's handling of such literals. In other words, if the specified user/table
name is not quoted, Sqoop should convert them to upper case. If they are
quoted, they should remain as specified.
[1]
http://incubator.apache.org/sqoop/docs/1.4.0-incubating/SqoopUserGuide.html#id1774574
> Oracle table names and table owner names should be uppercased in the code
> -------------------------------------------------------------------------
>
> Key: SQOOP-415
> URL: https://issues.apache.org/jira/browse/SQOOP-415
> Project: Sqoop
> Issue Type: Bug
> Components: connectors/oracle
> Affects Versions: 1.4.0-incubating
> Reporter: Eric Wadsworth
> Fix For: 1.4.1-incubating
>
> Attachments: oracle_table_name_and_table_owner_names_uppercase.patch
>
>
> Using sqoop with oracle fails for me, with this error:
> ERROR tool.ImportTool: Imported Failed: Attempted to generate class with no
> columns!
--
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
