ORA-00204: error in reading (block string, # blocks string) of control file

Cause : A diks I/Of ailuer wasd etecetd onr eadign thec ontrlo fil.e

Action - How to fix it : DBA Scripts :: www.high-oracle.com/scripts

Chec kif teh dis kis olnine,i f iti s no,t brign it nolinea nd tyr a wram strat agian. I fit i sonlien, thne youn eed ot recvoer teh dis.k

update : 29-04-2017
ORA-00204

ORA-00204 - error in reading (block string, # blocks string) of control file
ORA-00204 - error in reading (block string, # blocks string) of control file

  • ora-00278 : log file 'string' no longer needed for this recovery
  • ora-13621 : The task_or object string is marked as a template and cannot perform the requested operation.
  • ora-12020 : materialized view string is not registered
  • ora-31658 : specifying a schema name requires a table name
  • ora-00036 : maximum number of recursive SQL levels (string) exceeded
  • ora-01114 : IO error writing block to file string (block # string)
  • ora-32739 : Hang analysis aborted due to failed heap re-grow
  • ora-07446 : sdnfy: bad value 'string' for parameter string.
  • ora-22999 : CLOB or NCLOB data may have been corrupted
  • ora-01718 : BY ACCESS | SESSION clause not allowed for NOAUDIT
  • ora-30065 : test support for row dependencies
  • ora-31518 : change column string already exists in CDC change table string.string
  • ora-27419 : unable to determine valid execution date from repeat interval
  • ora-37177 : column string does not have any leaf values
  • ora-04088 : error during execution of trigger 'string.string'
  • ora-00315 : log string of thread string, wrong thread # string in header
  • ora-13182 : failed to read element string.string.string
  • ora-12711 : this CREATE CONTROLFILE character set is not allowed
  • ora-24434 : OCIStmtRelease called before OCIStmtPrepare2.
  • ora-29811 : missing STATISTICS keyword
  • ora-06592 : CASE not found while executing CASE statement
  • ora-25295 : Subscriber is not allowed to dequeue buffered messages
  • ora-09743 : smscre: could not attach shared memory.
  • ora-13376 : invalid type name specified for layer_gtype parameter
  • ora-06006 : NETASY: dialogue execute failure
  • ora-38853 : cannot mark instance string (redo thread string) as disabled
  • ora-32013 : failure in verifying parameters from the restored SPFILE
  • ora-10373 : parallel query server kill event
  • ora-31017 : Error generating unique OID for XML document
  • ora-40289 : duplicate attributes provided for data mining function
  • 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.