Hey DBA's, my question today might be simple. I couldn't find the answer anywhere having been searching for a while.
This question will use various different database versions as the isue is across a few DB's ... (10, 11) but for clarity we can just say Oracle 11gR2 and use my personal DB as a go-by. Consider the below queries..
In RMAN CATALOG...
SELECT db_name, start_time, end_time, input_type, status, input_bytes_display, output_bytes_display
FROM rman.rc_rman_backup_job_details a
where db_name = 'DB_SID' order by a.start_time desc;
---
DMM 01-JUL-10 01-JUL-10 DB FULL COMPLETED 3.13G 356.02M
DMM 30-JUN-10 30-JUN-10 DB FULL COMPLETED 3.13G 356.78M
DMM 30-JUN-10 30-JUN-10 DB FULL FAILED 1.49G 171.92M
DMM 02-JUN-10 02-JUN-10 DB FULL COMPLETED 4.43G 646.49M
DMM 02-JUN-10 02-JUN-10 DB FULL FAILED 2.39G 715.61M
DMM 01-JUN-10 01-JUN-10 DB FULL COMPLETED 7.93G 1.73G
DMM 01-JUN-10 (null) ARCHIVELOG FAILED 0.00K 0.00K
---
In DB to be backed up...
select start_time, end_time, input_type, status, input_bytes_display, output_bytes_display
from v$rman_backup_job_details order by start_time desc;
---
01-JUL-10 01-JUL-10 DB FULL COMPLETED 3.13G 356.02M
30-JUN-10 30-JUN-10 DB FULL COMPLETED 3.13G 356.78M
30-JUN-10 30-JUN-10 DB FULL FAILED 1.49G 171.92M
02-JUN-10 02-JUN-10 DB FULL COMPLETED 4.43G 646.49M
02-JUN-10 02-JUN-10 DB FULL FAILED 2.39G 715.61M
01-JUN-10 01-JUN-10 DB FULL COMPLETED 7.93G 1.73G
01-JUN-10 ARCHIVELOG FAILED 0.00K 0.00K
21-OCT-09 21-OCT-09 DB FULL COMPLETED 1.47G 232.44M
21-OCT-09 21-OCT-09 ARCHIVELOG COMPLETED 166.28M 63.86M
19-OCT-09 19-OCT-09 DB FULL COMPLETED 1.60G 278.96M
16-OCT-09 16-OCT-09 DB FULL COMPLETED 1.47G 241.16M
---
So for the above I have to ask, why does the DB store more information than the Catalog? When the catalog sync'd with the database, shouldn't it have copied that information (the October backups) from the control file?
Next...
RMAN> show all;
RMAN configuration parameters for database with db_unique_name DMM are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 1;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE COMPRESSION ALGORITHM 'BZIP2'; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO BACKED UP 3 TIMES TO 'SBT_TAPE';
CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'C:\APP\MADDEDO\PRODUCT\11.1.0\DB_1\DATABASE\SNCFDMM.ORA'; # default
RMAN> list backup summary;
List of Backups
===============
Key TY LV S Device Type Completion Time #Pieces #Copies Compressed Tag
------- -- -- - ----------- --------------- ------- ------- ---------- ---
1816 B F A DISK 30-JUN-10 1 1 YES TAG201006 30T134624
1864 B A A DISK 30-JUN-10 1 1 YES TAG201006 30T134842
1878 B F A DISK 30-JUN-10 1 1 NO TAG201006 30T134845
1922 B A A DISK 01-JUL-10 1 1 YES TAG201007 01T090822
1923 B F A DISK 01-JUL-10 1 1 YES TAG201007 01T090824
1942 B A A DISK 01-JUL-10 1 1 YES TAG201007 01T091043
1958 B F A DISK 01-JUL-10 1 1 NO TAG201007 01T091046
The views show much more history to the backups than simply stopping at June 30, just like this list backup command shows. However, I believe I understand that these are all that are available, due to me having redundancy set to 1. That said I'm asking for clarification: The views simply show all the history for backups, whether they are available or not (Eg, June 1st backup is deleted/inaccessible, there's just a record that it did exist at one point in the views)
Thanks in advance!
-- EDITED only for clarity/cleaning the post layout.
Edited by: knightace on Jul 1, 2010 6:29 AM