Answer / guest

Cause: The control file change sequence number in the
flashback database log file was greater than the number in
the control file. This implies that the wrong control file
was being used. Note that repeatedly causing this error can
make it stop happening without correcting the real problem.
Every attempt to open the database will advance the control
file change sequence number until it is great enough.

Action: FLASHBACK DATABASE can only be used with the current
control file. If it is not available, then a restore and an
incomplete recovery must be performed instead.

Please add more information about this Error

ORA-10641: Cannot find a rollback segment to bind to

1 Answers  

---

DRG-51019: unable to open or illegal format for fuzzy match data file: string

1 Answers  

---

ORA-00306: limit of string instances in this database

1 Answers  

---

ORA-40103: invalid case-id column: string

1 Answers  

---

ORA-19361: ONLINE option not allowed with this type of index

1 Answers  

---

ORA-15114: missing or invalid ASM file name

1 Answers  

---

KUP-02000: wrong message file version (msg number not found)

1 Answers  

---

ORA-36980: (XSRELGID02) Variable workspace object must have a numeric data type.

1 Answers  

---

ORA-19601: output file is string string (string)

1 Answers  

---

ORA-32741: Hang analysis already going on

1 Answers  

---

ORA-25531: MTTR specified is too small: string

1 Answers  

---

ORA-00321: log string of thread string, cannot update log file header

1 Answers  

---