Last updated on FEBRUARY 14, 2016
Applies to:Oracle Net Services - Version 10.2.0.4 to 188.8.131.52 [Release 10.2 to 11.2]
Information in this document applies to any platform.
The listener may start refusing connections when the RATE_LIMIT feature is in place.
See the following document for examples of this feature: However, the listener is not hung and an inspection of the listener.log reveals that SERVICE_UPDATEs continue after the "connection limit reached" message. In a RAC environment, the CRS may kill the listener process since it is unreachable.
The symptoms of this bug are:
The following error appears in the listener.log:
Then a series of SERVICE_UPDATEs:
15-APR-2010 13:46:41 * service_update * mydb * 0
15-APR-2010 13:47:43 * service_update * mydb * 0
15-APR-2010 13:47:56 * service_update * mydb * 0
15-APR-2010 13:48:05 * service_update * mydb * 0
15-APR-2010 13:48:15 * service_update * mydb * 0
15-APR-2010 13:48:50 * service_update * mydb * 0
Remote clients may experience the following error during this time:
Lsnrctl commands such as services or status may fail with the error code:
In a RAC installation, the listener will be killed by CRS because it has become unresponsive.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms