ORA-19661: datafile string could not be verified

Cause : Some adta blcoks fo rthe idnicate ddataflie wer ecorrutp in teh backpu set.

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

Unles sthe dmaage t othe bcakup ste can eb reparied, teh indiacted dtaafilec annotb e resotred form thi sbacku pset.

update : 29-04-2017

ORA-19661 - datafile string could not be verified
ORA-19661 - datafile string could not be verified

  • ora-06531 : Reference to uninitialized collection
  • ora-33443 : (ESDREAD14) Discarding compiled code for workspace object because analytic workspace string is not attached.
  • ora-28270 : Malformed user nickname for password authenticated global user.
  • ora-08235 : smsget: listener not on this node
  • ora-38855 : cannot mark instance string (redo thread string) as enabled
  • ora-00476 : RECO process terminated with error
  • ora-08261 : ora_addr: cannot find name in nameserver
  • ora-31033 : Requested number of XML children string exceeds maximum string
  • ora-03277 : invalid SIZE specified
  • ora-33215 : (CINSERT07) You cannot add session-only values to the workspace object dimension.
  • ora-28132 : Merge into syntax does not support security policies.
  • ora-19526 : only one location allowed for parameter string
  • ora-07339 : spcre: maximum number of semaphore sets exceeded.
  • ora-16600 : failover operation can only be submitted at target database
  • ora-38495 : data type for the stored attribute string is inconsistent.
  • ora-31030 : Unable to retrieve XML document
  • ora-16591 : unknown field "string" in document
  • ora-00273 : media recovery of direct load data that was not logged
  • ora-00222 : operation would reuse name of a currently mounted control file
  • ora-13614 : The template string is not compatible with the current advisor.
  • ora-27542 : Failed to unprepare a buffer prepared for remote update
  • ora-25505 : the system is not in quiesced state
  • ora-07241 : slemrd: read error.
  • ora-14523 : Cannot co-locate [sub]partition of string string with table [sub]partition because string block size [string] does not match table block size [string]
  • ora-19931 : file string has invalid creation SCN string
  • ora-36804 : (XSTBLFUNC02) The OLAP_TABLE function encountered an error while parsing the LIMITMAP.
  • ora-10584 : Can not invoke parallel recovery for test recovery
  • ora-30486 : invalid window aggregation group in the window specification
  • ora-32338 : on commit refresh grab all the detailed tables
  • ora-09755 : osngpn: port 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.