http://forums.visokio.com/discussions/tagged/ODBC/feed.rss Mon, 30 Oct 17 15:57:58 -0400 Tagged with ODBC - Visokio Forums en-CA http://forums.visokio.com/discussion/2989/sources-microsoft-access-odbc-support-on-java-8 Thu, 13 Aug 2015 09:39:24 -0400 chris 2989@/discussions
As discussed in a recent forum post, Java 8, which is now bundled with Omniscope, does not support ODBC:

http://forums.visokio.com/discussion/2988/database-odbc-support

If you have a Microsoft Access database block you will no longer be able to execute the block IF you have selected the "Microsoft Access driver". This driver uses ODBC to connect to the Access database.

To fix this issue please switch to the "Omniscope Access driver" and let us know if you experience any issues.]]> http://forums.visokio.com/discussion/2988/sources-database-odbc-support-on-java-8 Thu, 13 Aug 2015 09:34:43 -0400 chris 2988@/discussions
We recently integrated Java 8 into Omniscope 2.9 and 2.9 Plus:

http://forums.visokio.com/discussion/2941

Oracle, the developers of Java, have removed ODBC support in Java 8. As such if you have any ODBC database source/output blocks they will no longer work. If you try to run these blocks you will currently see the following error message:

Unable to connect to database. The JDBC driver file(s) are either currently unavailable or not correctly configured

We will improve this error message shortly, but you will need to update these blocks using one of the following options:

Option 1: In the "Select database" drop-down, check to see whether your database is listed as one already supported by Omniscope. If it is, simply select this option and configure accordingly.

Option 2: If your database is NOT supported you will need to use the "JDBC (Advanced)" database option. After selecting this option you will need to download and configure the Driver jar path. These can typically be downloaded from the database vendor's website and will be files with a ".jar" extension. You should search for "JDBC driver" on the vendors website. If you have any problems finding the driver please contact the vendor directly. The driver should provide instructions for configuring the Driver class and the JDBC URL. Please let us know if you encounter any database that is not currently supported by default in Omniscope and we will consider adding it.

If you have any problems migrating your ODBC database blocks using one of these options please let us know.

Chris

]]> http://forums.visokio.com/discussion/938/how-to-connect-to-an-odbcs Mon, 15 Aug 2011 11:05:41 -0400 elitem 938@/discussions I'm attached an image of how I did it in Access. Can anyone help? it doesn't look like Omniscope is giving me a similar path to connect to a file...

Thanks
Elite

]]> http://forums.visokio.com/discussion/1087/refresh-from-source-task-of-database-blockodbc-fails-to-execute. Tue, 08 Nov 2011 12:24:01 -0500 Aruna 1087@/discussions
When I refresh the Source manually from the Omniscope window, (Tools -> Update Data) the data is refreshed correctly.
When I use the "Refresh" Button on the Omniscope window, it also refreshes correctly. When I use the "Update All" button, Sometimes the data is refreshed, sometimes the Database error occurs. When I save and Reopen the file, then it works.
Qn: Why is the Data Refresh from the same source show such inconsistency?

When the iok file is Scheduled to be refreshed (Refresh from Source), it always fails and throws an ODBC Error.
This is the Error message from the Scheduler
..
CAUSE: [Microsoft][ODBC Driver Manager] Invalid string or buffer length
java.sql.SQLException: [Microsoft][ODBC Driver Manager] Invalid string or buffer length
at sun.jdbc.odbc.JdbcOdbc.createSQLException(Unknown Source)...

I use 64 bit versions of Oracle Drivers and 64 bit ODBC, Java and Omniscope Applications.

Qn:Why does the Scheduler always fails to execute this Task? How can I overcome this issue?

Thanks.]]> http://forums.visokio.com/discussion/2492/sources-odbc-connection-crashess Wed, 12 Mar 2014 06:27:00 -0400 Alexander 2492@/discussions
One of our clients is trying to connect to a ODBC Connection. When they hit the "connect" button. Omniscope closes and gives an error. Error messages just sent to Visokio.
They are using 2.8 b1216. ]]>