ORA-15132: block string of file string in diskgroup string could not be written

Cause : A block could not be written because the disk containing the block is either offline or an I/O error occured while writing the block. If this is mirrored file, then insufficient disks which 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 : 21-08-2017
ORA-15132

ORA-15132 - block string of file string in diskgroup string could not be written
ORA-15132 - block string of file string in diskgroup string could not be written

  • ora-24378 : user callbacks not allowed for this call
  • ora-25403 : could not reconnect
  • ora-00326 : log begins at change string, need earlier change string
  • ora-13704 : Invalid value "string" specified for parameter "string".
  • ora-32811 : subscriber string already exists
  • ora-01945 : DEFAULT ROLE[S] already specified
  • ora-40305 : invalid impurity metric specified
  • ora-25146 : EXTENT MANAGEMENT option already specified
  • ora-00091 : LARGE_POOL_SIZE must be at least string
  • ora-33920 : (MAKEDCL34) The string SURROGATE must have one of the following data types: ID, NTEXT, TEXT, NUMBER, or INTEGER.
  • ora-16042 : user requested cancel immediate of managed recovery operation
  • ora-13754 : "SQL Tuning Set" "string" does not exist for user "string".
  • ora-38307 : object not in RECYCLE BIN
  • ora-19122 : unsupported XQuery declaration
  • ora-14631 : the partition bounds do not match the subpartition bounds of the partition
  • ora-19335 : Invalid format type object
  • ora-27011 : skgfrd: cannot read from file opened for write
  • ora-15115 : missing or invalid ASM disk size specifier
  • ora-26040 : Data block was loaded using the NOLOGGING option
  • ora-09855 : removeCallback: bad message format.
  • ora-12854 : Parallel query is not supported on temporary LOBs
  • ora-24085 : operation failed, queue string is invalid
  • ora-12995 : no columns in partially dropped state
  • ora-06449 : The list IO or the sysvendor is not installed.
  • ora-01923 : CASCADE aborted, objects locked by another user
  • ora-14160 : this physical attribute may not be specified for a table subpartition
  • ora-35587 : (SQLOUT20) The nesting of table functions and SQL commands has exceeded the maximum of number levels.
  • ora-10633 : No space found in the segment
  • ora-38482 : no elementary attributes defined in the attribute set
  • ora-12607 : TNS: Connect timeout occurred
  • 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.