restore archivelog all validate; gives RMAN-06025

[Woody McKay]

Hi, ( note, cross posted in Oracle community Database Backup and Recovery )



I'm not super-versed with RMAN but am trying to resolve an rman issue on a
development server. The DB environment can be rebuilt if needed, but I'd
like to try and resolve this with a crosscheck command, etc.



The weekly rman backup script looks like:

run {

configure controlfile autobackup on;

configure controlfile autobackup format for device type disk to '%F';

configure retention policy to recovery window of 7 days;

allocate channel d1 type disk maxpiecesize=5G;

backup as compressed backupset incremental level 0 cumulative tag
'L0'database

plus archivelog delete all input;

restore database validate;

release channel d1;

delete noprompt obsolete;

restore database check logical validate;

backup validate database;

*restore archivelog from time 'SYSDATE-14' validate;*

host 'copy C:\oracle\product\12.1.0\dbhome_1\NETWORK\ADMIN\tnsnames.ora
C:\oradata\fast_recovery_area\';

host 'copy C:\oracle\product\12.1.0\dbhome_1\NETWORK\ADMIN\sqlnet.ora
C:\oradata\fast_recovery_area\';

host 'copy C:\oracle\product\12.1.0\dbhome_1\NETWORK\ADMIN\listener.ora
C:\oradata\fast_recovery_area\';

host 'copy C:\oracle\product\12.1.0\dbhome_1\database\pwd*.ora
C:\oradata\fast_recovery_area\';

}

list incarnation of database;

list backup summary;

list backup by file;

list recoverable backup of database;

report schema;

report need backup redundancy=3;

report need backup recovery window of 3 days;



The command "restore archivelog from time 'SYSDATE-14' validate;" is
throwing the below error:



RMAN> restore archivelog from time 'SYSDATE-14' validate;

Starting restore at 07-OCT-15

using channel ORA_DISK_1

RMAN-00571: ===========================================================

RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

RMAN-00571: ===========================================================

RMAN-03002: failure of restore command at 10/07/2015 15:15:49

RMAN-06026: some targets not found - aborting restore

RMAN-06025: no backup of archived log for thread 1 with sequence 38 and
starting SCN of 4330735 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 37 and
starting SCN of 4324802 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 36 and
starting SCN of 4311903 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 35 and
starting SCN of 4230358 found to restore

...


Note, that "RMAN> restore archivelog from time 'SYSDATE-1' validate;" does
work successfully.



I did find and removed on obsolete backup set, but that didn't resolve the
06026 error.



I tried "crosscheck archivelog all;", but that does not resolve the 06026
error during the restore archivelog validate.



Is there a crosscheck command or other command that would sync the catalog
and disk to resolve the 06026?



Thanks for all replies.

[Andrew Kerber]

I'm not sure I understand the problem. Everything seems to be working properly. You have a recovery window of 7 days and are asking for archive logs 14 days old, and they are gone as they should be. I don't actually see a problem here.

Sent from my iPad

Post by Woody McKay
Hi, ( note, cross posted in Oracle community Database Backup and Recovery )
I'm not super-versed with RMAN but am trying to resolve an rman issue on a development server. The DB environment can be rebuilt if needed, but I'd like to try and resolve this with a crosscheck command, etc.
run {
configure controlfile autobackup on;
configure controlfile autobackup format for device type disk to '%F';
configure retention policy to recovery window of 7 days;
allocate channel d1 type disk maxpiecesize=5G;
backup as compressed backupset incremental level 0 cumulative tag 'L0'database
plus archivelog delete all input;
restore database validate;
release channel d1;
delete noprompt obsolete;
restore database check logical validate;
backup validate database;
restore archivelog from time 'SYSDATE-14' validate;
host 'copy C:\oracle\product\12.1.0\dbhome_1\NETWORK\ADMIN\tnsnames.ora C:\oradata\fast_recovery_area\';
host 'copy C:\oracle\product\12.1.0\dbhome_1\NETWORK\ADMIN\sqlnet.ora C:\oradata\fast_recovery_area\';
host 'copy C:\oracle\product\12.1.0\dbhome_1\NETWORK\ADMIN\listener.ora C:\oradata\fast_recovery_area\';
host 'copy C:\oracle\product\12.1.0\dbhome_1\database\pwd*.ora C:\oradata\fast_recovery_area\';
}
list incarnation of database;
list backup summary;
list backup by file;
list recoverable backup of database;
report schema;
report need backup redundancy=3;
report need backup recovery window of 3 days;
RMAN> restore archivelog from time 'SYSDATE-14' validate;
Starting restore at 07-OCT-15
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 10/07/2015 15:15:49
RMAN-06026: some targets not found - aborting restore
RMAN-06025: no backup of archived log for thread 1 with sequence 38 and starting SCN of 4330735 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 37 and starting SCN of 4324802 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 36 and starting SCN of 4311903 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 35 and starting SCN of 4230358 found to restore
...
Note, that "RMAN> restore archivelog from time 'SYSDATE-1' validate;" does work successfully.
I did find and removed on obsolete backup set, but that didn't resolve the 06026 error.
I tried "crosscheck archivelog all;", but that does not resolve the 06026 error during the restore archivelog validate.
Is there a crosscheck command or other command that would sync the catalog and disk to resolve the 06026?
Thanks for all replies.
--
Sincerely,
WoodyMcKay

[Woody McKay]

Hi Andrew,

This is a script I've inherited and won't be able to change till next
spring - and I do appreciate any improvements. However, this script has
been working fine in thousands of servers for several years. I'm thinking
there must be something about this particular server.

