Content Consistency Checker Overview
Content Engine provides a Content Consistency Checker that synchronizes
the object store database with file storage area content.
The Content Consistency Checker detects inconsistencies between
the metadata in the object store database and files in associated storage areas.
NOTE This
procedure is not necessary when backing up or restoring your object store database
if you store the content with the metadata in the database. If you manage your database backups and restores using the tools provided
with the database itself, its data is always in-sync with the object store.
When to use the Content Consistency Checker
You should use the Content Consistency Checker under any of these conditions.
- After restoring a storage area from backup media, you need to detect any missing
files or files with out-of-date security settings.
- After restoring an object store (including the database and file storage areas)
from backup media, you need to determine if there are any documents without
corresponding file storage-based content files, or files with inconsistent security
settings.
- If users are unable to view a document's content when the content is stored
in a file storage area, even when they have view-content permissions on the document.
In this case, you should check the document content to determine if the file
is missing or if the security settings on the file are incorrect.
- When moving a file storage area to another location.
Selecting documents to check
With the Content Consistency Checker, you can check content stored in the
file system. You can select one or more file storage areas within a specific object
store.
Security requirements
To run the Content Consistency Checker, you need permissions to read the file
storage area you want to check. You do not need read permissions for the documents
stored in the file store.
By default, object
store administrators have access to all objects in the system, enabling
them to perform the check. If you change the default security settings,
you can affect who has permissions to run the Content Consistency
Checker.
Error detection
The Content Consistency Checker detects the following major error types:
- File does not exist
- This error indicates one of two conditions:
- The document is valid, but its content is missing. You can obtain the
path name where the document exists using the content element resource
name property. This path enables you to search backup archives for the
file.
- The document was previously deleted, then restored when restoring
an object store database. However, the content was not restored. In this case,
you must decide whether to delete the document or restore the content
file.
- File is not the right size
- The file size is never wrong under
normal conditions. This error indicates that either the object store or the storage area contains the wrong size for the file. The incorrect size can result if, for example, the file in the storage area is either an old version or has been overwritten by another file. Examine the document content and restore the proper file if possible.
For details on other error types,
see Validation Errors.