ODBC and Infomaker

so. I've been using SQL*Plus to query our Oracle 10.2 database and finally got the Infomaker 11.5 tool for some reporting. I have it all installed but having NO luck in setting up a ODBC connection. I can go into the Mircrosoft ODBC admin tool and see the TNS service name if I select Oracle in Ora_10.2. So I select the database I want and when I test connection, everything is good. When I launch infomaker, database painter, I select the ODB ODBC option and new profile. Data source is the one I just tested.
When I try and connect to this new profile, I get:
"SQLSTATE = IM003 Specified driver could not be loaded due to system error 1114 (Oracle in Ora10_2)."
Help??
GrayStricklandAsked:
Who is Participating?
 
pcelbaConnect With a Mentor Commented:
So, let suppose all your software is 32 bits.

You should look what DLL file is used for your ODBC driver. It is visible on Drivers page in ODBC Data Source Administrator. Then you have to look for dependences - it means to list all DLLs which are necessary for the driver DLL.

Dependences can be viewed by special software which is available e.g. here: http://www.dependencywalker.com/

After you know what DLLs you really need then you have to check if they are available and accessible by the user which is executing the Infomaker database painter.

ODBC DLLs are located in Windows\System32 folder obviously.
0
 
pcelbaCommented:
Aren't you mixing 32 and 64 bit environments?

ODBC setup must run under Administrator account but this is probably not valid for Infomaker user. Some of your DLLs is not accessible, so you should check if all DLLs are on the right place and if access rights are OK for the user which is executing Infomaker database painter.

You could also look here:
http://www.experts-exchange.com/Database/Oracle/Q_23726910.html
0
 
GrayStricklandAuthor Commented:
I don't think I'm mixing environments but I guess I wouldn't really know how to check that. I don't know where my DLL's should be, but I did go into regedit and change the permissions for them all so that all accounts have the same 'full access'.
0
 
GrayStricklandAuthor Commented:
turns out that the case ORACLE vs Oracle was wrong so Sybase wasn't seeing the driver file. That's pretty much what you were saying, just specific to this event. Anyway- thanks for the assist.
0
All Courses

From novice to tech pro — start learning today.