Database Backup and Recovery (MOSC)

MOSC Banner

Automatic Archivelog Management

edited Jan 13, 2014 10:26PM in Database Backup and Recovery (MOSC) 4 commentsAnswered ✓
 I am trying to fix a botched archive setup that I have inherited and am running into issues with archive logs not being cleaned up.
Here is the scenario:
Full RMAN backup taken nightly (RMAN> Backup database plus archivelog)
Archive log deletion policy is set to 1 times backed up.
Archive files still exist after multiplie backups and causing space constraints.

Backup parameters:

CONFIGURE RETENTION POLICY TO REDUNDANCY 5;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'D:\Data\PRMY01\%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center