Answer / guest

Cause: When comparing the controlfile with the data
dictionary after a CREATE CONTROLFILE or OPEN RESETLOGS, it
was noted that this datafile was inconsistent with the
dictionary. Most likely the file is a backup of a file that
was dropped from the database, and the same file number was
reused for a new file. It may also be that an incomplete
recovery stopped at a time when this file number was used
for another datafile.

Action: Do a CREATE CONTROLFILE with the correct file or
none at all.

Please add more information about this Error

ORA-06923: CMX: illegal break condition

1 Answers  

---

ORA-07703: error in archive text: need '/' after device type

1 Answers  

---

NID-00372: Change database ID and database name string to string? (Y/[N]) =>

1 Answers  

---

LSX-00260: unexpected end of pattern

1 Answers  

---

ORA-27490: cannot open disabled window "string.string"

1 Answers  

---

ORA-14252: invalid ALTER TABLE MODIFY PARTITION option for a Hash partition

1 Answers  

---

ORA-24398: connection pool already exists

1 Answers  

---

ORA-22319: type attribute information altered in ALTER TYPE

1 Answers  

---

ORA-16011: Archivelog Remote File Server process in Error state

1 Answers  

---

PLS-00421: synonym definitions nested too deeply; possible loop in synonyms

1 Answers  

---

ORA-37111: Unable to load the OLAP API sharable library: (string)

1 Answers  

---

ORA-09350: Windows 32-bit Two-Task driver unable to allocate context area

1 Answers  

---