| Why did rman complain about archivelog not available based on the current retention policy [message #651795] |
Wed, 25 May 2016 03:15  |
 |
juniordbanewbie
Messages: 250
Registered: April 2014
|
Senior Member |
|
|
Dear all,
when I run the following restore archivelog all validate, I encounter the following error:
Spooling started in log file: validate_archivelog.log
Recovery Manager11.2.0.4.0
RMAN>
RMAN> SET ECHO ON
echo set on
RMAN>
RMAN> restore archivelog all validate;
Starting restore at 2016-05-25 15:46:00
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=40 device type=DISK
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 05/25/2016 15:46:01
RMAN-06026: some targets not found - aborting restore
RMAN-06025: no backup of archived log for thread 1 with sequence 19 and starting SCN of 1377915 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 18 and starting SCN of 1294312 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 17 and starting SCN of 1254478 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 16 and starting SCN of 1050064 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 15 and starting SCN of 912921 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 14 and starting SCN of 867019 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 13 and starting SCN of 756910 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 12 and starting SCN of 733014 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 11 and starting SCN of 719078 found to restore
RMAN>
RMAN> EXIT
Recovery Manager complete.
here's my retention policy and my backup available
Spooling started in log file: list_backup.log
Recovery Manager11.2.0.4.0
RMAN>
RMAN> SET ECHO ON
echo set on
RMAN>
RMAN> show retention policy;
RMAN configuration parameters for database with db_unique_name NOWATZKI are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
RMAN>
RMAN> list backup of controlfile;
List of Backup Sets
===================
BS Key Type LV Size Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ -------------------
22 Full 9.36M DISK 00:00:02 2016-05-25 14:19:38
BP Key: 22 Status: AVAILABLE Compressed: NO Tag: TAG20160525T141936
Piece Name: C:\USERS\ADMINISTRATOR\BACKUP\AUTOBACKUP\C-4036717104-20160525-00
Control File Included: Ckp SCN: 1748336 Ckp time: 2016-05-25 14:19:36
BS Key Type LV Size Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ -------------------
24 Full 9.36M DISK 00:00:01 2016-05-25 14:51:28
BP Key: 24 Status: AVAILABLE Compressed: NO Tag: TAG20160525T145127
Piece Name: C:\USERS\ADMINISTRATOR\BACKUP\AUTOBACKUP\C-4036717104-20160525-01
Control File Included: Ckp SCN: 1750385 Ckp time: 2016-05-25 14:51:27
RMAN>
RMAN> list backup of database;
List of Backup Sets
===================
BS Key Type LV Size Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ -------------------
17 Incr 0 1.11G DISK 00:02:07 2016-05-10 20:12:16
BP Key: 17 Status: AVAILABLE Compressed: NO Tag: NOWATZKI_20160510_INC0
Piece Name: F:\APP\ORACLE\FAST_RECOVERY_AREA\NOWATZKI\BACKUPSET\2016_05_10\O1_MF_NNND0_NOWATZKI_20160510_IN_CM3MX9VW_.BKP
List of Datafiles in backup set 17
File LV Type Ckp SCN Ckp Time Name
---- -- ---- ---------- ------------------- ----
1 0 Incr 1468172 2016-05-10 20:10:09 E:\APP\ORACLE\ORADATA\NOWATZKI\SYSTEM01.DBF
2 0 Incr 1468172 2016-05-10 20:10:09 E:\APP\ORACLE\ORADATA\NOWATZKI\SYSAUX01.DBF
3 0 Incr 1468172 2016-05-10 20:10:09 E:\APP\ORACLE\ORADATA\NOWATZKI\UNDOTBS01.DBF
4 0 Incr 1468172 2016-05-10 20:10:09 E:\APP\ORACLE\ORADATA\NOWATZKI\USERS01.DBF
BS Key Type LV Size Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ -------------------
23 Incr 0 1.10G DISK 00:01:40 2016-05-25 14:51:21
BP Key: 23 Status: AVAILABLE Compressed: NO Tag: NOWATZKI_20160525_INC0
Piece Name: F:\APP\ORACLE\FAST_RECOVERY_AREA\NOWATZKI\BACKUPSET\2016_05_25\O1_MF_NNND0_NOWATZKI_20160525_IN_CNBLR60B_.BKP
List of Datafiles in backup set 23
File LV Type Ckp SCN Ckp Time Name
---- -- ---- ---------- ------------------- ----
1 0 Incr 1750299 2016-05-25 14:49:41 E:\APP\ORACLE\ORADATA\NOWATZKI\SYSTEM01.DBF
2 0 Incr 1750299 2016-05-25 14:49:41 E:\APP\ORACLE\ORADATA\NOWATZKI\SYSAUX01.DBF
3 0 Incr 1750299 2016-05-25 14:49:41 E:\APP\ORACLE\ORADATA\NOWATZKI\UNDOTBS01.DBF
4 0 Incr 1750299 2016-05-25 14:49:41 E:\APP\ORACLE\ORADATA\NOWATZKI\USERS01.DBF
RMAN>
RMAN> list backup of archivelog all;
List of Backup Sets
===================
BS Key Size Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ -------------------
19 108.76M DISK 00:00:06 2016-05-10 20:28:18
BP Key: 19 Status: AVAILABLE Compressed: NO Tag: NOWATZKI_20160510_ARC
Piece Name: F:\APP\ORACLE\FAST_RECOVERY_AREA\NOWATZKI\BACKUPSET\2016_05_10\O1_MF_ANNNN_NOWATZKI_20160510_AR_CM3NYX01_.BKP
List of Archived Logs in backup set 19
Thrd Seq Low SCN Low Time Next SCN Next Time
---- ------- ---------- ------------------- ---------- ---------
1 20 1439431 2016-05-10 17:46:59 1468920 2016-05-10 20:28:05
BS Key Size Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ -------------------
21 270.37M DISK 00:00:18 2016-05-25 14:19:28
BP Key: 21 Status: AVAILABLE Compressed: NO Tag: NOWATZKI_20160525_ARC
Piece Name: F:\APP\ORACLE\FAST_RECOVERY_AREA\NOWATZKI\BACKUPSET\2016_05_25\O1_MF_ANNNN_NOWATZKI_20160525_AR_CNBJYYWF_.BKP
List of Archived Logs in backup set 21
Thrd Seq Low SCN Low Time Next SCN Next Time
---- ------- ---------- ------------------- ---------- ---------
1 21 1468920 2016-05-10 20:28:05 1557087 2016-05-16 13:58:03
1 22 1557087 2016-05-16 13:58:03 1586601 2016-05-17 07:28:22
1 23 1586601 2016-05-17 07:28:22 1608485 2016-05-18 09:07:20
1 24 1608485 2016-05-18 09:07:20 1635177 2016-05-18 11:24:44
1 25 1635177 2016-05-18 11:24:44 1672465 2016-05-18 15:29:25
1 26 1672465 2016-05-18 15:29:25 1716704 2016-05-25 07:29:31
1 27 1716704 2016-05-25 07:29:31 1748302 2016-05-25 14:19:05
RMAN>
RMAN> SPOOL LOG OFF
why is rman regarding the missing archivelog as required to fulfilled the retention policy.
While I understand we can use restore <> validate to validate the backup, how do I know if all the required backup is available to restore the database by viewing just the list of backup.
many thanks in advance!
|
|
|
|
| Re: Why did rman complain about archivelog not available based on the current retention policy [message #651813 is a reply to message #651795] |
Wed, 25 May 2016 10:17  |
Frank Naude
Messages: 4587
Registered: April 1998
|
Senior Member |
|
|
The 'restore archivelog all validate' command doesn't recognise deleted backups.
This falls into the category of "what were they thinking"! However, it's nothing to be too concerned about.
You can generate a command to check only what you need to check from sqlplus with:
select 'restore validate archivelog from scn '||min_first_change#||' until scn '||max_next_change#
from v$backup_archivelog_summary;
Remember to also check:
RMAN> RESTORE SPFILE VALIDATE;
RMAN> RESTORE CONTROLFILE VALIDATE;
RMAN> RESTORE DATABASE VALIDATE;
PS: I've just noticed the line "using target database control file instead of recovery catalog".
Connecting to both the target database and recovery catalog should resolve the problem as well.
Good luck!
Frank
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