Even though the "restore archivelog validate" is asking for the last 2
weeks, shouldn't it be able to run successfully even if there are only 2
days of backups?

Am I misunderstanding or missing something?

Thanks

Post by Andrew Kerber
I'm not sure I understand the problem. Everything seems to be working
properly. You have a recovery window of 7 days and are asking for archive
logs 14 days old, and they are gone as they should be. I don't actually see
a problem here.
Sent from my iPad
Hi, ( note, cross posted in Oracle community Database Backup and Recovery )
I'm not super-versed with RMAN but am trying to resolve an rman issue on a
development server. The DB environment can be rebuilt if needed, but I'd
like to try and resolve this with a crosscheck command, etc.
run {
configure controlfile autobackup on;
configure controlfile autobackup format for device type disk to '%F';
configure retention policy to recovery window of 7 days;
allocate channel d1 type disk maxpiecesize=5G;
backup as compressed backupset incremental level 0 cumulative tag 'L0'database
plus archivelog delete all input;
restore database validate;
release channel d1;
delete noprompt obsolete;
restore database check logical validate;
backup validate database;
*restore archivelog from time 'SYSDATE-14' validate;*
host 'copy C:\oracle\product\12.1.0\dbhome_1\NETWORK\ADMIN\tnsnames.ora
C:\oradata\fast_recovery_area\';
host 'copy C:\oracle\product\12.1.0\dbhome_1\NETWORK\ADMIN\sqlnet.ora
C:\oradata\fast_recovery_area\';
host 'copy C:\oracle\product\12.1.0\dbhome_1\NETWORK\ADMIN\listener.ora
C:\oradata\fast_recovery_area\';
host 'copy C:\oracle\product\12.1.0\dbhome_1\database\pwd*.ora
C:\oradata\fast_recovery_area\';
}
list incarnation of database;
list backup summary;
list backup by file;
list recoverable backup of database;
report schema;
report need backup redundancy=3;
report need backup recovery window of 3 days;
The command "restore archivelog from time 'SYSDATE-14' validate;" is
RMAN> restore archivelog from time 'SYSDATE-14' validate;
Starting restore at 07-OCT-15
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 10/07/2015 15:15:49
RMAN-06026: some targets not found - aborting restore
RMAN-06025: no backup of archived log for thread 1 with sequence 38 and
starting SCN of 4330735 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 37 and
starting SCN of 4324802 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 36 and
starting SCN of 4311903 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 35 and
starting SCN of 4230358 found to restore
...
Note, that "RMAN> restore archivelog from time 'SYSDATE-1' validate;" does
work successfully.
I did find and removed on obsolete backup set, but that didn't resolve the 06026 error.
I tried "crosscheck archivelog all;", but that does not resolve the 06026
error during the restore archivelog validate.
Is there a crosscheck command or other command that would sync the catalog
and disk to resolve the 06026?
Thanks for all replies.
--
Sincerely,
WoodyMcKay

[De DBA]

You say 2 days of backups - Do you run another script against this database during the week that also has a "delete obsolete" in it? A duplicate database or "refresh" script perhaps?

Cheers,
Tony

Post by Woody McKay
Hi Andrew,
This is a script I've inherited and won't be able to change till next spring - and I do appreciate any improvements. However, this script has been working fine in thousands of servers for several years. I'm thinking there must be something about this particular server.
Even though the "restore archivelog validate" is asking for the last 2 weeks, shouldn't it be able to run successfully even if there are only 2 days of backups?
Am I misunderstanding or missing something?
Thanks
I'm not sure I understand the problem. Everything seems to be working properly. You have a recovery window of 7 days and are asking for archive logs 14 days old, and they are gone as they should be. I don't actually see a problem here.
Sent from my iPad

Post by Woody McKay
Hi, ( note, cross posted in Oracle community Database Backup and Recovery )
I'm not super-versed with RMAN but am trying to resolve an rman issue on a development server. The DB environment can be rebuilt if needed, but I'd like to try and resolve this with a crosscheck command, etc.
run {
configure controlfile autobackup on;
configure controlfile autobackup format for device type disk to '%F';
configure retention policy to recovery window of 7 days;
allocate channel d1 type disk maxpiecesize=5G;
backup as compressed backupset incremental level 0 cumulative tag 'L0'database
plus archivelog delete all input;
restore database validate;
release channel d1;
delete noprompt obsolete;
restore database check logical validate;
backup validate database;
*restore archivelog from time 'SYSDATE-14' validate;*
host 'copy C:\oracle\product\12.1.0\dbhome_1\NETWORK\ADMIN\tnsnames.ora C:\oradata\fast_recovery_area\';
host 'copy C:\oracle\product\12.1.0\dbhome_1\NETWORK\ADMIN\sqlnet.ora C:\oradata\fast_recovery_area\';
host 'copy C:\oracle\product\12.1.0\dbhome_1\NETWORK\ADMIN\listener.ora C:\oradata\fast_recovery_area\';
host 'copy C:\oracle\product\12.1.0\dbhome_1\database\pwd*.ora C:\oradata\fast_recovery_area\';
}
list incarnation of database;
list backup summary;
list backup by file;
list recoverable backup of database;
report schema;
report need backup redundancy=3;
report need backup recovery window of 3 days;
RMAN> restore archivelog from time 'SYSDATE-14' validate;
Starting restore at 07-OCT-15
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 10/07/2015 15:15:49
RMAN-06026: some targets not found - aborting restore
RMAN-06025: no backup of archived log for thread 1 with sequence 38 and starting SCN of 4330735 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 37 and starting SCN of 4324802 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 36 and starting SCN of 4311903 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 35 and starting SCN of 4230358 found to restore
...
Note, that "RMAN> restore archivelog from time 'SYSDATE-1' validate;" does work successfully.
I did find and removed on obsolete backup set, but that didn't resolve the 06026 error.
I tried "crosscheck archivelog all;", but that does not resolve the 06026 error during the restore archivelog validate.
Is there a crosscheck command or other command that would sync the catalog and disk to resolve the 06026?
Thanks for all replies.
--
Sincerely,
WoodyMcKay

