JDBC dependency on ODBC

Can I use Oracle lite with JDBC without installing/configuring ODBC.
It seems that one needs to have a proper ODBC Data Source Name set-up to access Oracle Lite from Java/JDBC. Is ODBC the underlying access protocol for Oracle lite?
Is there any specific reason why not to have a pure Java model (much more portable)?
Jerome

Hi,
Thank you for the information.
I am a bit confused with the type4 JDBC driver.
You mention an Oracle Lite Database service. I though that olite was supposed to be a single user database not accessible from a network.
I never seen in the documentation a reference to an Oracle Lite Database service. There is only a reference in the olite 10g (not currently available) datasheet to a multi-user version with up to 32 silmutaneous connections.
Could you clarify on these issues:
is Oracle lite 9i multi-user?
If yes, where is the server/service part, is there any documentation about it (installation and configuration)...
Thank you in advance.
Note: I am reposting these questions to another thread (multi-user version?) because they are broader issues than the JDBC one.

Similar Messages

ERROR reports.reportdefinition : com.crystaldecisions.reports.queryengine.driverImpl.m: JDBC Error: [Microsoft][ODBC Driver Manager] Invalid string or buffer length

I have developed Java web application which uses Crystal Report 2013 , java 1.6 , Windows 32 bit System, All the reports are loading fine in the Following environment
Development Environment
Windows7 Professional Service pack 1 -32 bit
Java - 1.6
Internet Explorer 11
Oracle Client 10g 32 bit ODBC driver
Testing Environment
Windows Server 2008 R2 Enterprise - 64 bit
java 1.6
Internet Explorer 9
Oracle Client 11g 62 bit ODBC driver
While loading reports in the 64 bit server the error occurs
ERROR reports.reportdefinition : com.crystaldecisions.reports.queryengine.driverImpl.m: JDBC Error: [Microsoft][ODBC Driver Manager] Invalid string or buffer length
ERROR dataengine.datasource : Failed to read next recurring database record: database row set error.
com.crystaldecisions.reports.reportdefinition.datainterface.j: JDBC Error: [Microsoft][ODBC Driver Manager] Invalid string or buffer length
    at com.crystaldecisions.reports.reportdefinition.datainterface.q.a(Unknown Source)
    at com.crystaldecisions.reports.dataengine.n.m(Unknown Source)
    at com.crystaldecisions.reports.dataengine.n.l(Unknown Source)
    at com.crystaldecisions.reports.dataengine.n.bn(Unknown Source)
    at com.crystaldecisions.reports.dataengine.n.bp(Unknown Source)
    at com.crystaldecisions.reports.dataengine.n.else(Unknown Source)
    at com.crystaldecisions.reports.dataengine.s.a(Unknown Source)
    at com.crystaldecisions.reports.dataengine.bk.a(Unknown Source)
    at com.crystaldecisions.reports.dataengine.bk.ab(Unknown Source)
    at com.crystaldecisions.reports.dataengine.bk.<init>(Unknown Source)
    at com.crystaldecisions.reports.dataengine.bk.if(Unknown Source)
    at com.crystaldecisions.reports.dataengine.bk.a(Unknown Source)
    at com.crystaldecisions.reports.formatter.formatter.objectformatter.bv.a(Unknown Source)
    at com.crystaldecisions.reports.formatter.formatter.objectformatter.bv.a(Unknown Source)
    at com.crystaldecisions.reports.formatter.formatter.objectformatter.be.a(Unknown Source)
    at com.crystaldecisions.reports.formatter.formatter.objectformatter.be.h(Unknown Source)
    at com.crystaldecisions.reports.formatter.formatter.objectformatter.i.h(Unknown Source)
    at com.crystaldecisions.reports.formatter.formatter.objectformatter.be.for(Unknown Source)
    at com.crystaldecisions.reports.formatter.formatter.objectformatter.bt.a(Unknown Source)
    at com.crystaldecisions.reports.formatter.formatter.objectformatter.bv.a(Unknown Source)
    at com.crystaldecisions.reports.formatter.formatter.objectformatter.bv.a(Unknown Source)
    at com.crystaldecisions.reports.formatter.formatter.objectformatter.bf.a(Unknown Source)
    at com.crystaldecisions.reports.formatter.formatter.objectformatter.cd.for(Unknown Source)
    at com.crystaldecisions.reports.formatter.formatter.objectformatter.cd.for(Unknown Source)
    at com.crystaldecisions.reports.formatter.formatter.objectformatter.b3.for(Unknown Source)
    at com.crystaldecisions.reports.formatter.formatter.objectformatter.bt.a(Unknown Source)
    at com.crystaldecisions.reports.formatter.formatter.objectformatter.cd.a(Unknown Source)
    at com.crystaldecisions.reports.formatter.formatter.objectformatter.cd.a(Unknown Source)
    at com.crystaldecisions.reports.formatter.formatter.objectformatter.cd.a(Unknown Source)
    at com.crystaldecisions.reports.formatter.formatter.objectformatter.ca.a(Unknown Source)
    at com.crystaldecisions.reports.formatter.formatter.objectformatter.a9.a(Unknown Source)
    at com.crystaldecisions.reports.formatter.formatter.e.m.a(Unknown Source)
    at com.crystaldecisions.reports.formatter.formatter.objectformatter.cd.for(Unknown Source)
    at com.crystaldecisions.reports.formatter.formatter.objectformatter.cd.for(Unknown Source)
    at com.crystaldecisions.reports.formatter.formatter.objectformatter.b3.for(Unknown Source)
    at com.crystaldecisions.reports.formatter.formatter.e.m.for(Unknown Source)
    at com.crystaldecisions.reports.formatter.formatter.objectformatter.bt.a(Unknown Source)
    at com.crystaldecisions.reports.formatter.formatter.e.p.l(Unknown Source)
    at com.crystaldecisions.reports.formatter.formatter.e.p.void(Unknown Source)
    at com.crystaldecisions.reports.formatter.formatter.e.p.l(Unknown Source)
    at com.crystaldecisions.reports.formatter.formatter.e.p.aE(Unknown Source)
    at com.crystaldecisions.reports.formatter.a.c.a(Unknown Source)
    at com.crystaldecisions.reports.formatter.a.c.if(Unknown Source)
    at com.crystaldecisions.reports.formatter.a.c.a(Unknown Source)
    at com.businessobjects.reports.sdk.b.b.int(Unknown Source)
    at com.businessobjects.reports.sdk.JRCCommunicationAdapter.request(Unknown Source)
    at com.crystaldecisions.proxy.remoteagent.x.a(Unknown Source)
    at com.crystaldecisions.proxy.remoteagent.q.a(Unknown Source)
    at com.crystaldecisions.sdk.occa.report.application.dd.a(Unknown Source)
    at com.crystaldecisions.sdk.occa.report.application.ReportSource.a(Unknown Source)
    at com.crystaldecisions.sdk.occa.report.application.ReportSource.a(Unknown Source)
    at com.crystaldecisions.sdk.occa.report.application.PrintOutputController.export(Unknown Source)
    at com.crystaldecisions.sdk.occa.report.application.PrintOutputController.export(Unknown Source)
    at com.crystaldecisions.reports.sdk.PrintOutputController.export(Unknown Source)
    at com.erm.controller.ALMReportsController.queryDll(ALMReportsController.java:1681)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at org.springframework.web.servlet.mvc.multiaction.MultiActionController.invokeNamedMethod(MultiActionController.java:471)
    at org.springframework.web.servlet.mvc.multiaction.MultiActionController.handleRequestInternal(MultiActionController.java:408)
    at org.springframework.web.servlet.mvc.AbstractController.handleRequest(AbstractController.java:153)
    at org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControllerHandlerAdapter.java:48)
    at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:925)
    at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:856)
    at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:936)
    at org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:838)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:643)
    at org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:812)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:723)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
    at com.erm.authentication.HttpSecurityFilter.doFilter(HttpSecurityFilter.java:658)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
    at org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:88)
    at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)
    at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:861)
    at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:606)
    at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
    at java.lang.Thread.run(Unknown Source)
