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-02271: table does not have such constraint

1 Answers  

---

ORA-30735: cannot create multiple subtables of the same type under a supertable

1 Answers  

---

NID-00107: File I/O error on datafile "string" during string operation (number/string)

1 Answers  

---

UDE-00011: parameter string is incompatible with parameter string

1 Answers  

---

ORA-25506: resource manager has not been continuously on in some instances

1 Answers  

---

TNS-12152: TNS:unable to send break message

1 Answers  

---

ORA-08314: sllfcf: Error closing file

1 Answers  

---

ORA-02259: duplicate UNIQUE/PRIMARY KEY specifications

1 Answers  

---

PLS-00430: FORALL iteration variable string is not allowed in this context

1 Answers  

---

NNL-00235: Auto-refresh failure-retry expiration period is now string

1 Answers  

---

ORA-16721: unable to set LOG_ARCHIVE_DEST_n parameters

1 Answers  

---

ORA-37018: (XSACQUIRE03) Multiwriter operations are not supported for object workspace object.

1 Answers  

---