we reactivated an older RAC (2 nodes) and ran into the following situation:
- the original IP's of the scan-address have been reused, therefore we had to use new IP's
After confuguring the new IP's the command <nslookup> myrac-scan.de.domain.dns returns this result:
Executing <srvctl config scan> returns this:
SCAN name: myrac-scan.de.domain.dns, Network: 1/10.137.1.0/255.255.255.0/bond0
SCAN VIP name: scan1, IP: /myrac-scan.de.domain.dns/10.xxx.x.212
SCAN VIP name: scan2, IP: /myrac-scan.de.domain.dns/10.xxx.x.211
SCAN VIP name: scan3, IP: /myrac-scan.de.domain.dns/10.xxx.x.213
Therefore: everything looks good to us!
When executing <lsnrctl services> we get this:
Service "RAC_DB.de.domain.dns" has 1 instance(s).
Instance "RAC02", status READY, has 1 handler(s) for this service...
"DEDICATED" established:19 refused:0 state:ready
Testing the service RAC_DB.de.domain.dns works fine, too.
But when trying to connect from my PC (or any other client) we are getting the error ORA-12514 TNS:listener does not currently know of service requested in connect descriptor
My TNSNAMES.ORA looks like this:
(ADDRESS = (PROTOCOL = TCP)(HOST = myrac-scan.de.domain.dns)(PORT = 1521))
(SERVICE_NAME = RAC_DB.de.domain.dns)
(SERVER = DEDICATED)
Any idea? When using PUTTY with myrac-scan.de.domain.dns I get connected to one of the nodes of the RAC - therefore the address itself is OK.
If the IP's have changed: is ther anything else which needs to be reconfigured?
Any help will be appreciated.
The REMOTE_LISTENER database parameter needs to point to the SCAN listener to enable the PMON process to register its instance's services with the SCAN listener.
On a RAC db instance:
sqlplus "/ as sysdba"
SQL> alter system set remote_listener='myrac-scan.de.domain.dns:1521' scope=both sid='*';
SQL> alter system register;
.. check for services registered on SCAN listener..
Refer to Oracle® Database Reference for details on the parameter's settings.
Does the SCAN listener show any registered services from the RAC db instances?
If not, then it means that the registration process fails - in which case you need to check things like hostname resolution and firewalls on the RAC server nodes.
If the SCAN listener does show RAC services, confirm that the service name used by the client's TNS connection is supported.
If there still does not seem to be an error, enable SQL*Net tracing on the client. Set the client's sqlnet.ora file to include the following settings:
DIAG_ADR_ENABLED = off
TRACE_LEVEL_CLIENT = admin
TRACE_DIRECTORY_CLIENT = <your-local-trace-dir>
Try connecting from the client again and investigate the trace for that connection attempt.
Sorry for the typo (I replaced coface with domain since I didn't want to post our domain here).
Therefore the configuration is correct...
SQL> show parameter remote_listener
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
remote_listener string myrac-scan.de.domain.dns:1521