Caused by: com.crystaldecisions.reports.queryengine.driverImpl.m: JDBC Error: [Microsoft][ODBC Driver Manager] Invalid string or buffer length
    at com.crystaldecisions.reports.queryengine.driverImpl.o.if(Unknown Source)
    at com.crystaldecisions.reports.queryengine.ap.if(Unknown Source)
    at com.crystaldecisions.reports.queryengine.l.bN(Unknown Source)
    at com.crystaldecisions.reports.queryengine.ap.eg(Unknown Source)
    at com.crystaldecisions.reports.queryengine.ap.e(Unknown Source)
    at com.crystaldecisions.reports.queryengine.b2.f(Unknown Source)
    at com.crystaldecisions.reports.queryengine.b2.dy(Unknown Source)
    ... 89 more
Caused by: java.sql.SQLException: [Microsoft][ODBC Driver Manager] Invalid string or buffer length
    at sun.jdbc.odbc.JdbcOdbc.createSQLException(Unknown Source)
    at sun.jdbc.odbc.JdbcOdbc.standardError(Unknown Source)
    at sun.jdbc.odbc.JdbcOdbc.SQLGetDataString(Unknown Source)
    at sun.jdbc.odbc.JdbcOdbcResultSet.getDataString(Unknown Source)
    at sun.jdbc.odbc.JdbcOdbcResultSet.getBigDecimal(Unknown Source)

