Service name and TAF tnsnames entry for Data Guard and client/service connections
edited May 22, 2013 7:33PM in High Availability Data Guard, Sharding and Global Data Services (MOSC) 7 commentsAnswered
I created a new physical
standby for a new primary DB. It's not clear to me based on the standby
creation notes available or the TAF note available how to setup the
unique service name that seems to be used in the tns entry. I remember
having issues with this in a prior DG setup & current production
system back in 2009. Those note are below:
1. Is a trigger and unigue service name required to be created as shown below?
2. What is this service? Does it have any relationship ti a listener service?
3. Is this documented anywhere?
4. Does it have any relationship to, or require any changes to my current listener?
1. Is a trigger and unigue service name required to be created as shown below?
2. What is this service? Does it have any relationship ti a listener service?
3. Is this documented anywhere?
4. Does it have any relationship to, or require any changes to my current listener?
0