Answer / guest

Cause: Either an earlier database recovery session specified
BACKUP CONTROLFILE, or the controlfile was recreated with
the RESETLOGS option, or the controlfile being used is a
backup controlfile. After that only BACKUP CONTROLFILE
recovery is allowed and it must be followed by a log reset
at the next database open.

Action: Perform recovery using the BACKUP CONTROFILE option.

Please add more information about this Error

ORA-13780: SQL statement does not exist.

1 Answers  

---

NNF-00003: Naming adapter string does not exist

1 Answers  

---

ORA-38704: Checksum error in flashback database log file header.

1 Answers  

---

ORA-00029: session is not a user session

1 Answers  

---

ORA-25124: Database link name not allowed.

1 Answers  

---

---

RMAN-06544: Do you really want to delete the above objects (enter YES or NO)?

1 Answers  

---

RMAN-06033: channel string not allocated

1 Answers  

---

ORA-02174: Missing required thread number

1 Answers  

---

RMAN-08522: input datafile fno=string name=string

1 Answers  

---

ORA-06546: DDL statement is executed in an illegal context

1 Answers   Oracle,

---

ORA-36206: (XSAGOP04R) In AGGMAP workspace object, REMOPERATOR string must be MIN, MAX, FIRST, LAST, HFIRST or HLAST.

1 Answers  

---

PLS-00495: too many columns in SELECT...INTO statement after bursting record targets

1 Answers  

---