Link to home
Start Free TrialLog in
Avatar of crishna1
crishna1Flag for United States of America

asked on

driver's sqlsetconnectattr failed

Hi,

I have an application running on 32-Bit OS and pointing to a 64bit Oracle and i encounter the driver's sqlsetconnectattr failed error. is it due to the drivier being 32-bit? It make the connection fine but when trying to retrieve (SELECT) data to a screen in the apllication it throws this error. any ideas?

Thanks!
Avatar of crishna1
crishna1
Flag of United States of America image

ASKER

I just looked at the dll on both the machines. The application which has Oracle 32-bit running has the driver dll as SQORA32.DLL. suprisingly the 64-bit Oracle also has the same driver. so i guess the driver is not the problem?
ASKER CERTIFIED SOLUTION
Avatar of slightwv (䄆 Netminder)
slightwv (䄆 Netminder)

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
The application server has 32-bit Oracle installed. yes, it is using ODBC. The app is written in Visual C++. It is using Oracle odbc. But it is not the driver that was installed by client , this server originally had Oracle db server (which is shutdown now) and the driver is from that install.
Avatar of slightwv (䄆 Netminder)
slightwv (䄆 Netminder)

I saw that from your other related question.

Not sure about the driver that 'is not the driver' versus 'from that install' means.

Not a C++ person but I wonder if the versions from the old working server does not match the new app server.

This is an issue in the .Net world once an app is compiled.  Different Oracle clients normally need a recompile.  Might be different in the C++/ODBC world.

Check with the app developers.
1) there is no new app server
2) previosuly the app and database were on the same server ( since you refered to the other question you already know this)
3) the database has been moved to a new 64-bit server ( which you already know from the other  question) The database on the old server has been shutdown.
4) the above is issue is the app connceting using ODBC to the new database.
     The ODBC driver on teh app server was from teh install of the database that existed there before. there is no Oracle client on teh app server since teh driver is already there

can be any more eloberate? let me know.
Got it.

Not sure on this one.  There should be no problems I can see if the tnsnames.ora file is pointing to the new server.

That looks like an odbc error.  It will have to wait for tomorrow for me to get on a real computer.

Hopefully another Expert will have an answer before then.
sure, no problem, can wait. thnx!

It is making the connection , i can see that cause it is writing the data to the database ( i check a table data time stamp). It is one of the screen where it reteives database (select) from the database.
For grins and future Experts:

What are the Oracle client and new database versions?

Please use all 4 numbers.  For example:10.2.0.4
sorry for the delayed reply, was out for couple of days.

sys@meterboth client and server are 11.2.0.1
I'm unable to locate anything specific with just that fragment of the error.

Can you get the entire stack trace form the app?  I'm looking for a more descriptive error message or Oracle error number.
None.