Answer / guest

Cause: The recovery step of FLASHBACK DATABASE encountered
the creation of a datafile that could not be added to the
controlfile. An entry has been added to the controlfile for
the new datafile, but with the file name UNNAMEDnnnn, where
nnnn is the file number. Related error messages provide the
file names that were originally used to create the files.

Action: Rename the file in the controlfile, or use the ALTER
ALTER DATABASE CREATE DATAFILE command to create a file
suitable for recovery. If the file is not going to be
recovered, then take it offline with the FOR DROP option.
The recovery step of Flashback can be resumed by entering a
RECOVERY command with the same SCN or timestamp as used in
the FLASHBACK DATABASE command. For example, RECOVER
AUTOMTAIC DATABASE UNTIL CHANGE <flashback-scn>.

Please add more information about this Error

ORA-16213: ddl encountered, stopping apply engine

1 Answers  

---

PLS-00617: at least one result in the CASE expression must not be NULL

1 Answers  

---

ORA-26025: SKIP_INDEX_MAINTENANCE option requested

1 Answers  

---

ORA-02092: out of transaction table slots for distributed transaction

1 Answers  

---

ORA-30014: operation only supported in Automatic Undo Management mode

1 Answers  

---

ORA-07280: slsget: unable to get process information.

1 Answers  

---

TNS-04231: Trace Assistant WARNING: Assuming Oracle trace format

1 Answers  

---

ORA-07285: sksaprd: volume size should not be specified for a disk file.

1 Answers  

---

ORA-01522: file 'string' to be renamed does not exist

1 Answers  

---

DGM-16934: You must start instance "string" manually.

1 Answers  

---

SQL*Loader-00621: Field in data file exceeds maximum length

1 Answers  

---

DRG-11004: duplicate or conflicting value for string

1 Answers  

---