Reset the Web content event log
From time to time you may need to reset the Web content event log. You should reset the Web content event log under these circumstances:
- The contents of the repository have been modified through an external mechanism such as a JCR import or some other custom application.
- As a post migration step during migration prior to syndication.
- In order to troubleshoot syndication problems such as items on the syndicator not being sent.
- Before resetting the Web content event log edit...
WP_PROFILE/ConfigEngine/properties/wkplc_dbtype.properties...and ensure the DbSafeMode property is set to false.
- In clustered environments, you should only reset the event log on the primary node.
- Any objects that were "purged" on the syndicator since the last syndication will not be purged on the subscriber. Purged objects are lost since the event log does not maintain records of objects that were deleted. To clean up purged items on a subscriber, you will need to go the subscriber and manually delete them.
Procedure
- Stop the WebSphere Portal server.
- Run...
cd WP_PROFILE/ConfigEngine
ConfigEngine.sh wcm-reset-event-log- Restart the server. This may take longer than usual as the event log will be recreated.
Parent topic
Additional configuration options