Skip Headers
Oracle® Fusion Middleware Administering Oracle WebCenter Content
11g Release 1 (11.1.1)

Part Number E26692-01
Go to Documentation Home
Go to Book List
Book List
Go to Table of Contents
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Go to next page
PDF · Mobi · ePub

35 Using Archiver Replication Exceptions

The Archiver Replication Exceptions feature can be used to prevent failed Archiver imports from stopping replication in a Content Server instance.

This chapter covers the following topics:

35.1 Overview of Archiver Replication Exceptions

Archiver Replication Exceptions enables administrators to prevent failed imports from stopping replication. It does this by capturing such failed imports and putting them into an exceptions archive and sending email to the administrator that such a failed import has occurred.

The ArchiverReplicationExceptions component is installed and enabled by default with the Content Server instance.

35.1.1 How Archiver Replication Exceptions Works

Several configuration entries must be manually added to the IntradocDir/config/config.cfg file to support Archiver Replication Exceptions. The configuration entries define a variety of conditions to determine the level of error reporting, to direct failed imports to an exceptions directory, and to ignore and handle multiple failed imports when a systemic error is detected. Parameters for both automatic and manual imports are provided.

35.1.2 Scenario 1

In this scenario an import of a document has failed because the content type "DOC" does not exist in the importing server. The error reporting level (ArchiverEmailErrorLevel) was set to collision, standard, severe, and the ArchiverErrorNotifyUser was set to sysadmin. The following is an example of an archiver import failure email notification:

Archiver Import Failure
There was a serious error during the import of a document which may prevent that 
document from being properly synchronized in state with the exporting content 
server. Content item 'test1' was not successfully checked in. The content 
type 'DOC' is not defined in the system.
Revision Being Imported
Collection:  idc
Archive Name:  ar1
Source Instance:  idc
Batch Name:  07-sep-24_15.15.41_766/07267151541~1.hda
Content ID:  test1
Title:  test1
Author:  sysadmin
Revision:  1
Release Date:  9/24/07 3:13 PM
Create Date:  9/24/07 3:14 PM

The Document Has Been Copied To An Exceptions Archive

Collection:  idc
Archive Name:  ImportExceptions
Batch Name:  07-sep-24_15.15.41_766/07267151541~1.hda
Total Captured In Archive:  1

35.1.3 Scenario 2

In this scenario an import is being attempted but continually fails. The system administrator is aware that there may be problems during the import, but does not want an email notification of every failure. By setting ArchiverMaxConsecutiveImportErrors (default is 10), the system administrator can set several failures that can occur before the cessation of email notification. E-mail is sent until this number of errors is reached. If any import from the exporter should succeed before the set number is reached, or if the Content Server instance is restarted, the counter is reset to 0. Note that when the maximum number of errors is reached the automated import of the archive is aborted.

35.2 Administering and Using Archiver Replication Exceptions

The primary purpose for Archiver Replication Exceptions is to allow filtering of failed imports to optimize the handling and notification of such failures. For content items to be processed by Archiver Replication Exceptions, the administrator must manually set configuration entries in the IntradocDir/config/config.cfg file. The configuration variables customize the behavior of the importing Content Server instance to allow for certain situations and to distribute the error reporting based on the configured criteria.

The following configuration variables can be used to customize behavior. These values should be set in the IntradocDir/config/config.cfg file under #Additional Variables.

By prepending any of the configuration entries with the name of an archive, with a colon (:) as a separator, that configuration entry will only apply to that archive. For example, to enable capturing exceptions for the archive MyRemoteImportArchive, use the following entry in the config.cfg file:


If an archive name prefix is not applied, then the value set is the global default for all archives.

The parameter ArchiverMaxConsecutiveImportErrors addresses the issue of skipping over errors and sending email notifications on the errors when the error is caused by a systemic problem (such as all documents having the same wrong metadata field on export). This results in numerous documents being unnecessarily captured and generating the attendant volume of unwanted email. This configuration entry helps detect such scenarios. During an automated import, if too many consecutive import errors are detected, then the current archive import is aborted. Manual imports follow the standard rules for maximum errors (see MaxarchiveErrorsAllowed).If any import (from any archive) is successful, then the consecutive import failure count is reset to 0.

If the same document fails an import (twice or more) sequentially email is sent out only for the first failure. If the same document fails an import but is from a different batch load file, the email for it is not suppressed if email for that document has already been sent for a previous error.