Oracle on OpenVMS

[ericfjchen]

This is Oracle 9.2.0.5 on OpenVMS 7.3-2.
The listener port of Oracle DB is 1521. When a client connects to Oracle, the session should be established by OracleHost@1521 & Client@random port. However, we found the session was not established on Oracle listener port 1521. It is a random port large than 1000. Is it normal? Can we fix the Oracle listener port?

[Steven E. Protter]

Shalom,

The oracle listener always defaults to port 1521.

It is best to not use a random port and fix a port. Oracle will listen on any port you tell it to use.

SEP

[ericfjchen]

We set the port 1521 to be the Oracle listener port. However, the session was NOT extablished on 1521. Why? How to fix it?

[Darrel Louis]

Hi,

What is the Oracle error-message your getting?

If you do a telnet from a different server to the database server on port 1521 do you get a connetion refused error?

telnet 1521

Darrel

[melvyn burnard]

This thread was posted in completely the wrong forum, moving to more appropriate forum

[Willem Grooters]

Just a reminder: See thread http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1029299, it may hold a clue:
* Port ownership/protection
* Commanfile ownership/protection
* Protection of log directroy (typically SYS$LOGIN of service UIC)

Willem

[Louis in Michigan]

Since I touched ORACLE 7 on OpenVMS many years ago, this may not be how ORACLE 9 works. As I recall, under ORACLE 7, the listener would field the incoming connections on port 1521, then, send back to the caller a port number which should be used for the ORACLE database SQL connection. Then a new connection is established to the port which was designated by the listener. This way the listener is always free to do it job as traffic director.

[Bojan Nemec]

As Louis mentioned the Oracle default way to service connections is to open a new port for each connection.
You have a special parameter in listener.ora:
use_shared_socket = true

which instruct Oracle listener to use the service port (normaly 1521) for connections and communications. With this parameter Oracle listener acts as a normal TCP/IP service.

But there is little problem. The last time I try this parameter on VMS it does not work :(. It was a little older version of Oracle (I think 9.1...) and VMS 7.2-1. When I try with the same version on NT and on Linux it works OK.

You can try to put the parameter in yours listener.ora and see how it works.

Bojan