[This topic is migrated from our old forums. The original author name has been removed]
Hi,
I'm trying to connect to a new database we have that came with an accounting application. The application is Greentree and the database is Jade (an object oriented database that only has an ODBC connector to give access to relational views of database).
I configured an ODBC connection (called greentree) on my PC and it works with MS Excel and WinSQL.
When I use DbVisualiser, I'm trying to use the JDBC/ODBC Bridge.
My connection line is:
jdbc:odbc:greentree
But I get this error:
An error occurred while establishing the connection:
Type: java.sql.SQLException Error Code: 0 SQL State: IM014
Message:
[Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application
I have no idea why this is or how to fix it.
Is the JDBC/ODBC Bridge what I'm meant to be using to connect an odbc connection?
Can anyone point me in the right direction please?
Product: DbVisualizer Personal 7.0
Build: #1482 (2010/01/17 12:38)
Java VM: Java HotSpot(TM) 64-Bit Server VM
Java Version: 1.6.0_17
Java Vendor: Sun Microsystems Inc.
OS Name: Windows 7
OS Arch: amd64
OS Version: 6.1
Thanks,
Bryce Stenberg
IT Department
Harness Racing New Zealand Inc.
Hi Bryce,
We have unfortunately no experience with Jade or Greentree.
If you only have an ODBC driver then you're right that it is the JDBC/ODBC driver in DbVisualizer that should be used.
I Googled for the error message and found the following:
http://msdn.microsoft.com/en-us/library/ms712362(VS.85).aspx
Hope it helps.
Best Regards
Roger
a
anonymous
said
over 14 years ago
[This reply is migrated from our old forums. The original author name has been removed]
Re: Connect to Jade database using ODBC?
Thanks Roger. I checked out that link and think I've done everything right, as in used the SysWOW64\odbcad32.exe program to configure the odbc driver.
Is the 64bit version of DbVisualiser just as happy to use a 32bit odbc driver setup this way?
Regards, Bryce.
a
anonymous
said
over 14 years ago
[This reply is migrated from our old forums. The original author name has been removed]
Re: Connect to Jade database using ODBC?
Hi, answered my own question about 64bit by installing 32bit version - now almost running except I now get the following error message:
An error occurred while establishing the connection:
[Jade Software Corporation|http://www.dbvis.com/forum/][JADE ODBC Driver|http://www.dbvis.com/forum/] Optional feature not implemented
Debug log shows:
10:57:45 [http://DEBUG Thread-24 H.?] Connecting: GreentreeTEST
10:57:45 [http://DEBUG Thread-24 I.?] Loading class using CLASSPATH: sun.jdbc.odbc.JdbcOdbcDriver
10:57:45 [http://DEBUG Thread-24 I.?] Loading class using CLASSPATH: sun.jdbc.odbc.JdbcOdbcDriver
10:57:45 [http://DEBUG pool-2-thread-7 D.?] RootConnection: JdbcOdbcDriver.acceptsURL("jdbc:odbc:GT-testing")
10:57:45 [http://DEBUG pool-2-thread-7 D.?] RootConnection: JdbcOdbcDriver.connect("jdbc:odbc:GT-testing", {user=*****, password=*****})
10:58:00 [http://DEBUG pool-2-thread-7 C.?] RootConnection: JdbcOdbcConnection.setAutoCommit(true)
10:58:00 [http://DEBUG pool-2-thread-7 C.?] RootConnection: EXCEPTION -> java.sql.SQLException: [Jade Software Corporation|http://www.dbvis.com/forum/][JADE ODBC Driver|http://www.dbvis.com/forum/] Optional feature not implemented
10:58:00 [http://DEBUG Thread-24 H.?] Disconnecting: GreentreeTEST
10:58:00 [http://DEBUG pool-2-thread-7 C.?] RootConnection: JdbcOdbcConnection.close()
10:58:01 [http://DEBUG Thread-24 H.?] Connection closed: GreentreeTEST
The exception is on the optional feature 'setAutoCommit(true)' I think - in the profile I have auto-commit unticked. This is an optional feature, and the database is read-only also. Is it greentree disconnecting me or the jdbc/odbc bridge due to not being able to set feature? Can it be told to ignore errors on optional features?
Thanks, Bryce.
Roger Bjärevall
said
over 14 years ago
[This reply is migrated from our old forums.]
Re: Connect to Jade database using ODBC?
Hi Bryce,
The default connection mode in DbVisualizer is to establish one root connection and then one additional physical connection for each SQL editor that is created. The root connection is always auto commit = true.
What you can try is to disable:
"Use a Single Shared Physical Database Connection" in the connection properties.
DbVisualizer will then only establish one physical connection independent of how many SQL editors are created. This mode may result in negative side effects such as when executing two long running scripts in multiple SQL editors accessing the same database connection.
Best Regards
Roger
a
anonymous
said
over 14 years ago
[This reply is migrated from our old forums. The original author name has been removed]
Re: Connect to Jade database using ODBC?
Hi Roger,
I tried that and I see from the debug that setAutoCommit is now trying to be set to false.
However, that doesn't help as it is still trying to set it and that seems to be source of problem:
09:26:08 [DEBUG pool-2-thread-6 C.?] RootConnection: JdbcOdbcConnection.setAutoCommit(false)
09:26:08 [DEBUG pool-2-thread-6 C.?] RootConnection: EXCEPTION -> java.sql.SQLException: [Jade Software Corporation][JADE ODBC Driver] Optional feature not implemented
09:26:08 [DEBUG Thread-19 H.?] Disconnecting: GreentreeTEST
Are you able to tell me which piece would be deciding to do the disconnect, like is it jdbc/odbc bridge or odbc driver or jade database? I'm just trying to get a handle on it to see if I should now be talking to Jade about their driver disconnecting if someone attempts to set optional parameter or if it is in the jdbc/odbc bridge.
Regards,
Bryce Stenberg.
Roger Bjärevall
said
over 14 years ago
[This reply is migrated from our old forums.]
Re: Connect to Jade database using ODBC?
Hi Bryce,
Auto commit is initialized by DbVisualizer directly when a connection has been established. If setting it fails due to errors reported by the driver, DbVisualizer then automatically disconnect.
This is the first time we get a report that a JDBC (ODBC in this case) driver don't support setting auto commit and that it reports an error if doing so. Even if we would allow this kind of error during connect I suspect there may be other ODBC calls that are handled the same way by their driver, yet to be discovered while running DbVisualizer.
We will add a fix so that DbVisualizer wont disconnect when setting auto commit fail during the connect phase. Note however that there may be other discrepancies in the driver resulting in various errors in DbVisualizer.
Expect this fix in the next 7.0.5 version.
Best Regards
Roger
a
anonymous
said
over 14 years ago
[This reply is migrated from our old forums. The original author name has been removed]
Re: Connect to Jade database using ODBC?
Hi Roger,
That would be great - I've also been talking with Greentree people who are looking into it. Searching the internet I found one other person who ran into this problem with the Jade ODBC driver using other tools. The main difference I can see between products that work and those that don't is the not working ones all come from tools that expect to be able to make changes to the connected databases, and the working ones are all reporting type tools and I guess never try to set autocommit as they won't be making changes to database. Hopefully, as long as I'm only doing 'select' statements, the connection will stay up with this 7.0.5 change.
Many thanks,
Bryce.
Roger Bjärevall
said
over 14 years ago
[This reply is migrated from our old forums.]
Re: Connect to Jade database using ODBC?
Bryce,
DbVisualizer 7.0.5 has just been released with a fix for the auto commit issue.
Note that other issue may appear as commented earlier.
Best Regards
Roger
anonymous