1

Topic: Removal arhived redo log through interface EM

Kind time of days, sharply there was a question of learning of Oracle. Knowledge only surface and while I master Enterprise Manager. The version 11g is installed. Some time ago there was a problem with overflow db_recovery_file_dest_size which managed to be solved booted with pfile. Coming into section in Fast Recovery saw that occupy the place most part Arhived Redo Log, in log they are displayed, however in section Manage Current Backups they are not present. Whether probably them to delete through Enterprise Manager?

2

Re: Removal arhived redo log through interface EM

Basic purpose arhived redo log - protection of the data, the main task - to provide "hot" reserve copying, without a basis stop. Upon termination of such  broad gulls are erased normally automatically.
If  it is necessary, (it can was a spirit, but broke) it is necessary to correct it. If  it is not necessary, archive broad gulls can be erased (including through EM) or even simply to disconnect their generation in basis.

3

Re: Removal arhived redo log through interface EM

in this business wrote:

a basic purpose arhived redo log - protection of the data, the main task - to provide "hot" reserve copying, without a basis stop. Upon termination of such  broad gulls are erased normally automatically.
If  it is necessary, (it can was a spirit, but broke) it is necessary to correct it. If  it is not necessary, archive broad gulls can be erased (including through EM) or even simply to disconnect their generation in basis.

I thank, about assignment of dens I read, at me they automatically are not erased and occupy now 200G how them to delete through EM?

4

Re: Removal arhived redo log through interface EM

ernik;
Sequentially, in the same interface Manage Current Backups.

5

Re: Removal arhived redo log through interface EM

env wrote:

ernik;
Sequentially, in the same interface Manage Current Backups.

But they at me there are not displayed, or I not correctly do something

6

Re: Removal arhived redo log through interface EM

Button nearby "catalog additional files"
If they are not picked up, means they not from this basis
If other basis is not present, they can be erased simply
But I before it would try to register and check up them manually, through rman

7

Re: Removal arhived redo log through interface EM

Vadim Lejnin wrote:

the Button nearby "catalog additional files"
If they are not picked up, means they not from this basis
If other basis is not present, they can be erased simply
But I before it would try to register and check up them manually, through rman

The DB, but part once deleted from this manually.
Tried through catalog additional files, are not picked up. Through rman  errors at attempt of removal by a command delete archivelog all;

8

Re: Removal arhived redo log through interface EM

Vadim Lejnin wrote:

the Button nearby "catalog additional files"
If they are not picked up, means they not from this basis

Once again selected the directory through catalog additional files and now the occupied size increased for 30
Non-reclaimable Fast Recovery Area (GB) 218,58
EM still them does not see.

9

Re: Removal arhived redo log through interface EM

All I thank, especially Vadim Lejnin and env , after a choice catalog additional files and serial start of jobs the place was released.

10

Re: Removal arhived redo log through interface EM

ernik;
If does not work GUI, try pens

start-> run-> cmd.exe
set ORACLE_HOME=D:\APP\PRODUCT\....
set ORACLE_SID=XXX
set PATH = % ORACLE_HOME %\bin; %PATH %
rman target / trace %TEMP %\rman.lst
set echo on
catalog start with ' D:\app\fast_recovery_area ' noprompt;
list archivelog all;
list backup of archivelog all;
delete noprompt expired archivelog;
delete noprompt obsolete;

If there are lines
File %TEMP %\rman.lst you pack and you put

11

Re: Removal arhived redo log through interface EM

[quote =-2] And control_file_record_keep_time increase not to lose any more files.

Thanks, I will deliver 3 months (92), but I will try more to such level basis not to launch, all the same (it is unexpected for me) it appeared that it is necessary to track it.