--
Sincerely,
WoodyMcKay

[Woody McKay]

Hi Tony,

This script is the weekly level 0 backup. There is also a weekday level 1
that runs during the week.

Just looked at the weekday level 1 and it does have a "delete noprompt
obsolete"

No kind of duplicate or refresh or restore. Just weekend full level 0 and
weekday incremental level 1.

Post by De DBA
You say 2 days of backups - Do you run another script against this
database during the week that also has a "delete obsolete" in it? A
duplicate database or "refresh" script perhaps?
Cheers,
Tony
Hi Andrew,
This is a script I've inherited and won't be able to change till next
spring - and I do appreciate any improvements. However, this script has
been working fine in thousands of servers for several years. I'm thinking
there must be something about this particular server.
Even though the "restore archivelog validate" is asking for the last 2
weeks, shouldn't it be able to run successfully even if there are only 2
days of backups?
Am I misunderstanding or missing something?
Thanks

Post by Andrew Kerber
I'm not sure I understand the problem. Everything seems to be working
properly. You have a recovery window of 7 days and are asking for archive
logs 14 days old, and they are gone as they should be. I don't actually see
a problem here.
Sent from my iPad
Hi, ( note, cross posted in Oracle community Database Backup and Recovery )
I'm not super-versed with RMAN but am trying to resolve an rman issue on
a development server. The DB environment can be rebuilt if needed, but I'd
like to try and resolve this with a crosscheck command, etc.
run {
configure controlfile autobackup on;
configure controlfile autobackup format for device type disk to '%F';
configure retention policy to recovery window of 7 days;
allocate channel d1 type disk maxpiecesize=5G;
backup as compressed backupset incremental level 0 cumulative tag 'L0'database
plus archivelog delete all input;
restore database validate;
release channel d1;
delete noprompt obsolete;
restore database check logical validate;
backup validate database;
*restore archivelog from time 'SYSDATE-14' validate;*
host 'copy C:\oracle\product\12.1.0\dbhome_1\NETWORK\ADMIN\tnsnames.ora
C:\oradata\fast_recovery_area\';
host 'copy C:\oracle\product\12.1.0\dbhome_1\NETWORK\ADMIN\sqlnet.ora
C:\oradata\fast_recovery_area\';
host 'copy C:\oracle\product\12.1.0\dbhome_1\NETWORK\ADMIN\listener.ora
C:\oradata\fast_recovery_area\';
host 'copy C:\oracle\product\12.1.0\dbhome_1\database\pwd*.ora
C:\oradata\fast_recovery_area\';
}
list incarnation of database;
list backup summary;
list backup by file;
list recoverable backup of database;
report schema;
report need backup redundancy=3;
report need backup recovery window of 3 days;
The command "restore archivelog from time 'SYSDATE-14' validate;" is
RMAN> restore archivelog from time 'SYSDATE-14' validate;
Starting restore at 07-OCT-15
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 10/07/2015 15:15:49
RMAN-06026: some targets not found - aborting restore
RMAN-06025: no backup of archived log for thread 1 with sequence 38 and
starting SCN of 4330735 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 37 and
starting SCN of 4324802 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 36 and
starting SCN of 4311903 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 35 and
starting SCN of 4230358 found to restore
...
Note, that "RMAN> restore archivelog from time 'SYSDATE-1' validate;"
does work successfully.
I did find and removed on obsolete backup set, but that didn't resolve the 06026 error.
I tried "crosscheck archivelog all;", but that does not resolve the 06026
error during the restore archivelog validate.
Is there a crosscheck command or other command that would sync the
catalog and disk to resolve the 06026?
Thanks for all replies.
--
Sincerely,
WoodyMcKay

--
Sincerely,
WoodyMcKay

[De DBA]

Right. That means that you will be able to restore archived logs only up to the last level 1 taken before the weekly script ran previously.

Cheers,
Tony

Post by Woody McKay
Hi Tony,
This script is the weekly level 0 backup. There is also a weekday level 1 that runs during the week.
Just looked at the weekday level 1 and it does have a "delete noprompt obsolete"
No kind of duplicate or refresh or restore. Just weekend full level 0 and weekday incremental level 1.
You say 2 days of backups - Do you run another script against this database during the week that also has a "delete obsolete" in it? A duplicate database or "refresh" script perhaps?
Cheers,
Tony

Post by Woody McKay
Hi Andrew,
This is a script I've inherited and won't be able to change till next spring - and I do appreciate any improvements. However, this script has been working fine in thousands of servers for several years. I'm thinking there must be something about this particular server.
Even though the "restore archivelog validate" is asking for the last 2 weeks, shouldn't it be able to run successfully even if there are only 2 days of backups?
Am I misunderstanding or missing something?
Thanks
I'm not sure I understand the problem. Everything seems to be working properly. You have a recovery window of 7 days and are asking for archive logs 14 days old, and they are gone as they should be. I don't actually see a problem here.
Sent from my iPad

