On 8/16/06, Loo, Peter # PHX <[EMAIL PROTECTED]> wrote:
Hi John,
It turns out that the INSTANCE that I am trying to connect to is a
32-bit 9.2 Oracle database while my profile is pointing to Oracle 10.2
path. Once I changed the ORACLE_HOME to /opt/app/oracle/product/9.2,
the connection worked.
Now I just have to remember that when I connect to an INSTANCE that is
lower in version than my local INSTANCE, I will need to first set my
ORACLE_HOME to the version I am connecting to. So the question now is,
is there a way to check dynamically what version the remote INSTANCE is
running? Is there a tool out there that would give me this information
or will I have to create one of my own? Trying not to re-invent the
wheel. :D
Peter
select version from v$instance
But you should always be able to connect to older versions from a
newer version $ORACLE_HOME. I suspect that the earlier suggestion of
a possible 32BIT OCI bug may be the real issue.
--
--------------------------------------------------------------------------------------------------------------
The darkest places in hell are reserved for those who maintain their
neutrality in times of moral crisis.
Dante Alighieri (1265 - 1321)
They who would give up an essential liberty for temporary security,
deserve neither liberty or security.
Benjamin Franklin
Our lives begin to end the day we become silent about things that matter.
Martin Luther King
The right of the people to be secure in their persons, houses, papers,
and effects, against unreasonable searches and seizures, shall not be
violated, and no warrants shall issue, but upon probable cause,
supported by oath or affirmation, and particularly describing the
place to be searched, and the persons or things to be seized.
Amendment IV to the Constitution of the United States
--------------------------------------------------------------------------------------------------------------
