Oracle RAC - Grid deconfigure and reconfigure commands
Oracle RAC Solution · Config document · referenced from Grid patches and the multicast problem
The commands that take the Clusterware configuration off both nodes and install it again from a response file. The notes say only that the chapter applies if you are experimenting, not when it was used; the remark in step [4.3] about a change of the network subnet suggests, in my reading, that it belonged to the move of the interconnect. The commands are not part of a clean installation.
| Item | Value |
|---|---|
| Grid home | /data/u01/app/grid11204 |
| Run on | both nodes, each line on the node given in the table below |
| Run as | root; the installer as grid |
| Response file | /data/install/grid.rsp, not kept in the notes |
| Software | Grid Infrastructure 11.2.0.4 |
The commands
The notes prefix each line with the node it ran on. The table after the fence says which lines ran on which node.
$ /data/u01/app/grid11204/crs/install/rootcrs.pl -deconfig -force -verbose $ /data/u01/app/grid11204/crs/install/rootcrs.pl -deconfig -force -verbose -keepdg -lastnode $ cd /data/u01/app/grid11204/gpnp $ mv -i profiles/peer/profile.xml profiles/peer/profile.xml.0 $ mv -i oradb01/profiles/peer/profile.xml oradb01/profiles/peer/profile.xml.0 $ cd /data/u01/app/grid11204/gpnp $ mv -i profiles/peer/profile.xml profiles/peer/profile.xml.0 $ mv -i oradb02/profiles/peer/profile.xml oradb02/profiles/peer/profile.xml.0 $ cd /data/u01/app/grid11204/crs/install $ cp -pi crsconfig_params crsconfig_params.0 $ cd /data/u01/app/grid11204/crs/install $ cp -pi crsconfig_params crsconfig_params.0 $ su - grid $ /data/install/grid/runInstaller -responseFile /data/install/grid.rsp
| Lines | Step in the notes | Node | What it does |
|---|---|---|---|
| 1 | [4.1] | oradb02 | Deconfigures Clusterware on the node that is not the last one |
| 2 | [4.1] | oradb01 | Deconfigures the last node: -lastnode also removes the cluster-wide configuration, -keepdg keeps the disk group |
| 3 to 5 | [4.2] | oradb01 | Puts the old Grid Plug and Play profiles aside |
| 6 to 8 | [4.2] | oradb02 | The same, with the node's own directory name |
| 9 to 10 | [4.3] | oradb01 | Backs up the parameters rootcrs.pl was configured with |
| 11 to 12 | [4.3] | oradb02 | The same |
| 13 to 14 | [4.4] | oradb01 | Starts the installer as grid with the response file; in the graphical interface only "Next", "Next", "Next" |
The remark beside step [4.3] says to back up the CRS configuration parameters that were used during the installation and, if needed, to make the change of the network subnet. No edited line of crsconfig_params is shown, so the notes do not record whether or how the file was changed.
The procedure is taken from a web page the notes cite as http://www.ewan.cc/?q=node/109. After the installer has run, the root scripts follow as in Grid Infrastructure installation; the notes do not repeat them here.
Checked against Oracle Grid Infrastructure 26ai
| As built | Today |
|---|---|
rootcrs.pl -deconfig -force -verbose | The script is rootcrs.sh: rootcrs.sh -deconfig -force |
-lastnode on the last node | Unchanged: it completes the deconfiguration of the cluster, including the OCR and voting files |
-keepdg | Occurs nowhere in the 19c and 26ai guides; whether the script still accepts it was not confirmed |
GPnP profiles moved aside by hand, reinstallation with runInstaller -responseFile | Not a documented procedure in 11.2 or today. The documented path: run rootcrs.sh -deconfig -force on the nodes with the installation error, correct the cause, run root.sh again |
The first two lines are still how a failed configuration is taken off a node. The rest was my own experiment after a web page and should not be copied.