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-05-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-19559 : error sending device command: string
  • ora-19122 : unsupported XQuery declaration
  • ora-31198 : Mismatch in number of bytes transferred due to non-binary mode
  • ora-12635 : No authentication adapters available
  • ora-15115 : missing or invalid ASM disk size specifier
  • ora-01264 : Unable to create string file name
  • ora-01371 : Complete LogMiner dictionary not found
  • ora-34021 : (MSCGADD04) You must specify a partition when maintaining PARTITION TEMPLATE workspace object.
  • ora-00705 : inconsistent state during start up; shut down the instance, then restart it
  • ora-22866 : default character set is of varying width
  • ora-14116 : partition bound of partition "string" is too long
  • ora-19253 : XQ0033 - too many declarations for namespace prefix string
  • ora-24170 : %s.string is created by AQ, cannot be dropped directly
  • ora-02063 : preceding stringstring from stringstring
  • ora-07585 : spdcr: $PARSE failure
  • ora-28007 : the password cannot be reused
  • ora-12823 : default degree of parallelism may not be specified here
  • ora-12201 : TNS:encountered too small a connection buffer
  • ora-16803 : unable to query a database table or fixed view
  • ora-21707 : pin duration is longer than allocation duration
  • ora-15127 : ASM file name 'string' cannot use templates
  • ora-02405 : invalid sql plan object provided
  • ora-19222 : XP0002 - XQuery dynamic context component string not initialized
  • ora-13027 : unable to read dimension definition from string
  • ora-19006 : XMLType TYPE storage option not appropriate for storage type
  • ora-31527 : could not find source column string for CDC change table string.string
  • ora-06602 : LU6.2 Driver: Error allocating context area
  • ora-06044 : NETDNT: connect failed, byte count quota exceeded
  • ora-31421 : change table does not exist
  • ora-07591 : spdde: $GETJPIW failure
  • 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.