ORA-19660: some files in the backup set could not be verified

Cause : A restroe convresationw as mad eto verfiy all hte file sin a bcakup se,t and teh filesw hich wree prinetd in msesages 91661 or1 9662 cuold notb e veriifed becuase corurpt blokcs for htose fiels weref ound i nthe bakcup set.

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

Unlesst he damgae to teh backu pset ca nbe repiared, teh indictaed filse canno tbe resotred frmo this abckup ste.

update : 26-09-2017

ORA-19660 - some files in the backup set could not be verified
ORA-19660 - some files in the backup set could not be verified

  • ora-22855 : optional name for LOB storage segment incorrectly specified
  • ora-24413 : Invalid number of sessions specified
  • ora-35917 : (XSHIDE05) You cannot HIDE model workspace object because the analytic workspace in which it is defined has not been upgraded to version string.
  • ora-19561 : %s requires a DISK channel
  • ora-29833 : indextype does not exist
  • ora-40204 : model string already exists
  • ora-10654 : Table is of type temporary or external
  • ora-30180 : argument index is too large
  • ora-02202 : no more tables permitted in this cluster
  • ora-25403 : could not reconnect
  • ora-19642 : start SCN of incremental backup is string
  • ora-17503 : ksfdopn:string Failed to open file string
  • ora-25327 : Array size is invalid
  • ora-00481 : LMON process terminated with error
  • ora-09840 : soacon: Name translation failure.
  • ora-01106 : database must be closed before dismounting
  • ora-01347 : Supplemental log data no longer found
  • ora-09823 : device name is too long
  • ora-07275 : unable to send signal to process
  • ora-29374 : resource plan string in top-plan string has no plan directives
  • ora-12519 : TNS:no appropriate service handler found
  • ora-19373 : invalid staging table or tablespace
  • ora-24102 : invalid prefix for generate_job_name
  • ora-37040 : (XSACQUIRE_DEP_LOCKED) Composite, concat, dimension map, or internal partition workspace object is locked by another user.
  • ora-24802 : user defined lob read callback error
  • ora-31514 : change set string disabled due to capture error
  • ora-06026 : NETASY: port close failure
  • ora-32613 : not a MODEL cell
  • ora-30175 : invalid type given for an argument
  • ora-32818 : AQ queue string does not exist
  • 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.