Skip to Main Content

SQL Developer

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

Third Party JDBC Drivers disappearing if attempted to use Data Modeler

Christos Iraklis TsatsoulisFeb 11 2016 — edited Feb 17 2016

Hi all,

I am trying to reproduce the steps in this Oracle blog post: https://blogs.oracle.com/datawarehousing/entry/oracle_sql_developer_data_modeler regarding Hive JDBC connectivity. I can successfully connect to Hive and query Hive tables without a problem. However, if I attempt to use Data Modeler (File -> Data Modeler -> Import -> Data Dictionary), Hive connectivity is no more available, and going back to Third Party JDBC Drivers (via Tools -> Preferences) shows that there are no additional drivers listed (although they had just been added and successfully used in the previous step).

Here are some screenshots

  1. Adding Hive to Third Party JDBC Drivers:

1.PNG

  1. Successful connection to Hive:

2.PNG

  1. Connection properties in Data Modeler ((File -> Data Modeler -> Import -> Data Dictionary) - notice that the Hive tab is now not available:

3.PNG

4\) Going back to Tools -> Preferences, to check Third Party JDBC Drivers - now empty:

4.PNG

This behavior is not confined to Hive - the exact same thing happens with the MySQL driver, too.

Tested in both Windows & OEL 6.6

SQL Developer v 4.1.1.19.59

Any ideas?

Many thanks in advance

This post has been answered by Gary Graham-Oracle on Feb 12 2016
Jump to Answer

Comments

Gary Graham-Oracle
Answer

Thanks for reporting this.  I also see the issue on 4.1.3.  Perhaps adding the third party jars under both the Database and Data Modeler preferences will immunize you from it.  Of course, this is a bug, and should get logged.  It is best if you could do it via MOS since 4.1.3 is a production release.  Our team typically only logs bugs for the early adopter releases.

Marked as Answer by Christos Iraklis Tsatsoulis · Sep 27 2020

Thanks Gary. Indeed, adding the jars also to the Data Modeler preferences resolves the issue. Nevertleless, I have reported it via MOS, as you suggested

Many thanks again!

Christos Iraklis Tsatsoulis

UPDATE: After reporting the issue in MOS (yesterday), it has now been logged as Bug 22746791 : THIRD PARTY JDBC DRIVERS DISAPPEARING IF ATTEMPTED TO USE DATA MODELER


Thanks to everyone involved for the swift response!


Christos

1 - 3
Locked Post
New comments cannot be posted to this locked post.

Post Details

Locked on Mar 16 2016
Added on Feb 11 2016
3 comments
2,606 views