A few things to note:
1) Crystal Report 2013 doe snot install any SDK. Thus the assumption is that you are using CR from teh following link:
SAP BusinessObjects - SAP Crystal Reports, Version For Eclipse Download
2) Since you are using a 64 bit connection (Oracle Client 11g 62 bit ODBC driver) you will have to make sure you are using 64 bit JVM. Otherwise, follow Dell's advice and use a 32 bit ODBC datasource.
3) On one test you are using Oracle Client 10g 32 bit ODBC driver and the other you are using Oracle Client 11g 64 bit ODBC driver. You might want to see if you can run your app using Client 11g 32 bit ODBC driver.
- Ludek
Senior Support Engineer AGS Product Support, Global Support Center Canada

How to connect informix database from informatica through JDBC instead of ODBC

How to connect informix database from informatica through JDBC instead of ODBC.

Hi mate,
You may get fast reply for this in informatica forums.
Thanks
http://mkashu.blogspot.com

Oracle Heterogenous Services using JDBC (not using ODBC)

Dear Friends,
I need to configure Oracle HS to connect with MS SQL Server using JDBC as our company don't want to go for ODBC connection.
Operating System is HP-UX
Oracle Database Version is
Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bi
PL/SQL Release 10.2.0.3.0 - Production
CORE 10.2.0.3.0 Production
TNS for HPUX: Version 10.2.0.3.0 - Production
NLSRTL Version 10.2.0.3.0 - Production
Can anyone please help me.

The options you have for Heterogeneous Services are ODBC and OleDB.
JDBC is not an option.
The only other option is Transparant Gateway, a separately licenseable product.
I don't know whether Transparant Gateway relies on other drivers.
From the Sqlserver end there is MSDTC.
Oracle generally doesn't underdocument their products.
You can safely assume if it isn't documented, it isn't there.
Sybrand Bakker
Senior Oracle DBA

Diff jdbc and odbc

without odbc
there is a possible to connect
any database
-sun_jothi

odbc is an older standard that doesn't have anything to do with Java.
JDBC is the Java-equivalent to ODBC, it's a Java-based standard. There are JDBC drivers that are based on ODBC (so called JDBC-ODBC-bridges), but they are usually of bad quality and only usefull for testing/experimentation). Most Databases provide JDBC drivers that don't depend on ODBC in any way.

Why jdbc api ?why not use odbc api from java application?

hi guys....am pretty confused abt these jdbc drivers...am unable to understand why we r using jdbc api when odbc api has been in market prior to jdbc.....please clarify my doubt

