Connecting to Oracle database via SQLTalk

[hroitner]

Hi there,

I have properly installed Oracle database 11g 64bit and want to connect to it via the SQLTalk that is part of my TD6.1 SP6 installation (SQLTalk version 10.0.1.13914).

But I get the error '00401 DBA COD Cannot open database'.

Further info: in my sql.ini I have under [oragtwy] remotedbname=orcl,@tns:orcl

I would urgently need your help on this!

Thanks, Heinz

[Dave Rabelink]

TD (Win32) does not support 64Bit database drivers.
Install Oracle 32 bit.

[wardies]

To clarify a little:

It is possible for an application to use an Oracle 32-bit Client to connect to an Oracle 64-bit server (and vice versa).

If you have installed Oracle 11g Server 64-bit on the same machine you wish to run the test, you cannot use the 64-bit client that will have been installed with the server to connect TD 6.x applications, because TD6.x applications can only use 32-bit DLLs.

However, you can install an additional 32-bit Oracle 11g Client on the same machine. Providing your paths, etc. are set up to use the 32-bit Oracle client when running your TD6.x application (and IDE), you're good to go. Remember that since you now have two clients on the same machine, you also have two TNSNames.ora files to maintain (one for each bitness).

[hroitner]

Thanks for your responses.

I have now additionally installed Oracle 11g 32 bit client version, but I get another error:

00133 SQL IVE ERROR 32154 NOT FOUND IN ERROR.SQL

Any idea what this error means or where it is documented ?

Thanks, Heinz

[wardies]

Yes, remember to deduct 20,000 from the Oracle error numbers to get the true error code:

32154 - 20000 = 12154 = ORA-12154 (TNS: Could not resolve the connect ID)

If you search for "ORA-12154" you will find many hits with advice. Usually the issue is your ...\Network\ADMIN\TNSNames.ORA file does not contain an entry for your TNS Name, or the entry is incorrect.

Remember that since you now have two folders containing Oracle clients (64- and 32-bit) you will probably be safer keeping both copies of TNSNames.ORA up-to-date/in sync to avoid confusion. Just be careful with editing the 64-bit client's version because if you break this, your database/maintenance utilities may stop working.