Post by Woody McKay
Hi, ( note, cross posted in Oracle community Database Backup and Recovery )
I'm not super-versed with RMAN but am trying to resolve an rman issue on a development server. The DB environment can be rebuilt if needed, but I'd like to try and resolve this with a crosscheck command, etc.
run {
configure controlfile autobackup on;
configure controlfile autobackup format for device type disk to '%F';
configure retention policy to recovery window of 7 days;
allocate channel d1 type disk maxpiecesize=5G;
backup as compressed backupset incremental level 0 cumulative tag 'L0'database
plus archivelog delete all input;
restore database validate;
release channel d1;
delete noprompt obsolete;
restore database check logical validate;
backup validate database;
*restore archivelog from time 'SYSDATE-14' validate;*
host 'copy C:\oracle\product\12.1.0\dbhome_1\NETWORK\ADMIN\tnsnames.ora C:\oradata\fast_recovery_area\';
host 'copy C:\oracle\product\12.1.0\dbhome_1\NETWORK\ADMIN\sqlnet.ora C:\oradata\fast_recovery_area\';
host 'copy C:\oracle\product\12.1.0\dbhome_1\NETWORK\ADMIN\listener.ora C:\oradata\fast_recovery_area\';
host 'copy C:\oracle\product\12.1.0\dbhome_1\database\pwd*.ora C:\oradata\fast_recovery_area\';
}
list incarnation of database;
list backup summary;
list backup by file;
list recoverable backup of database;
report schema;
report need backup redundancy=3;
report need backup recovery window of 3 days;
RMAN> restore archivelog from time 'SYSDATE-14' validate;
Starting restore at 07-OCT-15
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 10/07/2015 15:15:49
RMAN-06026: some targets not found - aborting restore
RMAN-06025: no backup of archived log for thread 1 with sequence 38 and starting SCN of 4330735 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 37 and starting SCN of 4324802 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 36 and starting SCN of 4311903 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 35 and starting SCN of 4230358 found to restore
...
Note, that "RMAN> restore archivelog from time 'SYSDATE-1' validate;" does work successfully.
I did find and removed on obsolete backup set, but that didn't resolve the 06026 error.
I tried "crosscheck archivelog all;", but that does not resolve the 06026 error during the restore archivelog validate.
Is there a crosscheck command or other command that would sync the catalog and disk to resolve the 06026?
Thanks for all replies.
--
Sincerely,
WoodyMcKay

--
Sincerely,
WoodyMcKay

--
Sincerely,
WoodyMcKay

[Chitale, Hemant K]

Oracle may retain archivelogs older than the retention window – it does a purge only if the FRA is running out of space.
That can explain why some servers have older archivelogs – simply their FRAs are larger relative to the sizes of the backups and archivelogs.


You should be running a “CROSSCHECK BACKUP OF ARCHIVELOG ALL” {not “crosscheck archivelog all”} because you want to mark Expired the *backups* of archivelogs that are not available to restore from.
Once you do a CROSSCHECK and find that some backups are marked EXPIRED, you might want to DELETE EXPIRED BACKUP OF ARCHIVELOG ALL



Hemant K Chitale


From: oracle-l-***@freelists.org [mailto:oracle-l-***@freelists.org] On Behalf Of Woody McKay
Sent: Thursday, October 08, 2015 7:56 AM
To: Andrew Kerber
Cc: ORACLE-L
Subject: Re: restore archivelog all validate; gives RMAN-06025

Hi Andrew,

This is a script I've inherited and won't be able to change till next spring - and I do appreciate any improvements. However, this script has been working fine in thousands of servers for several years. I'm thinking there must be something about this particular server.

Even though the "restore archivelog validate" is asking for the last 2 weeks, shouldn't it be able to run successfully even if there are only 2 days of backups?

Am I misunderstanding or missing something?

Thanks




On Wed, Oct 7, 2015 at 7:43 PM, Andrew Kerber <***@gmail.com<mailto:***@gmail.com>> wrote:
I'm not sure I understand the problem. Everything seems to be working properly. You have a recovery window of 7 days and are asking for archive logs 14 days old, and they are gone as they should be. I don't actually see a problem here.

Sent from my iPad

On Oct 7, 2015, at 6:27 PM, Woody McKay <***@gmail.com<mailto:***@gmail.com>> wrote:

Hi, ( note, cross posted in Oracle community Database Backup and Recovery )



I'm not super-versed with RMAN but am trying to resolve an rman issue on a development server. The DB environment can be rebuilt if needed, but I'd like to try and resolve this with a crosscheck command, etc.



The weekly rman backup script looks like:

run {

configure controlfile autobackup on;

configure controlfile autobackup format for device type disk to '%F';

configure retention policy to recovery window of 7 days;

allocate channel d1 type disk maxpiecesize=5G;

backup as compressed backupset incremental level 0 cumulative tag 'L0'database

plus archivelog delete all input;

restore database validate;

release channel d1;

delete noprompt obsolete;

restore database check logical validate;

backup validate database;

restore archivelog from time 'SYSDATE-14' validate;

host 'copy C:\oracle\product\12.1.0\dbhome_1\NETWORK\ADMIN\tnsnames.ora C:\oradata\fast_recovery_area\';

host 'copy C:\oracle\product\12.1.0\dbhome_1\NETWORK\ADMIN\sqlnet.ora C:\oradata\fast_recovery_area\';

host 'copy C:\oracle\product\12.1.0\dbhome_1\NETWORK\ADMIN\listener.ora C:\oradata\fast_recovery_area\';

host 'copy C:\oracle\product\12.1.0\dbhome_1\database\pwd*.ora C:\oradata\fast_recovery_area\';

}

