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-01426: numeric overflow

1 Answers  

---

NNL-00912: Alias loops detected: number

1 Answers  

---

ORA-12032: cannot use rowid column from materialized view log on "string"."string"

1 Answers  

---

TNS-12524: TNS:listener could not resolve HANDLER_NAME given in connect descriptor

1 Answers  

---

ORA-02239: there are objects which reference this sequence

1 Answers  

---

QSM-00776: the user-defined workload string is missing the following column: string

1 Answers  

---

ORA-07483: snlkget: cannot convert(get) lock.

1 Answers  

---

TNS-00103: Parameter file load error

1 Answers  

---

ORA-01616: instance string (thread string) is open - cannot disable

1 Answers  

---

QSM-02025: no aggregate functions

1 Answers  

---

ORA-08109: nosort is not a supported option for online index build

1 Answers  

---

ORA-06535: statement string in string is NULL or 0 length

1 Answers   RoboSoft,

---