ORA-01248: file string was created in the future of
incomplete recovery
- 1 Answers
- 4622 Views
- I also Faced
- E-Mail Answers
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
| Is This Answer Correct ? | 0 Yes | 0 No |
RMAN-03015: error occurred in stored script string
NNO-00708: cache flush countdown aborted
DRG-10845: column string is not indexed
ORA-30110: syntax error at 'string'
NNL-01041: Data stream open failures: number
QSM-02034: no joins are present in the HAVING clause
NID-00109: DBNAME string length number exceeds maximum length of number
DRG-52203: invalid object name: string
SQL-02157: Source or destination lob is invalid
EXP-00101: Version 1 extensible index "string"."string" can not be included in Transportable Tablespace Export
ORA-06024: NETASY: VTM error
ORA-13631: The task string contains no execution results.
Oracle Errors 
