AMM module now uses RMAN to delete the archive logs

[Arjen Visser]

Since Dbvisit Standby 6.0.34, the AMM module now uses RMAN to delete logs.

Questions
1. Why are the arch log files on the standby server still deleted while remaining compressed ? I noticed the AMM cleaning with gzipped files was still operational on my standby server, contrary to the primary server.

Answer: RMAN is not used on the standby server, so the archives can be compressed on the standby.

2. You say RMAN is now used to delete logs. Does it mean AMM is no longer used, at least on primary server ? Why are the ARCHSOURCE_MANAGEMENT/DAYS_TO_KEEP_ARCHSOURCE parameters still valid in the configuration if RMAN now takes control of the cleaning according to its retention policy?

Answer: Yes RMAN is used underneath AMM, but AMM still uses all the same AMM settings. It does not use the RMAN settings such as retention plocy etc. AMM is determining which archives to remove and then calls RMAN to remove the actual archive files. The reason RMAN is used to remove the archives is so that it can also support ASM and also so that the controlfile is updated and the crosscheck command does not have to be run any longer.