Scheduled Service Change: Restart Shark CRS
The users may see a delay in login while the service fails to the other node.
There is no workaround for this issue
We need to bounce the Cluster services on Shark1 and Shark2 which house the PSPROD and ELMPROD databases. We can do this in a rolling fashion so service will not be disrupted instead they will fail over to the other node.