Answer / guest

Cause: In a CREATE CONTROLFILE command either this file or
all previous files were backups from before the last
RESETLOGS. This may also occur if this is a file that is
offline and has been offline since before the last RESETLOGS.

Action: If the file was taken offline normal before the last
RESETLOGS, and is still offline, omit it from the CREATE
CONTROLFILE command. Rename and online the file after the
database is open. Otherwise find the version of the
mentioned file consistent with the rest of the datafiles and
resubmit the command.

Please add more information about this Error

ORA-01591: lock held by in-doubt distributed transaction string

1 Answers  

---

ORA-12599: TNS:cryptographic checksum mismatch

1 Answers  

---

RMAN-20310: proxy copy not found in the recovery catalog

1 Answers  

---

ORA-29825: invalid name for indextype

1 Answers  

---

ORA-22889: REF value does not point to scoped table

1 Answers  

---

---

PROC-00003: Cannot perform cluster registry operation because context is invalid.

1 Answers  

---

ORA-16504: The Data Guard configuration already exists.

1 Answers  

---

SQL*Loader-00258: Maximum number of SORTED INDEXES (number) exceeded on table string

1 Answers  

---

ORA-24181: The type string does not exist

1 Answers  

---

ORA-13628: Insufficient privileges to access the task belonging to user string

1 Answers  

---

LSX-00020: unknown type "~S"

1 Answers  

---

ORA-01216: thread string is expected to be disabled after CREATE CONTROLFILE

1 Answers  

---