Re: [Iodbc-applications] About access via iODBC to Oracle

[Tim H. <th...@op...>]

On 9 Dec 2005, at 02:33, Yumiko Izumi wrote:

> It is a question about the procedure which accesses Oracle via iodbc.
> It is that the following accesses are realized by ODBC on us now.
> It thinks. "iODBC" is used for the ODBC driver manager.
> 1) Unix Oracle (local)
> 2) Unix Oracle(client) => Windows Oracle
> Although it is going to realize each in the procedure investigated  
> by WEB etc.
> It is in the state where became errors, such as IM003 and IM008,  
> and it has failed.
> Then, we want to check a procedure etc. again and it contributes.
> Wanting to know is [ following ] a point.
> - Setup required for the Oracle side
> - The ODBC driver and setup of Oracle
>   hsdb_odbc.so suited the machine.
> - Setup by the side of iODBC
>   Description of odbcinst.ini and odbc.ini
> - Others

Hi,

OK, I'm having difficulty working out what you're trying to achieve,  
but taking a general case: the ODBC architecture is that a client  
application which talks to the Driver Manager (iODBC in this case),  
which loads a driver (for Oracle) which connects to the database.
You will need to install an ODBC driver for Oracle from somewhere.  
(OpenLink provide these for Unix and Windows platforms.)

Taking your questions: odbcinst.ini tells the driver manager what  
ODBC drivers have been installed:

> [ODBC Drivers]
> Oracle = Installed
>
> [Oracle]
> Driver = /opt/openlink/lib/ora100_mt_lu.so

(optionally with a Setup= line for the setup dialog library for the  
driver).

odbc.ini contains a list of ODBC Data-sources (DSNs), thus:

> [ODBC Data Sources]
> oralocal = Oracle
>
> [oralocal]
> Driver = /opt/openlink/lib/ora100_mt_lu.so
> Description = Oracle instance on localhost
> Options = TNSname
> Database =
> JetFix = No
> Username = scott
> Password = tiger
> FetchBufferSize = 99
...

The exact name of the Driver library and the parameters in odbc.ini  
depend on which ODBC Driver you're using; the example above is for  
OpenLink Lite.

You should seek to make a connection work with iodbctest first, and  
then when that works, set up your application to use it - it might be  
wise to check LD_LIBRARY_PATH (or equivalent), the ODBCINI and  
ODBCINSTINI environment variables.
It would help if you copied the whole error message for these IM008  
and IM003 errors and the contents of your odbc*.ini files.

In the case where Oracle is on a remote server, it depends on what  
version of Oracle you're using: if it's <10, you'll need to configure  
tnsnames.ora with an entry for the remote instance; if it's >=10, you  
can use the Instant Client to connect by providing a full connection- 
string.

We have a document on connecting Hosted Services here:
http://support.openlinksw.com/opie/kbase/851

HTH,

~Tim
-- 
Tim Haynes
Product Development Consultant
OpenLink Software
<http://www.openlinksw.com/>