This content has been marked as final. Show 6 replies
The static listener is needed for the RMAN connection later. Since there is no database to connect to RMAN uses it.
1)Why do we need to use the static listener?
So the extra entry for the clone database is needed because otherwise RMAN has nothing to connect to.
You also need an entry for the CLONE in your TNSNAMES.ORA on both servers.
I also add these : ( To prevent timeouts )
INBOUND_CONNECT_TIMEOUT_ = 120
SQLNET.INBOUND_CONNECT_TIMEOUT = 120
Then stop and start the listener.
For question two I don't know the answer as I have never done that setup. That said you don't need it on the Primary nodes. Adding to all Standby nodes is harmless.
So for active duplicate you want an entries for the new duplicate in the source and destination. The process needs these because it does not just talk one way.
So update tnsnames.ora on primary and standby systems. If the Primary was Chicago and the Standby was Boston make sure you have entries for both Chicago and Boston on both servers in the tnsnames.ora
It occurs to me for RAC this has to be a requirement cluster-network nodes.
I'm having trouble finding the exact document but "Update Network Configuration Files" in the White Paper "Rapid Oracle RAC Standby Deployment: Oracle Database 11g Release 2"
The problem is I cannot find a quote where "Broker" is not in the picture.
At this point there are two similarly configured but different Oracle RAC databases, each in the primary role. Before creating the standby database, update the network configuration files on all systems to ensure proper client access to both databases and to create the static service entries used by the Oracle Data Guard observer and broker command line utility, DGMGRL.
There is also a "Listener.ora Files" section to this document which supports this.
A search of "static" that document may provide your answer.
Edited by: mseberg on Aug 30, 2012 2:32 PM