ORA-19696: control file not found in backup set

Cause : The control file could not be restored because it is not in this backup set.

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

This message is issued when the directory from the first backup piece is read and one or more files named for restoration were not found in the piece. You must supply the first backup piece of a backup set that contains the requested file.

update : 29-04-2017
ORA-19696

ORA-19696 - control file not found in backup set
ORA-19696 - control file not found in backup set

  • ora-25143 : default storage clause is not compatible with allocation policy
  • ora-02204 : ALTER, INDEX and EXECUTE not allowed for views
  • ora-01417 : a table may be outer joined to at most one other table
  • ora-00117 : PROTOCOL, ADDRESS or DESCRIPTION must be specified
  • ora-00374 : parameter db_block_size = string invalid ; must be a multiple of string in the range [string..string]
  • ora-36800 : (XSTBLFUNC00) The OLAP_TABLE function can only have a single LOOP statement within the LIMITMAP
  • ora-12224 : TNS:no listener
  • ora-13026 : unknown element type for element string.string.string
  • ora-26536 : refresh was aborted because of conflicts caused by deferred transactions
  • ora-26513 : push error: master proc. string$RP.string failed for trans:string seq:string
  • ora-24171 : creation properties are only for internal use
  • ora-29818 : column name not properly specified
  • ora-02847 : Server did not terminate when posted
  • ora-04044 : procedure, function, package, or type is not allowed here
  • ora-32606 : missing NAV keyword in MODEL clause
  • ora-00408 : parameter string is set to TRUE
  • ora-39960 : scope can only be SYSTEM or SESSION
  • ora-02072 : distributed database network protocol mismatch
  • ora-26734 : different datafiles_directory_object parameter must be specified
  • ora-01165 : MAXDATAFILES may not exceed string
  • ora-19715 : invalid format string for generated name
  • ora-38860 : cannot FLASHBACK DATABASE during instantiation of a logical standby
  • ora-34360 : (MXDSS15) number other users writing
  • ora-13023 : interior element interacts with exterior element
  • ora-31410 : change set string is not an existing change set
  • ora-26030 : index string.string had string partitions made unusable due to:
  • ora-13459 : GeoRaster metadata SRS error
  • ora-06522 : %s
  • ora-36726 : (XSALERR00) The character 'character' is not a valid format specifier for the ALLOCATE error log.
  • ora-09743 : smscre: could not attach shared memory.
  • 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.