ODBC Driver 8.1.7.3 - pending bugs?

Does somebody know if the problem below has been fixed with Oracle ODBC 8.1.7.3 driver for NT?
Version 8.1.7.2.0 of the Oracle ODBC driver (with Net8 8.1.7.0.0) tends to fail with multithreading application, running only on a single processor. Therefore we do not recommend it. The failure typically occurs as a conversion error ("ORA-01461 can bind a LONG value only for insert into a LONG column" or "ORA-01460 unimplemented or unreasonable conversion requested").
Gisella Saavedra
null

My e-mail is [email protected]
I guess I have not updated my profile for a while.
<BLOCKQUOTE><font size="1" face="Verdana, Arial, Helvetica">quote:</font><HR>Originally posted by Gisella Saavedra ([email protected]):
Does somebody know if the problem below has been fixed with Oracle ODBC 8.1.7.3 driver for NT?
Version 8.1.7.2.0 of the Oracle ODBC driver (with Net8 8.1.7.0.0) tends to fail with multithreading application, running only on a single processor. Therefore we do not recommend it. The failure typically occurs as a conversion error ("ORA-01461 can bind a LONG value only for insert into a LONG column" or "ORA-01460 unimplemented or unreasonable conversion requested").
Gisella Saavedra
<HR></BLOCKQUOTE>
null

Similar Messages

Oracle 10g ODBC Driver Bug (10.1.0.3.1)