chari wrote:
hi guys....am pretty confused abt these jdbc drivers...am unable to understand why we r using jdbc api when odbc api has been in market prior to jdbc.....please clarify my doubtbecause jdbc is the way that java does it.
use it or don't.
C++ was in the market before java - why was java developed at all? cobol was in the market before C++ - why was C++ developed at all?
%

ODBC vc. JDBC

We are moving, (hopefully,) from CF5 to CF8, and from SQL
Server 2000 to SQL Server 2005. My question is on the database
access - is there a performance improvement going with JDBC instead
of ODBC, and are there any gotchas?

I'd use JDBC, mainly because ODBC support in CF7+ seems be
flaky based on the number of posts I've seen regarding the
ColdFusion ODBC services. I've had to manually install them on a
server when they failed to be setup properly by CF's installer.
Items to consider.
Changes to cfquery: Versions 6+ of ColdFusion drops support
for including connection properties (such as the connectionstring
attribute) in cfquery. You must use the datasource attribute to
connect to your server.
Changes to cfprocparam: Named parameters using dbvarname are
no longer supported.
JDBC Drivers: Note that in addition to the SQL Server JDBC
driver bundled with ColdFusion you can also use Microsoft's JDBC
driver.
http://msdn2.microsoft.com/en-us/data/aa937724.aspx
http://www.adobe.com/go/tn_18800
http://www.adobe.com/go/tn_19135

JDBC vs ODBC

Hi
2 quick beginner questions:
1. Can you use odbc with java
2. How does JDBC compare with ODBC performance wise.
Thanks in advance

2 quick answers:
1. You can use the JDBC-ODBC bridge.
2. In this case it's a wrapper over ODBC only. But the bridge is a real Java driver.
Some people supported god experiences with it, for example jschell here:
http://forums.java.sun.com/thread.jsp?forum=48&thread=213474
Feel free to ask more specific, when you have begun.
Good luck!

ODBC IN WIN95 & NT

