Configure the Listeners and
SQLNet.ora
Configure the listeners on all nodes for the Oracle Database Exadata Cloud Service and the on-premises Oracle Exadata Database Machine.
Add a Static Listener to the Standby Instance
Add a static listener to Grid Home on the Oracle Database Exadata Cloud Service instance.
Configure SQL Net.Ora
Configure and copy the sqlnet.ora
file to all the nodes of
both the primary and standby Exadata instances, including grid home. The SQLNET.ora
configuration must exist on the on-premises Oracle Exadata Database Machine and the Oracle Database Exadata Cloud
Service.
The following is a snap shot of the values across the nodes.
The wallet file location must exist in the SQLNet.ora file on both the primary and
standby Exadata instances. Ensure that there are no line breaks or white spaces in
the SQLNET.ora
file.
Update the Instance and Database Names on All Nodes
Change the instance and database names in the tnsnames.ora
file on all nodes of the primary on-premises Exadata and the standby Oracle Database Exadata Cloud
Service. Entries for each database are needed in both primary and standby
tnsnames.ora
files for proper redo
transport.
In this example.
- DB1: Primary on-premises Oracle Exadata Database Machine DB Name
- db11: Database Instance Name on Node 1
- db12: Database Instance Name on Node 2
- DB1_phx3g7: Unique Oracle Database Exadata Cloud Service instance name.
- DB11: Oracle Database Exadata Cloud Service instance Name 1 on Node 1
- DB12: Oracle Database Exadata Cloud Service instance Name 2 on Node 2
If the primary database has a TNS entry in the on-premises
tnsnames.ora
file with a server name for the HOST, then change
the server name in that entry to use the IP address for the host instead. IP
addresses are used since there is no DNS between on-premises and cloud environments
to resolve server names to IP addresses.
Oracle Real Application Clusters (Oracle RAC) configurations cannot resolve the scan listener name; therefore, you must use an address list that lists all nodes. Those will be added later, the initial instance should only list one IP in the TNS entries to ensure Oracle Recovery Manager (RMAN) is always connecting to the same nodes
Use the following example, replacing values relevant to the configuration.