Skip to main content

Scheduled Service Change: Restart Shark CRS

Last Updated:
2011-08-26 00:00:00
Event:
2011-08-29 00:00:00
Status:
Closed
Brief Description:
User Impact:
The users may see a delay in login while the service fails to the other node.
Workaround:
There is no workaround for this issue
Current Status:
N/A
Services Affected:
Full Description:
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.