About migrating ocr votedisk from rac

About the migration of ocr votedisk environment in rac: hpunixoracle rac 11.2.0.3 Problem description: Due to user error operations, put ocr and votedisk in + GRID. Now we need to migrate it to + OCR_VOTE: solution: the specific operation is as follows: (only the Operation Command is logged) [root @ node2 ~] $/U01/app/11.2.0/grid/bin/ocrcheckStatus of Oracle Cluster Registry is as follows: Version: 3 Total space (kbytes): 262120 Used space (kbytes ): 2992 Available space (kbytes): 259128 ID: 601346144 Device/File Name: + GRID Device/File integrity check succeeded Device/File not configured Cluster registry integrity Check succeeded Logical upload uption check bypassed due to non-privileged user here we can see that ocr is placed in + GRID and then Add a new OCR device/file: [root @ node2 ~] /U01/app/11.2.0/grid/bin/ocrconfig-add + OCR_VOTE [root @ node2 ~] $/U01/app/11.2.0/grid/bin/ocrcheckStatus of Oracle Cluster Registry is as follows: Version: 3 Total space (kbytes): 262120 Used space (kbytes ): 2992 Available space (kbytes): 259128 ID: 601346144 Device/File Name: + GRID Device/File integrity check succeeded + OCR_VOTE Device/File integrity check succeeded Device/File not configured Cluste R registry integrity check succeeded Logical transaction uption check bypassed due to non-privileged user (ocr does not exist in + OCR_VOTE at this time) Migration ocr: [root @ node2 ~] $/U01/app/11.2.0/grid/bin/ocrconfig-replace + GRID-replacement + OCR_VOTE and migrate votedisk: [root @ node2 ~] $ Su-grid [grid @ node2 ~] $ Crsctl replace votedisk + OCR_VOTE query the storage directory of votedisk: [grid @ node2 ~] $ Crsctl query css votedisk; query the resource status: [grid @ node2 ~] $ Crsctl status resource-t and then log on to asm to view asmdisk information: sqlplus/as sysasm SQL> select group_number, name, state, type from V $ asm_diskgroup; SQL> select group_number, name, path from v $ asm_disk; note, in this case, You cannot delete the + GRID disk group because the asm parameter file is very likely to be stored in + GRID. Run the show parameter spfile command to view the path. If it is stored in + GRID, you can recreate the spfile: perform the following operations: SQL> create pfile = '/u01/11.2.0/grid/dbs/asmpfile. ora 'from spfile; SQL> create spfile = '+ OCR_VOTE' from pfile = '/U01/11.2.0/grid/dbs/asmpfile. ora '; then use the root user to restart the crs (if you are idle, you can try to modify the storage path of the spfile by not starting asm when the crs is started, this workload is a bit heavy !) [Root @ node2 ~] $/U01/app/11.2.0/grid/bin/crsctl stop crs [root @ node2 ~] $/U01/app/11.2.0/grid/bin/crsctl start crs and then use the grid user su-grid SQL> alter diskgroup OCR_VOTE mount; switch to the root user/u01/app/11.2.0/grid/bin/ocrconfig-delete + GRID and delete + GRID (you can also delete the grid by using asmca. Note, if the disk in the GRID cannot be found after deletion, use the dd command to clear the disk header. command: dd if =/dev/zero of =/dev/rdisk/xx count = 100, remember that the dd command is quite dangerous.) SQL> alter diskgroup GRID dismount; SQL> drop diskgroup GRID including contents;