Setting up an Oracle ODBC Driver and Essbase

Hi all,
I am trying to retrieve data directly from Essbase into SAS (Statistical Analysis Software) by setting up an Oracle ODBC Driver and Essbase.
I read this document in the below link and I was convinced that I could use ODBC to connect to Essbase, but our data administrator says that Essbase is an OLAP database and can NOT use ODBC.
http://docs.oracle.com/cd/E10530_01/doc/epm.931/esb_sqlint.pdf
I am a SAS programmer, but I have no background in technical configuration, so I was wondering if someone can help me if it is really possible or not to connect to Essbase using ODBC.
If it is possible, I have a follow up question...
I followed this link below to do a set up and did so successfully before the actual step to add a new data source to ODBC driver.
I should be able to select the TNS Service Name from the drop down list. This name will be that which I named in the TNSNAMES.ora file’s Alias = section, but I don’t see this option…
It would be great if someone knows why I do not see this option populated under drop-down in the screenshot.
Setting up an Oracle ODBC Driver and Data Source | Ten Six Consulting

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

Similar Messages

Oracle ODBC driver and TIMESTAMP with timezone

Does anyone know if it is possible to return data from a "TIMESTAMP WITH TIMEZONE" column using the Oracle ODBC driver and an ADO Recordset?
I am using the Oracle driver version 10.2.0.2 and TIMESTAMP fields work fine.
I can call Recordset->Open() with a query like "SELECT * FROM TABLE" when the table contains a column of type timestamp with timezone but when I execute a statement to see if there are results as in
if (!(srcRecsetPtr->BOF && srcRecsetPtr->EndOfFile))
my application throws an unhandled exception and exits. The exception is not a COM exception and I'm not sure how to get back additional information if that's possible.
The only information I've been able to find in searching TechNet and MetaLink is that a workaround is to wrap the columns in a TO_CHAR or TO_DATE conversion first but that's not a good solution for my problem since I am executing user specified SQL which may join multiple tables.
I've found one other note that says the documentation should be corrected and that these fields are NOT supported period (Bug #4011640).
I've experimented with the Bind Timestamp as Date option in the ODBC connection and with various ALTER SESSION settings to attempt to change the NLS_TIMESTAMP_TZ_FORMAT but I have been unable to get past the problem.
Any ideas are greatly appreciated.
Thanks,
Troy

Hi Justin
Thanks for your help.
I tried what you mentioned and I could connect myself via SQL*Plus without passing a password and a login, Extern authentification seems to work and my user seems to be right configurated.
But he problem goes on via ODBC. When I test connection in the ODBC Data Source Administrator of Windows XP, test fails and seems to forbid connection without userID and password. When I try to connect via ODBC in my program the same problem appears : "Unable to connect SQLSTATE=28000 [Oracle][ODBC][ORA]Ora-01017: Invalid username/password;logon denied" I could not connect in this way.. What's wrong ?

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

Download and installing oracle odbc driver alone

Hi all,
I wanted to find out if I can download just the oracle odbc driver and install in without actually installing oracle database or client version on windows PC.
thank you

You will need to have some Oracle software on your machine for the Oracle ODBC driver to function.
If you can use the 10g client, you can install the 10g Instant Client and the ODBC driver. The Instant Client is a minimal set of libraries that allow components like the Oracle ODBC driver to work. The 10g client, though, is not certified to connect to databases earlier than 8.1.7.
If you have to use an earlier version, you have to install the full Oracle client, which is not a small install, to be able to use the Oracle ODBC driver.
Justin
Distributed Database Consulting, Inc.
http://www.ddbcinc.com/askDDBC

Slow performance in W2K using Oracle ODBC Driver

