Re: total backup size (lvl0/lvl1) out of rman catalog

On Tue, 03 Apr 2007 15:25:21 -0400, NetComrade <netcomradeNSPAM_at_bookexchange.net> wrote:

>On Tue, 03 Apr 2007 15:00:22 -0400, NetComrade
><netcomradeNSPAM_at_bookexchange.net> wrote:
>
>>On 3 Apr 2007 08:57:11 -0700, "sybrandb" <sybrandb_at_gmail.com> wrote:
>>
>>>On Apr 3, 5:20 pm, NetComrade <netcomradeNS..._at_bookexchange.net>
>>>wrote:
>>>> Does anyone has a query, or at least a column that identifies the
>>>> whole backup in catalog views? We need a report of backup sizes, w/o
>>>> having to look at the file system.
>>
>>>It's not THAT difficult and all the RC views are fully documented.
>>>You would need RC_BACKUP, RC_BACKUPSET and RC_BACKUPPIECE.
>>
>>I am having trouble grouping a single 'backup' together... e.g. this
>>lvl0 spans 2 days.. what do you suggest I group by with?
>>
>>
>>
>> 1583520 2952708691 1811176 2516 30-mar-2007 8 31-mar-2007
>> 1583520 2952708691 1811186 2526 31-mar-2007 13 31-mar-2007
>>
>> DB_KEY DB_ID BS_KEY RECID START_TIME PIECES COMPLETION_
>>-------- ---------- -------- ----- ----------- ------ -----------
>> 1583520 2952708691 1811192 2532 31-mar-2007 11 31-mar-2007
>> 1583520 2952708691 1811195 2535 31-mar-2007 11 31-mar-2007
>> 1583520 2952708691 1811196 2536 31-mar-2007 9 31-mar-2007
>> 1583520 2952708691 1811197 2537 31-mar-2007 10 31-mar-2007
>> 1583520 2952708691 1811198 2538 31-mar-2007 6 31-mar-2007
>> 1583520 2952708691 1811199 2539 31-mar-2007 7 31-mar-2007
>> 1583520 2952708691 1811200 2540 31-mar-2007 6 31-mar-2007
>> 1583520 2952708691 1811201 2541 31-mar-2007 7 31-mar-2007
>> 1583520 2952708691 1811202 2542 31-mar-2007 6 31-mar-2007
>> 1583520 2952708691 1811203 2543 31-mar-2007 4 31-mar-2007
>> 1583520 2952708691 1811204 2544 31-mar-2007 4 31-mar-2007
>>
>> DB_KEY DB_ID BS_KEY RECID START_TIME PIECES COMPLETION_
>>-------- ---------- -------- ----- ----------- ------ -----------
>> 1583520 2952708691 1811205 2545 31-mar-2007 5 31-mar-2007
>> 1583520 2952708691 1811206 2546 31-mar-2007 5 31-mar-2007
>> 1583520 2952708691 1813242 2547 31-mar-2007 14 31-mar-2007
>> 1583520 2952708691 1813243 2548 31-mar-2007 2 31-mar-2007
>> 1583520 2952708691 1813244 2549 31-mar-2007 1 31-mar-2007
>> 1583520 2952708691 1813245 2550 31-mar-2007 1 31-mar-2007
>
>The only way i can see of grouping these, is to have a unique 'tag'
>per backup, which we don't currently do. We can try going by date, but
>whenever there is an occasional backup failure it's not going to work.
>
>Default RMAN Backup Tag Format
>If you do not specify a tag, then RMAN creates a default tag for
>backups (except for control file autobackups) in the format
>TAGYYYYMMDDTHHMMSS, where YYYY is the year, MM is the month, DD is the
>day, HH is the hour (in 24-hour format), MM is the minutes, and SS is
>the seconds. For example, a backup of datafile 1 may receive the tag
>TAG20030208T133437. The date and time refer to when RMAN started the
>backup, in the time zone of the instance performing the backup. If
>multiple backup sets are created by one BACKUP command, then each
>backup piece is assigned the same default tag.
>
>
>
>.......
>We run Oracle 9iR2,10gR1/2 on RH4/RH3 and Solaris 10 (Sparc)
>remove NSPAM to email

I use %d_%T_%s_%p in the format clause.
I also sed the date in as tag. I have a template which I edit using sed, the output of sed is piped to RMAN. Works like a charm. Remember a backup set consists of 1 or more backup pieces, so the data is hierarchic.

-- 

Sybrand Bakker
Senior Oracle DBA