PJ39576: PROBLEM WITH STORAGE POLICY WHEN SAVING VERSION 2 OF A DOCUMENT

APAR status

• Closed as duplicate of another APAR.

Error description

• Issue is caused by the following actions:
  1. A new document (version 1) is created with content. The
  default storage policy configured for the documents class
  definition is overridden.
  2. A new version of this document is created (version 2), again
  with content. The storage policy is not set or touched for this
  version. It is our understanding, that version 2 should be
  created using the same storage area as version 1.
  3. However version 2 somehow is stored using the default storage
  policy configured for the documents class definition, where as
  FileNet P8 expects version 2's content to be stored in the same
  storage area as version 1's content.
  4. Afterwards, retrieving version 1's content works well, but
  trying to retrieve version 2's content results in the reported
  FCA exception.
  
  Expected Results: Accept same document storage policy as version
  one of document, instead accepts default storage policy.
  
  Their application remains oblivious to the storage policy used
  by previous version of a document. The storage policy for the
  reservation object is not known at the time of checkout. The
  workaround would require for them to retrieve the previous
  version of the document before doing a checkout, to read the
  current storage policy. Changing this, would inccur a
  performance penalty as it would require one additional call
  towards content engine server.
  
  Please note that this error only occurs when using FileNet P8
  Batch Processing by means of API class UpdatingBatch.
  They want version 2 to use the same storage area as version 1.
  At the time of checkout, theye don't have any information about
  version 1 available (apart from the ID). Determining which
  storage area was used for version 1 would inccur a roundtrip to
  content engine server and lower performance.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * This is a bug in all CE versions. It happened when there is  *
  * a mismatch between the storage area PutContentHandler picks  *
  * to upload content and the storage area the persister picks   *
  * to store in the DocVersion table. The fix addresses this     *
  * issue by changing the storage area to where the content is   *
  * uploaded to in executeChange when a mismatch is found.       *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See Error Description                                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Upgrade 4.5.1.8-P8CE-FP008 or higher.                        *
  ****************************************************************
  

Problem conclusion

• The same fix is applied to 4.5.1.8-P8CE-FP008 and higher.
  

Temporary fix

Comments

• This APAR is a duplicate of PJ39395
  

APAR Information

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

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

Fix information

Applicable component levels