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 : 26-09-2017
ORA-15131

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-07280 : slsget: unable to get process information.
  • ora-32696 : HTI: No free slot
  • ora-32147 : Environment not specified
  • ora-14453 : attempt to use a LOB of a temporary table, whose data has alreadybeen purged
  • ora-06794 : TLI Driver: shadow process could not retrieve protocol info
  • ora-29800 : invalid name for operator
  • ora-04020 : deadlock detected while trying to lock object stringstringstringstringstring
  • ora-13155 : invalid number of dimensions specified
  • ora-31408 : invalid value specified for begin_scn or end_scn
  • ora-08457 : syntax error in SEPARATE CHARACTER option of SIGN clause
  • ora-39098 : Worker process received data objects while loading metadata. Invalid process order range is string..string
  • ora-09362 : Windows 3.1 Two-Task driver unable to deallocate context area
  • ora-03298 : cannot shrink datafile - file string is under hot backup
  • ora-12914 : Cannot migrate tablespace to dictionary managed type
  • ora-37173 : null dimension source data
  • ora-16661 : the standby database needs to be reinstated
  • ora-31618 : dump file size too small
  • ora-31209 : DBMS_LDAP: PL/SQL - LDAP count_entry error.
  • ora-36690 : (NTEXTCNV01) Error during conversion from NTEXT to TEXT.
  • ora-16548 : object not enabled
  • ora-01936 : cannot specify owner when creating users or roles
  • ora-25147 : UNIFORM SIZE value greater than maximum extent size
  • ora-14053 : illegal attempt to modify string in string statement
  • ora-09788 : sllfrb: unable to read file.
  • ora-36269 : (XSCGMDLAGG10) 'workspace object' does not exist or is not a dimension.
  • ora-19044 : character length specified for XMLSerialize is too small.
  • ora-12443 : policy not applied to some tables in schema
  • ora-26694 : error while enqueueing into queue string.string
  • ora-23345 : table "string"."string" not registered to collect statistics
  • ora-30104 : 'string' is not a legal integer for 'string'
  • 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.