archivelog deletion not happening on primary
edited Mar 19, 2010 5:54AM in High Availability Data Guard, Sharding and Global Data Services (MOSC) 2 commentsAnswered
I have now configured my dataguard config for RMAN backups. I am using the FRA and have the following set:
CONFIGURE DB_UNIQUE_NAME 'D20AC' CONNECT IDENTIFIER 'D20AC';
CONFIGURE DB_UNIQUE_NAME 'D21AC' CONNECT IDENTIFIER 'D21AC';
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;
I did an rman backup on my Standby:
but it did not remove the archivelogs on the primary database. Maybe this isn't supposed to happen this way. Also, maybe this doesn't matter because supposedly the FRA will remove old archivelogs as it needs space.
CONFIGURE DB_UNIQUE_NAME 'D20AC' CONNECT IDENTIFIER 'D20AC';
CONFIGURE DB_UNIQUE_NAME 'D21AC' CONNECT IDENTIFIER 'D21AC';
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;
I did an rman backup on my Standby:
backup database plus archivelog delete all input;
but it did not remove the archivelogs on the primary database. Maybe this isn't supposed to happen this way. Also, maybe this doesn't matter because supposedly the FRA will remove old archivelogs as it needs space.
0