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

NNL-00013: not performed, permission denied for supplied password

1 Answers  

---

NZE-29049: Unknown record

1 Answers  

---

DRG-12601: invalid user datastore procedure name: string

1 Answers  

---

DRG-11525: invalid commitafter parameter of string specified

1 Answers  

---

ORA-23538: cannot explicitly refresh a NEVER REFRESH materialized view ("string")

1 Answers  

---

ORA-13288: point coordinate transformation error

1 Answers  

---

ORA-38715: Invalid log number specified in the DUMP FLASHBACK command.

1 Answers  

---

ORA-22304: input type is not an object type

1 Answers  

---

ORA-09929: GLB of two labels is invalid

1 Answers  

---

PCC-00047: Unterminated comment/string constant beginning near line number in file string

1 Answers  

---

ORA-15113: alias name 'string' refers to a directory

1 Answers  

---

RMAN-06502: skipping archive log file string; already backed on string

1 Answers  

---