Forum Stats

  • 3,757,132 Users
  • 2,251,200 Discussions
  • 7,869,737 Comments

Discussions

ORA-00257 on FRA and archives are not being deleted

User_NK0CG
User_NK0CG Member Posts: 1 Green Ribbon

Hi, I'm a kinda new in teh ORACLE world.

I'm dealing with an issue with a homologation base:

The FRA is 100% used and there was archives from a month ago.

I had to delete some archives to give some free space to FRA.

My client's RMAN configs are:

RMAN configuration parameters for database with db_unique_name HML are:

CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default

CONFIGURE BACKUP OPTIMIZATION OFF; # default

CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default

CONFIGURE CONTROLFILE AUTOBACKUP OFF; # default

CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default

CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default

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 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default

CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;

CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/11.2.0.4/dbhome_2/dbs/snapcf_hmlmv2.f'; # default

--

My question is: If I change the archivelog deletion police to CONFIGURE ARCHIVELOG DELETION POLICY TO BACKED UP 1 TIMES TO DISK; is it going to prevent it happens again? Is it enough?


My best regards

Answers