My company is upgrading our NT4 servers to W2K. One or our App servers is running MTS with several packages, one of those being a dataaccess package that is responsible for all data actions.
In testing the OS upgrade, I found considerable performance degradation with our data access package. I finally solved the problem by changing the ODBC driver from Oracle ODBC Driver to the Microsoft ODBC for Oracle Driver. I have also found that under XP, I can still retain the use of the Oracle ODBC Driver without any performance hits.
All systems currently have the 8.1.7 Oracle Client and MDAC 2.7. I have also tried the Oracle Objects for OLE with similar performance losses in W2K.
More info about the problem...
In using the Oracle ODBC Driver, I connect this way -
Dim RS As ADOR.Recordset
Set RS = CreateObject("ADOR.Recordset")
RS.ActiveConnection = "DSN=" & p_strDSN & ";" & "uid=" & strUser & ";pwd=" & strPassword & ";"
RS.Source = "Select stuff from aTable"
RS.LockType = adLockReadOnly
RS.Open
Using W2K, I found that the majority of processing time comes from the RS.ActiveConnection call, not from object creation.
I would like to use an Oracle developed driver to connect to my database, however, I am forced to use the Microsoft driver. I have not seen any similar problem on this message board, nor have I seen any mention of this in MSDN's discussion board. Can anyone shed some light on what is going on?
Thanks,
Matt

The performance lag we have been seeing is in the milliseconds, but when we make repeated calls, those milliseconds add up. I am seeing a difference of about 7 - 10 milliseconds each call between the Oracle ODBC Driver and the Microsoft driver.
TNSPings seem quick in all setups as does the connection tests.
The Oracle ODBC driver version is 8.01.07.00. I haven't tried the new 8.01.07.6+ drivers yet. I'll give them a shot and reply back with results in a day or so.

Result Sets with the Microsoft ODBC Driver for Oracle

Howdy all.
I have an Oracle database that I have migrated from MSSQL2K. My front end is mostly VB, and I have many (hundreds) DLL's that use ADO to access the database and execute stored procedures in the database. I cannot seem to get result sets from the Oracle procedures. I have tried passing a SYS_REFCURSOR as an IN OUT parameter, and I have tried returning a SYS_REFCURSOR in a function. The Microsoft ODBC Driver for Oracle does not seem to handle the ref cursors. If I use the Oracle ODBC driver, then ref cursors are handled sort of magically. Just like the result sets are in MSSQL with the SQL Server ODBC Driver.
The question that I would like to pose to anybody willing to answer is this: Is there any way to use the Microsoft ODBC Driver for Oracle without changing the way I do the database access (using ADO connection/command/recordset objects)? I need the same DLL's to work on top of both MSSQL and Oracle.
I know that what I want to do is possible using the Oracle ODBC driver, but this will take some major changes to some of my DB components. I am trying to stay away from this, but it looks like I am going to have to go that route - that is unless somebody wows me with a good answer to this post.
wally

As you are using Microsoft driver which works in XP and does not on Win 2003 you should post this on microsoft forum.

Help w/ODBC driver and Oracle 7 (and maybe 8)

Hi,
Can anyone give me some information about using the Oracle ODBC driver for Windows? I know that it is no longer supported, but our application uses the Oracle 7 (7.3.4) client to connect to an Oracle 8i server. I have some reports written in a MS Access front end that connect through the ODBC (Oracle 7 driver) to the server.
When I run a query that takes a long time to return results, I find the connection times out whenever I use Windows2000/NT but is fine when I use 98. I also have this problem when I use the Oracle 8 client/driver and I am sure to remove the check from the "Enable Query Timeout" box in the ODBC setup. Again, even with 8, no problem on 98, but timeouts still happen on NT/2000
Is there a known bug out there on this and is there some way to fix it?
Thanks for your help and regards,
Eugene

The Oracle ODBC driver is certainly still a supported product. There are old versions (i.e. the Oracle7 driver that are no longer supported).
Which version of the Oracle 8 client & ODBC driver are you using? If you're using a older 8.0.x client and ODBC driver, those may not have been certified on Windows 2000. Can you connect to the database with SQL*Plus on the machines where the Oracle 8 client & ODBC driver are installed?
Is it possible that the user that's running the Access front-end doesn't have sufficient privs to the %ORACLE_HOME% directory? I know NT & 2000 actually enforce this sort of thing, where 98 doesn't.
Justin

