We have an application that make a jdbc connection using the thin driver.
The application set up includes specifying the port number to the Oracle
database. Our DBA tells me that from time to time they will change port
numbers of the databases which means I will have to re-point the application
to the new port.
How do people deal with constantly changing Oracle port numbers when using
the thin driver? Is constant re-configuring of the port number just a fact
of life when it comes to the thin driver?
On the wall of the virtual bathroom stall, "Jim Havero" <jhavero@shaw.ca> scratches:
> We have an application that make a jdbc connection using the thin driver.
> The application set up includes specifying the port number to the Oracle
[quoted text clipped - 5 lines]
> the thin driver? Is constant re-configuring of the port number just a fact
> of life when it comes to the thin driver?
not sure about your specific driver but the jdbc docs show that the
connection port number is an optional part of the url. it should be
kind of trivial to use:
jdbc:oracle://host:port/dbname
to connect, assuming your driver recognizes it...
just pass the connection URL into the app as a system property or cmd line
argument so that you can change it at runtime.
-Wiseguy