Federated content might be stored twice with different document IDs.
You can create a trigger file that is named cfs_avoid_duplicate_content to avoid duplicate content on the FileNet Image Services system. If this trigger file exists, the replication process from Content Platform Engine to FileNet Image Services verifies that the content is not already stored on the FileNet Image Services system. Duplicate content is not stored again. The replication forces the DOCTABA entry on FileNet Image Services to reference the same content.
cd /fnsw/local/trigger
touch cfs_avoid_duplicate_content
Be aware that using this feature has some consequences. When a document is initially created, the system tags the content as "native P8" content. When this document is replicated with the cfs_avoid_duplicate_content trigger file in place, the document is no longer just a native P8 document. However, the "native P8" tag on the content is not updated. The FileNet Image Services disaster recovery tools, such as document import, ignore the "native P8" content. Hence, if the cfs_avoid_duplicate_content trigger file exists, the FileNet Image Services disaster recovery tools are not able to recover these specific documents.