Effect Of --preserveCritical On Configure Utility
Last updated on FEBRUARY 03, 2018
Applies to:Oracle Communications Messaging Server - Version 8.0.2 and later
Information in this document applies to any platform.
Question about the initial configuration of a new instance: The LDAP error log file containing errors - Duplicate value addition in attribute even when using preserveCritical. The documentation indicates that -- preserveCritical "Does not overwrite critical attributes.".
Since both --preserveCritical was specified and "p" was input during the interactive configure session, it was expected these attributes would be preserved. However based on logs from LDAP it appears the values were preserved but actually re-written with the same value as what was there previously. This was unexpected. It was expected that the critical attribute values would not be changed at all, in any way. The effect of the current behaviour is:
1) LDAP error log "spam"
2) changing the value of modifytimestamp LDAP attributes
Is this behaviour intentional? Is there an opportunity to change --preserveCritical to actually make zero changes to the "critical attributes"?
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