Discussions
Categories
- 17.9K All Categories
- 3.4K Industry Applications
- 3.3K Intelligent Advisor
- 62 Insurance
- 536.1K On-Premises Infrastructure
- 138.2K Analytics Software
- 38.6K Application Development Software
- 5.7K Cloud Platform
- 109.4K Database Software
- 17.5K Enterprise Manager
- 8.8K Hardware
- 71.1K Infrastructure Software
- 105.2K Integration
- 41.6K Security Software
Point in Time recovery with timestamp

Hello,
I'm attempting a Point in time recovery for a database backup done about a month ago.
Restore of the datafiles completes successfully. However recovery fails as it looks for an archive log of a future backup, which no longer exists.
RMAN-20506: no backup of archived log found
RMAN-06053: unable to perform media recovery because of missing log
RMAN-06025: no backup of archived log for thread 1 with sequence 1538 and starting SCN of 1365326 found to restore
How do I select a timestamp for which the recovery will not require archive logs of future backups.
Answers
-
You can do a RMAN "list backup" to find the low SCN of the next archived log sequence contained in a backupset. Your options to recover the database, however, depend on the type of backup you performed, and what data is available. Keep in mind that a recovery cannot run backwards with the exception of undo for uncommitted transactions. To perform a recovery of an inconsistent or open database using a backup you need to have archielogs or backup of archivelogs available, including archived redo logs, that were used during the RMAN backup.
If you used "backup database plus archivelog" to backup the database, then RMAN automatically includes archive logs including the current redo log prior and after the backup of the datafiles. However, if all you have is a single backup of an open database that included no archivelogs, have no backup of archivlogs and no online archivlogs, and no appropriate redo logs, then your database cannot be recovered and is essentially lost. Specifying a timestamp in such case won't help you.