checking status on two listeners on one server

We have just set up a second environment on the same server to test an upgrade. We set up a separate listener because we want to be sure we are running the new version of the listener in the test environment. We have it running, but I'm not 100% sure if I really have 2 separate listeners because of the following:

• When we run "lsnrctl status" from the original environment, we see the new environment in the status output like it's all on the same port.
• When we switch to the new environment and run "lsnrctl status", we see the same thing, it reports on all listener environments. We expected an error saying that the default listener doesn't exist.
• When we run "lsnrctl status LISTTEST" which is the new/second listener from the first environment, we get "TNS-01101: Could not find service name NNC-00405: network failure" which we would expect.
• When we run "lsnrctl status LISTTEST" from the new environment we see the correct output with the correct port # and only for the new listener.

So, question, why is output for the new listener displayed when we just do the default "lsnrctl status"? We expected it to only show output for things associated with the default/existing listener.

Also, when we do a ps, we only see one listener process running. However, we see both ports in output from netstat. We expected to see two listener processes in the "ps" output too. So do we have one listener running or two?

FYI, this is a 9.2 server just being patched up to a slightly higher version of 9.2. Part of the reason we are doing this is so we can later start testing the upgrade to 10g. The first step though is to get 2 separate environments up and running and part of that is to have 2 separate listeners. We know you can have one listener, managing both, but we want to be able to test emergency bug fixes to the current environment while working on fixes resulting from the upgrade. And for the sake of thoroughness, we want to isolate the impact of possible changes to the listener code along with everything else.

Thanks in advance for your help
Teresa Masino Received on Fri Feb 24 2006 - 11:02:39 CST