Answer / guest

Cause: Attempting to do a RESETLOGS open with a file entry
in the controlfile that was originally created after the
UNTIL time of the incomplete recovery. Allowing such an
entry may hide the version of the file that is needed at
this time. The file number may be in use for a different
file which would be lost if the RESETLOGS was allowed.

Action: If more recovery is desired then apply redo until
the creation time of the file is reached. If the file is not
wanted and the same file number is not in use at the stop
time of the recovery, then the file can be taken offline
with the FOR DROP option. Otherwise a different controlfile
is needed to allow the RESETLOGS. Another backup can be
restored and recovered, or a controlfile can be created via
CREATE CONTROLFILE.

Please add more information about this Error

RMAN-08054: starting media recovery

1 Answers  

---

ORA-02196: PERMANENT/TEMPORARY option already specified

1 Answers  

---

ORA-38467: user cannot GRANT/REVOKE privileges to/from himself

1 Answers  

---

ORA-27087: unable to get share lock - file not readable

1 Answers  

---

LCD-00204: left parenth and no parameter specified [string]

1 Answers  

---

ORA-07218: slkhst: could not perform host operation

1 Answers  

---

ORA-13826: empty SQL profile not allowed for create or update SQL profile

1 Answers  

---

ORA-12352: object string.string@string is invalid

1 Answers  

---

ORA-01217: logfile member belongs to a different logfile group

1 Answers  

---

ORA-12812: only one PARALLEL or NOPARALLEL clause may be specified

1 Answers  

---

KUP-03018: invalid date mask "string" specified for column string

1 Answers  

---

ORA-27481: "string.string" has an invalid schedule

1 Answers  

---