If you use the type 4 driver, then the listener.ora is ignored.
Does that mean the requesting port would alway be 1521?
Brad Rhoads wrote:
Here's a bit from our listener.ora. It appears that the jdbc driver may be
sending a sequential request number as the port, or something like that.
Why
Nope:
url = jdbc:oracle:thin:@aserver:1521:instance
-Tim
Brad Rhoads wrote:
If you use the type 4 driver, then the listener.ora is ignored.
Does that mean the requesting port would alway be 1521?
Brad Rhoads wrote:
Here's a bit from our listener.ora. It
: RE: [OT] Oracle Connection Problem Due To Dynamic Port
Numbers
If you use the type 4 driver, then the listener.ora is ignored.
Does that mean the requesting port would alway be 1521?
Brad Rhoads wrote:
Here's a bit from our listener.ora. It appears that the jdbc driver
may
be
sending
If you use the type 4 driver, then the listener.ora is ignored.
-Tim
Brad Rhoads wrote:
Here's a bit from our listener.ora. It appears that the jdbc driver may be
sending a sequential request number as the port, or something like that. Why
isn't it just 1521?
listener.log:04-FEB-2002 16:49:30 *
Oracle listens on one port. It then tells you to connect to another and
that's where it actually does the work from. Also, if you're running
through a NAT or a proxy you're not going to be able to talk to Oracle
through it unless you have a SQL*Net proxy built into the NAT box or
proxy (and even
