ORA-19577: file string is MISSING

Cause : A copyDataFileCopy, restoreDataFileTo or proxyRestoreDataFile function specified a file number but no output file name, indicating that the output filename should be taken from the control file. However, the control file entry for this file indicates that it was created for a file that was present in the data dictionary but not named during the last CREATE CONTROLFILE statement, so the name in the control file cannot be used for restoration.

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

Either specify an output filename or issue a SQL RENAME command to enter a valid name for this file in the control file.

update : 18-08-2017

ORA-19577 - file string is MISSING
ORA-19577 - file string is MISSING

  • ora-38474 : attribute set may not have attributes of TABLE COLLECTION type.
  • ora-39022 : Database version string is not supported.
  • ora-30014 : operation only supported in Automatic Undo Management mode
  • ora-12715 : invalid character set specified
  • ora-13270 : OCI error string
  • ora-37050 : (XSMLTDCL06) You cannot use the RELATION command with workspace object because analytic workspace string is attached in MULTI mode.
  • ora-16810 : multiple errors or warnings detected for the database
  • ora-13140 : invalid target type
  • ora-32010 : cannot find entry to delete in SPFILE
  • ora-07215 : slsget: getrusage error.
  • ora-39057 : invalid worker request string for string jobs.
  • ora-30944 : Error during rollback for XML schema 'string' table string column 'string'
  • ora-13511 : invalid INTERVAL string, must be in the range (string, string)
  • ora-13607 : The specified task or object string already exists
  • ora-01560 : LIKE pattern contains partial or illegal character
  • ora-39778 : the parallel load option is not allowed when loading lob columns
  • ora-14075 : partition maintenance operations may only be performed on partitioned indices
  • ora-26035 : Error attempting to encrypt or decrypt column
  • ora-07550 : sftopn: $CONNECT failure
  • ora-16001 : database already open for read-only access by another instance
  • ora-27033 : failed to obtain file size limit
  • ora-12590 : TNS:no I/O buffer
  • ora-30489 : Cannot have more than one rollup/cube expression list
  • ora-02767 : Less than one request descriptor was allocated per server
  • ora-22287 : invalid or modified directory occurred during string operation
  • ora-04030 : out of process memory when trying to allocate string bytes (string,string)
  • ora-39167 : Tablespace string was not found.
  • ora-14317 : cannot drop the last value of partition
  • ora-36814 : (XSTBLFUNC07) The datatype of the column used in the ROW2CELL clause of a LIMITMAP must be RAW(16).
  • ora-26563 : renaming this table is not allowed
  • 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.