What Is the Recommended Way To Have FolderStructureArchive (FSA) Work with Multiple Archives Going to the Same Server?

(Doc ID 844600.1)

Last updated on DECEMBER 15, 2017

Applies to:

Oracle Universal Content Management - Version: 7.5.1 to - Release: Stellent to 10gR3
Information in this document applies to any platform.


You are using Folder Structure Archive (FSA), and have multiple automatic replication archives set up, all going from the same source server to the same destination server. The archives use a metadata field for the export query, and have different values of that field defined as the export criteria. You have FSA set up for every archive to replicate the Contribution Folders and the Trash folder.

This causes FSA to replicate any new folders that were added in every archive. In turn, this causes the Archive log files on the target Content Server to contain lines like the following:

Info 5/27/09 1:02 PM Skip importing Row: [8, A506B579-96E0-F74E-51EF-6DA369F298BC, 2, Folder 3, 0, , , 1, 1, 0, 1, {ts '2009-05-27 13:01:13.117'}, , , , {ts '2009-05-27 13:01:13.307'}, , ADENG, , , , , , sysadmin, /Contribution Folders/Folder 3/, /B4C8AA18-F4C4-CF5D-487C-0F589535D150/A506B579-96E0-F74E-51EF-6DA369F298BC, /2/8] in Table Collections.

What is the recommended way to have FolderStructureArchive (FSA) work with multiple archives going
to the same server?


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms