Re: Oracle Client & ORA-12535

On 13 Jan 2005 11:02:23 -0800, "HARI OM" <hari_om_at_hotmail.com> wrote:

>ANy other hints or related informaiton is appreciated...
>THANKS!
Oracle always uses 2 ports. The listener is a broker, initially the client connects over the well documented 1521 port. Then the listener will fork a process and create a socket, this socked will communicate over a *RANDOM* port.
You can verify this by tracing the sqlnet connection. Evidently the Oracle assigned port is not open, and no firewall administrator will open a random series of ports.

There are several solutions to this problem, as published on Metalink, and in the Net documentation

1 Make sure your firewall recognizes sqlnet traffic by means of a so-called sqlnet proxy.
2 Put use_shared_sockets=true in sqlnet.ora on the server. Now you will use only one port
Disadvantage of this solution: when you stop the listener, the port is closed and all sessions are disconnected. 3 Set up connection manager (documented in the Net manual). All communications will be redirected over the port you have configured in cman.ora. No real disadvantages, works like a charm. 4 Configure multithreaded server in your database, and limit access to one distinct single port.
Disadvantage: need to configure the large pool, and several operations are not possible when using shared server.

I would prefer solution 3. I know it works for a fact.

--
Sybrand Bakker, Senior Oracle DBA