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-12701: CREATE DATABASE character set is not known

1 Answers  

---

ORA-12413: labels do not belong to the same policy

1 Answers  

---

ORA-01162: block size string in file header does not match configured block sizes

1 Answers  

---

ORA-07276: no dba group in /etc/group.

1 Answers  

---

ORA-19758: failed to enable/disable block change tracking: out of SGA memory

1 Answers  

---

ORA-33456: (ESDREAD08) Discarding compiled code for workspace object because number is a(n) string, which string did not expect to find in a compiled program.

1 Answers  

---

DRG-11722: invalid language specification

1 Answers  

---

SQL*Loader-00951: Error calling once/load initialization

1 Answers  

---

ORA-15103: conflicting or duplicate REPAIR options

1 Answers  

---

ORA-29872: parameters clause cannot be combined with the specified options

1 Answers  

---

RMAN-08153: deleted global script: string

1 Answers  

---

ORA-25291: Buffer does not exist for the specified queue

1 Answers  

---