Unique Service Names in Data Guard ?

[BJE_DBA]

Well I used the Oracle docs and have two machines that both come up and all the commands working out but my logs dont get sent.

I know it has to do with my lack of understanding of the tnsnames and listener configs for Data Guard.

The Docs say to use the same db_name and instance_name but I cant get connectivity to both unless I use the same service_name = db_name. That wont work as I need a different service_name for the standby so the primary knows where to ship them off too but I cant find this info anywhere.

Thanks in advance.

[BV1963]

How about using different domains?

DB.MYDOMAIN1=
DB.MYDOMAIN2=

[sreddy]

You are confused with terminology interpretations of

instance_name ---> Memory structures associated with database
db_name ----> databse associated with instance
service_name ---> a connect string which locates database associated with instance.

db_name=instance_name!= service_name

You can configure different service_name(name it xyz) to your standby instance and use that service_name in initSTBY.ora for log transport.

[BJE_DBA]

Originally posted by sreddy

You can configure different service_name(name it xyz) to your standby instance and use that service_name in initSTBY.ora for log transport.

Well that is what I thought. But I was up passed midnight trying to get the xyz service_name to work with connect /@xyz as sysdba.

This is windows in my lab and try as I might I would create a new windows service xyz and it just never works I must have tried it 50 times and concluded it would only work when the service_name = db_name.

I would really like to make this work since I was just handed a broken Data Guard system on Solaris at work. I would like to fully understand windows manual setup before venturing forth to fix the OEM auto setup here.

btw doesnt the service_name need to be in the initPrimary.ora and not initSTDBY.ora ? I wish the docs were more complete. A couple examples would be great.

Thank you for your support