제품 : ODBC
작성날짜 : 1997-10-10
The ODBC (Open Database Connectivity) interface allows applications to
access data in DBMS ( Database management systems) using SQL(structured query language). Oracle ODBC driver is a DLL that implements ODBC
function callsand interacts with a data source.
The flow of control when communicating from an application through
ODBC to Oracle database is as shown below.
Application
|
ODBC driver manager
|
Oracle7 ODBC Driver
|
OCI layer
|
SQL*Net Driver
|
Network Software
( PCTCP, Novell NetWare, Microsoft LAN Manager, etc,.)
|
SQL*Net Listener
|
Oracle7 RDBMS
When a third party application communicates with the Oracle database
in a Client/Server environment, several dynamic link libraries are
involved. ODBC driver is a DLL that implements ODBC function calls.
The ODBC driver communicates with the OCI layer. The DLLs used in
the OCI layer are part of Required Support Files. Required Support
Files are bundled with SQL*Net. Each version of the ODBC driver is
linked with a specific version of RSF. Each version of SQL*Net is
also dependent on a specific version of RSF. The matrix below shows
the dependency.
ODBC driver| 16/32| Supported | Supported | RSF version | RDBMS
version | bit | Platforms | SQL*NET ver| used | version
1.11.00.05 | 16 | Windows | 2.0.X | 7.0.X | 7.0
| bit | 3.1X | for Windows| |
| | | | |
1.11.01.05 | 16 | Windows | 2.1.X | 7.1.X | 7.1
| bit | 3.1X | for Windows| |
1.14.01.00 | 16 | Windows | 2.2.X | 7.2.X | 7.2
| bit | 3.1X | for Windows| |
1.15.3.0.1A| 16 | Windows | 2.3.X | 7.3.X | 7.3
| bit | 3.1X | for Windows| |
1.15.3.1 | 16 | Windows | 2.3.X | 7.3.2.1.1 | 7.3
| bit | 3.1X | for Windows| |
1.16.3.1A | 16 | Windows | 2.3.X | 7.3.2.1.1 | 7.3
| bit | 3.1X | for Windows| or later |
1.13.05.00 | 32 | Windows NT | 2.2.X | 7.2.X | 7.2
| bit | 3.1/3.51 | (32-bit)~~ | |
| | and | | |
| | Windows95 | | |
1.13.05.04 | 32 | Windows NT | 2.2.X | 7.2.X | 7.2
| bit | 3.1/3.51 | (32-bit)~~ | |
| | and | | |
| | Windows95 | | |
1.15.3.0.1A| 32 | Windows NT | 2.3.X | 7.3.X | 7.3
| bit | 3.1/3.51 | (32-bit)~~ | |
| | and | | |
| | Windows95 | | |
1.15.3.1 | 32 | Windows NT | 2.3.X | 7.3.X | 7.3
| bit | 3.1/3.51 | (32-bit)~~ | |
| | and | | |
| | Windows95 | | |
1.16.3.1.0A| 32 | Windows NT | 2.3.X | 7.3.2.1.1 | 7.3
| bit | 4.0 and | (32-bit)~~ | or later |
| | Windows95 | | |
~~ : You must use SQL*Net for Windows NT, if you are running your
application
on Windows NT. If you are running your application on Windows 95,
you must use SQL*Net for Windows 95.
NOTES:
If you are running an ODBC driver not listed in the above matrix, we
strongly recommend that you upgrade your ODBC driver.
Basics:
If your application is a 32-bit application, you must use 32-bit Oracle
ODBC driver and 32-bit SQL*Net for the platform, your application is
targeted. For a 16-bit application, you must use 16-bit Oracle ODBC
driver along with SQL*Net for Windows(16-bit).
SQL*Net Version 1.X
If you are using SQL*Net Version 1.X, your connection should work
against 7.2 or older Oracle databases. SQL*Net Version 1.X was
de-supported June 30,1996. We recommend that you upgrade your SQL*Net.
Connecting to Standalone Personal Oracle Database:
If you connect to a local, standalone Personal Oracle database, you
will use a two-task driver ( In the above flow chart the two-task
driver will replace SQL*Net). The connect string is 2:<SID> where
<SID> is the instance ID. The default SID is ORCL. (no period)
ODBC Documentation:
The Oracle7 ODBC driver comes with on-line help. The help file name
is DRVORA7*.HLP * could take values NULL, 1, or 2 depending upon the
version of the Oracle ODBC driver installed.
For ODBC API documentation, refer ODBC 2.0 Programmer's Reference and
SDK Guide from Microsoft Press. The online version of ODBC 2.0
Programmer's Reference and SDK guide is part of MSVC++ compiler.
Version of Oracle product: How to find ?
To find the versions of Oracle software installed on your machine run
the Oracle installer (ORAINST.EXE). In case of errors, versions
numbers are an important part of problem definition.
Common ODBC Q&A
Q. I have two ODBC drivers, 1.11.0.5.0 and 1.11.1.5.0. Which driver
should I install?
A. The version of the ODBC driver you will install is dependent on the
Required Support Files (RSF) you have on your system. If you are
running RSF 7.0.X, you need to install 1.11.5.0. If you are running
RSF 7.1X, you need to install 1.11.1.5.0.
You can find the RSF version by running ORAINST.EXE, the Oracle installer.
When ORAINST.EXE is run the Software Asset Manager displays the
products
available to install as well as those products already installed.
Search for the Required Support File and make note of the version.
Q. What other products do I need so that the ODBC driver works?
A. You definitely need the appropriate SQL*Net version (16-bit or 32-bit).
Make sure that SQL*Net is installed and configured correctly before you
try to connect through ODBC. For example, if you are using 32-bit ODBC
driver for Windows 95, and TCP/IP is your protocol, you must have SQL*Net
for Windows 95 (TCP/IP) installed and configured, before you can make a
connection through ODBC.
Note: If you are connecting to a standalone Personal Oracle7 for
MS Windows, you do not need SQL*Net. Personal Oracle7 uses a two
task driver - SQL2TT.dll to connect to its standalone databse.
32-bit ODBC driver required 32-bit SQL*Net and
16-bit ODBC driver requires 16-bit SQLNet.
You also need the appropriate version of Required Support Files installed
on your system.
Error: specified driver could not be located
solution:
a) Check the odbc driver is present (see 1. above) and pointed to.
b) Check correct RSFs are installed and OH\bin is on the DOS path.
For Windows can set the DOS path in autoexec.bat or before
running windows. For Win 95 can only set in autoexec.bat. For
NT can set in autoexec.bat but usually through Control Panel,
System - has list of system environment variables.
c) For older installs nettest may be available else may have
tnsping. If this or any Oracle product can connect then the
net (and Sqlnet if Oracle product) is ok.
Error: error occurred in networking software, check log file
c:\msocklib.txt
but only from ODBC connections - other oracle products are fine.
Log file: TSR/DLL version incorrect
Solution:
a) Check the version of msocklib.dll. Sqlplus etc often picks up
the correct one whereas ODBC will use the DOS path. Ensure
OH\bin is first in the DOS path.
Problem: Have ODBC 1.11 and Sqlnet 2.2 and getting gpfs in nls dlls etc.
Solution:
a) Generally any version of the RSFs can call any equivalent or
later version of Sqlnet. In 2.2 of Sqlnet they changed the
calls so they were no longer backwardly compatible. This was
fixed in Sqlnet 2.3. Thus 7.0 and 7.1 RSFs can use net 2.0, 2.1
or 2.3.
Problem: Want to connect to a V6 database.
Answer: Can't. ODBC queries the dictionary views which changed in O7.
Problem: Using Lotus Approach version 3.0 and having various problems,
eg no tables being retrieved for users.
Solution: Get a patch from Lotus to take Approach to version 3.0.2.
Problem: VB Enterprise Edition (4.0) provides a remote data control.
This gives "driver not capable" errors.
Reason: The data control uses RDO which we would not support most
features of anyway since RDO is ODBC level 2 (see compliancy
above). There is also a bug (371374) that prevents any part
of it being used.
Problem: Calling a stored procedure from Visual C++ with an out
character parameter gives ora-6502: numeric or value error.
Solution: a) initialise the C variable before it is passed to the
procedure.
b) make the C variable a char and not an unsigned char (uchar).
Problem: Getting a "driver not capable" error when calling
SQLBindParameter or SQLSetParam.
Solution: Change any references to SQL_C_ULONG or SQL_C_SLONG to
SQL_C_LONG (equivalent of SQL_C_SLONG). SQL_C_ULONG and
SQL_C_SLONG are level 2 datatypes and so not supported.
Note SQLBindParameter is also level 2 but is allowed since
our drivers simply convert the calls to SQLSetParam.
Problem: With NLS settings such that the NLS_NUMERIC_CHARACTERS are
the opposite to usual (G = . and D = ,) a fetch of a decimal
number gives "SQLSTATE: 22005, Native Return Code: 0" errors
when querying through ODBCTEST, MS Query etc.
Solution: This is a bug (297648) which is fixed in the 1.16 ODBC drivers.
Question: Is there an ODBC driver for use with Java?
Answer: JavaSoft is currently writing one for Oracle 7 on SUNOS.
General Suggestions:
Please read the release notes and the online documentation. They contain
important information.
In case of error, please write down the entire error message as seen on the
monitor(screen). An error message is key in finding the problem.
Where can I get Oracle ODBC drivers?
The Oracle ODBC drivers are available as free products on the world-wide web.
The URL is http://www.oracle.com/

