Re: Using Service Names for database

From: Stefan Koehler <>
Date: Fri, 20 Feb 2015 13:25:17 +0100 (CET)
Message-ID: <>

Hi Jeff,
yes, i also use and implement multiple service names in most of my client's RAC environments. Why? Mostly due to load balancing goals for different apps / client technologies (e.g. OCI, JDBC, etc.) with feature limits (e.g. TAF, FAN, etc.).

I also just enable the features (per service) that they can use for that particular app in order to avoid unnecessary overhead, e.g. like FAILOVER_TYPE = SELECT and Oracle Net tracking.

Another main reason for implementing an additional service is tracing dedicated sessions or apps with DBMS_MONITOR.SERV_MOD_ACT_TRACE_ENABLE.

Best Regards
Stefan Koehler

Freelance Oracle performance consultant and researcher Homepage:
Twitter: _at_OracleSK  

> Jeff C <> hat am 19. Februar 2015 um 20:43 geschrieben:
> Does anybody use or have experience with using multiple Service Names for your database? Is this a normal thing people do? I have a database that
> is a mix of a bunch of different applications and I would like to better identify them from database connection and so giving them their own service
> name to connect to seems like the perfect fit. One thing I did noticed that we will have to be careful about is if you restore that database to the
> same server with a different name and you don't change the service name parameter then the listener will pick up that service name and your users
> may be going to the restored database and not production.
> Any other things to think about and/or is this a bad practice?
> Thanks,
> Jeff

Received on Fri Feb 20 2015 - 13:25:17 CET

Original text of this message