Using the ODBC driver version 10.1.0.3.1, there is a problem retrieving BLOB data in chunks using multiple calls to SQLGetData() when the datatype specified is SQL_CHAR.
Instead of returning (<BufferLength> - 1) characters (ANSI) along with a NULL, it returns exactly <BufferLength> characters (possibly with a NULL, I haven't double checked this) - pretty much the behavior you would expect if SQL_BINARY was specified. This has the affect of losing one character for each truncated chunk.
According to the ODBC spec, "If the length of character data (including the null-termination character) exceeds BufferLength, SQLGetData truncates the data to BufferLength less the length of a null-termination character. It then null-terminates the data. If the length of binary data exceeds the length of the data buffer, SQLGetData truncates it to BufferLength bytes."
The way I read this, as long as you specify the datatype as SQL_CHAR, the character data rules should be applied.
I tried to submit this as a TAR in Metalink, but it seems I don't have the TAR button. Is this the correct forum for this issue? Thanks.
Jon

AFAIK, Oracle doesn't officially monitor these forums and where/when they do it is a haphazard and volunteer basis (personal observations).
They do monitor the MetaLink forums so perhaps that was the cause of the confusion. At any rate the answer to use a forum to file a bug is wrong you do it through a support TAR and that can either be created from MetaLink (TARS button--missing for you) or via the phone.

[Fwd: Creating an ODBC Driver with Forte]

Has anyone created an ODBC driver with Forte? The Microsoft ODBC
Software Development Kit (SDK) assumes that ODBC drivers will be
developed in C. I would like to write the driver in Forte TOOL. Even
though C++ code can be generated from TOOL code, I am not certain that
the generated C++ code will conform to the ODBC API, and be compatible
with other ODBC components, such as the ODBC Driver Manager, ODBC
Installer, and ODBC Test applications supplied by Microsoft with the
ODBC SDK. Any advice would be appreciated. (The purpose of my ODBC
driver is to enable data access by any ODBC client application, using
calls to Forte service objects to retrieve and process the data before
it is sent to the client application.)
Chris Johnson
Unified Information, Inc.
425-814-4007
MailTo:[email protected]

The following is extracted from Oralce's Metalink: (sorry lost the link)
"This is an NLS related issue. The ODBC driver uses the values derived from the NLS_LANG setting from the Oracle Home where the driver is installed.
The application actually uses the number setting from the NT Regional Settings.
When these two settings differ, then the decimal character will be cut off. This behaviour is also described in Bug:694323.
Example:
You have set your NLS_LANG in the ORACLE_HOME of your ODBC driver to GERMAN_GERMANY.WE8ISO8859P1. This will result in a value for the NLS_NUMERIC_CHARACTERS of ",." (the first part of the NLS_NUMERIC_CHARACTERS being the decimal character and the second part being the group separator).
So the "." is used by the Application and the "," is used by the Oracle ODBC driver.
As a result numeric values in your Oracle Database with an integer and a decimal part will thus be displayed by the application without the decimal character, i.e. a value of 10,734 will be displayed as 10734 a value of 0,123 will be displayed as 123.
To fix this, you will either have to correct the character used for the Decimal Symbol of your NT Regional settings to match the value of your Oracle NLS_LANG setting or vice versa. To change the value for NLS_LANG, go to your registry and change the NLS_LANG parameter that is situated under HKEY_LOCAL_MACHINE/SOFTWARE/ORACLE/HOMEnnn/NLS_LANG where HOMEnnn is the home where your Oracle ODBC driver is installed."
Hope this helps, resolved our issue with this problem.

Oracle 10g ODBC driver (ver 10.1.0.2) : SQLConnect Hangs

hi,
We have a Win32 multithreaded app which uses the given 10g driver, but intermittently all the threads hang on SqlConnect.
After running Adplus the call stack that we get , always point to oranls10. This is the call stack from the last time the server hanged when it tried to do a SQLConnect.The call stack generated by adplus is given below:
ChildEBP RetAddr Args to Child
WARNING: Stack unwind information not available. Following frames may be wrong.
0135f088 612a1833 003ee494 00001399 00000002 ORANLS10!lmsapsc+0x78
0135f2bc 612a176e 003ee494 00000002 00001399 ORANLS10!lmsagbcmt+0x103
0135f2f0 612a1722 003ee494 00001399 00000000 ORANLS10!lmsagbcmt+0x3e
0135f31c 031990f4 003ee494 00001399 00000000 ORANLS10!lmsagbf+0x22
0135f334 036e0bcf 003ee494 00001399 00000000 oci!lmsagbf+0x24
0135f360 036bed2f 02675e4c 00000000 00001399 sqora32!SQLTablesW+0x372df
0135f3b8 036b61c3 02675e4c 0268f418 0267682c sqora32!SQLTablesW+0x1543f
0135f4f0 036a3b2c 0268f334 02675bcc 00000006 sqora32!SQLTablesW+0xc8d3
0135f524 4bf8e667 0268f334 0135f65c 00000006 sqora32!SQLConnectW+0xfc
0135f554 4bf8efed 00000001 0135f65c 00000006 odbc32!SQLInternalConnectW+0xfa
0135f6a4 4bfa1e5e 00781b28 00782628 00000006 odbc32!SQLConnectW+0x250
0135f6e0 00397454 00781b28 01d7fffd fffffffd odbc32!SQLConnect+0x140
01360068 016dc13a 00000005 0136f9d0 0136fa14 libsas!CM_dbopen+0x341
Since we have been facing this issue for a long time, we decided on making use of the SQL_ATTR_LOGIN_TIMEOUT value before we issue a SQLConnect, but that driver doesn't seem to like that option even though it says its 3.5 compliant
lRetcode = SQLSetConnectAttr( OD_DBDBC(pCtx), SQL_ATTR_LOGIN_TIMEOUT,(SQLUINTEGER )10, SQL_IS_UINTEGER );
Setup details
Oracle 10g Release 1 Enterprise database server
App has been built using VC++6 and is running on Win2003 Enterprise Server
Our analysis has shows that the network was fine as other apps were able to connect to the database at that time
Question
1. Is this a Driver related issue? Because when we were using Merant ODBC driver, everything seems to be working fine!
2. Is there some patch that is out there which might resolve this issue?
If you all folks could help or provide some kind of advice , i would really appreciate that.
regards,
GG

Well, do you have a code example that causes it? Don't take this the wrong way, but I've seen more than a few badly written multi-threaded applications which do nothing but corrupt memory and use handles in non-threadsafe ways; all of which cause issues which rear their ugly heads in various odd ways. It may also be an Oracle bug, but comparing two different drivers does not mean it's not your application causing the crash as well.
If you could provide a quick little code sample which causes the issue, I'll take a look at it for you.

ODBC Driver-specific TNSName issue

I seem to be having a problem resolving TNSnames frm a local TNS file that is unique to the ODBC driver and would appreciate suggestions.
I have Oracle Client 10.2.0.3 and the like-versioned ODBC driver, on Windows Vista SP1. We are configured to use a central TNS Names file with an IFILE entry that includes a per-user names file. The IFILE entry looks like this:
IFILE=h:\oracle_tns\tnsnames.ora
(Everyone has an H drive in our environment).
The Oracle ODBC Driver, ONLY, seems to not be able to use names in the 'included' personal names file (you always get a name not resolved error). Interestingly, the dropdown list in the TNS Service Name part of the Oracle DNS configuration dialog has an entry for 'IFILE', and not any entries for the names in the included file. Even manually entered names don't work.
HOWEVER, these same names work fine with both SQL*Plus and the Microsoft ODBC Driver for Oracle.
Looks like a bug in the Oracle ODBC driver - though I can't understand why it's doing name lookup differently than SQL*Plus is. ANyway, did a look with Process Monitor and verified that doing a test connection in the ODBC DSN configuraiton dialog doesn't even try to open the 'included' file, just the central one, while doign the same thing with SQL*Plus DOES open the 'included' file.
Can anyone confirm this issue occurs and/or doesn't occur, and with other ODBC driver versions? Anyone know of any fiix or workaround to get my included file's names to work?

Doh.
I have figured out my problem.
We have a custom set of policy for Vista UAC in our setup, especially for 'privileged users', who have administrator-like permissions. When these users get elevated, some quirk in how things works means they lose a few things - one of those things is the 'H' drive. I noticed that eaerlier in testing our new PC iamges but hadn't tweaked to the ramifications. I'll have to ask our Windows admin guys why it works that way; not an Oracle issue, anyhow.
I'd been testing the Oracle ODBC driver using the ODBC Administrator applet.
When you start the applet, and you're a 'privileged user', you get the UAC elevation prompt.
So I was, in effect, disconnecting my H drive. Needless to say, that disconnected me from my personal names file...
Tested with an ODBC-enabled app, not elevated, and everything works fine.
Thanks for the suggestion to check with purely-local files, which got me started; would've taken quite a bit longer to figure things out otherwise!

Oracle ODBC driver: NO_DATA_FOUND blocked

Hello,
I found that NO_DATA_FOUND exceptions thrown inside stored_procedures are sometimes not propagated to ODBC errors. This happens with the Oracle ODBC driver, but not with the MS one (the MS one does propagate the exception/error).
Test-Procedure:
Create or Replace Procedure throws_exception(p1 in number)
IS
BEGIN
raise NO_DATA_FOUND;
END;
If I call this stored_procedure the ODBC call will return with no errors:
Begin THROWS_EXCEPTION(1); end;
Versions:
- oracle server: 10.02
- oracle driver: 10.02
- mirosoft driver: 2.575
Is this a known bug in the oracle ODBC driver, or is this a bad setup, etc?
If this is a bug, it is a very inconvenient one, because basically it means your stored_procedure can fail completely silentely. It implies that the use of the oracle driver is completely unreliable.
I have copied this text from another user, he got no answer to this :-(
Thanks
Joachim Paulus
Message was edited by:
user517727
Message was edited by:
user517727

Any answers? Same problem on 10.2.0.2.0

Oracle 9i Lite Issue with ODBC driver

Cannot reference table in user schema without schema ref
I create a user TESTUSR and a table TESTTBL, and when I log in with user TESTUSR in SQL*Plus,
the following will work just fine.
SELECT * FROM TESTTBL
but then when my ASP on IIS does the same SELECT,
it will report "[POL-5130] table or view not found".
But if I use a schema alias,
SELECT * FROM TESTUSR.TESTTBL
it will work fine.
ODBC Admin shows: "Oracle Lite 40 ODBC Driver 4.00.00.00".
Is this a bug ?

I connect to the database through the same user that created those tables. Do I still need a public synonym ?

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 ?

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

Sybase ODBC driver - numeric or decimal datatype problem

Hello!
I have Sybase Adaptive Server Enterprise 15.0.2 and Oracle 10.2.0 ("show release" in SQL*plus prints 1002000100) on the same machine (OS = Windows XP, name = Workstation). I wanna load correct information from the table in Sybase via Oracle database link.
Well, I've edited tnsnames.ora, listener.ora. Also I've created initmysybase.ora in hs\admin directory. And, of course, set up DSN (using Sybase ODBC driver) via odbcad32.exe - and named it "mysybase".
Table ("test", user = guest) definition in Sybase is:
column "id" - int, column "data_num" - numeric(10, 5), column "data_dec" - decimal(10, 5). And it's content is: (1, 1.12345, 5.54321). I've set up a database link.
My problem is that whenever I do the SELECT statement (SELECT * FROM "guest.test"@mysybase) I get 0 (zero) for both data_num and data_dec columns.
Status of investigation:
The "describe" command in SQL*plus returns:
id NOT NULL NUMBER(10)
data_num NUMBER(10,5)
data_dec NUMBER(10,5)
UPDATE statement works perfectly.
I've downloaded a trial version of ODBC drivers from www.datadirect.com and all works fine.
So, I believe that maybe there are some bugs in ODBC driver from Sybase, or maybe I should configure smth.
My initmysybase.ora:
HS_FDS_CONNECT_INFO = mysybase
# HS_FDS_TRACE_LEVEL = DEBUG
HS_FDS_TRACE_LEVEL = ON
HS_NLS_NUMERIC_CHARACTER = ",."
HS_LANGUAGE = American
tnsnames.ora:
mysybase =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = WORKSTATION)(PORT = 1521))
(CONNECT_DATA =
(SID = mysybase)
(HS = OK)
listener.ora:
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1))
(ADDRESS = (PROTOCOL = TCP)(HOST = WORKSTATION)(PORT = 1521))
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(GLOBAL_DBNAME = mysybase)
(SID_NAME = mysybase)
(ORACLE_HOME = C:\oracle\product\10.2.0\db_1)
(PROGRAM = hsodbc)
So, maybe anybody know how to solve this problem?
Thanks,
Yury

