188.8.131.52: service not registering to SCAN Listener after Failover
Last updated on JULY 27, 2017
Applies to:Oracle Database - Enterprise Edition - Version 184.108.40.206 and later
Information in this document applies to any platform.
After applied <patch 17947785> which is part of 220.127.116.11 GI PSU 3 onward, service is not registering to SCAN listener after SCAN VIP/Listener fail over from one node to another.
Bug 17947785 - CRSD ORAAGENT KEEPS CONSUMING 25-35% CPU WITH 500 SERVICES
Comparing agent log, one can see that the following is missing after fail over in agent log:
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