ORA-1248 by DBPITR that used a current controlfile
(Doc ID 1558515.1)
Last updated on DECEMBER 20, 2019
Applies to:
Oracle Database Cloud Schema Service - Version N/A and laterOracle Database Backup Service - Version N/A and later
Oracle Database Cloud Service - Version N/A and later
Oracle Database - Enterprise Edition - Version 10.2.0.4 to 11.2.0.4 [Release 10.2 to 11.2]
Oracle Database Exadata Cloud Machine - Version N/A and later
Information in this document applies to any platform.
Symptoms
NOTE: In the images and/or the document content below, the user information and environment data used represents fictitious data from the
Oracle sample schema(s), Public Documentation delivered with an Oracle database product or other training material. Any similarity to actual
environments, actual persons, living or dead, is purely coincidental and not intended in any manner.
Oracle sample schema(s), Public Documentation delivered with an Oracle database product or other training material. Any similarity to actual
environments, actual persons, living or dead, is purely coincidental and not intended in any manner.
For the purposes of this document, the following fictitious environment is used as an example to describe the procedure:
Directory Name: /oracle/dbs and sub-directories
**********
RMAN or manual Point In time Recovery (DBPITR / PITR) fail with ORA-1248.
$ oerr ora 1248
01248, 00000, "file %s was created in the future of incomplete recovery"
*Cause: Attempting to do a RESETLOGS open with a file entry in the
control file 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 control file is needed to allow the RESETLOGS.
Another backup can be restored and recovered, or a control file can
be created via CREATE CONTROLFILE.
01248, 00000, "file %s was created in the future of incomplete recovery"
*Cause: Attempting to do a RESETLOGS open with a file entry in the
control file 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 control file is needed to allow the RESETLOGS.
Another backup can be restored and recovered, or a control file can
be created via CREATE CONTROLFILE.
Example of errors for a recovery session (RMAN or manual RECOVER):
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01248: file 4 was created in the future of incomplete recovery
ORA-01248: file 4 was created in the future of incomplete recovery
Open database fails with:
ORA-01248: file <file#> was created in the future of incomplete recovery
As an example the next PITR command is used:
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |
| Step 1. Make the datafiles OFFLINE DROP created after PITR and try to OPEN |
| Step 2. Recreate the CONTROL FILE and OPEN if step 1 did not allow the database to be OPEN |