Dont let history logs for your wcm content grow too big

While a rare scenario, allowing the history log for wcm content items could cause problems in saving the item and or the log itself. This happen if grows past the internal default size.. typical errors will look similar to this

Error rendering content: com.ibm.workplace.wcm.api.exceptions.DocumentSaveException:
Message: Could not save object in repository., Cause: com.ibm.workplace. wcm.services.repository.RepositoryException: Message:
PrivilegedActionException caught, Cause: javax.jcr.nodetype.ConstraintViolationException: NT6577E: The value for the binary
property ibmcontentwcm:historyLogEntries on node/XXXXXXXXXXXXXXXXXXXXXXXXXXXXX/jcr:versionedNode/icm:
copiedValues exceeds its max length. The max length is 5000000 while the value is of length 5000679 (Message: Could not save object in repository., Cause: com.ibm.workplace.wcm.services.repository.RepositoryException: Message: PrivilegedActionException caught, Cause:javax.jcr.nodetype.ConstraintViolationException: NT6577E: The value for the binary property ibmcontentwcm:historyLogEntries on node /XXXXXXXXXXXXXXXXXXXXXXXXXXXX/jcr:versionedNode/icm:copiedValues exceeds its max length. The max length is 5000000 while the value is of length 5000679)

As part of routine maintenance you may consider truncating the history log