What are Options to Verify That the Retro Change Log is Trimming?
(Doc ID 1384020.1)
Last updated on AUGUST 07, 2017
Applies to:Oracle Directory Server Enterprise Edition - Version 6.0 to 184.108.40.206.0 [Release 6.0 to 11gR1]
Oracle Directory Server Enterprise Edition - Version 220.127.116.11.0 to 18.104.22.168.0 [Release 11gR1]
Information in this document applies to any platform.
***Checked for relevance on 27-09-2013***
Using the procedure documented in, How to trim Retro Change Log and recover allocated disk space ? (Doc ID 1286881.1)
stopped the directory
checked the file size:
-rw------- 1 ldap ldap 63G Nov 23 13:40 changelog_id2entry.db3
performed export of changelog
performed import of changelog
confirmed file size was resized.
-rw------- 1 ldap ldap 152M Nov 23 13:43 changelog_id2entry.db3
started directory successfully.
After having enabled trimming of the Retro Change Log and not verifying firstchangenumber of the Retro Change Log, what are other options to verify that the Retro Change Log is trimming ?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!