Need RDB ODBC driver version 2.10.17

I need this older release for Visual Foxpro 9.0 ODBC connections. This version is no longer available for download on your website. Or, alternatively, I need a way to transfer this working release from one PC to another. Version 3 works with some apps but not VFP 9.

here you should find what you are looking for:
http://www.oracle.com/technetwork/developer-tools/visual-studio/downloads/index.html

Similar Messages

Memory leak in ODBC Driver version 8.1.7.8?

We have a web application connected to an 8.1.7 database on a MS Windows 2000 SP 2 server.
We recently upgraded ODBC driver from 8.1.7.7 to 8.1.7.8 and found that we ran out of virtual memory.
On further investigations, a simple refresh of our summary web page (going to the database to select a small recordset - even when there are only 2 records with 6 small VARCHAR2 fields) causes the virtual memory usage to increase by approximately 1Mb each refresh.
The same refresh using driver 8.1.7.7 occasionally increases the VM usage by 4Kb!
Is there a memory leak in ODBC driver version 8.1.7.8?

Hello Thomas,
thanks for your tips, but they did not help. Activating Connection Polling did not change anything. And opening another connection did not help, either. I did it the following way:
Sub memtest2()
Dim conODBC As New ADODB.Connection
conODBC.ConnectionString = "Data Source='xxxx';User ID='xxx';Password='xxx'"
conODBC.Open
Dim Rs1 As Recordset, Rs2 As Recordset, DB1 As Database
Set DB1 = CurrentDb
Set Rs1 = DB1.OpenRecordset("select id from artikel")
Do While Not Rs1.EOF
    Set Rs2 = DB1.OpenRecordset("select * from artikel where id=" & Rs1("id"))
    'do something
    Rs2.Close
    Set Rs2 = Nothing
    Rs1.MoveNext
Loop
Rs1.Close
Set Rs1 = Nothing
DB1.Close
Set DB1 = Nothing
conODBC.Close
End Sub
Perhaps one of you has another tip how this can be done.
@Lukasz:
using a seperate ADODB.Connection works fine, but that does not solve the problem itself. At first I would have to rewrite much code and the second much bigger thing is that the memory leak occurs even when working with bound forms in MS Access. For example: I have one large form with many subforms on it. If i go from record to record on this form the memory usage is increasing dramatically fast and there is no way to influence what kind of connection MS Access is using for bound forms.
Regards
Thorstem

Oracle ODBC Driver version

Hello,
I installed the latest ODAC version (ODAC 11.2 Release 3 and Oracle Developer Tools for Visual Studio (11.2.0.2.1)) on my Windows system.
However, when I check the ODBC driver version in ODBC Data Source Administrator I see:
Orcale in OraClient11g_home1 - version 11.01.00.07
I was expecting version 11.2.0.2.0
How can I check what Oracle ODBC driver version I have installed?
Thank you,
M.R

Problem solved, the driver has been updated but not the version number+ (there is a bug filled for that).
Edited by: user7047382 on Jan 12, 2011 9:51 AM

Has anybody had any problems with the ODBC driver version 10.2.0.2.0?

Hi,
I have experienced a problem with my current version of the ODBC driver (version 10.1.0.2) and have been advised to upgrade to the newest version 10.2.0.2.0.
As the driver was only released a couple of months ago, I am a bit wary about upgrading. Has anybody out there had any issues with the reliability of this driver or does it seem to be pretty stable?
Thanks very much,
Caroline

Sorry, forgot to mention it is on linux.
Setting SetJavaHome in the jdev.conf did not help.
I did find a way to at least start the IDE though.
Either comment out SetJavaVM in the jdev.conf or start jdev with the -client option
Also to note:
I downloaded the jdk 1.4.2 32 bit for x86 and i can't get jdev to start:
current locale is not supported in X11, locale is set to CX locale modifiers are not supported, using defaultjava.lang.InternalError: Current locale is not supported
at sun.awt.motif.MWindowPeer.pSetTitle(Native Method)
at sun.awt.motif.MWindowPeer.init(MWindowPeer.java:97)
at sun.awt.motif.MFramePeer.<init>(MFramePeer.java:58)
So right now i'll try to hack it with j2se 5...