list incarnation of database;

list backup summary;

list backup by file;

list recoverable backup of database;

report schema;

report need backup redundancy=3;

report need backup recovery window of 3 days;



The command "restore archivelog from time 'SYSDATE-14' validate;" is throwing the below error:



RMAN> restore archivelog from time 'SYSDATE-14' validate;

Starting restore at 07-OCT-15

using channel ORA_DISK_1

RMAN-00571: ===========================================================

RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

RMAN-00571: ===========================================================

RMAN-03002: failure of restore command at 10/07/2015 15:15:49

RMAN-06026: some targets not found - aborting restore

RMAN-06025: no backup of archived log for thread 1 with sequence 38 and starting SCN of 4330735 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 37 and starting SCN of 4324802 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 36 and starting SCN of 4311903 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 35 and starting SCN of 4230358 found to restore

...



Note, that "RMAN> restore archivelog from time 'SYSDATE-1' validate;" does work successfully.



I did find and removed on obsolete backup set, but that didn't resolve the 06026 error.



I tried "crosscheck archivelog all;", but that does not resolve the 06026 error during the restore archivelog validate.



Is there a crosscheck command or other command that would sync the catalog and disk to resolve the 06026?



Thanks for all replies.

--
Sincerely,

WoodyMcKay



--
Sincerely,

WoodyMcKay

This email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please delete all copies and notify the sender immediately. You may wish to refer to the incorporation details of Standard Chartered PLC, Standard Chartered Bank and their subsidiaries at https://www.sc.com/en/incorporation-details.html

[Woody McKay]

Thanks Hemant - I'll give it a go.

Post by Chitale, Hemant K
Oracle may retain archivelogs older than the retention window – it does a
purge only if the FRA is running out of space.
That can explain why some servers have older archivelogs – simply their
FRAs are larger relative to the sizes of the backups and archivelogs.
You should be running a “CROSSCHECK BACKUP OF ARCHIVELOG ALL” {not
“crosscheck archivelog all”} because you want to mark Expired the *
*backups** of archivelogs that are not available to restore from.
Once you do a CROSSCHECK and find that some backups are marked EXPIRED,
you might want to DELETE EXPIRED BACKUP OF ARCHIVELOG ALL
Hemant K Chitale
*Sent:* Thursday, October 08, 2015 7:56 AM
*To:* Andrew Kerber
*Cc:* ORACLE-L
*Subject:* Re: restore archivelog all validate; gives RMAN-06025
Hi Andrew,
This is a script I've inherited and won't be able to change till next
spring - and I do appreciate any improvements. However, this script has
been working fine in thousands of servers for several years. I'm thinking
there must be something about this particular server.
Even though the "restore archivelog validate" is asking for the last 2
weeks, shouldn't it be able to run successfully even if there are only 2
days of backups?
Am I misunderstanding or missing something?
Thanks
I'm not sure I understand the problem. Everything seems to be working
properly. You have a recovery window of 7 days and are asking for archive
logs 14 days old, and they are gone as they should be. I don't actually see
a problem here.
Sent from my iPad
Hi, ( note, cross posted in Oracle community Database Backup and Recovery )
I'm not super-versed with RMAN but am trying to resolve an rman issue on a
development server. The DB environment can be rebuilt if needed, but I'd
like to try and resolve this with a crosscheck command, etc.
run {
configure controlfile autobackup on;
configure controlfile autobackup format for device type disk to '%F';
configure retention policy to recovery window of 7 days;
allocate channel d1 type disk maxpiecesize=5G;
backup as compressed backupset incremental level 0 cumulative tag 'L0'database
plus archivelog delete all input;
restore database validate;
release channel d1;
delete noprompt obsolete;
restore database check logical validate;
backup validate database;
*restore archivelog from time 'SYSDATE-14' validate;*
host 'copy C:\oracle\product\12.1.0\dbhome_1\NETWORK\ADMIN\tnsnames.ora
C:\oradata\fast_recovery_area\';
host 'copy C:\oracle\product\12.1.0\dbhome_1\NETWORK\ADMIN\sqlnet.ora
C:\oradata\fast_recovery_area\';
host 'copy C:\oracle\product\12.1.0\dbhome_1\NETWORK\ADMIN\listener.ora
C:\oradata\fast_recovery_area\';
host 'copy C:\oracle\product\12.1.0\dbhome_1\database\pwd*.ora
C:\oradata\fast_recovery_area\';
}
list incarnation of database;
list backup summary;
list backup by file;
list recoverable backup of database;
report schema;
report need backup redundancy=3;
report need backup recovery window of 3 days;
The command "restore archivelog from time 'SYSDATE-14' validate;" is
RMAN> restore archivelog from time 'SYSDATE-14' validate;
Starting restore at 07-OCT-15
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 10/07/2015 15:15:49
RMAN-06026: some targets not found - aborting restore
RMAN-06025: no backup of archived log for thread 1 with sequence 38 and
starting SCN of 4330735 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 37 and
starting SCN of 4324802 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 36 and
starting SCN of 4311903 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 35 and
starting SCN of 4230358 found to restore
...
Note, that "RMAN> restore archivelog from time 'SYSDATE-1' validate;" does
work successfully.
I did find and removed on obsolete backup set, but that didn't resolve the 06026 error.
I tried "crosscheck archivelog all;", but that does not resolve the 06026
error during the restore archivelog validate.
Is there a crosscheck command or other command that would sync the catalog
and disk to resolve the 06026?
Thanks for all replies.
--
Sincerely,
WoodyMcKay
--
Sincerely,
WoodyMcKay
This email and any attachments are confidential and may also be
privileged. If you are not the intended recipient, please delete all copies
and notify the sender immediately. You may wish to refer to the
incorporation details of Standard Chartered PLC, Standard Chartered Bank
and their subsidiaries at https://www.sc.com/en/incorporation-details.html

