Database startup or shutdown may hang if another application uses TCP port 61xxx in Windows Non-RAC Env (Doc ID 2632767.1)
APPLIES TO:Oracle Database - Standard Edition - Version 12.1.0.1 and later
Oracle Database - Enterprise Edition - Version 12.1.0.1 and later Microsoft Windows x64 (64-bit)
SYMPTOMS
In a Windows non-RAC (single instance) environment, if the 61xxx port is blocked by another application which does not reject or respond to connections, start or stop of the database may hang.
This issue may be seen on release 12c or later.
CAUSE
When starting or stopping the database, oracle server attempts to communicate with the local clusterware stack, regardless of whether RAC is used or not.
On Windows platform, oracle clusterware processes use TCP protocol on pre-defined ports at 61xxx to listen to the requests from clients. In a non-RAC environment, there are no clusterware processes, but oracle server will still attempt to communicate with the clusterware. Usually this works fine, as the connection will immediately fail and server will continue to startup. However, the ports at 61xxx are available to be used by any process, so if another application occupies that port and does not return a reponse to TCP connections, it may cause the oracle server thread to hang.
SOLUTION
Run the following commands to configure exclusion of the 61xxx port range.
netsh int ipv4 add excludedportrange protocol=tcp startport=61000 numberofports=1000 netsh int ipv4 add excludedportrange protocol=udp startport=61000 numberofports=1000
Or
Configure the other applications so that port 61xxx are not used.
REFERENCES
NOTE:2412631.1 - RAC on Windows: We recommend the exclusion of the 61xxx port for RAC on Windows . NOTE:2246758.1 - Failed Logon Delay Causing Performance Hit
