Toad World® Forums

TOAD vs 64bit version of Oracle database

Message from: ptomasek_859

Hi Everybody! I have kind of annoying issue with TOAD installation in our
company. I have been given a task to install TOAD right on server running 64nit
version of Oracle database. Here is the detailed setup: Server Windows 2003
64bit standard Oracle database 10.2.0.4 (64bit for windows) TOAD 32bit version
9.7 Here are my problems: The TOAD did not start, because it was missing
oci.dll. I realized that there might be a problem of TOAD not being friendly
with 64bit version od Oracle database. Or at least this version of TOAD we have.
So I installed 32bit Oracle client as well to get over this problem. It was
working fine and TOAD can actually connect the running database instance without
any problems. BUT … there is one problem. Only direct connect is actually
working. If I use the information stored in tnsnames.ora file so it says the
TOAD could not resolve given SID. I have the same tnsnames.ora in both oracle
homes (database and client). Listener is running fine. tnsping is also working
fine. As soon as I choose oracle client home in TOAD and I try to connect via
tnsnames.ora so it does not work. There is no mess in sqlnet.ora files. I have
nothing else there but NAMES.DIRECTORY_PATH= (TNSNAMES). Anyone experiencing the
same problem ?


Historical Messages

Author: ptomasek_859
Date: Mon Nov 14 01:06:59 PST 2011
Hi Everybody! I have kind of annoying issue with TOAD installation in our
company. I have been given a task to install TOAD right on server running 64nit
version of Oracle database. Here is the detailed setup: Server Windows 2003
64bit standard Oracle database 10.2.0.4 (64bit for windows) TOAD 32bit version
9.7 Here are my problems: The TOAD did not start, because it was missing
oci.dll. I realized that there might be a problem of TOAD not being friendly
with 64bit version od Oracle database. Or at least this version of TOAD we have.
So I installed 32bit Oracle client as well to get over this problem. It was
working fine and TOAD can actually connect the running database instance without
any problems. BUT … there is one problem. Only direct connect is actually
working. If I use the information stored in tnsnames.ora file so it says the
TOAD could not resolve given SID. I have the same tnsnames.ora in both oracle
homes (database and client). Listener is running fine. tnsping is also working
fine. As soon as I choose oracle client home in TOAD and I try to connect via
tnsnames.ora so it does not work. There is no mess in sqlnet.ora files. I have
nothing else there but NAMES.DIRECTORY_PATH= (TNSNAMES). Anyone experiencing the
same problem ?
__


Morning,

Server Windows 2003 64bit standard Oracle database 10.2.0.4 (64bit for
windows)

BUT … there is one problem. Only direct connect is actually
working. If I use the information stored in tnsnames.ora file so it says
the TOAD could not resolve given SID.

I have the same tnsnames.ora in
both oracle homes (database and client). Listener is running fine.
tnsping is also working fine.

Would that be the 32 bit tnsping or the 64?

As soon as I choose oracle client home in
TOAD and I try to connect via tnsnames.ora so it does not work. There is
no mess in sqlnet.ora files. I have nothing else there but
NAMES.DIRECTORY_PATH= (TNSNAMES). Anyone experiencing the same problem ?

This means that your default domain name will be “.world” and unles your
tnsnames.ora file has the database alias names suffixed with .world, you
won’t get tnsping etc to work.

Check the following:

  • You are definitely running 32 bit tnsping when you say “it’s working”.
    Cd to the bin folder and .\tnsping.

  • Does the registry for the 32 bit client have an entry for tns_admin
    which is pointing you at the wrong location? If so, set it to where you
    find the 64 bit sqlnet.ora and tnsnames.ora.

I suspect that it is set to point into your 32 bit home\network\admin
and all your data are found in the 64 bit home.

  • Can you connect ok using the 32 bit sqlplus? Remember to run it from
    the bin directory of the 32 bit client.


Cheers,
Norm. [TeamT]

Message from: DougK

Did you set the TNS_ADMIN environment variable so both ORACLE_HOME’s can
share the same tnsnames.ora file?


Historical Messages

Author: DougK
Date: Wed Nov 16 15:07:58 PST 2011
Did you set the TNS_ADMIN environment variable so both ORACLE_HOME’s can
share the same tnsnames.ora file?
__