Insert into CLOB fails with Oracle ODBC driver version 9.02.00.65

I tried to insert into CLOB using the latest Oracle ODBC driver 9.02.00.65 and it fails. But the same works with earlier versions of ODBC driver earlier to 9.02.00.65 ie., 9.02.00.63.
Here is the code snippet I tried. Any help now is highly appreciated as I am in the crunch time.
I tried the same code snippet with VARCHAR2 column with the same driver and it works.
** CONVDSN.C - This is the ODBC sample code for
** creating File DSN pointers to machine DSNs.
**This code is furnished on an as-is basis as part of the ODBC SDK and is
**intended for example purposes only.
#include <windows.h>
#include <stdio.h>
#include <tchar.h>
#include <sql.h>
#include <sqlext.h>
#include <odbcinst.h>
#include <sqltypes.h>
#define MAXDATALEN 25 //maximum data length per column
#define MAX_COL 15 //maximum column in result set
#define MAX_ROW 100 //maximum number of rows
#define MAXBUFLEN 256
#define SQLERR_FORMAT "SQL Error State:%s, Native Error Code: %lX, ODBC Error: %s"
#define MAXDISPLAYSIZE MAX_COL*(MAXDATALEN+1)
#define SQLWRNMSGTITLE "SQL_SUCCESS_WITH_INFO results"
#define SQLERRCNTDTITLE "SQL_ERROR results continued"
#define SQLWRNMSGTITLE "SQL_SUCCESS_WITH_INFO results"
#define SQLWRNCNTDTITLE "SQL_SUCCESS_WITH_INFO results continued"
#define NULLDATASTRING "SQL_NULL_DATA"
#define SQLERRMSGTITLE "SQL_ERROR results"
// prototypes
void ExpandFileName(LPSTR szFileDSNName, LPCSTR szDSNName);
void MakeLegalName(LPSTR szLegalDSNName, LPCSTR szDSNName);
// main routine: Iterate through the user and system DSNs, creating a pointer
// to each.
void FAR PASCAL DisplayError(SQLRETURN nResult, HWND hWnd, SWORD fHandleType, SQLHANDLE handle);
void insertSelectClob();
void checkRcCode(RETCODE rc);
int main (int argc, char* argv[])
     insertSelectClob();
return 0;
void FAR PASCAL DisplayError(SQLRETURN nResult, HWND hWnd, SWORD fHandleType, SQLHANDLE handle)
     UCHAR szErrState[SQL_SQLSTATE_SIZE+1]; // SQL Error State string
     UCHAR szErrText[SQL_MAX_MESSAGE_LENGTH+1]; // SQL Error Text string
     char szBuffer[SQL_SQLSTATE_SIZE+SQL_MAX_MESSAGE_LENGTH+MAXBUFLEN+1];
     // formatted Error text Buffer
     SWORD wErrMsgLen; // Error message length
     UDWORD dwErrCode; // Native Error code
     int iSize; // Display Error Text size
     SQLRETURN nErrResult; // Return Code from SQLGetDiagRec
     SWORD sMsgNum = 1;
     SWORD fFirstRun = TRUE;
     char szDispBuffer[MAXDISPLAYSIZE+1]; // Display Buffer
     szBuffer[0] = '\0';
     do
          // continue to bring messageboxes till all errors are displayed.
          // more than one message box may be reqd. as err text has fixed
          // string size.
          // initialize display buffer with the string in error text buffer
          strcpy(szDispBuffer, szBuffer);
          // call SQLGetDiagRec function with proper ODBC handles, repeatedly until
          // function returns SQL_NO_DATA. Concatenate all error strings
          // in the display buffer and display all results.
          while ((nErrResult = SQLGetDiagRec(fHandleType, handle, sMsgNum++,
               szErrState, &dwErrCode, szErrText,
               SQL_MAX_MESSAGE_LENGTH-1, &wErrMsgLen)) != SQL_NO_DATA)
               if(nErrResult == SQL_ERROR || nErrResult == SQL_INVALID_HANDLE)
               break;
               wsprintf(szBuffer, SQLERR_FORMAT, (LPSTR)szErrState, dwErrCode, (LPSTR)szErrText);
               iSize = strlen(szDispBuffer);
               if (iSize && (iSize+strlen(szBuffer)+1) >= MAXDISPLAYSIZE)
               break;
               if (iSize)
               strcat(szDispBuffer, "\n");
               strcat(szDispBuffer, szBuffer);
          // display proper ERROR or WARNING message with proper title
          if (nResult == SQL_SUCCESS_WITH_INFO)
               MessageBox(hWnd, szDispBuffer, (fFirstRun? SQLWRNMSGTITLE : SQLWRNCNTDTITLE),
               MB_OK | MB_ICONINFORMATION);
          else
               MessageBox(hWnd, szDispBuffer, (fFirstRun? SQLERRMSGTITLE : SQLERRCNTDTITLE),
               MB_OK | MB_ICONEXCLAMATION);
          if (fFirstRun)
               fFirstRun = FALSE;
     while (!(nErrResult == SQL_NO_DATA || nErrResult == SQL_ERROR || nErrResult == SQL_INVALID_HANDLE));