I've played with HS_LANGUAGE option but without success.
Well, this is the export from the registry:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\mysybase]
"Driver"="C:\\sybase\\DataAccess\\ODBC\\dll\\sybdrvodb.dll"
"dsprincipal"=""
"secondaryport"=""
"logintimeout"="10"
"dsn"="mysybase"
"restrictmaximumpacketsize"="0"
"initializationstring"=""
"database"=""
"packetsize"=""
"ignoreerrorsifrspending"="0"
"dsservicename"=""
"server"="WORKSTATION"
"serverinitiatedtransactions"="1"
"quotedidentifier"="0"
"charset"="ServerDefault"
"ansinull"="0"
"encryptpassword"="0"
"fetcharraysize"="25"
"language"=""
"buffercachesize"="20"
"trustedfile"=""
"port"="5000"
"userid"="sa"
"hasession"="0"
"tightlycoupledtransaction"="0"
"serverprincipal"=""
"enableserverpacketsize"="1"
"applicationname"=""
"description"=""
"dsurl"=""
"userprincipal"=""
"dynamicprepare"="0"
"crc"="0"
"secondaryserver"=""
"textsize"=""
"clienthostproc"=""
"clienthostname"=""
"codepagetype"="oem"

ODBC Driver with Access problem

I have problems with fields of the number(9.3) datatype. in my linked access tables numbers like 1555.33 are shown as 155533.
I'm using the oracle odbc driver version 9.2.0.54 with a 9i (9.2.0.1.0) Database.
I've reading at an old post called "number(9.3) DataType in MS Access". Where I've found someone with the same problem as me. I've done everythink which is explained on that message, but it still doesn't work.
Is there anything else to do?
Thank you in advance!

