Repeating CRS-8503 in Grid Infrastructure Log

During my odyssey of applying the current Bundlepatch to a 12.1.0.2 Grid Infrastructure installation on Windows I stumbled upon a repeating error in the cluster alert.log.

PS C:\> get-content %ORACLE_BASE%/diag/crs/<hostname>/crs/trace/alert.log -tail 4 -wait
Tue Dec 15 02:28:58 2015
Errors in file D:\app\oracle\diag\crs\<hostname>\crs\trace\ocrcheck_8216.trc  (incident=81):
CRS-8503 [] [] [] [] [] [] [] [] [] [] [] []
Incident details in: D:\app\oracle\diag\crs\<hostname>\crs\incident\incdir_81\ocrcheck_8216_i81.trc

This error occurs over and over again with an interval of several hours. The My Oracle Support research revealed Doc ID 1997476.1 which can be worked around easily by setting the “asm_diskstring” parameter explicitly.

D:\>set ORACLE_SID=+ASM1

D:\>sqlplus / as sysdba

SQL*Plus: Release 12.1.0.2.0 Production on Tue Dec 15 09:07:53 2015

Copyright (c) 1982, 2014, Oracle.  All rights reserved.


Connected to:
Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production
With the Real Application Clusters and Automatic Storage Management options

SQL> show parameter asm

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
asm_diskgroups                       string      OCR, GIMGMT, DATA, FRA, SSD
asm_diskstring                       string
asm_power_limit                      integer     1
asm_preferred_read_failure_groups    string
SQL> alter system set asm_diskstring='\\.\ORCLDISK*' scope=both sid='*';

System altered.

SQL> show parameter asm

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
asm_diskgroups                       string      OCR, GIMGMT, DATA, FRA, SSD
asm_diskstring                       string      \\.\ORCLDISK*
asm_power_limit                      integer     1
asm_preferred_read_failure_groups    string

After that the errors did not occur anymore in the alert.log. And that’s it finally. The cluster may now go live… May the force be with me 🙂

Advertisements