ODSEE - What are the Options to Verify That the Retro Change Log is Trimming?
(Doc ID 1384020.1)
Last updated on FEBRUARY 01, 2019
Applies to:Oracle Directory Server Enterprise Edition - Version 6.0 to 18.104.22.168.0 [Release 6.0 to 11gR1]
Oracle Directory Server Enterprise Edition - Version 22.214.171.124.0 to 126.96.36.199.0 [Release 11gR1]
Information in this document applies to any platform.
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 the 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!
In this Document