The following is extracted from Oralce's Metalink: (sorry lost the link)
"This is an NLS related issue. The ODBC driver uses the values derived from the NLS_LANG setting from the Oracle Home where the driver is installed.
The application actually uses the number setting from the NT Regional Settings.
When these two settings differ, then the decimal character will be cut off. This behaviour is also described in Bug:694323.
Example:
You have set your NLS_LANG in the ORACLE_HOME of your ODBC driver to GERMAN_GERMANY.WE8ISO8859P1. This will result in a value for the NLS_NUMERIC_CHARACTERS of ",." (the first part of the NLS_NUMERIC_CHARACTERS being the decimal character and the second part being the group separator).
So the "." is used by the Application and the "," is used by the Oracle ODBC driver.
As a result numeric values in your Oracle Database with an integer and a decimal part will thus be displayed by the application without the decimal character, i.e. a value of 10,734 will be displayed as 10734 a value of 0,123 will be displayed as 123.
To fix this, you will either have to correct the character used for the Decimal Symbol of your NT Regional settings to match the value of your Oracle NLS_LANG setting or vice versa. To change the value for NLS_LANG, go to your registry and change the NLS_LANG parameter that is situated under HKEY_LOCAL_MACHINE/SOFTWARE/ORACLE/HOMEnnn/NLS_LANG where HOMEnnn is the home where your Oracle ODBC driver is installed."
Hope this helps, resolved our issue with this problem.

