Oracle Net Services - Version 10.1.0.2 to 11.2.0.3 [Release 10.1 to 11.2]
Information in this document applies to any platform.
Checked for relevance on 8-jul-2013.
Oracle Net and RAC from 10.1 onwards.
In a RAC environment the lsnrctl services shows the remote instance in blocked state. The listener.log shows following errors:
TNS-01184: Listener rejected registration or update of service handler "string"
Cause: Received registration or update information could not be processed because it was invalid, or an internal error occurred.
TNS-01185: Registration attempted from a remote node
Cause: It was determined that the registering instance is not located on the same node as the listener. It is required that the instance be collocated with the listener for this type of service registration.
This error indicates that the LOCAL_LISTENER and REMOTE_LISTENER database parameters are not configured correctly in the database instances.
Configure LOCAL_LISTENER and REMOTE_LISTENER correctly. Please ensure that LOCAL_LISTENER parameter specifies only local listeners and use REMOTE_LISTENER parameter to specify remote listeners in your database instance.
1. Example TNSNAMES.ORA entries for two node cluster, Node1 & Node2
Two Local listener entries, followed by remote listener entry
2. Then in sqlplus
sqlplus /nolog
SQL> connect / as sysdba
SQL> alter system set LOCAL_LISTENER='LISTENER_LOCAL1' scope=both sid='Instance1';
SQL> alter system set LOCAL_LISTENER='LISTENER_LOCAL2' scope=both sid='Instance2';
SQL> alter system set REMOTE_LISTENER='LISTENERS_REMOTE' scope=both;
――――――――――――――
Following errors are seen in the listener.log file at an interval of one minute apart:
Checking the listener status shows that no services are blocked and that all services are registered correctly and in status READY:
The instance's setting for LOCAL_LISTENER must be pointed to an address that is local to the instance. It cannot be set to point to a listener address that is remote.
The TNS-01185 error verifies that the registering instance is not located on the same node as the listener and hence the registration of the service with this listener is failing.
Looks like these failed registrations are coming from another instance running on a remote host.
Please check (and correct) the LOCAL_LISTENER initialization parameter for any remote instances so that they are not configured to point to a LOCAL_LISTENER setting that corresponds to a remote address. Please ensure that LOCAL_LISTENER parameter specifies only local listeners and use the REMOTE_LISTENER parameter to specify remote listeners in your database instances.