[De DBA]

First thing that strikes me is that you configure a recovery period of 7 days, then backup and delete obsolete, then hope to restore archived logs from 14 days back. RMAN retains only as many backups as necessary to restore the *database* to up to 7 days ago, and in your script you create a new level 0 backup. The backups of more than 14 days ago will have been deleted, as you run this weekly, so the oldest archived logs in a 14 * 24 hour period could be gone - it looks a bit like a race condition really.

...
configure retention policy to recovery window of *7 days*;

...

*backup* as compressed backupset incremental *level 0* cumulative tag 'L0'database

plus archivelog delete all input;

...

delete noprompt *obsolete*;

...*
restore archivelog from time 'SYSDATE-14' validate;

*


Did you try to restore archived logs of less than 14 days ago, e.g. 13.5?

Cheers,
Tony

Post by Woody McKay
Hi, ( note, cross posted in Oracle community Database Backup and Recovery )
I'm not super-versed with RMAN but am trying to resolve an rman issue on a development server. The DB environment can be rebuilt if needed, but I'd like to try and resolve this with a crosscheck command, etc.
run {
configure controlfile autobackup on;
configure controlfile autobackup format for device type disk to '%F';
configure retention policy to recovery window of 7 days;
allocate channel d1 type disk maxpiecesize=5G;
backup as compressed backupset incremental level 0 cumulative tag 'L0'database
plus archivelog delete all input;
restore database validate;
release channel d1;
delete noprompt obsolete;
restore database check logical validate;
backup validate database;
*restore archivelog from time 'SYSDATE-14' validate;*
host 'copy C:\oracle\product\12.1.0\dbhome_1\NETWORK\ADMIN\tnsnames.ora C:\oradata\fast_recovery_area\';
host 'copy C:\oracle\product\12.1.0\dbhome_1\NETWORK\ADMIN\sqlnet.ora C:\oradata\fast_recovery_area\';
host 'copy C:\oracle\product\12.1.0\dbhome_1\NETWORK\ADMIN\listener.ora C:\oradata\fast_recovery_area\';
host 'copy C:\oracle\product\12.1.0\dbhome_1\database\pwd*.ora C:\oradata\fast_recovery_area\';
}
list incarnation of database;
list backup summary;
list backup by file;
list recoverable backup of database;
report schema;
report need backup redundancy=3;
report need backup recovery window of 3 days;
RMAN> restore archivelog from time 'SYSDATE-14' validate;
Starting restore at 07-OCT-15
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 10/07/2015 15:15:49
RMAN-06026: some targets not found - aborting restore
RMAN-06025: no backup of archived log for thread 1 with sequence 38 and starting SCN of 4330735 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 37 and starting SCN of 4324802 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 36 and starting SCN of 4311903 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 35 and starting SCN of 4230358 found to restore
...
Note, that "RMAN> restore archivelog from time 'SYSDATE-1' validate;" does work successfully.
I did find and removed on obsolete backup set, but that didn't resolve the 06026 error.
I tried "crosscheck archivelog all;", but that does not resolve the 06026 error during the restore archivelog validate.
Is there a crosscheck command or other command that would sync the catalog and disk to resolve the 06026?
Thanks for all replies.
--
Sincerely,
WoodyMcKay

[Woody McKay]

Thanks Tony. You've mentioned the same as Andrew. I'll for sure create a
ticket to get that changed for the next release.

This is a development server and there is nothing for restoring archived
logs. I thought the restore archive validate was just to validate that the
backed up archived logs were good?

I'd like to just somehow tell the rman catalog that the archive logs are
gone (seq 1-38) and start with the next backup. I was thinking that "crosscheck
archivelog all" would sync the catalog, but it did not.

Is there another crosscheck command?

