Certain content might be unexpectedly deleted when storing content in FileNet Content Engine Database Storage Areas that have the Suppress Duplicate Content Elements feature enabled.
Certain content might be unexpectedly deleted when storing content in FileNet Content Engine Database Storage Areas that have the Suppress Duplicate Content Elements feature enabled on the FileNet Content Engine 4.5.1.x, 5.0.0.x and 5.1.0.x releases. This issue does not apply to content stored in FileNet Content Engine Database Storage Areas with the Suppress Duplicate Content Elements feature disabled, which is the default. This issue also does not apply to content stored in FileNet Content Engine File Storage Area or Fixed Storage Areas.
Resolving the problem
An issue has been identified in IBM FileNet Content Engine versions 4.5.1, 5.0.0 and 5.1.0 when the Database Storage Areas functionality is used with the Suppress Duplicate Content Elements feature enabled. Clean-up processing might delete single instance content that has a computed hash value beginning with a 'T' before it has been stored in the Database Storage Area. If this deletion occurs, the deleted content will need to be re-ingested into the FileNet Content Engine.
Fixes addressing this potential issue are available on the following code lines:
4.5.1.x: As a test fix, 188.8.131.52-P8CE-ALL-TF030
5.0.0.x: In a fix pack, 184.108.40.206-P8CE-FP002
5.1.0.x: In a fix pack, 220.127.116.11-P8CE-FP002
The fix packs are available on IBM Fix Central. Please contact IBM Support for download information if the 4.5.1 test fix is needed.
If the fixes above cannot be immediately applied, the following steps should be implemented as soon as possible to limit database content clean-up processing execution and the potential loss of content.
1. Start FileNet Enterprise Manager (FEM) and navigate to the Content tab on the P8 domain properties dialog.
2. Set the Abandoned DB Content Cleanup Interval property to 31356000 seconds.
3. Set the Temporary Database Content Lifetime value to 630720000 seconds.
4. Apply the changes and restart all Content Engine servers in the domain for the settings to take effect.
If you have any questions, please contact IBM Support.
More support for:
FileNet Content Manager
Software version: 4.5.1, 5.0, 5.1.0
Operating system(s): AIX, HP-UX, Linux, Solaris, Windows
Reference #: 1617178
Modified date: 05 April 2013