ASM block corruption ORA-01115

At the time recovery in standby database if you see error (Version

ORA-01115: IO error reading block from file 201 (block # 11080)
ORA-01110: data file 263: ‘+DATADG/datafile/indx_8m.655.665578’
ORA-15055: unable to connect to ASM instance
ORA-00020: maximum number of processes (100) exceeded
ORA-01115: corruption in asm based datafile of 11g database on a standby database

Steps to resolve issue:

1. Check ASM alert log file alert_+ASM1.log.

2. From ASM instance
sqlplus “/as sysasm”

Increase the number of processes

SQL> alter system set processes=200 scope=spfile;

System altered.

SQL> alter system set “_allow_cell_smart_scan_attr”=false scope=spfile;

System altered.

The parameter “_allow_cell_smart_scan_attr” is specific to exadata and in Normal systems with ASM will have this value as True which caused unwanted scans/processes to the ASM disks which caused ORA-20 and slight performance impact.
By setting the value to FALSE in Non-Exadata will work around the issue.

If OCR/Voting disk placed on shared Cluster file system, then bounce the ASM instance to reflect these changes,otherwise bounce the cluster in case OCR/voting disk placed on ASM file system.


Share This Post with Your Friends over Social Media!

About the Author Brijesh

I'm 10gR2 RAC Oracle certified professional, working from last 6 year in the field of database.

Leave a Comment:

Muhammad Ahmad says May 29, 2012

try to quantify the maximum concurrent process which could run on your system as per your application workload environment and set processes parameter approapiately.

the required command set already given in previous post by Brijesh.

Muhammad Ahmad

Add Your Reply