APPLIES TO:
Oracle Server - Enterprise Edition - Version 11.2.0.1 and later
Information in this document applies to any platform.
GOAL
This note is to list OCR storage requirement and to provide location of diagnostic information if PROT-30 is reported.
FIX
OCR Storage Requirement:
A. If located on shared file system:
A1. At least 280 MB of free space is required for each OCR volume as per the following documentation:
Oracle Grid Infrastructure Installation Guide
11g Release 2 (11.2)
Verify System Requirements
A2. Shared file systems must be mounted on all nodes before you can place OCR on them.
B. If located on ASM:
B1. The space requirement is slightly different depend on diskgroup redundance level, refer to the following documentation for details:
Oracle Grid Infrastructure Installation Guide
11g Release 2 (11.2)
Verify System Requirements
For External redundancy: The space requirement for the OCR is: 300MB
For Normal redundancy: The space requirement for the OCR is: 600MB
For High redundancy: The space requirement for the OCR is: 900MB
B2. The diskgroup intended for OCR must be mounted on all nodes
B3. Compatible.asm setting for diskgroup must be at least 11.2
B4. oracle binary in <GRID_HOME> must have permission of "6751" or "-rwsr-s--x" on all nodes.
Diagnostic information:
If ocrconfig still reports the error after requirement is met, please refer to following for traces:
A. $GRID_HOME/log/$HOST/crsd/crsd.log; example:
2010-01-25 11:11:12.374: [ OCRASM][1291008320]proprasmo: Error in open/create file in dg [DG1]
[ OCRASM][1291008320]SLOS : SLOS: cat=8, opn=kgfoCr2P01, dep=15056, loc=kgfokge
ORA-17502: ksfdcre:4 Failed to create file +DG1.255.1
ORA-15221: ASM operation requires compatible.asm of 11.1.0.0.0 or higher
ORA-06512: at line 4
B. $GRID_HOME/log/$HOST/client/ocrconfig_pid.log; example:
Oracle Database 11g Clusterware Release 11.2.0.1.0 - Production Copyright 1996, 2009 Oracle. All rights reserved.
2010-01-25 11:11:11.088: [ OCRCONF][2151603648]ocrconfig starts...
2010-01-25 11:11:12.571: [ OCRCLI][2151603648]proac_replace_dev:[+DG1]: Failed. Retval [8]
2010-01-25 11:11:12.571: [ OCRAPI][2151603648]procr_replace_dev: failed to replace device (8)
2010-01-25 11:11:12.571: [ OCRCONF][2151603648]The new OCR device [+DG1] cannot be opened
2010-01-25 11:11:12.571: [ OCRCONF][2151603648]Exiting [status=failed]...
C. $ORACLE_BASE/diag/asm/+asm/+ASMn/trace/alert_+ASMn.log, example:
Mon Jan 25 11:11:12 2010
Errors in file /opt/oracle/admin/diag/asm/+asm/+ASM1/trace/+ASM1_ora_22997.trc:
ORA-17502: ksfdcre:4 Failed to create file +DG1.255.1
ORA-15221: ASM operation requires compatible.asm of 11.1.0.0.0 or higher
ORA-15041: diskgroup "DG1" space exhausted
D. To verify ASM diskgroup free space and compatible setting, as grid user:
export ORACLE_SID=+ASMn
export ORACLE_HOME=home_of_grid_installation
$ORACLE_HOME/bin/sqlplus / as sysasm
SQL> set linesize 100
SQL> select inst_id, name, state, type, free_mb, substr(compatibility,1,10) compatibility from gv$asm_diskgroup where name='DG3' order by name,inst_id;
INST_ID NAME STATE TYPE FREE_MB COMPATIBIL
--------- ------------------------------ ----------- ------ ---------- ----------
1 DG3 MOUNTED EXTERN 1134 11.2.0.0.0
2 DG3 MOUNTED EXTERN 1134 11.2.0.0.0
Miscellaneous
1. If you are trying to delete a non-exist OCR device, due to unpublished bug 8739774, ocrconfig fails with PROT-30, the error can be ignored; the bug has been fixed in 11.2.0.2 with new error PROT-34
2. To set compatible.asm to 11.2, log into ASM and execute:
ALTER DISKGROUP DG1 SET ATTRIBUTE 'compatible.asm' = '11.2';
