RE: Using Service Names for database

From: Stephens, Chris <>
Date: Thu, 19 Feb 2015 15:17:15 -0600
Message-ID: <>

Service names also allow you to take better advantage of all the fantastic instrumentation oracle provides through V$* and AWR.

From: [] On Behalf Of Andrew Kerber Sent: Thursday, February 19, 2015 2:47 PM To:
Cc:; Subject: Re: Using Service Names for database

Most places use service names for RAC and non-RAC. It has many uses related to workload separation. A common one is to distinguish between a primary and a standby open in read only or read only with apply. You don't need to change your tnsnames entry if you do a switch over.

Sent from my iPhone

On Feb 19, 2015, at 1:28 PM, Steve Harville <<>> wrote: Hi Jeff,
It is a good practice, especially on RAC. We create services for each distinct workload. For instance the Warehouse Operations group use a service that is different from the Order Management group. This way we can "pin" one type of workload to it's own node and another type of workload to a different node. This reduces the interconnect traffic between nodes since the different services are not updating the same data blocks. Steve

On Thu Feb 19 2015 at 2:44:29 PM Jeff C <<>> wrote: 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,

This message is intended for the use of the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient or the employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by email reply.

Received on Thu Feb 19 2015 - 22:17:15 CET

Original text of this message