void insertSelectClob()
SQLCHAR clobdata[1001];
SQLCHAR resultdata[1001];
SQLINTEGER ind = SQL_DATA_AT_EXEC;
SQLCHAR *bufp;
     SQLINTEGER cbOrderID = sizeof(SQLSMALLINT);
     SQLSMALLINT sTmp=13;
     SQLCHAR *sqlStmt1 = _T("INSERT INTO clobtbl(id, clob1) VALUES(?, ?)");
     SQLCHAR *sqlStmt2 = _T("SELECT id, clob1 FROM clobtbl");
//     SQLCHAR *sqlStmt1 = _T("INSERT INTO testInsert(id, clob1) VALUES(?, ?)");
// SQLCHAR *sqlStmt2 = _T("SELECT id, clob1 FROM testInsert");
int clobdatalen, chunksize, dtsize, retchklen;
     HENV envHnd;
HDBC conHnd;
HSTMT stmtHnd;
RETCODE rc;
     int nRowcnt=0;
     SQLPOINTER pToken = NULL;
rc = SQL_SUCCESS;
// ENV is allocated
rc = SQLAllocEnv(&envHnd);
// Connection Handle is allocated
rc = SQLAllocConnect(envHnd, &conHnd);
rc = SQLConnect(conHnd, T("testd734"), SQLNTS, T("ipathdba"), SQLNTS, T("ipathdba"), SQLNTS);
printf(_T("Insert CLOB1 using SQLPutData...\n[%s]\n"), sqlStmt1);
// Set CLOB Data
int i;
SQLCHAR ch;
for (i=0, ch=_T('A'); i< sizeof(clobdata)/sizeof(SQLCHAR); ++i, ++ch)
if (ch > _T('Z'))
ch = _T('A');
clobdata[i] = ch;
clobdata[sizeof(clobdata)/sizeof(SQLCHAR)-1] = _T('\0');
clobdatalen = lstrlen(clobdata); // length of characters
chunksize = clobdatalen / 7; // 7 times to put
     rc = SQLAllocHandle(SQL_HANDLE_STMT, conHnd, &stmtHnd);