try to use trust connection in sql server
and it will work

Coldfusion 9 will not connect to sql database set up as ODBC

I've just installed the 64 bit version Coldfusion 9 on a 64 bit Win 7 machine where I have several SQL Server data bases set up with ODBC.
When I go into CF admin to add a datasource, it will not see the ODBC connections I have set up.
Unless I find a solution I will have to uninstall this 64 bit version of Coldfusion and try the 32 bit version instead.
Just a note, these ODBC data sources were set up using c:\windows\sysWOW64\odbcad32.exe
I hope there is a setting somewhere that I missed.

Have you considered using JDBC rather than ODBC? I suspect that both Adobe and Microsoft view ODBC as a legacy technology.

Re: Hibernate Dialect error against Firebird 2.1.2 DB via JDBC

ColdFusion9 ColdFusionBuilder1 on XP Pro
Ok, now I'm completely stuck. After 2 days of configuring CFB9 (and it's Administrator) I was able to, in CFB connect to a Firebird DB in design time using JDBC instead of ODBC. However, when I try to Run the project, I have exactly the same problem as when I configured to connect CF to FB via ODBC...and that problem is...
Hibernate is complaining that it needs to know the Dialect of the Firebird database. Well, it's 3.. but, how do I configure Hibernate so that it knows this value? I know nothing about Hibernate, nor how to configure it. I've done a search on my HD for files with the extension *.hbm.xml but no results come up.
If this can be solved, then CF9 can be used on the many hundreds of thousands of Firebird databases that are in use today, and CF's market will grow substantially.
Thanks in advance.

