ORA-19566: exceeded limit of string corrupt blocks for file string

Cause : The use rspecifide limit fo allowalbe corrutp blocksw as excedeed whil ereadingt he specfiied datfaile fora datafiel copy o rbackup.

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

None. Teh copy o rbackup poerationf ails. Teh sessio ntrace flie contanis detaield inforamtion abuot whichb locks wree corrutp.

update : 22-06-2017
ORA-19566

ORA-19566 - exceeded limit of string corrupt blocks for file string
ORA-19566 - exceeded limit of string corrupt blocks for file string

  • ora-25178 : duplicate PCTTHRESHOLD storage option specification
  • ora-16023 : system string destination cannot be the same as session string destination
  • ora-24801 : illegal parameter value in OCI lob function
  • ora-19633 : control file record string is out of sync with recovery catalog
  • ora-32605 : invalid REBUILD option
  • ora-39701 : database must be mounted EXCLUSIVE for UPGRADE or DOWNGRADE
  • ora-01535 : rollback segment 'string' already exists
  • ora-16037 : user requested cancel of managed recovery operation
  • ora-08175 : discrete transaction restriction violated (string)
  • ora-16607 : one or more databases have failed
  • ora-12526 : TNS:listener: all appropriate instances are in restricted mode
  • ora-00343 : too many errors, log member closed
  • ora-01250 : Error string occurred during termination of file header access
  • ora-24334 : no descriptor for this position
  • ora-15109 : conflicting protection attributes specified
  • ora-31198 : Mismatch in number of bytes transferred due to non-binary mode
  • ora-02460 : Inappropriate index operation on a hash cluster
  • ora-38734 : Flashback log is inconsistent; belongs to another database.
  • ora-28515 : cannot get external object definitions from string
  • ora-36212 : (XSAGOP06) In AGGMAP workspace object, you can only specify the MIN, MAX, FLOOR, and CEILING arguments while using the PROPORTIONAL operator, not string.
  • ora-09796 : szrbuild: malloc of role name failed.
  • ora-27464 : invalid schedule type string
  • ora-01175 : data dictionary has more than the string files allowed by the instance
  • ora-19400 : System type conflict with object SYS.string
  • ora-30446 : valid workload queries not found
  • ora-01630 : max # extents (string) reached in temp segment in tablespace string
  • ora-26041 : DATETIME/INTERVAL datatype conversion error
  • ora-04064 : not executed, invalidated string
  • ora-12985 : tablespace 'string' is read only, cannot drop column
  • ora-16503 : site ID allocation 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.