E:\dbscripts>rem set oracle 9.2 environment
E:\dbscripts>set ORACLE_HOME=C:\oracle\ora92
E:\dbscripts>set
path=C:\oracle\ora92\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;\\CFOLDC1\fopublic\
E:\dbscripts>set TNS_ADMIN=C:\oracle\ora92\network\admin
E:\dbscripts>c:
C:\>C:\oracle\ora92\bin\lsnrctl.exe
LSNRCTL for 32-bit Windows: Version 9.2.0.5.0 - Production on 20-JAN-2010
17:03:
59
Copyright (c) 1991, 2002, Oracle Corporation. All rights reserved.
Welcome to LSNRCTL, type "help" for information.
LSNRCTL> version
Connecting to (ADDRESS=(PROTOCOL=tcp)(PORT=1521))
TNSLSNR for 64-bit Windows: Version 10.2.0.4.0 - Production
TNS for 64-bit Windows: Version 10.2.0.4.0 - Production
Oracle Bequeath NT Protocol Adapter for 64-bit Windows: Version
10.2.0.4
.0 - Production
Windows NT Named Pipes NT Protocol Adapter for 64-bit Windows:
Version 1
0.2.0.4.0 - Production
Windows NT TCP/IP NT Protocol Adapter for 64-bit Windows: Version
10.2.0
.4.0 - Production,,
The command completed successfully
LSNRCTL>
--
Terry Dykstra
Please check that:
- c:\oracle\ora92 is indeed 32-bit ORACLE_HOME
- It contains file oracle.key
- This file points to Registry entries for 32-bit ORACLE_HOME
Also please check that Registry entries for different ORACLE_HOME are
at the same level in the Registry, something like
HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\HOME0
HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\HOME1
HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\HOME2
In other words you don't have entry at the higher level
HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE
I believe that only one listener is necessary independing of mixing 32Bit
and 64Bit.
Arne Ortlinghaus
In addition to the above, currently active (default) Oracle Home is
determined from the PATH variable: whichever comes first is default.
This simple. But might cause service startup issues if two different
Oracle versions are sharing the same Windows host, both registered
services and both services start under LocalSystem account: one of
them will use wrong home because they both will use system PATH for
determining default home.
As of OP's issue: you surely noticed that though you used lsnrctl v9
it connected to the currently running 64-bit 10.2 listener and had no
problems communicating with it. That's the beauty of Oracle Net in
action. lsnrctl communicates with the listener via TCP - you can
control remote listeners with this utility the same way you control
local one. Better than that: you don't have to install 32-bit listener
alongside the 64-bit one. Bitness of the listener is irrelevant as it
communicates with Oracle instances in platform-independent manner. You
can even have several listeners running on different machines
(possibly all on different platforms) presenting the same Oracle
service (for example, for load-balancing or connect-time failover/
TAF.) To make sure your 32-bit 9i instance correctly registered its
services with the 64-bit 10g listener (which PMON attempts
automatically on instance startup via TCP at localhost:1521, unless
you overridden LOCAL_LISTENER server parameter) issue STATUS command
in lsnrctl and check if all expected services are listed.
More information can be found in Oracle Net Administrator's Guide for
your release.
And why don't you consider running this 32-bit 9i instance in a VM?
Indeed, will require another Windows license, but you'll get isolated,
independent environment without the need to invest into additional
hardware. And Sun's VirtualBox is free and pretty stable.
Hth,
Vladimir M. Zakharychev
N-Networks, makers of Dynamic PSP(tm)
http://www.dynamicpsp.com
Regarding the database server software, running 32 bit Oracle database
server software on a 64 bit OS is not supported.
That's a good enough stopping condition for me.
You need to run the 32 bit software on a 32 bit OS, be it on a
physical or virtual server.
-bdbafh
C'mon! No need for VM's!
Any idea how much 16-bit applications still run under MS Windows?!?
Don't you think Microsoft emulates that, just like any OS vendor/producer?
@Terry: Vladimir is correct; apart from that: it is good practice
to run the highest version of a utility (RMAN/listener/imp/exp).
Of course, if you would insist on a 9.2 listener: it can be done.
--
Regards, Frank van Bortel
Topposting in Usenet groups I regard as offensive - I will not reply
Using 64-bit listener clients cannot connect. I get ora-12518. Lots of
google hits, went through every Oracle on metalink and cannot get it to
work.
--
Terry Dykstra
Did you trace the listener? If you didn't - turn on listener tracing
and see what's being reported as the cause (and post the trace here.)
Also, inspect the alert log for errors and check any associated trace
files. If you see errors mentioning skgpspawn, this might indicate
that PROCESSES is set too low. This might also be an out of memory
problem.
Did you consider the VM approach yet? ;)
Regards,