How To Setup Changelog Purging To Ignore LACNs (Doc ID 827056.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Internet Directory - Version 10.1.4.0.1 and later
Information in this document applies to any platform.
Information in this document applies to any platform.

Goal

How to setup changelog purging to only purge changelogs older than 10 days, and completely ignore the LACNs (Last Applied Change Numbers).


Background:
Purges are done based on whether the changelog entry has been processed or not. And if the changelog entry is still there after orclpurgetargetage, it too is purged. However, there is a way around this. One can create a dummy DIP export profile, in which the LACN is never incremented. Then orclpurgetargetage alone will control the deletion.

For details on how purging works, reference the Oracle Internet Directory Administrator's Guide 10g (10.1.4.0.1) > Section 26.1.4 Change Log Purging in Multimaster Replication > Change Log Purging Methods

Also review the Oracle® Identity Management User Reference 10g (10.1.4.0.1) > Section 9.2.342 orclPurgeTargetAge, which says:

This attribute enables time-based purging of change log records. Set this to the number of hours after which old change logs will be purged. Time-based purging respects the change status of replication, but not the change status of other consumers. When time-based purging is enabled, the change log garbage collector purges all change logs that are not needed by replication and that are at least the specified number of hours old.

The default behavior is change number-based purging, meaning this attribute is NULL or set to a value less than zero. Change number-based purging respects the change status of all change log consumers. That is, it does not purge change logs unless they have been consumed by all consumers. In addition, it does not purge change logs until they are 10 days old.

The behavior has changed as a result of the patching of <<bug /> in 10.1.4.


If the attribute orclpurgetargetage=0, then changelog entries are purged immediately in phase 2, and if a value is not set, the default of 240 hours is used automatically.

Use the following command to determine the current value of orclpurgetargetage:

ldapsearch -h <OID_host> -p <OID_port> -D "cn=orcladmin" -w <pwd> -s base -b "cn=changelog purgeconfig, cn=purgeconfig, cn=subconfigsubentry" objectclass=* orclpurgetargetage

Solution

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms