Welcome Guest ( Log In | Register )


 
 
 
 
 
 

 
 
Oracle 

Performance Tuning Reference poster
 
Oracle training in Linux 

commands
 
Oracle training Weblogic Book
 
Easy Oracle Jumpstart
 
Oracle training & performance tuning books
 
Burleson Consulting Remote DB Administration
 
 
 
Reply to this topicStart new topic
> Specification does not match any backup in the repository -- need help to resolve
Susja
post Mar 20 2017, 08:20 PM
Post #1


Member
**

Group: Members
Posts: 13
Joined: 20-March 17
Member No.: 51,849



Hello,
We have established process to delete files from FRA for a while but recently it stopped to delete 'expired', 'obsolete' files. The issue started January 1st. Retention policy is 10 days. I noticed that we have files from December 21 2016. They were not deleted while it should be only for the last 10 days.
This is the script that runs every day. I ran it manually and here's the output:
RMAN> run {
2> crosscheck archivelog all;
3> delete expired archivelog all;
4> delete expired backup;
5> delete obsolete;
6> }
7> EXIT
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
......
\2017_03_17\O1_MF_1_2517_DDR25H66_.ARC RECID=5071 STAMP=938865776
Crosschecked 613 objects


released channel: ORA_DISK_1
released channel: ORA_DISK_2
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=201 device type=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: SID=16 device type=DISK
specification does not match any archived log in the repository

using channel ORA_DISK_1
using channel ORA_DISK_2
specification does not match any backup in the repository

RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 10 days
using channel ORA_DISK_1
using channel ORA_DISK_2
no obsolete backups found

Recovery Manager complete.
***
Today I ran it manually again but get another output:
using channel ORA_DISK_2
specification does not match any backup in the repository

RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 10 days
using channel ORA_DISK_1
using channel ORA_DISK_2
Deleting the following obsolete backups and copies:
Type Key Completion Time Filename/Handle
-------------------- ------ ------------------ --------------------
Backup Set 7263 10-MAR-17
Backup Piece 7263 10-MAR-17 C:\BACKUPS\ORACLE\C-1707466105-20170310-03
Backup Set 7266 10-MAR-17
Backup Piece 7266 10-MAR-17 C:\BACKUPS\ORACLE\C-1707466105-20170310-04
Backup Set 7267 10-MAR-17
Backup Piece 7267 10-MAR-17 C:\BACKUPS\ORACLE\C-1707466105-20170310-05
deleted backup piece
backup piece handle=C:\BACKUPS\ORACLE\C-1707466105-20170310-03 RECID=7263 STAMP=938239310
deleted backup piece
backup piece handle=C:\BACKUPS\ORACLE\C-1707466105-20170310-04 RECID=7266 STAMP=938260910
deleted backup piece
backup piece handle=C:\BACKUPS\ORACLE\C-1707466105-20170310-05 RECID=7267 STAMP=938260944
Deleted 3 objects


Recovery Manager complete.

C:\BAT>
**
It sounds to me that for some reason it stopped to recognize 'expired' file and does not delete it anymore.
Could you please help me to troubleshoot and fix the issue?
Thanks
Go to the top of the page
 
+Quote Post
burleson
post Mar 21 2017, 01:46 PM
Post #2


Advanced Member
***

Group: Members
Posts: 13,409
Joined: 26-January 04
Member No.: 13



Hi Sysja, and welcome to the forum!

>> The issue started January 1st.

Since you know that is related to the date, I would focus on this issue:

This related thread may help:

http://dbaforums.org/oracle/index.php?showtopic=16916




--------------------
Hope this helps. . .

Donald K. Burleson
Oracle Press author
Author of Oracle Tuning: The Definitive Reference
Go to the top of the page
 
+Quote Post
Susja
post Mar 21 2017, 02:11 PM
Post #3


Member
**

Group: Members
Posts: 13
Joined: 20-March 17
Member No.: 51,849



QUOTE (burleson @ Mar 21 2017, 02:46 PM) *
Hi Sysja, and welcome to the forum!

>> The issue started January 1st.

Since you know that is related to the date, I would focus on this issue:

This related thread may help:

http://dbaforums.org/oracle/index.php?showtopic=16916

Thanks so much. I just browsed it and it looks very valuable. I'll read more carefully later.
I'm just confused why you mentioned/pointed to January 1st. Does it have some relation to particular timestamp?
Sorry for that,
Thanks
Go to the top of the page
 
+Quote Post
burleson
post Mar 21 2017, 04:01 PM
Post #4


Advanced Member
***

Group: Members
Posts: 13,409
Joined: 26-January 04
Member No.: 13



Hi,

>> Does it have some relation to particular timestamp?

From what you said, that date change event precipitated the problem!




--------------------
Hope this helps. . .

Donald K. Burleson
Oracle Press author
Author of Oracle Tuning: The Definitive Reference
Go to the top of the page
 
+Quote Post
Susja
post Mar 24 2017, 10:33 AM
Post #5


Member
**

Group: Members
Posts: 13
Joined: 20-March 17
Member No.: 51,849



QUOTE (burleson @ Mar 21 2017, 05:01 PM) *
Hi,

>> Does it have some relation to particular timestamp?

From what you said, that date change event precipitated the problem!

Hi,
I tried all steps described in topic you pointed me http://dbaforums.org/oracle/index.php?showtopic=16916 but it did not have any effect.
Then I ran these sets of commands:
list backup summary
o Run “crosscheck backup;”
o Run “crosscheck archivelog all;”
o Run “crosscheck backupset;”
o Run “delete noprompt expired backup;”
o Run “delete noprompt expired backupset;”
o Run “delete noprompt expired archivelog all;
• Run “list backup summary’” again and see that nothing has changed
o Run “delete noprompt backupset <12345> <12346;”>
o Run “list backup summary” again and see that nothing has changed
Finally ran this: delete force noprompt backupset 12345 12346;” but again nothing has changed.
Note: From the thread you pointed me I did all steps except this one: (my management did not recommend me to do it)
3. If your database is flashback enabled, then just for a moment, disable this.
SQL> shutdown immediate;
SQL> startup mount;
SQL> alter flashback off;
SQL> alter flashback on;
SQL> alter database open;
Any other suggestions? It sounds to me that those files for some reason do not have 'attributes' for deletion.
Thanks
Go to the top of the page
 
+Quote Post
Susja
post Apr 3 2017, 12:05 PM
Post #6


Member
**

Group: Members
Posts: 13
Joined: 20-March 17
Member No.: 51,849



QUOTE (Susja @ Mar 24 2017, 11:33 AM) *
Hi,
I tried all steps described in topic you pointed me http://dbaforums.org/oracle/index.php?showtopic=16916 but it did not have any effect.
Then I ran these sets of commands:
list backup summary
o Run “crosscheck backup;”
o Run “crosscheck archivelog all;”
o Run “crosscheck backupset;”
o Run “delete noprompt expired backup;”
o Run “delete noprompt expired backupset;”
o Run “delete noprompt expired archivelog all;
• Run “list backup summary’” again and see that nothing has changed
o Run “delete noprompt backupset <12345> <12346;”>
o Run “list backup summary” again and see that nothing has changed
Finally ran this: delete force noprompt backupset 12345 12346;” but again nothing has changed.
Note: From the thread you pointed me I did all steps except this one: (my management did not recommend me to do it)
3. If your database is flashback enabled, then just for a moment, disable this.
SQL> shutdown immediate;
SQL> startup mount;
SQL> alter flashback off;
SQL> alter flashback on;
SQL> alter database open;
Any other suggestions? It sounds to me that those files for some reason do not have 'attributes' for deletion.
Thanks


Well eventually I was able to delete all backup and arhievelog files using these commands:
delete noprompt backupset <12345>, <12346>;
BUT the problem still is there. I mean files that should be deleted as 'expired' or 'obsolete' or etc do not have attribute 'expired' hence not get deleted.
My retention policy is 10 days but none of the files older that 10 days are marked 'expired'.
Any clue what this could be and how to troubleshoot it?
Thanks
Go to the top of the page
 
+Quote Post
burleson
post Apr 4 2017, 01:50 PM
Post #7


Advanced Member
***

Group: Members
Posts: 13,409
Joined: 26-January 04
Member No.: 13



Hi,

>> My retention policy is 10 days but none of the files older that 10 days are marked 'expired'.

With a redundancy-based retention policy, even if the specified KEEP UNTIL time has expired, the backup is retained as long as it is required to satisfy the redundancy requirement

This may help:

http://dba-oracle.com/t_rman_recovery_window_retention.htm






--------------------
Hope this helps. . .

Donald K. Burleson
Oracle Press author
Author of Oracle Tuning: The Definitive Reference
Go to the top of the page
 
+Quote Post
Susja
post Apr 5 2017, 02:02 PM
Post #8


Member
**

Group: Members
Posts: 13
Joined: 20-March 17
Member No.: 51,849



QUOTE (burleson @ Apr 4 2017, 02:50 PM) *
Hi,

>> My retention policy is 10 days but none of the files older that 10 days are marked 'expired'.

With a redundancy-based retention policy, even if the specified KEEP UNTIL time has expired, the backup is retained as long as it is required to satisfy the redundancy requirement

This may help:

http://dba-oracle.com/t_rman_recovery_window_retention.htm

Well ... this article was very helpful although I can't state that I understood all steps. Anyway ... I'm not sure what redundancy has been set in my case ... I only know that retention policy in my case is 10 days and backup not determined as 'expired' or 'obsolete' anymore .
I am going to do this: ( I don't need more than 1 copy of backup )
1. configure retention policy to redundancy 1;
After that:
2. configure retention policy to recovery window of 10 days;

Does it sound right for you?
Thanks
Go to the top of the page
 
+Quote Post
burleson
post Apr 6 2017, 12:24 PM
Post #9


Advanced Member
***

Group: Members
Posts: 13,409
Joined: 26-January 04
Member No.: 13



Hi Susja,

>> Does it sound right for you?

If that meets your requirements, you should be good!

For complete details, get this book:

http://www.rampant-books.com/book_1002_rma...up_recovery.htm




--------------------
Hope this helps. . .

Donald K. Burleson
Oracle Press author
Author of Oracle Tuning: The Definitive Reference
Go to the top of the page
 
+Quote Post
Susja
post Apr 22 2017, 12:03 PM
Post #10


Member
**

Group: Members
Posts: 13
Joined: 20-March 17
Member No.: 51,849



QUOTE (burleson @ Apr 6 2017, 01:24 PM) *
Hi Susja,

>> Does it sound right for you?

If that meets your requirements, you should be good!

For complete details, get this book:

http://www.rampant-books.com/book_1002_rma...up_recovery.htm

Well I read that interesting article. I tried to make some changes nothing has happened I.e. expired/obsolete backups don't get deleted.
Finally I decided to schedule another backup and point it to another disc on another PC. I never did it before hence I decided to use Enterprise console would be easier for me. Expectation is that 'new' backup will work properly i.e. will delete expired pieces properly.
My question : will this backup have the same retention policy as the first one or I should setup retention policy explicitly for each backup?
Thanks
Go to the top of the page
 
+Quote Post

Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:

 

Lo-Fi Version Time is now: 25th May 2017 - 07:26 AM