Home » RDBMS Server » Backup & Recovery » rman error (19c)
rman error [message #685466] Fri, 21 January 2022 13:04 Go to next message
culligandxb
Messages: 8
Registered: December 2020
Junior Member
While trying to restore the test db using the prod database i am getting an error like this “RMAN-06054: media recovery requesting unknown archived log for thread 1 with sequence 2963 and starting SCN of 17671820486”. I checked for the old archieve logs in Prod they are not available . How to overcome this.
Re: rman error [message #685467 is a reply to message #685466] Fri, 21 January 2022 14:22 Go to previous messageGo to next message
Michel Cadot
Messages: 68257
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator

If you lost the needed archived logs, the only thing you can do is to open with "reset logs" option and lose all modification since the first archived log you lost.

Re: rman error [message #685470 is a reply to message #685467] Sat, 22 January 2022 13:31 Go to previous messageGo to next message
culligandxb
Messages: 8
Registered: December 2020
Junior Member
Thanks Michael, is there a way to find the archieved logs which are missing from v$tables or any query.
Re: rman error [message #685471 is a reply to message #685470] Sat, 22 January 2022 14:18 Go to previous messageGo to next message
Michel Cadot
Messages: 68257
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator

On the source database:
select name from v$archived_log where sequence# >= 2963;
Re: rman error [message #685472 is a reply to message #685471] Sat, 22 January 2022 23:49 Go to previous messageGo to next message
culligandxb
Messages: 8
Registered: December 2020
Junior Member
Thanks Michael, when i run this query the name is comming as blank, but there are records . I cannot see the exact location path.
Re: rman error [message #685473 is a reply to message #685472] Sun, 23 January 2022 00:40 Go to previous messageGo to next message
Michel Cadot
Messages: 68257
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator

Try to use, in SQL*Plus, still on source database:
show parameter log_archive
This will give you the different location and state of current archive destinations and current archive name format.

[Updated on: Sun, 23 January 2022 00:45]

Report message to a moderator

Re: rman error [message #685474 is a reply to message #685472] Sun, 23 January 2022 02:09 Go to previous messageGo to next message
John Watson
Messages: 8738
Registered: January 2010
Location: Global Village
Senior Member
culligandxb wrote on Sun, 23 January 2022 05:49
Thanks Michael, when i run this query the name is comming as blank, but there are records . I cannot see the exact location path.
If the name is null, that suggests that the archive logs were backed up and deleted. So you'll have to find the backup set containing them.
Re: rman error [message #685475 is a reply to message #685474] Sun, 23 January 2022 02:45 Go to previous messageGo to next message
Michel Cadot
Messages: 68257
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator

@OP, starts a RMAN session (with target as source database) and execute the following statement to know the backup(s) containing the needed archived logs:
list backup of archivelog from sequence 2963;
Re: rman error [message #685501 is a reply to message #685471] Tue, 25 January 2022 09:26 Go to previous messageGo to next message
culligandxb
Messages: 8
Registered: December 2020
Junior Member
Thanks Michael, i came to know from the person who installed our DB that archieve logs will be maintained only for last 7 days , previous are deleted.
i am getting the error as attached. How can i restore my db using the rman backups.
Re: rman error [message #685503 is a reply to message #685501] Tue, 25 January 2022 10:44 Go to previous messageGo to next message
Michel Cadot
Messages: 68257
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator

Quote:
archieve logs will be maintained only for last 7 days , previous are deleted.

Not a problem if you backed up them.
Of course, deleting needed archive logs without backing up them is the biggest error a DBA can do (whose prime duty is to guarantee to be able to restore the database).

You have to post the complete command, script you executed and log you got.
It is not possible to answer to an error from something that looks different (duplicate database) from the original question (restore database).

[Updated on: Tue, 25 January 2022 10:47]

Report message to a moderator

Re: rman error [message #685506 is a reply to message #685503] Tue, 25 January 2022 10:55 Go to previous messageGo to next message
culligandxb
Messages: 8
Registered: December 2020
Junior Member
HI Michael,

Please find below the commands that i used. i have attached the log file as well.

C:\Windows\system32>rman auxiliary /

Recovery Manager: Release 19.0.0.0.0 - Production on Tue Jan 25 05:08:12 2022
Version 19.3.0.0.0

Copyright (c) 1982, 2019, Oracle and/or its affiliates.  All rights reserved.

connected to auxiliary database: TST10CDB (not mounted)

RMAN> RUN
2> {
3>   DUPLICATE DATABASE TO 'TST10CDB' BACKUP LOCATION 'D:\IFS\RMANRestore\Backupfiles' NOFILENAMECHECK;
4> }

Re: rman error [message #685507 is a reply to message #685506] Tue, 25 January 2022 11:04 Go to previous messageGo to next message
Michel Cadot
Messages: 68257
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator

You still have the same error than originally:
RMAN-20515: archived log file not found
RMAN-06054: media recovery requesting unknown archived log for thread 1 with sequence 2963 and starting SCN of 17671820486
If you have no backup of the needed archived logs then you have to do an incomplete recovery something like:
DUPLICATE DATABASE TO 'TST10CDB' BACKUP LOCATION 'D:\IFS\RMANRestore\Backupfiles' NOFILENAMECHECK
until sequence 2963;
Re: rman error [message #685508 is a reply to message #685507] Tue, 25 January 2022 11:14 Go to previous messageGo to next message
culligandxb
Messages: 8
Registered: December 2020
Junior Member
The problem is i dont have logs prior to that sequence. Is there a way to restore it using cold backup in Multi tenant. Please share some links or steps to do that.
Re: rman error [message #685509 is a reply to message #685508] Tue, 25 January 2022 12:53 Go to previous message
Michel Cadot
Messages: 68257
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator

If you have an RMAN cold backup, it is not difficult to restore and recover until the backup time.

Backup and Recovery User's Guide
Chapter 20 Performing RMAN Recovery: Advanced Scenarios
Section 20.5 Restoring a Database on a New Host

Previous Topic: Archivelog backup and Incremental backup
Next Topic: exclude tablespace from backup
Goto Forum:
  


Current Time: Wed Aug 10 02:16:34 CDT 2022