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 : 23-04-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-00367 : checksum error in log file header
  • ora-30737 : cannot create subtable of a type which is not a subtype of the type of the supertable
  • ora-13040 : failed to subdivide tile
  • ora-32832 : failure string trying to acquire administration lock
  • ora-16716 : clearing parameter LOG_ARCHIVE_DEST failed
  • ora-02327 : cannot create index on expression with datatype string
  • ora-31409 : one or more values for input parameters are incorrect
  • ora-17618 : Unable to update block 0 to version 10 format
  • ora-32638 : Non unique addressing in MODEL dimensions
  • ora-26565 : Call to _arg made before calling dbms_defer.call
  • ora-15094 : attempted to write to file opened in read only mode
  • ora-13908 : Invalid combination of metrics id and object type parameters.
  • ora-30108 : invalid positional parameter value 'string'
  • ora-39104 : cannot call this function from a SQL parallel query slave process
  • ora-27366 : job "string.string" is not running
  • ora-28578 : protocol error during callback from an external procedure
  • ora-19927 : CONVERT DATABASE operation cannot proceed
  • ora-12025 : materialized view log on "string"."string" already has primary keys
  • ora-01590 : number of segment free list (string) exceeds maximum of string
  • ora-29266 : end-of-body reached
  • ora-08323 : scnmin: close of bias lock failed
  • ora-32631 : illegal use of objects in MODEL
  • ora-00336 : log file size string blocks is less than minimum string blocks
  • ora-09937 : Chmod of ORACLE password file failed.
  • ora-16037 : user requested cancel of managed recovery operation
  • ora-16775 : target standby database in broker operation has potential data loss
  • ora-23361 : materialized view "string" does not exist at master site
  • ora-16017 : cannot use LOG_ARCHIVE_DUPLEX_DEST without a primary archive destination
  • ora-16143 : RFS connections not allowed during or after terminal recovery
  • ora-30504 : system triggers cannot have a FOR EACH ROW clause
  • 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.