listener.ora parameters

Quote:

---

actually that's a windooze port redirection, not an oracle redirect as I understand it

---

Looks like it's both (http://metalink.oracle.com/metalink/...&p_id=125021.1)

Quote:

---

Oracle Multi-Threaded Server (MTS) on Unix platforms, (without specifying the address with the ports in the INIT.ORA file), Oracle Secure Sockets Layer (SSL) and Windows NT/2000 platforms will cause port redirection.

---

Quote:

---

Shared socket doesn't always work on all platforms and releases

---

OK, but it's a darn sight quicker to try that first than set up a CMAN!

There are more details here: http://metalink.oracle.com/metalink/...T&p_id=66382.1

You're right. We tried it first and it didn't work, which is why we went to CMAN for one of our apps. It worked.

If I remember correctly, the problem is more release level than intent. IE, it may work now, but not on the release we use/were using on that server config (which is Windows). The mix of OS release and Oracle release was our problem, I believe.

We are running into the same thing currently with allowing connections through a firewall. We are on win2k so we are getting the port redirection action happening.

With our firewall (checkpoint) you can set up a sql*net proxy that will allow connections to pass through. However, with our current version checkpoint does not support port redirection, however, with the latest version of checkpoint that is currently available you can do port redirection.

regards,

steve

You can set up shered server configuration (aka multithreaded server) of Oracle database, where you can easily prevent port redirection, that is you can "fix" the port where all the talking between the database and the client process will take place. So there's no need for CMAN or shared socket configuration if you don't want to use them.