user569151 wrote:If your RAC environment is configured properly follow this step:
I have a 3 node RAC on Linux redhat. DB version is 11gr2.
I want to know the steps to perform each node OS patch upgrade.
I want to be sure I did right steps:
1). Node 1, stop crs and do the OS patch upgrade.
2). same steps for Node 2, 3.
My concern is here, let's say each node has to be restarted.Yes "CRSCTL STOP CRS" will try stop all clusterware resource with clean state. If any problem occurs will be raised on your prompt.
So my procedure should be on 1st node: crsctl stop crs to stop everything and failover everything to other nodes.
I wonder crsctl stop crs will cause ASM instance to be down?
user569151 wrote:Yes. The RAC is designed to do it without relocate service manually because he do it automatically keeping all connection alive since you have one node active.
our rac system is configured with transparent client failover. So service name is created per Oracle MAA document.
If so do I still have to relocate the service before maintenance?
If node 1 down without service relocation, will other node still get the connection? since service name is created for all three node rdbms.