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 (Issue Comment Edited) (JIRA)" <ji...@apache.org> on 2012/03/09 03:25:58 UTC
[jira] [Issue Comment Edited] (SQOOP-457) Issue with connecting
oracle
[ https://issues.apache.org/jira/browse/SQOOP-457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13225791#comment-13225791 ]
Kathleen Ting edited comment on SQOOP-457 at 3/9/12 2:25 AM:
-------------------------------------------------------------
@sathish - As it happens, by explicitly specifying the driver oracle.jdbc.driver.OracleDriver, the impact is the opposite of your intent. That is, 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 your intended Oracle driver. This is because by default, the built-in Oracle connection manager will chose the very driver you are trying to pass in. As a result, please remove the option "driver oracle.jdbc.driver.OracleDriver" and then re-run your Sqoop command. Once you've verified your command works, please close this JIRA as not a bug. Going forward, for faster response, please post user-related questions to sqoop-user@incubator.apache.org. Thanks.
was (Author: kathleen):
@sathish - As it happens, by explicitly specifying the driver oracle.jdbc.driver.OracleDriver, the impact is the opposite of your intent. That is, 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 your intended Oracle driver. This is because by default, the built-in Oracle connection manager will chose the very driver you are trying to pass in. As a result, please remove the option "--driver oracle.jdbc.driver.OracleDriver" and then re-run your Sqoop command. Once you've verified your command works, please close this JIRA as not a bug. Going forward, for faster response, please post user-related questions to sqoop-user@incubator.apache.org. Thanks.
> Issue with connecting oracle
> ----------------------------
>
> Key: SQOOP-457
> URL: https://issues.apache.org/jira/browse/SQOOP-457
> Project: Sqoop
> Issue Type: Bug
> Components: connectors/oracle
> Affects Versions: 1.4.1-incubating
> Environment: Linux
> Reporter: sathish
>
> While trying to connect using the Oracle JDBC URL getting errors
> sqoop import --connect jdbc:oracle:thin:@myhose:myport/SID --username scott --password tiger --driver oracle.jdbc.driver.OracleDriver --table=TEST_SQOOP
> INFO manager.SqlManager: Using default fetchSize of 1000
> 12/03/08 15:51:14 INFO tool.CodeGenTool: Beginning code generation
> 12/03/08 15:51:15 INFO manager.SqlManager: Executing SQL statement: SELECT t.* FROM TEST_SQOOP AS t WHERE 1=0
> 12/03/08 15:51:15 ERROR manager.SqlManager: Error executing statement: java.sql.SQLSyntaxErrorException: ORA-00933: SQL command not properly ended
> java.sql.SQLSyntaxErrorException: ORA-00933: SQL command not properly ended
> at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445)
> I read and understood this issue is fixed via SQOOP 317 but still it doesnt work for me. This table test_scoop is created in the default user schema.
> Please help
> sqoop version
> Sqoop 1.4.1-incubating
> git commit id
> Compiled by jarcec on Tue Feb 7 20:46:19 CET 2012
--
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