ORA-01152: file string was not restored from a sufficiently
old backup
Answers were Sorted based on User's Feedback
Answer / guest
Cause: An incomplete recovery session was started, but an
insufficient number of logs were applied to make the
database consistent. This file is still in the future of the
last log applied. The most likely cause of this error is
forgetting to restore the file from a backup before doing
incomplete recovery.
Action: Either apply more logs until the database is
consistent or restore the database file from an older backup
and repeat recovery.
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / suhas d
Hello,
If we use a backup controlfile and do recovery, it is
mandatory to open the database with the RESETLOGS option
(incomplete or point in time recovery).
The Backup and Recovery Basics Oracle doc states this
clearly.
If this is an ARCHIVE mode database and controlfile was
backed up using RMAN 'BACKUP CURRENT CONTROLFILE' or such,
we can do incomplete recovery and open resetlogs.
SQL> recover database until cancel using backup controlfile;
Copy over as many archived logs from source to the local
(target) log_archive_dest folder (suggested) and give full
path directions in the above command.
Recovery can happen until you wish to. Type CANCEL when
done and open the database with resetlogs option.
Regards,
Suhas
| Is This Answer Correct ? | 0 Yes | 0 No |
ORA-25453: invalid iterator: string
QSM-00750: the specified value string for parameter string is invalid or contains an invalid item
PLS-00241: invalid external type specification for SQLSTATE
TNS-04067: Number of connections: number.
ORA-09344: spsig: error signalling thread
ORA-27066: number of buffers in vector I/O exceeds maximum
ORA-32588: supplemental logging attribute string exists
ORA-32034: unsupported use of WITH clause
ORA-30084: invalid data type for datetime primary with time zone modifier
QSM-01109: while rewriting with MV, string, table, string, migrated to query delta
ORA-01549: tablespace not empty, use INCLUDING CONTENTS option
ORA-10563: Test recovery had to corrupt data block (file# string, block# string) in order to proceed