ASP pages and Oracle ODBC Driver

I have a number of ASP pages that need to be updated to connect to Oracle using the ORACLE ODBC driver. Currently, these pages connect using the Microsoft ODBC driver for Oracle. I do not know of all the details yet as I havent seen the pages or network for which they reside on and I havent been supplied with details on version information. I would assume I am working with recent versions of all software.
What Im curious about is if anyone has done this sort of driver change before and if you have any suggestions on how I would go about doing this, or if there are things that I need to be aware of that arent evident at first glance.
Again, I am switching from the odbc driver provided by Microsoft to a version of the odbc driver provided by Oracle.
Thanks for any and all information.

I'll assume that there is some reason that necessitates switching drivers. If there's not going to be a benefit, I'd suggest not changing.
That said, changing drivers should be relatively painless. If your ASP makes database connections using DSN's, simply go to the ODBC Data Source Administrator, rename the old Microsoft DSN, and create a new DSN using the Oracle driver with the name your ASP is looking for. If your ASP specifies the ODBC driver in its connect string, you'll have to modify all the ASP connect strings to use the Oracle driver. If all goes well, your ASP will now be up & running using the Oracle driver.
As we all know, however, reality and theory are often at odds with each other. While your ASP should be connecting to the database correctly when you make these changes, please do some thorough testing to verify that everything works like you expect. The ODBC specification permits drivers to have a variety of behaviors in certain conditions. Applications written with one ODBC driver often end up relying on one of these behaviors, and may break when the ODBC driver changes.
Justin Cave
ODBC Development

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.

Oracle ODBC Driver is very slow?

Hi,
I installed Oracle8.1.7 on my machine and setted up an odbc connection using
VC to the database. I created a statement adding records in the database using
the SQLPrepare and SQLExecute by setting some parameters.
It takes about 5 seconds to create 100 records! During this the PC is not so buisy.
Oracle has some of 1% CPU time and my application has lesser than 1% CPU.
If I look in the oracle trace file, it shows for this statement
parsing 1 times, executed 100 times, cpu 0,01
If I try a similar example using PL/SQL it adds 1000 records in one second.
What I'm doing wrong here and what is the key to get the odbc driver work
faster?
I already read the Oracle ODBC documentation and have done all the steps there,
like disabling the thread safe mode, but without any improvment.
thanks
khamis
[email protected]

My guess, since I'm not sure exactly what the structure of your program is, is that the slowness of ODBC comes from the fact that ODBC statements are, by default, automatically committed. This means that each time you execute a statement successfully, the database must take additional time to commit the changes, which can be expensive. In PL/SQL, however, the commit operation only occurs when you explicitly commit a statement.
You can turn off autocommit mode and choose to manage your transactions manually. In straight ODBC, this is an option in the SQLSetConnectAttr function. I'm not sure whether your application is using straight ODBC or some higher-level API, though.
Justin

How to install Oracle ODBC driver...?

TOM,
Presently, I have oracle client version. But there no Oracle ODBC driver in my PC. But, I want to install only Oracle ODBC driver in my PC for ODBC Connectivity purpose.
How to install & where can get the source?

