ORA-10583: Can not recovery file string renamed as missing during test recovery

Cause : One of the files to be recovered is renamed as missing.

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

Rename the file to the correct file or offline it.

update : 26-04-2017

ORA-10583 - Can not recovery file string renamed as missing during test recovery
ORA-10583 - Can not recovery file string renamed as missing during test recovery

  • ora-22286 : insufficient privileges on file or directory to perform string operation
  • ora-06438 : ssaio: the asynchronous read was unable to read from the database file.
  • ora-02171 : invalid value for MAXLOGHISTORY
  • ora-16210 : Logical standby coordinator process terminated with error
  • ora-27030 : skgfwrt: sbtwrite2 returned error
  • ora-02483 : Syntax error in process specification (string)
  • ora-38306 : this object is not recoverable standalone
  • ora-01030 : SELECT ... INTO variable does not exist
  • ora-01988 : remote os logon is not allowed
  • ora-27014 : skgfqpini: translation error while expanding SS_UDMPDIR
  • ora-08118 : Deferred FK constraints cannot be enforced, index too big (string)
  • ora-38408 : The ADT "string" does not exist in the current schema.
  • ora-22899 : cannot specify both scope and rowid constraint on ref column
  • ora-19640 : datafile checkpoint is SCN string time string
  • ora-19804 : cannot reclaim string bytes disk space from string limit
  • ora-31521 : CDC subscription string already subscribes to publication ID string column string
  • ora-00219 : required control file size (string logical blocks) exceeds maximum allowable size (string logical blocks)
  • ora-25198 : only range, list, and hash partitioning are supported for index-organized table
  • ora-10926 : trace name context forever
  • ora-16795 : database resource guard detects that database re-creation is required
  • ora-33098 : (APABBR01) A value of 'string' is not valid for the workspace object option.
  • ora-12835 : No instances are active in the GLOBAL_VIEW_ADMIN_GROUP
  • ora-19332 : Invalid column in the CREATE_DBURI operator
  • ora-00965 : column aliases not allowed for '*'
  • ora-36392 : (XSMXCLEA02) When using CLEAR with the PRECOMPUTES or NONPRECOMPUTES options, you must supply an AGGMAP.
  • ora-07685 : sou2os: supervisor stack set error
  • ora-23449 : missing user name
  • ora-25116 : invalid block number specified in the DUMP DATAFILE/TEMPFILE command
  • ora-24270 : a row already exists in the string table for these parameters
  • ora-19380 : invalid plan filter
  • 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.