PJ40746: CONTENT LOSS MAY OCCUR WHEN USING DATABASE CONTENT STORAGE WITH DUPLICATE SUPPRESSION ENABLED

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

APAR status

  • Closed as program error.

Error description

  • Due to a defect in the database abandoned content cleanup code,
    content loss may randomly occur on add or check-in operations to
    your database storage area if you use duplicate suppression with
    database content storage.
    
    You will know that data loss has occurred if "Cannot find the
    content element" exceptions appear in your P8 logs, listing
    element names that start with "T", after clients attempt to
    access the missing content:
    2012-09-27T15:32:16.947Z 5E995E99 ENG  FNRCE0103E - ERROR method
    name: initContentInputStream principal name:
    P8Admin@yourdomain.com Global Transaction: false User
    Transaction: false Exception Info: Cannot find the content
    element T@~QRR)&RCHVTXW9(W!Y,{X]+P\<\A;M,[\(}@7!&Z)M.
    com.filenet.api.exception.EngineRuntimeException:
    CONTENT_DCA_CONTENT_ELEMENT_NOT_FOUND: Cannot find the content
    element T@~QRR)&RCHVTXW9(W!Y,{X]+P\<\A;M,[\(}@7!&Z)M.
     at
    com.filenet.engine.content.DatabaseContentInputStream$DatabaseRe
    aderTask.initContentInputStream(DatabaseContentInputStream.java:
    492)
    

Local fix

  • To temporarily work around this problem, disable the abandoned
    database cleanup process.  Set these parameters to high values,
    then restart the Content Engine JVM:
    Abandoned DB Content Cleanup Interval = 31356000 (1 year)
    Temporary Database Content = 630720000 (20 years)
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Customers using Content Engine 5.1.0.0-P8CE and              *
    * 5.1.0.0-P8CE-FP001 with duplicate suppression of database    *
    * content storage enabled.                                     *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Due to a defect in the database abandoned content cleanup    *
    * code, content loss may randomly occur after add or check-in  *
    * operations to your database storage area if you use          *
    * duplicate suppression with database content storage.         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to Content Engine 5.1.0.0-P8CE-FP002 or higher.      *
    ****************************************************************
    

Problem conclusion

  • Content Engine 5.1.0.0-P8CE-FP002 and higher will resolve the
    database content cleanup issue.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PJ40746

  • Reported component name

    CONTENT ENGINE

  • Reported component ID

    5724R8101

  • Reported release

    510

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-11-06

  • Closed date

    2013-05-01

  • Last modified date

    2013-05-01

  • APAR is sysrouted FROM one or more of the following:

    PJ40743

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    CONTENT ENGINE

  • Fixed component ID

    5724R8101

Applicable component levels

  • R510 PSY

       UP



Rate this page:

(0 users)Average rating

Document information


More support for:

FileNet P8 Platform
Content Engine

Software version:

510

Reference #:

PJ40746

Modified date:

2013-05-01

Translate my page

Machine Translation

Content navigation