[ https://issues.apache.org/jira/browse/DRILL-3992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eric Roma closed DRILL-3992. ---------------------------- resolved in 1.3 update > Unable to query Oracle DB using JDBC Storage Plug-In > ---------------------------------------------------- > > Key: DRILL-3992 > URL: https://issues.apache.org/jira/browse/DRILL-3992 > Project: Apache Drill > Issue Type: Bug > Components: Query Planning & Optimization > Affects Versions: 1.2.0 > Environment: Windows 7 Enterprise 64-bit, Oracle 10g, Teradata 15.00 > Reporter: Eric Roma > Assignee: Jacques Nadeau > Priority: Minor > Labels: newbie > Fix For: 1.3.0 > > > *****See External Issue URL for Stack Overflow Post***** > *****Appears to be similar issue at > http://stackoverflow.com/questions/33370438/apache-drill-1-2-and-sql-server-jdbc***** > Using Apache Drill v1.2 and Oracle Database 10g Enterprise Edition Release > 10.2.0.4.0 - 64bit in embedded mode. > I'm curious if anyone has had any success connecting Apache Drill to an > Oracle DB. I've updated the drill-override.conf with the following > configurations (per documents): > drill.exec: { > cluster-id: "drillbits1", > zk.connect: "localhost:2181", > drill.exec.sys.store.provider.local.path = "/mypath" > } > and placed the ojdbc6.jar in \apache-drill-1.2.0\jars\3rdparty. I can > successfully create the storage plug-in: > { > "type": "jdbc", > "driver": "oracle.jdbc.driver.OracleDriver", > "url": "jdbc:oracle:thin:@<IP>:<PORT>:<SID>", > "username": "USERNAME", > "password": "PASSWORD", > "enabled": true > } > but when I issue a query such as: > select * from <storage_name>.<schema_name>.`dual`; > I get the following error: > Query Failed: An Error Occurred > org.apache.drill.common.exceptions.UserRemoteException: VALIDATION ERROR: > From line 1, column 15 to line 1, column 20: Table > '<storage_name>.<schema_name>.dual' not found [Error Id: > 57a4153c-6378-4026-b90c-9bb727e131ae on <computer_name>:<PORT>]. > I've tried to query other schema/tables and get a similar result. I've also > tried connecting to Teradata and get the same error. -- This message was sent by Atlassian JIRA (v6.3.4#6332)