I found out the real answer!!!
On another thread there was a link to the client 10g installation. I download that 480Meg monster. Unzipped the package and launced the setup.exe.
You can then install just the ODBC using the custom option. But, it will not install the tnsnames.ora file. If you have ever done this from a VB app, copy the tsnnames.ora over to the \network\admin folder. It's usually under the oracle\product\client\10.0.2\ folder. Once installed you can launch the ODBC administer either from the link Oracle installs or from the control panel.
Next, you need to make sure the folders where the .dll file is readable to the iis. Change the folder to add whatever permission group you use for iis (I happen to have setup a local users group {machinename\users}. Add them to the entire folder structure (check the embedded folders to ensure they are readable).
While setting up the ODBC, the TSN names will now be listed from the tsnnames.ora file (if properly located). To make the connection work, the userid should be 'userid;pwd=password'. Otherwise the connection failed for me.
Now, if your connection works okay from the odbc test connection, it will probably fail if accessing through iis (like from a .asp page). There are environment path variables that need to be set. Reboot the server for them to get set. Otherwise you will get a ODBC driver can not be loaded do to system error 1114 message.

How to install the Oracle ODBC driver for all NT users

I need to schedule a task on a SQL server running on NT to access an Oracle DB.
I have installed the Oracle ODBC driver on it and it is working well under my NT account.
But the SQL scheduler runs on another NT account and the task failed.
How is it possible to install the Oracle ODBC Driver for all NT users ???
Thanks for your inputs...

http://forum.java.sun.com/thread.jsp?forum=48&thread=187964&start=0&range=15#608968
The above link is a comprehensive "How to get set up and on my way" that I made for someone else learning Oracle/jdbc. Kind of a self-help resource page. I would start from the beginning and download the newest drivers, then set up your environment,...etc.
hope this helped,
Jamie

Oracle ODBC Driver unsupported?

Hello,
I was reviewing the Oracle 10g Release 2, Release Notes for hp-ux PA-RISC (64-bit) and saw this:
-====================-
2 Unsupported Products
The following products are not supported with Oracle Database 10g release 2 (10.2):
Oracle ODBC Driver
-====================-
Does that mean that Oracle's ODBC driver is not supported to connect to an Oracle 10g Release 2 DB?

Hello,
I downloaded the gateway package of Oracle version 11.1.0.6.0, and installed Informix gateway driver. I made the necessary settings, and i have exactly the same problem, as described above.
I receive error message "OracleODBC Informix Wire Protocol driverUnsupported Informix Server version.OracleODBC Informix Wire Protocol driverInvalid attribute in connection string: ArraySize.OracleODBC Informix Wire Protocol driverInvalid attribute in connection string: TruncateOversizedColumnValues." when trying to set up a connection from Oracle to Informix 7.3. I read here, that there is a patch of Informix gateway: fix 6799360, which is unfortunately not available for for download for Windows XP. I cannot search MetaLink for this problem, because I just would like to test this Oracle feature, I did not buy Oracle license.
Does anybody know about this patch? Can anybody help how could I make working this Informix gateway?
Thanks for help, Gyula

Oracle ODBC Driver Connect window appears frequently

prashant wrote:
hi
I am running an application wriiten in vc++.I have installed the
application at the remote client end
succesfully.Initaily set the DSN for Oracle (10g exe) .When I start
using application I get "oracle ODBC Driver Window" after regular
intervals.
why this window is appearing frequently when i set the DSN initally and
tested succesfully.
pls help!!!

Oracle doesn't produce such a beast. Microsoft provides a lot of important ODBC infrastructure on Windows that driver writers rely on which isn't available on Linux.
There are third parties that have developed ODBC drivers for Oracle on Linux. There's an open source project at <http://www.unixodbc.com> that you might be able to use. Companies like Merant may also provide drivers.
Justin

Installed Oracle 9.2 Administrator - No Oracle ODBC Driver Option Found

If anyone can help me, I would greatly appreciate it. I just recently de-installed Oracle 8i on my laptop and installed Oracle 9.2. Once I finished installing 9.2, I went to set up a data source and realized that there is no Oracle ODBC Driver option available when setting up my datasource. In addition, I am unable to configure or delete any of my existing data sources that were created with the Oracle ODBC Driver.
I have de-installed and re-installed 9.2 Administrator at least four times now. In between the installs, I have removed the old Oracle directories, services, entries in my registry and PATH. The result is still the same, not Oracle ODBC Driver option available after the installation. I get no errors when installing and the ODBC Drivers indicate that they have been installed. I have even tried re-installing the drivers and still get nothing.
Please help.
DGolay

Hi
Strange behaviour.
Anyway, you can find the drivers here :
http://www.oracle.com/technology/software/tech/windows/odbc/index.html

Setting up an Oracle ODBC Driver and Essbase

Similar Messages

Maybe you are looking for