Home » RDBMS Server » Backup & Recovery » RMAN recovery not working as I expected (recovery manager 19.28, RHEL 7.9)
RMAN recovery not working as I expected [message #690448] Mon, 29 December 2025 12:01 Go to next message
jacklieb
Messages: 2
Registered: December 2025
Junior Member
It will be difficult, but I'll try to be as brief as possible...
I'm working on a db refresh process that will use storage vendor snapshots and roll-forward to a point-in-time using rman recover. I created a test table in the source database and logged the current log sequence number. I copied the snapshot to the target server and I'm trying to get rman to perform an "until time" recovery. The rman logfile actually shows it finding the log sequence number in online redo and states: "media recovery complete". However, the table i created in the source is not there after open resetlogs.

Here's a log snippet:
starting media recovery

archived log for thread 1 with sequence 11780 is already on disk as file /u02/oradata/vtxprd/redo02a.log
archived log file name=/u02/oradata/******/redo02a.log thread=1 sequence=11780
media recovery complete, elapsed time: 00:00:00
Finished recover at 29-dec-2025 11:04:50

I'll happily provide more details if there's someone willing to help. I will say this - I do put the database in backup mode prior to taking the daily snapshot (I knew youd ask that). I can get this process to work but only up to the time the snapshot was taken. I can't get this figured out and really could use some help. I've seen and used many good posts from this site so I know there's someone who can help.

Thanks - Jack
Re: RMAN recovery not working as I expected [message #690449 is a reply to message #690448] Fri, 02 January 2026 09:10 Go to previous messageGo to next message
jacklieb
Messages: 2
Registered: December 2025
Junior Member
I finally figured this out and I'm posting in-case it can help someone else. We're changing our non-prod refresh strategy from RMAN duplicate to using storage vendor snapshots to trim time off an already time-consuming process. Eventually I discovered that the presence of online redo logs (ours co-exist on our datafile volumes) was preventing the RMAN RECOVER command from using archived logs and in-turn not honoring the UNTIL TIME parameter. I deleted all online redo logfiles after copying the snapshot and everything started working as I expected. HTH - Jack
Re: RMAN recovery not working as I expected [message #690450 is a reply to message #690449] Fri, 02 January 2026 12:02 Go to previous messageGo to next message
Michel Cadot
Messages: 68774
Registered: March 2007
Location: Saint-Maur, France, https...
Senior Member
Account Moderator

Thanks for your feedback.

Re: RMAN recovery not working as I expected [message #690451 is a reply to message #690449] Mon, 05 January 2026 06:51 Go to previous message
John Watson
Messages: 8996
Registered: January 2010
Location: Global Village
Senior Member
There may be something else going on.
The presence or absence of online logfiles should have no effect on whether or not recovery will use archive logfiles, but if you delete them you will not be able to do a complete recovery: you can recover only up to the last archive logfile. Is that what you want? To deliberately lose all work after the last archive?
You have found a solution that works for you, but be aware that it may not be appropriate for all situations.
HT, John.
Previous Topic: moving rman backup and restore on new server
Goto Forum:
  


Current Time: Mon Jan 19 08:28:24 CST 2026