Re: backup files location?

Thanks Niall and Dimitre for replying.
I could not find a command for list backupiece (without knowing the names
of pieces). I did a full 'list backup' to see the backup pieces it displays
at the end - but no luck there. It says all the files are in 'FLASH' and
shows the deleted ones as expired correctly.
I tried Dimitre's suggestion and got this:


RMAN> backup recovery area;

Starting backup at 28-MAR-12

specification does not match any archive log in the recovery catalog

specification does not match any datafile copy in the repository

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

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

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

RMAN-03002: failure of backup command at 03/28/2012 17:26:19

RMAN-06747: at least 1 channel of tertiary storage must be allocated to
execute this command

I tried to check this command in another database where things are good,
but I got the same response. Not sure what this command does.

I am inclined to think that this is a bug. I need to work on that more.


On Wed, Mar 28, 2012 at 1:26 PM, Radoulov, Dimitre <cichomitiko@xxxxxxxxx>wrote:

> On 27/03/2012 00:53, Ram Raman wrote:
>> v10.2. We have a dev db whose backups have been failing with message that
>> db_recovery_file_dest_size is full. Our location in FLASH group in ASM.
>> Upon looking into the FLASH diskgroup I see that there are only 2 files
>> taking about 670Mb:
> [...]
> Hi Ram,
> there are some bugs with somehow *similar* symptoms (see ID 4911954.8, bug
> 4911954 - they talk about different values between v$recovery_file_dest
> (here the values are incorrect) and v$flash_recovery_area_usage).
> I would try to backup the recovery area (rman> backup recovery area;) to
> check what rman is *trying* to back up.
> You could also check Space Usage Figures in V$flash_recovery_area_usage
> Misleading When FRA Location is Changed [ID 460145.1] if you've changed the
> fra location.
> Let us know if you find what's happening.
> Regards
> Dimitre


Other related posts: