JDBC OCI Query Notification Sample - jdbc

I am looking for a sample program using the OCI JDBC driver (Implementation-Version: 11.2.0.1.0) trying the query notification feature provided by Oracle 11gr2. Since the oracle link shows a c/c++ example it would be great if someone has already tried out and can share a working sample using the oci jdbc driver.
Thank you.

What about the examples in the JDBC developer's guide:
http://download.oracle.com/docs/cd/B28359_01/java.111/b31224/dbmgmnt.htm#CHDEJECF
(Btw: I don't think OCI is required for this, with the 11.x drivers, this should work with the thin driver as well)

Related

Tableau driver-resolver definition for JDBC Drivers in a custom connector

I'm trying to figure out how to get Tableau to recognize my JDBC Driver when creating a custom JDBC connector using the Tableau Connector SDK . Currently when Tableau loads my custom connector I can tell the driver is not found because there is a link that shows up in the Connector that says:
"Download and install the drivers, and then connect."
Tableau online does not have the drivers for the SAS data I want to connect to: so I cannot download the drivers to install from Tableau
Luckily I already have the .jar files and have placed them at C:\Program Files\Tableau\Drivers on Windows
In the Connector API Reference "driver-resolver" states that: "This is mainly used for ODBC connections but can be used for JDBC as well" but I do not see specific instructions for working with JDBC drivers explicitly. Except for the Postgres JDBC Example which DOES NOT use a driver-resolver. I also have not seen a JDBC example in the Resolvers github samples
In the Tableau logs I can see that the .jar files containing my driver are recognized by searching for their names, they are shown in the logs.
Logs Environment Section Excerpt:
"environment","v":{...all my jar files listed here}
Drivers not being recognized screenshot that says to download the drivers
Finally, here is what my .tdr file looks like with my current driver-resolver definition that does not work
<tdr class='sas_jdbc'>
<connection-resolver>
<connection-builder>
<script file="connectionBuilder.js" />
</connection-builder>
<connection-properties>
<script file="connectionProperties.js" />
</connection-properties>
</connection-resolver>
<driver-resolver>
<driver-match>
<driver-name type='exact'>com.sas.rio.MVADriver</driver-name>
</driver-match>
</driver-resolver>
</tdr>
Can anyone shed some light on this for me? I feel like I'm close. An example using a JDBC driver-resolver in a .tdr file would be nice.
You don't actually need a .tdr file with JDBC, as all the driver resolution happens in the connectionBuilder.js file today. The URL of the connection there includes the driver name. I added a story to our backlog to make this more clear. I should also mention, that hopefully you are using 2019.4 or higher for the best experience. Thanks for using the SDK!
The answer to this is that driver-resolver is not used in JDBC custom connector definitions. The problem I'm experiencing with getting the SAS JDBC Driver to work is because the SAS JDBC Driver is JDBC Type 2.0. JDBC Drivers need to be Type 4.0 to work with a Tableau custom connector using the Tableau Connector SDK.
The resolution is to use a Type 4.0 JDBC Driver which I have not seen from SAS yet.

How to use Oracle's Jdbc OCI driver for Direct Path inserts?

Trying to see if there's a good programmatic way to implement Direct Path inserts using OCI. Has anyone here tried to use the jdbc OCI driver for Direct Path and succeeded? If so, can you please give out the details for doing so?
I see that for oci to work one might have to download the oracle sql client. I just want to be sure that oci driver supports Direct Path inserts via OCI JNI calls before actually trying it out.
Thanks

Talend Connecting to ODBC Source with JDBC

In Talend 5x, I was able to use the Generic ODBC connection to connect to an ODBC source (QuickBooks QODBC). I was able to read and extract data fine from QuickBooks.
I see that Talend 6 doesn't have that ability to connect to Generic ODBC any longer. Can someone suggest an example, workaround or alternative to be able to connect to a Windows ODBC source? I see the JDBC connection - is there an example somewhere I can see if it will do the same thing?
Thanks in advance,
HL
odbc support was removed in Talend 6.0
Presumably, you could rollback to Talend 5.x and Java 1.7. Or, look in the Talend Exchange 3rd-party components for an odbc component.
https://www.talendforge.org/forum/viewtopic.php?id=46670
In Talend 6x you can use tJDBCConnection and the other components that start with tJDBC to make a connection with ODBC. It's a built in Java driver for ODBC.

Using UCanAccess to read excel sheet instead of JDBC-ODBC Bridge

I tried to upgrade my server JVM to java 8 but I was surprised that Oracle has removed JDBC ODBC bridge from Java 8 !
I searched for alternatives and I found people here provide another solution by a library called UCanAccess but it's mainly for accessing Access DB not Excel sheet.
My question is, can I use UCanAccess to access excel sheeting using same JDBC ODBC bridge used on current application ?
Thanks.
UCanAccess is for accessing a Micrsoft Access database through JDBC, so it cannot be used to access an Excelsheet. You could have found this information by looking at the UCanAccess sourceforge page:
UCanAccess is a pure Java JDBC Driver implementation which allows java developers and jdbc client programs to read/write Microsoft Access database (.mdb and .accdb files). No ODBC needed.
As Stackoverflow is not for software recommendations, I suggest you use your favorite search engine to look for an Excel JDBC driver (they exist, but some of them cost money).

Where can I find the specifications of the Wire Protocol used by Oracle database server?

I want to write my own Oracle ODBC driver, and wanted to know if the specifications of the Client Driver are published somewhere.
To write an oracle odbc driver all you'd need is to follow the instructions here -
http://msdn.microsoft.com/en-us/library/ms714629(v=VS.85).aspx
I may be misunderstanding the question though - I'm not sure why you'd need the wire protocol - for oracle this would be sqlnet.
hth

Resources