RAC - OCR and Voting Disk
11g R2 - Moving your voting disk and cluster registry
What happens if you've created your voting disk or cluster registry in the wrong place?They're very simple to move, for example to move them from a cluster filesystem to ASM
OCR
Login as rootRun ocrcheck to see where your existing OCR location (so you can delete it later).
- ocrcheck
Status of Oracle Cluster Registry is as follows :
Version : 3
Total space (kbytes) : 262120
Used space (kbytes) : 2744
Available space (kbytes) : 259376
ID : 277541681
Device/File Name : /OCR/b-rac-cluster/ocr
Device/File integrity check succeeded
Cluster registry integrity check succeeded
Logical corruption check succeeded
# ocrconfig -delete /OCR/b-rac-cluster/ocr
Run ocrcheck to check it's all ok
# ocrcheck
Status of Oracle Cluster Registry is as follows :
Version : 3
Total space (kbytes) : 262120
Used space (kbytes) : 2744
Available space (kbytes) : 259376
ID : 277541681
Device/File Name : +DATA
Device/File integrity check succeeded
Cluster registry integrity check succeeded
Logical corruption check succeeded
Useful : # ocrconfig -showbackup
Voting
Login as OracleFind your existing voting disk
$ crsctl query css votedisk
## STATE File Universal Id File Name Disk group
- ---- --------- ----- -------
1. ONLINE 96953eb1cac64fcabf4d0f60d0012ef9 (/OCR/b-rac-cluster/vdsk) []
Change your voting disk to the +DATA diskgroup
b-rac1 $ crsctl replace votedisk +DATA
CRS-4256: Updating the profile
Successful addition of voting disk 3ddb5231538c4fc3bf2d0053e34a75f0.
Successful deletion of voting disk 96953eb1cac64fcabf4d0f60d0012ef9.
Successfully replaced voting disk group with +DATA.
CRS-4256: Updating the profile
CRS-4266: Voting file(s) successfully replaced
Check it's moved ok
b-rac1 $ crsctl query css votedisk
## STATE File Universal Id File Name Disk group
- ---- --------- ----- -------
1. ONLINE 3ddb5231538c4fc3bf2d0053e34a75f0 (/ORACLE/ASM/ASM0103) [DATA]
Located 1 voting disk(s).
PROT-30 Error: The Oracle Cluster Registry location to be added is not accessible.
What does this error mean? by default when you create a diskgroup in 11gR2 RAC from the command promptusing SQL plus, the default compatibility attribute of the diskgroup is set to 10.1. This issue does not occur if you create it through ASMCA.
Note The ASM compatibility and the database (RDBMS) compatibility defaults to 10.1. This needs to be changed to 11.2 in order for the clusterware to recognize that this is a 11gR2 ASM configuration
ALTER DISKGROUP PRD_GRID2 SET ATTRIBUTE ‘COMPATIBILITY.ASM’=’11.2’
Comments