Don't forget, you can use a service with JDBC THin connections server:port/service_name Bradd Piontek On Mon, Dec 6, 2010 at 5:56 PM, CRISLER, JON A (ATTCORP) <JC1706@xxxxxxx>wrote: > If you are running your JDBC thick client on the same server, I imagine it > would work fine, but if you are running jdbc thin drivers on a separate > server where it does not use tnsnames, then an alias would not work, right ? > > > > Good tip about v$parameter2- I did not know that existed. > > > > > > *From:* Jared Still [mailto:jkstill@xxxxxxxxx] > *Sent:* Monday, December 06, 2010 6:53 PM > > *To:* CRISLER, JON A (ATTCORP) > *Subject:* Re: non-RAC service names ? > > > > On Mon, Dec 6, 2010 at 1:44 PM, CRISLER, JON A (ATTCORP) <JC1706@xxxxxxx> > wrote: > > Can additional service names be defined for a non-RAC 10g database, similar > to how multiple service names can be configured for RAC ? This would be to > support JDBC connections, so a tnsnames alias would not work. I have > looked over various docs and I do not see any way of creating them- and I > tried DBCA as well as that allows managing service names on a RAC db, but > that option is disabled for a non-RAC db. > > > > Hi Jon, > > > > I've never run into an issue using tns aliases with JDBC. > > > > Maybe I've just been lucky. > > > > What problems did you encounter? > > > > As for service names, I've been using several service names for quite some > time without issue. > > > > BTW, in case you don't already know, if you use v$parameter2 rather than > v$parameter > > to lookup service_names, they will each appear on a separate row. > > > > Jared > > > > > > >