Dataguard parameter "CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY"
Hello.
I configured our dataguard physical standby database with the parameter CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;
I did it a long time ago (dont remmember exact date).
When I connect to ASM with the asmcmd command and check the path +RECOVERY/orcl/archivelog/2013_05_10 for old files that should not be there because they were supposibly applied, I see a lot of folders back to 2013_05_10 that should not be there.
Anyone has a clue of what is causing the files to remain there?
I read one blog were one guy said that the files dont get deleted until FRA in Physical Standby reaches 100% usage.
I configured our dataguard physical standby database with the parameter CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;
I did it a long time ago (dont remmember exact date).
When I connect to ASM with the asmcmd command and check the path +RECOVERY/orcl/archivelog/2013_05_10 for old files that should not be there because they were supposibly applied, I see a lot of folders back to 2013_05_10 that should not be there.
Anyone has a clue of what is causing the files to remain there?
I read one blog were one guy said that the files dont get deleted until FRA in Physical Standby reaches 100% usage.
0