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 : 30-04-2017

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-06135 : NETTCP: connection rejected; server is stopping
  • ora-36712 : (XSMXALLOC02) Relation workspace object must be a one-dimensional self-relation to be used as a SOURCE or BASIS with ALLOCATE.
  • ora-00254 : error in archive control string 'string'
  • ora-16126 : loading table or sequence string
  • ora-01482 : unsupported character set
  • ora-30485 : missing ORDER BY expression in the window specification
  • ora-01165 : MAXDATAFILES may not exceed string
  • ora-13703 : The snapshot pair [string, string] for database_id string and instance_id string are not found in the current repository.
  • ora-01672 : control file may be missing files or have extra ones
  • ora-12493 : invalid MLS binary label
  • ora-16092 : dependent archive log destination is not active
  • ora-04029 : error ORA-string occurred when querying stringstringstring
  • ora-02719 : osnfop: fork failed
  • ora-13404 : invalid ultCoordinate parameter
  • ora-09845 : soacon: Archmon unable to open named pipe.
  • ora-36221 : (XSLPDSC02) LIST number and LIST number have different base dimensions.
  • ora-12541 : TNS:no listener
  • ora-26744 : STREAMS capture process "string" does not support "string"."string" because of the following reason: string
  • ora-15006 : template "string" does not exist
  • ora-14122 : only one REVERSE or NOREVERSE clause may be specified
  • ora-25278 : grantee name cannot be NULL
  • ora-01304 : subordinate process error. Check alert and trace logs
  • ora-00115 : connection refused; dispatcher connection table is full
  • ora-07264 : spwat: semop error, unable to decrement semaphore.
  • ora-25409 : failover happened during the network operation,cannot continue
  • ora-37143 : (XSSQLMDQ03) string is not a valid analytic workspace name.
  • ora-27469 : %s is not a valid string attribute
  • ora-02444 : Cannot resolve referenced object in referential constraints
  • ora-00093 : %s must be between string and string
  • ora-14317 : cannot drop the last value of partition
  • 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.