| OLEDB Error after upgrade from Client 8.1.7 to 9.1 and 9.2 [message #140748] |
Wed, 05 October 2005 08:07  |
DieterS
Messages: 4
Registered: October 2005
|
Junior Member |
|
|
Hi all,
after upgrading the oracle client on my Win Xp machine, some of my sql statements don't work anymore.
It seems, that the oledb-client removes blanks from the original sql-statement. It sounds strange, but unfortunately it' true.
Example:
Original statement:
SELECT FVOLOCKUSER , (SELECT SYSDATE FROM DUAL) as SERVERTIME FROM myschema.FVO WHERE FVOSATZ=-2147483645 FOR UPDATE
I traced the resulting statement at the server:
SELECT FVOLOCKUSER , (SELECTSYSDATEFROMDUAL) as SERVERTIME FROM myschema.FVO WHERE FVOSATZ=-2147483645 FOR UPDATE
Obviously, the oledb provider removed the blanks between the components of the subselect, so i get the error message
ORA-00904: invalid column name
If i start the subselect as single statement, everything works fine.
In other statements, i get "missing expression" error. All of the statements, that don't work any more, are using subselects.
I tried OLEDB-Provider 9.1 and 9.2, no chance.
If i change the provider to Microsoft MSDAORA everything works fine.
Unfortunately, our customer insists on the oracle provider.
Environment:
Client: Win XP
Server Oracle 8.1.7 on Win 2000 Server
Application VB 6 with ADO/OLEDB
Thanks,
Dieter
|
|
|
|
|
|
| Re: OLEDB Error after upgrade from Client 8.1.7 to 9.1 and 9.2 [message #140939 is a reply to message #140930] |
Thu, 06 October 2005 06:18  |
DieterS
Messages: 4
Registered: October 2005
|
Junior Member |
|
|
Hi sunilkumar,
but my application runs well with Oracle Client 8.1.7,
I'm able to reproduce the error on different machines.
There is nothing special, just a simple SELECT with a subquery,
fired with an ADO connection.execute to fill a recordset.
Is it possible to configure the client for that behaviour?
So what could I check on application side? Could you please give me a further explanation?
Thanks,
Dieter
[Updated on: Thu, 06 October 2005 06:26] Report message to a moderator |
|
|
|
|
|
| Re: OLEDB Error after upgrade from Client 8.1.7 to 9.1 and 9.2 [message #140972 is a reply to message #140748] |
Thu, 06 October 2005 07:57 |
DieterS
Messages: 4
Registered: October 2005
|
Junior Member |
|
|
Hi,
yes, i am able to connect.
The same SQL works fine on SQLPlus and PL/SQL-Developer,
so that's why i think, that the OLEDB-Provider causes the error.
My tnsnames.ora is configured, it works well with Client 8.1.7 and the same network configuration.
I had exactly the same problem on the customers machine in an complete independent network.
I can't believe, that i am the only one who has this reproduceable error. I've searched for hours in different forums and in news groups and found only one similar post but unfortunately no solution.
Thanks,
Dieter
|
|
|
|
| Re: OLEDB Error after upgrade from Client 8.1.7 to 9.1 and 9.2 [message #141140 is a reply to message #140972] |
Fri, 07 October 2005 02:49 |
sunil_v_mishra
Messages: 506
Registered: March 2005
|
Senior Member |
|
|
hi,
Well you are able to connect throung sqlplus from client machine that means there is no problem at database end i.e. at server
You had a problem of OLEDB if i m not wrong OLE stand for object linking & embeding, Secondly u are trying to connect to the database with some application which is made in VB or ASP It will be better if you check and see the OLEDB provider at client machine... well i m not guy of VB or ASP but i know OLEDB & ODBC is used to provide connection to the database by ASP or VB.
Note :- I think your message should be posted on that forum on which people discuss regarding VB ASP .NET technologies.
Regards
Sunilkumar
[Updated on: Fri, 07 October 2005 02:51] Report message to a moderator |
|
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
