IBM FileNet P8, Version 5.2.1            

Content freeze error is generated during Federation Administration rule management

Federation of IBM® Content Manager content completes with an error that content freeze failed before federation.

Symptoms

The Federation Administration Rule Management tab reports that federation completed with import errors when you federate content from a IBM Content Manager source repository that uses DB2®. The error listing includes the following error:
CFS0115: Content freeze failed before federation.
The detailed error records include a stack trace with the following entries:
Caused by: com.venetica.vbr.client.UnsupportedActionException: COEN0236E: The requested action
on item RBCBusFinSrvces.A1001001A11E20C20720A23377.A11E20C20720A23377.1108 cannot be performed.
The item is checked out by another user QWVVX9K.
at com.venetica.vbr.ejb.bridge.contentmgr.ContentMgrBridge.lockDownRecord(ContentMgrBridge.java:6425)
at com.venetica.vbr.ejb.bridge.contentmgr.ContentMgrBridge.customAction(ContentMgrBridge.java:15367)

Causes

When the source repository type is IBM Content Manager and the IBM FileNet® Content Federation Services for Content Integrator connector that is used to access the repository is configured with the Usage Mode custom property set to Records Management, the content federation importer calls a content freeze on each document when it is created for the first time in the target repository during federation. If the source document has mutable content, calling a content freeze results in an attempt to lock down the document in the source repository as if it were being declared a record. This operation fails if the source document is checked out.

Resolving the problem

In IBM Content Manager, check the document back in and then use the Federation Administration application to retry the failed rule.


Last updated: October 2015
p8pco030.htm

© Copyright IBM Corporation 2015.