The Hibernate dialect (ie: for this.ormsettings.dialect) for Firebird is org.hibernate.dialect.FirebirdDialect. I found that out by googling "hibernate firebird dialect".
I have installed FB, strummed up a datasource in CF and done some testing of CF's Hibernate integration at it all seems fine to me. My testing was only as extensive as having it create some tables and persisting some object in 'em though. But if it does that much, I have no reason to think it's doesn't fully work as one would expect.
Not that it matters, but I think you are overestimating the importance of Firebird in the general RDBMS market. One would never hear it mentioned in the same sentence as Oracle or SQL Server. Or even MySQL, PostgreSQL etc. Not that my own experience is authoritative, but in 15 years in the IT industry, I hadn't even heard of it until about a week ago. But still... that's neither here nor there. CF/Hibernate supports it already anyhow.
Adam

Trying to connect to Sybase with Java jdbc

Hoping someone can help me to connect to Sybase database (version is Sybase Adaptive Server Enterprise 12.5.3). I am using a technique I read that worked with Access and adapting by some examples for Syabase I found on the web but keep getting errors. Below is my code with some of the examples Ive been using commented out.
I have created a DSN on my Windows Xp o/s named GPTS_SYBASE via ODBC Use DSN set-up wizard, driver is Sybase ASE ODBC Driver.
import java.sql.*;
public class DBConn {
public DBConn(){
public static void main(String[] args) {
try {
//Class.forName("com.sybase.jdbc2.jdbc.SybDriver.class.getname()");
//Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
Class.forName("com.sybase.jdbc2.jdbc.SybDriver");
String sourceURL = "jdbc.odbc.GPTS_SYBASE";
//String sourceURL = "jdbc.sybase.Tds:GPTSPSYB1:5000/gpts";
Connection conn = DriverManager.getConnection(sourceURL, "gptsdbo", "gptsdbo");
//Connection conn = DriverManager.getConnection(sourceURL);
System.out.println("Success");
} catch (Exception e) {
System.err.println("Got an excpetion! ");
System.err.println(e.getMessage());
Error message from this code is
Got an excpetion!
com.sybase.jdbc2.jdbc.SybDriver

Have you read the Sybase docs or the Java JDBC docs? ODBC != JDBC. They sound the same but are totally different. The DSN is totally irrelevant for type 4 JDBC drivers.
It would help to actually print the stack trace by changing your code to:
catch (Exception e) {
System.err.println("Got an excpetion! ");
e.printStackTrace();
}Also, you're mixing the wrong class name with the URL. You need "com.sybase.jdbc2.jdbc.SybDriver" and, in your case jdbc:sybase:Tds:GPTSPSYB1:5000/gpts - note the change to colons, not periods! - when in doubt read the docs!

JDBC data conversion rules

Is there any document specifying the conversion rules for JDBC?
Specifically, ODBC says when a character array is passed to a BINARY column, two bytes of character data should be converted into a single binary byte. For eg. "01" becomes 00000001 and "ff" becomes 11111111. Similarly, when data is retrieved from a BINARY column as a character array, each byte is converted into two characters. Do these rules hold for JDBC as well?
Thanks!
Ravi

Is there any document specifying the conversion rules
for JDBC?
Specifically, ODBC says when a character array is
passed to a BINARY column, two bytes of character data
should be converted into a single binary byte. For eg.
"01" becomes 00000001 and "ff" becomes 11111111.The reference I have is for ODBC 3.5, and looking at SQLPutData I don't see anything like that. That method doesn't even differentiate between types of data.
I also checked for blobs and conversions and I didn't find anything that says that.
What happens when one uses a database that supports both binary and char blobs and you really want to store hex information in a char blob?

Coldfusion odbc errors

trying to connect to ibm u2 database. any ideas? coldfusion 7
with iis on xp sp2
Connection verification failed for data source: u2
java.sql.SQLException: [Macromedia][SequeLink JDBC
Driver][ODBC Socket][IBM][UVODBC][2701920]Error ID: 46 Severity:
ERROR Facility: DBCAPERR - UCI Error. Func: SQLConnect(); State:
IM980; uniVerse code: 0; Msg: [IBM][SQL Client]Remote password is
required..
The root cause was that: java.sql.SQLException:
[Macromedia][SequeLink JDBC Driver][ODBC
Socket][IBM][UVODBC][2701920]Error ID: 46 Severity: ERROR Facility:
DBCAPERR - UCI Error. Func: SQLConnect(); State: IM980; uniVerse
code: 0; Msg: [IBM][SQL Client]Remote password is required..

Yeah, IBM must have a JDBC driver for the U2 DBMS. Use it and
not ODBC. Put the jar(s) for the driver in CFMX's classpath and
restart. Create a DSN of type other. Get the JDBC URL and driver
classname from the IBM docs.
JDBC type IV drivers connect from CFMX (java app server) from
java to the jdbc driver over the wire to your IBM database. Very
direct. ODBC connection means java to JDBC to the ODBC client to
the ODBC server to windows ODBC to IBM's native client over the
wire to the IBM U2 database. Not a very direct path. Typically ODBC
connections like this are not very good performers or very
stable.

Opensource jdbc driver for foxpro (dbf file)

Hi!
Does anybody know an opensource jdbc driver for use with Visual Fox Pro database (dbf file)?
Thanks in advance
Edited by: leonardocb on Mar 2, 2009 9:54 AM

leonardocb wrote:
I wanted to say: the "costumer" alway is right I understood that part (customer by the way).
>
JDBC-ODBC bridge? I read about it. But I have doubts:
The dbf is in a windows system. Can I use the bridge it to connect remotely from a Linux System?
If true, Do I need ODBC driver in the Linux System?
However, I think jdbc is more standard (maybe some day the dbf will be moved to a "normal" db)The idea of the JDBC-ODBC bridge driver is that it is JDBC. So in your code you use JDBC. Then, in essence, the bridge driver maps your JDBC calls onto ODBC ones instead.
As far as the Linux part of this goes... I honestly don't know. I think I once heard of someone successfully doing this but I could be wrong. You would for sure need an ODBC Unix driver for DBF. I would suggest searching this forum (for using JDBC -. ODBC on Unix/Linux) before spending a lot of time going down this route. Like I said I think it is possible but I could be wrong, I've never done it
anyway and it wouldn't be a really popular idea.'
So that sort of leaves you wanting a type-4 (pure Java driver for DBF). I think your choices at this point are:
1) Pay money. I believe there are non-free pure Java JDBC drivers for DBF. So you would have to pay money for it however outside of that this is probably the easiest solution and best fits everything else you've talked about.
2) Don't use JDBC for the DBF part. Like the link I posted earlier there do seem to be a few free open-source projects for reading and writing DBF files from Java. This plan though has the serious drawback that it will tie the database interaction code tightly to DBF and not be portable to another database.
3) Drop FoxPro.
So I think your customer needs to pick the option above that best meets the requirements.

JDBC dependency on ODBC

Similar Messages

Maybe you are looking for