ORA-15131: block string of file string in diskgroup string could not be read

Cause : A block could not be read because the disk containing the block is either offline or an I/O error occured while reading the block. If this is mirrored file, then all disks that contain a the block are either offline or received errors.

Action - How to fix it : DBA Scripts :: www.high-oracle.com/scripts

Repair the affected disk and bring it back online. Refer to accompanying error messages to determine which disk has failed.

update : 22-06-2017

ORA-15131 - block string of file string in diskgroup string could not be read
ORA-15131 - block string of file string in diskgroup string could not be read

  • ora-02239 : there are objects which reference this sequence
  • ora-28271 : No permission to read user entry in LDAP directory service.
  • ora-02246 : missing EVENTS text
  • ora-13360 : invalid subtype in a compound type
  • ora-08266 : create_ora_addr: cannot register name in nameserver
  • ora-02758 : Allocation of internal array failed
  • ora-02837 : Unable to unlink temporary file
  • ora-28555 : pass-through SQL: required parameter missing or NULL
  • ora-38606 : FI support threshold not between [0, 1]
  • ora-33883 : (MAKEDCL36) You cannot use the string attribute when you define an EXTERNAL partition with an existing target.
  • ora-02817 : Read failed
  • ora-00437 : ORACLE feature is not licensed. Contact Oracle Corp. for assistance
  • ora-07682 : sou2os: set kernel dispatch fail err
  • ora-30358 : summary and materialized view are not in same schema
  • ora-16802 : downgrading redo transport mode from SYNC disallowed
  • ora-12678 : Authentication disabled but required
  • ora-06126 : NETTCP: ORASRV unable to open network connection
  • ora-00354 : corrupt redo log block header
  • ora-31638 : cannot attach to job string for user string
  • ora-30030 : suppress resumable related error message
  • ora-16194 : Modifying DB_UNIQUE_NAME requires SID='*' qualifier
  • ora-00910 : specified length too long for its datatype
  • ora-13381 : table:string not found in network:string
  • ora-30757 : cannot access type information
  • ora-15171 : invalid syntax in the alias path after 'string'
  • ora-16207 : Logical standby dictionary build not permitted.
  • ora-00408 : parameter string is set to TRUE
  • ora-16820 : Fast-Start Failover observer is no longer observing this database
  • ora-00206 : error in writing (block string, # blocks string) of control file
  • ora-09777 : osnpbr: cannot send break message
  • Oracle Database Error Messages

    Oracle Database High Availability Any organization evaluating a database solution for enterprise data must also evaluate the High Availability (HA) capabilities of the database. Data is one of the most critical business assets of an organization. If this data is not available and/or not protected, companies may stand to lose millions of dollars in business downtime as well as negative publicity. Building a highly available data infrastructure is critical to the success of all organizations in today's fast moving economy.

    Well, the reason for above error is that i have taken the above script from a 11g database and running it on 10g database. 11g has bring some changes in password management. Below code is executed on 11g and user created successfully, which is expected result.