Archive logs that are managed by ASM can be removed from ASM when they are no longer needed by Replication Agent for Oracle. When the pdb_archive_remove configuration parameter is set to true and the archive logs are managed by ASM, the pdb_archive_path configuration parameter must be set to the name of the ASM disk group in which the archive logs are stored. The disk group name must be preceded with a plus sign (+) indicating that the path is an ASM path. For example:
pdb_archive_remove=true
pdb_archive_path=+DISK_GROUP1
Archive logs stored in and managed by ASM are owned by the corresponding unique Oracle database name. If the Oracle database name differs from the global unique database name, the pdb_archive_path configuration parameter must be set to both the name of the ASM disk group and the globally unique name of the database in which the archive logs are stored:
pdb_archive_path=+DISK_GROUP1/database_name
In addition to automatic removal of archive logs from ASM, manual removal is supported with the pdb_truncate_xlog command. The pdb_archive_path must be set to the ASM disk group name and preceded with a plus (+) sign for archive logs to be manually removed.
The rman_enabled parameter
enables Replication Agent to use the Oracle RMAN utility
to truncate old archive log files. See the Replication
Agent Reference Manual.