Post by De DBA
First thing that strikes me is that you configure a recovery period of 7
days, then backup and delete obsolete, then hope to restore archived logs
from 14 days back. RMAN retains only as many backups as necessary to
restore the *database* to up to 7 days ago, and in your script you create
a new level 0 backup. The backups of more than 14 days ago will have been
deleted, as you run this weekly, so the oldest archived logs in a 14 * 24
hour period could be gone - it looks a bit like a race condition really.
...
configure retention policy to recovery window of *7 days*;
...
*backup* as compressed backupset incremental *level 0* cumulative tag 'L0'database
plus archivelog delete all input;
...
delete noprompt *obsolete*;
...
* restore archivelog from time 'SYSDATE-14' validate; *
Did you try to restore archived logs of less than 14 days ago, e.g. 13.5?
Cheers,
Tony
Hi, ( note, cross posted in Oracle community Database Backup and Recovery )
I'm not super-versed with RMAN but am trying to resolve an rman issue on a
development server. The DB environment can be rebuilt if needed, but I'd
like to try and resolve this with a crosscheck command, etc.
run {
configure controlfile autobackup on;
configure controlfile autobackup format for device type disk to '%F';
configure retention policy to recovery window of 7 days;
allocate channel d1 type disk maxpiecesize=5G;
backup as compressed backupset incremental level 0 cumulative tag 'L0'database
plus archivelog delete all input;
restore database validate;
release channel d1;
delete noprompt obsolete;
restore database check logical validate;
backup validate database;
*restore archivelog from time 'SYSDATE-14' validate;*
host 'copy C:\oracle\product\12.1.0\dbhome_1\NETWORK\ADMIN\tnsnames.ora
C:\oradata\fast_recovery_area\';
host 'copy C:\oracle\product\12.1.0\dbhome_1\NETWORK\ADMIN\sqlnet.ora
C:\oradata\fast_recovery_area\';
host 'copy C:\oracle\product\12.1.0\dbhome_1\NETWORK\ADMIN\listener.ora
C:\oradata\fast_recovery_area\';
host 'copy C:\oracle\product\12.1.0\dbhome_1\database\pwd*.ora
C:\oradata\fast_recovery_area\';
}
list incarnation of database;
list backup summary;
list backup by file;
list recoverable backup of database;
report schema;
report need backup redundancy=3;
report need backup recovery window of 3 days;
The command "restore archivelog from time 'SYSDATE-14' validate;" is
RMAN> restore archivelog from time 'SYSDATE-14' validate;
Starting restore at 07-OCT-15
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 10/07/2015 15:15:49
RMAN-06026: some targets not found - aborting restore
RMAN-06025: no backup of archived log for thread 1 with sequence 38 and
starting SCN of 4330735 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 37 and
starting SCN of 4324802 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 36 and
starting SCN of 4311903 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 35 and
starting SCN of 4230358 found to restore
...
Note, that "RMAN> restore archivelog from time 'SYSDATE-1' validate;" does
work successfully.
I did find and removed on obsolete backup set, but that didn't resolve the 06026 error.
I tried "crosscheck archivelog all;", but that does not resolve the 06026
error during the restore archivelog validate.
Is there a crosscheck command or other command that would sync the catalog
and disk to resolve the 06026?
Thanks for all replies.
--
Sincerely,
WoodyMcKay

[De DBA]

Hi Woody,

"Crosscheck archivelog all" does sync the catalog. You will probably see that they are deleted when you do a list. RMAN is asking for them, because you are specifically asking them to be restored. By the way, 1-38 are really low sequence numbers for archived logs. Is this a new database, or is it recreated often?

I'd suggest that you in the meantime try to manually restore the archived logs with decreasing periods. At least you should be able to sucessfully

restore archivelog from time 'sysdate - 6';


Cheers,
Tony

Thanks Tony. You've mentioned the same as Andrew. I'll for sure create a ticket to get that changed for the next release.
This is a development server and there is nothing for restoring archived logs. I thought the restore archive validate was just to validate that the backed up archived logs were good?
I'd like to just somehow tell the rman catalog that the archive logs are gone (seq 1-38) and start with the next backup. I was thinking that "crosscheck archivelog all" would sync the catalog, but it did not.
Is there another crosscheck command?
First thing that strikes me is that you configure a recovery period of 7 days, then backup and delete obsolete, then hope to restore archived logs from 14 days back. RMAN retains only as many backups as necessary to restore the *database* to up to 7 days ago, and in your script you create a new level 0 backup. The backups of more than 14 days ago will have been deleted, as you run this weekly, so the oldest archived logs in a 14 * 24 hour period could be gone - it looks a bit like a race condition really.
...
configure retention policy to recovery window of *7 days*;
...
*backup* as compressed backupset incremental *level 0* cumulative tag 'L0'database
plus archivelog delete all input;
...
delete noprompt *obsolete*;
...*
restore archivelog from time 'SYSDATE-14' validate;
*
Did you try to restore archived logs of less than 14 days ago, e.g. 13.5?
Cheers,
Tony

Post by Woody McKay
Hi, ( note, cross posted in Oracle community Database Backup and Recovery )
I'm not super-versed with RMAN but am trying to resolve an rman issue on a development server. The DB environment can be rebuilt if needed, but I'd like to try and resolve this with a crosscheck command, etc.
run {
configure controlfile autobackup on;
configure controlfile autobackup format for device type disk to '%F';
configure retention policy to recovery window of 7 days;
allocate channel d1 type disk maxpiecesize=5G;
backup as compressed backupset incremental level 0 cumulative tag 'L0'database
plus archivelog delete all input;
restore database validate;
release channel d1;
delete noprompt obsolete;
restore database check logical validate;
backup validate database;
*restore archivelog from time 'SYSDATE-14' validate;*
host 'copy C:\oracle\product\12.1.0\dbhome_1\NETWORK\ADMIN\tnsnames.ora C:\oradata\fast_recovery_area\';
host 'copy C:\oracle\product\12.1.0\dbhome_1\NETWORK\ADMIN\sqlnet.ora C:\oradata\fast_recovery_area\';
host 'copy C:\oracle\product\12.1.0\dbhome_1\NETWORK\ADMIN\listener.ora C:\oradata\fast_recovery_area\';
host 'copy C:\oracle\product\12.1.0\dbhome_1\database\pwd*.ora C:\oradata\fast_recovery_area\';
}
list incarnation of database;
list backup summary;
list backup by file;
list recoverable backup of database;
report schema;
report need backup redundancy=3;
report need backup recovery window of 3 days;
RMAN> restore archivelog from time 'SYSDATE-14' validate;
Starting restore at 07-OCT-15
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 10/07/2015 15:15:49
RMAN-06026: some targets not found - aborting restore
RMAN-06025: no backup of archived log for thread 1 with sequence 38 and starting SCN of 4330735 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 37 and starting SCN of 4324802 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 36 and starting SCN of 4311903 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 35 and starting SCN of 4230358 found to restore
...
Note, that "RMAN> restore archivelog from time 'SYSDATE-1' validate;" does work successfully.
I did find and removed on obsolete backup set, but that didn't resolve the 06026 error.
I tried "crosscheck archivelog all;", but that does not resolve the 06026 error during the restore archivelog validate.
Is there a crosscheck command or other command that would sync the catalog and disk to resolve the 06026?
Thanks for all replies.
--
Sincerely,
WoodyMcKay