Author: Norman Dunbar
Date: Mon Nov 14 01:06:59 PST 2011
Morning, > Server Windows 2003 64bit standard Oracle database 10.2.0.4 (64bit
for > windows) > … > BUT … there is one problem. Only direct connect is
actually > working. If I use the information stored in tnsnames.ora file so it
says > the TOAD could not resolve given SID. > I have the same tnsnames.ora in >
both oracle homes (database and client). Listener is running fine. > tnsping is
also working fine. Would that be the 32 bit tnsping or the 64? > As soon as I
choose oracle client home in > TOAD and I try to connect via tnsnames.ora so it
does not work. There is > no mess in sqlnet.ora files. I have nothing else there
but > NAMES.DIRECTORY_PATH= (TNSNAMES). Anyone experiencing the same problem ?
This means that your default domain name will be “.world” and unles your
tnsnames.ora file has the database alias names suffixed with .world, you won’t
get tnsping etc to work. Check the following: * You are definitely running 32
bit tnsping when you say “it’s working”. Cd to the bin folder and .\tnsping. *
Does the registry for the 32 bit client have an entry for tns_admin which is
pointing you at the wrong location? If so, set it to where you find the 64 bit
sqlnet.ora and tnsnames.ora. I suspect that it is set to point into your 32 bit
home\network\admin and all your data are found in the 64 bit home. * Can you
connect ok using the 32 bit sqlplus? Remember to run it from the bin directory
of the 32 bit client. – Cheers, Norm. [TeamT]
__

Author: ptomasek_859
Date: Mon Nov 14 01:06:59 PST 2011
Message from: ptomasek_859 Hi Everybody! I have kind of annoying issue with TOAD
installation in our company. I have been given a task to install TOAD right on
server running 64nit version of Oracle database. Here is the detailed setup:
Server Windows 2003 64bit standard Oracle database 10.2.0.4 (64bit for windows)
TOAD 32bit version 9.7 Here are my problems: The TOAD did not start, because it
was missing oci.dll. I realized that there might be a problem of TOAD not being
friendly with 64bit version od Oracle database. Or at least this version of TOAD
we have. So I installed 32bit Oracle client as well to get over this problem. It
was working fine and TOAD can actually connect the running database instance
without any problems. BUT … there is one problem. Only direct connect is
actually working. If I use the information stored in tnsnames.ora file so it
says the TOAD could not resolve given SID. I have the same tnsnames.ora in both
oracle homes (database and client). Listener is running fine. tnsping is also
working fine. As soon as I choose oracle client home in TOAD and I try to
connect via tnsnames.ora so it does not work. There is no mess in sqlnet.ora
files. I have nothing else there but NAMES.DIRECTORY_PATH= (TNSNAMES). Anyone
experiencing the same problem ? _______________________________________
Historical Messages Author: ptomasek_859 Date: Mon Nov 14 01:06:59 PST 2011 Hi
Everybody! I have kind of annoying issue with TOAD installation in our company.
I have been given a task to install TOAD right on server running 64nit version
of Oracle database. Here is the detailed setup: Server Windows 2003 64bit
standard Oracle database 10.2.0.4 (64bit for windows) TOAD 32bit version 9.7
Here are my problems: The TOAD did not start, because it was missing oci.dll. I
realized that there might be a problem of TOAD not being friendly with 64bit
version od Oracle database. Or at least this version of TOAD we have. So I
installed 32bit Oracle client as well to get over this problem. It was working
fine and TOAD can actually connect the running database instance without any
problems. BUT … there is one problem. Only direct connect is actually working.
If I use the information stored in tnsnames.ora file so it says the TOAD could
not resolve given SID. I have the same tnsnames.ora in both oracle homes
(database and client). Listener is running fine. tnsping is also working fine.
As soon as I choose oracle client home in TOAD and I try to connect via
tnsnames.ora so it does not work. There is no mess in sqlnet.ora files. I have
nothing else there but NAMES.DIRECTORY_PATH= (TNSNAMES). Anyone experiencing the
same problem ? __ _______________________________________
__


Did you set the TNS_ADMIN environment variable so both ORACLE_HOME’s can share the same tnsnames.ora file?