// Step 1: Prepare
rc = SQLPrepare(stmtHnd, sqlStmt1, SQL_NTS);
// checkSQLErr(envHnd, conHnd, stmtHnd, rc);
// Step 2: Bind Parameter with SQL_DATA_AT_EXEC
rc = SQLBindParameter(stmtHnd,
1,
SQL_PARAM_INPUT,
SQL_C_SSHORT,
SQL_INTEGER,
0,
0,
&sTmp,
0,
&cbOrderID);
rc = SQLBindParameter(stmtHnd,
2,
SQL_PARAM_INPUT,
SQL_C_CHAR,
SQL_LONGVARCHAR,
clobdatalen*sizeof(CHAR),
0,
(SQLPOINTER)clobdata,
clobdatalen*sizeof(CHAR),
&ind);
// checkSQLErr(envHnd, conHnd, stmtHnd, rc);
// Step 3: Execute
rc = SQLExecute(stmtHnd);
     while (rc == SQL_NEED_DATA) {
          rc = SQLParamData(stmtHnd, &pToken);
          if (rc == SQL_NEED_DATA) {
               for (dtsize=0, bufp = clobdata;
                    dtsize < clobdatalen;
                    dtsize += chunksize, bufp += chunksize)
               int len;
               if (dtsize+chunksize < clobdatalen)
                    len = chunksize;
                    rc = SQLPutData(stmtHnd, bufp, len*sizeof(SQLCHAR));
               else
                    len = clobdatalen-dtsize;
                    rc = SQLPutData(stmtHnd, bufp, SQL_NTS);
          rc = SQLParamData(stmtHnd, &pToken);
// Fails as row count retrieved is zero.
     rc = SQLRowCount(stmtHnd, &nRowcnt);
     if(rc != SQL_SUCCESS)
          DisplayError(rc, NULL, SQL_HANDLE_ENV, conHnd);
rc = SQLFreeStmt(stmtHnd, SQL_CLOSE);
printf(_T("Finished Update\n\n"));
rc = SQLAllocStmt(conHnd, &stmtHnd);
if (rc != SQL_SUCCESS)
printf(_T("Failed to allocate STMT\n"));
exit(-1);
// Clear Result Data
memset(resultdata, 0, sizeof(resultdata));
chunksize = clobdatalen / 15; // 15 times to gut
rc = SQLExecDirect(stmtHnd, sqlStmt2, SQL_NTS); // select
     if(rc != SQL_SUCCESS)
          DisplayError(rc, NULL, SQL_HANDLE_ENV, conHnd);
// Step 2: Fetch
rc = SQLFetch(stmtHnd);
for(dtsize=0, bufp = resultdata;
dtsize > sizeof(resultdata)/sizeof(CHAR) && rc != SQL_NO_DATA;
dtsize += chunksize-1, bufp += chunksize-1)
int len; // len should contain the space for NULL termination
if (dtsize+chunksize<sizeof(resultdata)/sizeof(CHAR))
len = chunksize;
else
len = sizeof(resultdata)/sizeof(CHAR)-dtsize;
// Step 3: GetData
rc = SQLGetData(stmtHnd,
2,
SQL_C_CHAR,
(SQLPOINTER)bufp,
len*sizeof(CHAR),
&retchklen);
if (!_tcscmp(resultdata, clobdata))
printf(_T("Succeeded!!\n\n"));
else
printf(_T("Failed!!\n\n"));
     if (conHnd)
          SQLFreeConnect(conHnd);
     if (envHnd)
          SQLFreeEnv(envHnd);
}

Hi,
Since 9.2 has been desupported for error correction you will not be able to download that version from OTN. You should ask whoever is providing the training if their is an alternate version you can use. The only versions that you will be able to download from oracle.com is 10.2 11.1, and 11.2.

Need to install ODBC driver 9.2.0.6.5 to client but how?

Greetings.
I have client PC (Not including DataBase engine) and I want install ODBC-driver version 9.2.0.6.5 (I have reasons). PC is normal Win XP 32bit.
I found this driver from Oracle's download pages -> OK
It's *.jar file, so I need to run it via Installer -> NOK
In Client PC I do not have this Oracle Installer, what I can to do?
It's seems that ODBC-driver need installer version 2.3.0.5.0a or later...
I will be very appreciate if someone can help.

Or download the 10g client, its in there and U can run it without having to install 10g...
this is whgat we did but it crashes when we try to create a ODBC DSN in control panel based on the new ODBC driver, this is what I am looking into currently

Oracle ODBC Driver for Rdb 2.10.11.00 on Windows 2008 64-bit

Hello,
Our application runs on Windows 2000 Professional SP4 and connects to RDB databases on Alpha Open/VMS via Oracle ODBC Driver fro Rdb release 2.10.11.00.
We are migrating to Windows Server 2008 64-bit environment.
We tested both recent Rdb ODBC driver releases (3.3.0.0 and 3.3.1.0) but we are getting errors intermittently when the application loads data from certain tables. Trace logs show no errors which could indicate the origin of the issue.
We want to use the old (2.10.11.00) release but it cannot be installed only on the Win 2008 32-bit version.
Can anyone suggest how to install the Oracle ODBC Driver for Rdb release 2.10.11.00 on a Windows 2008 64-bit Server?
Thanks in advance,
Momir

Hello,
Take a loot at http://www.connx-net.com/rdb.htm they have a 64 bit ODBC OLE DB JBC and .NET solution.
Regards,
Ant

I need to use a Driver Version 1.4 for my my Sharp printer. When I add the printer, it is driver version 1.3?

I need to use Driver Version 1.4 for my Sharp printer. When I add the printer it says Version 1.3?

Have you asked Sharp whether they have a driver that is Mavericks compliant?

I want to use the SQL Toolkit of NI and SQL Server as my databasis on a server. Do I need to install a client in each computer I want to handle the data into SQL tables or I need only a ODBC driver?

I want to use the SQL Toolkit of NI and SQL Server as my databasis on a server. Do I need to install a client in each computer I want to handle the data into SQL tables or I need only a ODBC driver?

You only need the ODBC driver on each computer. If you are distributing the SQL Toolkit app as an executable and do not install the whole toolkit on each computer, you'll need the SQL Toolkit support files. This is about a dozen files. You can get the list at http://digital.ni.com/public.nsf/websearch/b814be005f9da9258625658700550c75?OpenDocument.

Rdb ODBC 3.3.2.4 Driver

Hi,
I've found the release notes for the Rdb ODBC 3.3.2.4 driver, but I can't find the download link. The only Rdb ODBC driver I can find is 3.3.2.0 which was last updated in June of 2010. Can anyone point me towards the 3.3.2.4 driver?
Thanks,
Sean

Hi, the latest driver is released as a patch (19822870). The direct link is: https://support.oracle.com:443/epmos/faces/PatchSearchResults?searchdata=%3Ccontext+type%3D%22BASIC%22+search%3D%22%26lt…
It requires an oracle support account to access it.
Cheers,
Cameron

Oracle ODBC Driver - latest version

Hello,
I installed the latest ODAC version (i.e. ODAC 11.2 Release 3 and Oracle Developer Tools for Visual Studio (11.2.0.2.1)) on my Windows system.
However, when I check the ODBC driver version in ODBC Data Source Administrator I see:
Oracle in OraClient11g_home1 - version 11.01.00.07
I was expecting version 11.2.0.2.0
Also, if I create a new ODBC data source and click on Test Connection -> About, I get:
Oracle ODBC Driver
Version 11.1.0.7.0
Copyright @ 1996, 2007 Oracle
I am really confused, why I cannot see the latest 11.2.0.2 version installed???
Thank you,
M.R

There's a bug filed for that. The driver is actually 11202 (you can check the build date), but the version number didnt get rev'd.
Greg

Crystal Report Oracle ODBC driver invalid Thai character display problem

Hi,
   My server has CR Oracle ODBC 5.1 installed on last week. We have several reports in the servers which called by our Application to export to text file and pdf file. Sometimes, the output (both text file and pdf file) can't display Thai character correctly. The text file show Thai character in question mark and pdf file show in square box. This problem occur randomly and disappear without doing anything. Sometimes the problem occur for an hour and gone but sometimes occur 10-15 minutes and gone. This problem also not happen every days. Once the problem occur, all reports with Thai character will fail.
   However, we have another server installed the same Application, same OS level, same OS patches and same CR Oracle ODBC driver version installed on the same time as above server (the problem server). This server does not have any problems.
   Any suggestions would be appreciated.
Best Regards,
Noppadon S.

Hi Noppadon,
Thank you for the info. If it happens randomly in their application then it's something they need to debug. Could even be in the ODBC driver.
I suggest you tell them that because it works sometimes it shows the issue is likely in their software because if it failed all the time then it would be in Crystal dll's. They need to debug the problem, suggest they use tools like Process Monitor from www.sysinternals.com to step through to see where or what part is failing. If they having logging abilities that may help to find out what step is failing and in which API.
At this point we have no way of determining where the problem is, it's failing in their application and no one but them know what or how they are using CR runtime files.
If you can duplicate the problem using Crystal Report Designer then it's our problem, if not they have to help you to show us it is a CR issue.
Sorry we can't be of more help but without know their code we can't suggest anything to try. Suggest they log a call with support here to help them debug the problem if they don't know what to do.
Thank you
Don

Oracle 10G DB + 9.2 odbc driver error 12154

I installed on a Windows 2003 Server the Oracle 10G XE database.
then I installed the oracle client Version 9.2.0.1.0 where I only Installed the client and the windows services.
Why I installed the client in Version 9.2.0.1.0: I need the ODBC Driver in Version 9.2.0.0.0 for another software.
The Problem: When i try to connect via the Oracle odbc driver 9.2.0.0.0 (test connection),
I always get Error 12154 . On my Windows 2000 machine where I tested it, it works fine.
It also works fine when I use the odbc driver 10.2 from the XE installation.
Thanks in advance

Solved!

Oracle ODBC Driver and Numbers in ASP

When I try to retrieve a number field from my RecordSet I allways get 0, allthow when viewing the field from SQL Plus I get another value.
objRs is an ADODB.resultSet and state is a Number(5) field.
I've tried:
objRs("state")
objRs("state").value
objRs.Fields("state")
objRs.Fields("state").value
but they all return 0
null

1) As I recall, the problem of returning 0 is caused either by an outdated version of the ODBC driver or of the MDAC (Microsoft Data Access Components). Updated versions of the ODBC driver are available here on OTN and updated versions of the MDAC are available at <http://www.microsoft.com/data>.
2) Versioning-
To determine the version of the Oracle8 ODBC driver you should be using, simply match up the first three digits of the ODBC driver version and the Oracle client version (see chart Mr. Oehl posted). The 8.1.5.6 ODBC driver should go on an 8.1.5.x.x system, the 8.1.6.1 ODBC driver should go on an 8.1.6.x.x system. If you have an Oracle7 client, you'll need one of the version 2.5x Oracle7 ODBC drivers.
Any ODBC driver should connect with any Oracle database. No need to match anything up there. You can determine the version of the database you're connected to by calling the ODBC function SQLGetInfo with the InfoType SQL_DBMS_VER.
A little elaboration on version numbers
- Oracle versions are generally 5 digits (i.e. 8.0.5.2.4, 8.1.5.1.1). The versions that you get on CD's are generally (always?) x.x.x.0.0 versions (i.e. 8.1.5.0.0, 8.1.6.0.0). The last two digits are incremented by periodic patchkit releases <ftp://oracle-ftp.oracle.com/server/patchsets/wgt_tech/server/windowsNT/>
- ODBC drivers must report versions in 4 parts, each part having 2 digits (i.e. 8.01.05.05). Since we're lazy about typing extra 0's, we simplify this and just refer to the 8.1.5.5 ODBC driver.
- The 8.1.5.x ODBC driver is built with the client libraries that ship with Oracle 8.1.5.x.x, the 8.1.6.x ODBC driver is built with the client libraries that ship with Oracle 8.1.6.x.x, etc. This is why I said above that you need to match the first 3 version numbers between Oracle client and ODBC driver to determine which to use.
I hope this is more enlightening than confusing...
Justin Cave
ODBC Development
null

ODBC driver

Where would I find a copy of the Oracle ODBC driver version 9.2.0.5.4 for Windows as I need to test an application with this version ??

Hmmm... 9.2.0.6.5 is the only version of the 9.2 Oracle ODBC driver that's currently available for download from OTN. If you have a support contract with Oracle, you should be able to log a TAR with Metalink to get the older driver. Otherwise, the application vendor may be able to provide you with the supported driver.
Justin

Need RDB ODBC driver version 2.10.17

Similar Messages

Maybe you are looking for