Problem with ODBC Driver 8.1.7.7

When we try to execute the following sql command, an error message is displayed.
update tr_werk_tab set (name1,name2) = (select name1, name2 from tr_werk_tab)
The table in the "select" clause is originally another table. The statement only works with "one" field referenced.
The error message is:
ORA-00923 FROM keyword not found where expected.
This was not a Problem with all the other ODBC Driver versions (7.3, 8.0.5, 8.1.5, 8.1.6).
What can we do ? The statement works with sql-plus.
Regards
Dieter Burger
TRIAS Informatik GmbH

First, it appears that you've found the bug. I've confirmed it on my box. I would suggest that you log a TAR with Oracle support so that someone can start looking into the problem. I suspect that some of the SQL munging the driver has to do is mangling your query, but I'd need to do a trace at the TNS level or on the database to see exactly what's being passed over the wire.
There are previous versions of the 8.1.7.x ODBC driver available for download on OTN. Since it worked correctly in previous versions of the driver, perhaps one of these earlier 8.1.7.x drivers happens not to have this particular bug.
It appears that you could re-write the query, i.e.
update emp set empno = (select 1 from dual), ename = (select 'Justin' from dual);
though that's going to be almost twice as expensive as the proper form.
Justin

ODBC driver 8.1.5.7 won't configure after installing

After installing the updated ODBC driver 8.1.5.7 that I downloaded from OTN, the Windows apps that we use to dynamically add ODBS DSNs now fails. The app is using standard Windows API calls to dynamically add a DSN from a supplied name provided in the command line. This functionality has worked for many months with the original 8.1.5 ODBC driver but we needed to update it to fix other problems. Now the app is failing. The message I get is "Driver's ConfigDSN, ConfigDriver, or ConfigTranslator failed". Anybody have an idea of what went wrong??

In the release notes that accompany the 8.1.7.2 driver, there's a note that it includes a bug fix that "Fix[es] support of SQLConfigDataSource (Bug1548193)". I suspect I probably broke something when I was on the team for the 8.1.7.1 build when I re-vamped the configuration screen. If this is the case, 8.1.5.7 & 8.1.7.1 would both have this bug. Unfortunately, the ODBC team doesn't appear to be releasing new 8.1.5 drivers, so you'll either have to go back to the previous driver or update your client to 8.1.6 or .7
Justin
null

Can't see the odbc driver in windows 7

hallo everybody
I've just installed the oracle instant client 11.2.0.2.0 on a windows 7 machine. when i execute the file odbc_install the returned prompt is "Oracle ODBC Driver is installed successfully.". then when i go to system -> administration -> data sources (odbc) i can't see no oracle odbc driver. what wrong?
Edited by: 906540 on 07.01.2012 11:37

Great you have figured it out finally. Just thought you should know that there is a bug in 11gR2 client and because of that Oracle driver version is shown as 11.1.0.7 instead of 11.2.0.2. This can be confusing 6 months or a year later down the road if you wanted to go back and upgrade your client to, let's say' 12g. To fix this, there is a patch available from Oracle metalink, patch id is p11731183 for 32bit and p11731184 for 64bit windows. This bug is mentioned in 1308617.1

11G ODBC Driver For Linux x86_64

I've got Oracle Database 11G installed on a machine running Fedora Core.
I'm trying to find an ODBC driver for it, but I am not seeing anything except for one made by EasySoft that you have to pay for.
Oracle's documentation claims that they have ODBC drivers, but when I go to the software section all I see is one for 10G that was last updated in 2006.
Am I just not looking in the right place?
Thank you.

Sudheendra,
Clicking on your link provides a location where the instant client can be downloaded. However, the last x86-64 instant client with ODBC is 10.2.0.4 and (as you have mentioned in other threads) this is not "officially" support. Furthermore, there is a bug in this version that appears when trying to run any query (connect is OK though). So, can't use 10.2.0.4. It appears there are no 11.x versions of the x86-64 instant client that support ODBC.
So, given an x86-64 system, where everything is running 64-bit, what are we to do with regards to an Oracle Instant Client?
I have mysql, Teradata and SQL Server all running fine with 64-bit ODBC. Is my only choice to go back to all 32-bit libraries?
Thanks!
Keehan

ODBC Driver 8.1.7.3 - pending bugs?

Similar Messages

Maybe you are looking for