--
Sincerely,
WoodyMcKay

[Woody McKay]

Thanks Tony. Yes, this is a development test server where they use our DB
installer often to recreate the DB for the next round of testing. So,
that's why you see 1-38.

The real purpose of "*restore archivelog from time 'SYSDATE-14' validate;*"
is just for a validation step. Ahhh, I see what you are saying though.
They are not there and the catalog is sync'ed, but the script is
specifically telling it to restore/validate 14 days worth? Hence, the
error?

Post by De DBA
Hi Woody,
"Crosscheck archivelog all" does sync the catalog. You will probably see
that they are deleted when you do a list. RMAN is asking for them, because
you are specifically asking them to be restored. By the way, 1-38 are
really low sequence numbers for archived logs. Is this a new database, or
is it recreated often?
I'd suggest that you in the meantime try to manually restore the archived
logs with decreasing periods. At least you should be able to sucessfully
restore archivelog from time 'sysdate - 6';
Cheers,
Tony
Thanks Tony. You've mentioned the same as Andrew. I'll for sure create a
ticket to get that changed for the next release.
This is a development server and there is nothing for restoring archived
logs. I thought the restore archive validate was just to validate that the
backed up archived logs were good?
I'd like to just somehow tell the rman catalog that the archive logs are
gone (seq 1-38) and start with the next backup. I was thinking that "crosscheck
archivelog all" would sync the catalog, but it did not.
Is there another crosscheck command?

Post by De DBA
First thing that strikes me is that you configure a recovery period of 7
days, then backup and delete obsolete, then hope to restore archived logs
from 14 days back. RMAN retains only as many backups as necessary to
restore the *database* to up to 7 days ago, and in your script you
create a new level 0 backup. The backups of more than 14 days ago will have
been deleted, as you run this weekly, so the oldest archived logs in a 14 *
24 hour period could be gone - it looks a bit like a race condition really.
...
configure retention policy to recovery window of *7 days*;
...
*backup* as compressed backupset incremental *level 0* cumulative tag 'L0'database
plus archivelog delete all input;
...
delete noprompt *obsolete*;
...
* restore archivelog from time 'SYSDATE-14' validate; *
Did you try to restore archived logs of less than 14 days ago, e.g. 13.5?
Cheers,
Tony
Hi, ( note, cross posted in Oracle community Database Backup and Recovery )
I'm not super-versed with RMAN but am trying to resolve an rman issue on
a development server. The DB environment can be rebuilt if needed, but I'd
like to try and resolve this with a crosscheck command, etc.
run {
configure controlfile autobackup on;
configure controlfile autobackup format for device type disk to '%F';
configure retention policy to recovery window of 7 days;
allocate channel d1 type disk maxpiecesize=5G;
backup as compressed backupset incremental level 0 cumulative tag 'L0'database
plus archivelog delete all input;
restore database validate;
release channel d1;
delete noprompt obsolete;
restore database check logical validate;
backup validate database;
*restore archivelog from time 'SYSDATE-14' validate;*
host 'copy C:\oracle\product\12.1.0\dbhome_1\NETWORK\ADMIN\tnsnames.ora
C:\oradata\fast_recovery_area\';
host 'copy C:\oracle\product\12.1.0\dbhome_1\NETWORK\ADMIN\sqlnet.ora
C:\oradata\fast_recovery_area\';
host 'copy C:\oracle\product\12.1.0\dbhome_1\NETWORK\ADMIN\listener.ora
C:\oradata\fast_recovery_area\';
host 'copy C:\oracle\product\12.1.0\dbhome_1\database\pwd*.ora
C:\oradata\fast_recovery_area\';
}
list incarnation of database;
list backup summary;
list backup by file;
list recoverable backup of database;
report schema;
report need backup redundancy=3;
report need backup recovery window of 3 days;
The command "restore archivelog from time 'SYSDATE-14' validate;" is
RMAN> restore archivelog from time 'SYSDATE-14' validate;
Starting restore at 07-OCT-15
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 10/07/2015 15:15:49
RMAN-06026: some targets not found - aborting restore
RMAN-06025: no backup of archived log for thread 1 with sequence 38 and
starting SCN of 4330735 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 37 and
starting SCN of 4324802 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 36 and
starting SCN of 4311903 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 35 and
starting SCN of 4230358 found to restore
...
Note, that "RMAN> restore archivelog from time 'SYSDATE-1' validate;"
does work successfully.
I did find and removed on obsolete backup set, but that didn't resolve the 06026 error.
I tried "crosscheck archivelog all;", but that does not resolve the 06026
error during the restore archivelog validate.
Is there a crosscheck command or other command that would sync the
catalog and disk to resolve the 06026?
Thanks for all replies.
--
Sincerely,
WoodyMcKay

--
Sincerely,
WoodyMcKay