7.0-dm_verity_coll

DM_VERITY_COLL


ERROR: [DM_VERITY_COLL_F_STYLE_CURSOR_PROBLEM]

SEVERITY: FATAL
DESCRIPTION: SS Problem reading collection style cursor. Database: error %s. Query: %s
CAUSE: RDBMS error.
ACTION: Look for messages from RDBMS or OS.
PARAMS: %s – The RDBMS error message.

ERROR: [DM_VERITY_COLL_F_CANT_CREATE_DUMMY_FILE]

SEVERITY: FATAL
DESCRIPTION: S Cant create the dummy file for updating non-indexable or no-content sysobjects (update phase I). Filename %s.
CAUSE: Out of space on disk, read-only filesystem or filesystem off-line, or other filesystem or disk problem.
ACTION: Look for operating system error messages. Partition Facility errors ** Documentum Content Server ** Confidential Property of EMC Corporation ** (c) Copyright Documentum, Inc., 2007 – 2010 ** All rights reserved. **
PARAMS:

ERROR: [DM_VERITY_COLL_F_CANT_FIND_UPDATE_WORKDIR]

SEVERITY: FATAL
DESCRIPTION: S Cant find an update work directory. Filename %s.
CAUSE: Internal error. Probably filesystem or disk problem.
ACTION: Look for operating system error messages.
PARAMS:

ERROR: [DM_VERITY_COLL_F_CANT_CREATE_PHASE1_LOCKFILE]

SEVERITY: FATAL
DESCRIPTION: S Cant create the lock file for update phase I. Filename %s.
CAUSE: Out of space on disk, read-only filesystem or filesystem off-line, or other filesystem or disk problem.
ACTION: Look for operating system error messages.
PARAMS:

ERROR: [DM_VERITY_COLL_F_UPDATE_SESSION_PROBLEM]

SEVERITY: FATAL
DESCRIPTION: Cant open vdk sessions or collections for this fulltext index.
CAUSE: Verity failed to establish a session or open all collections for this index, or the index has invalid references.
ACTION: See other accompanying error messages, and retry the operation in a new session.
PARAMS:

ERROR: [DM_VERITY_COLL_F_CANT_LAUNCH_UPDATE_PHASE2]

SEVERITY: FATAL
DESCRIPTION: Update phase 2 launch failed.
CAUSE: Probable OS resource problem: out of memory, disk space, etc.
ACTION: Look for OS error messages.
PARAMS:

ERROR: [DM_VERITY_COLL_F_CANT_CREATE_UPDATE_WORKDIR]

SEVERITY: FATAL
DESCRIPTION: S Cant create an update work directory. Filename %s.
CAUSE: Out of space on disk, read-only filesystem or filesystem off-line, or other filesystem or disk problem.
ACTION: Look for operating system error messages.
PARAMS:

ERROR: [DM_VERITY_COLL_F_CANT_RENAME_BATCH_PREP_FILE]

SEVERITY: FATAL
DESCRIPTION: SI Rename of file %s failed after %d tries. OS error: %s
CAUSE: Internal error. Probably filesystem or disk problem.
ACTION: Retry indexing with a larger batch size.
PARAMS:

ERROR: [DM_VERITY_COLL_F_DOC_CURSOR_PROBLEM]

SEVERITY: FATAL
DESCRIPTION: S Problem reading document cursor. Database: error %s.
CAUSE: RDBMS error.
ACTION: Look for messages from RDBMS or OS
PARAMS: %s – The RDBMS error message.

ERROR: [DM_VERITY_COLL_F_CANT_ACQUIRE_PHASE1_LOCK]

SEVERITY: FATAL
DESCRIPTION: S Cant acquire file lock for update phase I. Filename %s.
CAUSE: Internal error. Another server may be holding the lock.
ACTION: Verify that there is only one server running an update, then try again.
PARAMS:

ERROR: [DM_VERITY_COLL_E_COMMIT_FAILED]

SEVERITY: ERROR
DESCRIPTION: The fulltext update operation failed to commit the changes made to the database.
CAUSE: Database error
ACTION: Examine the database logs. Once error is resolved, rerun the fulltext operation.
PARAMS:

ERROR: [DM_VERITY_COLL_E_CANT_MAKE_FILES]

SEVERITY: ERROR
DESCRIPTION: S Could not initialize Verity files for partition %s
CAUSE: Out of space on disk, read-only filesystem or filesystem off-line, or other filesystem or disk problem.
ACTION: Look for operating system error messages.
PARAMS:

ERROR: [DM_VERITY_COLL_E_FTINDEX_BAD_STATUS]

SEVERITY: ERROR
DESCRIPTION: The fulltext index object is in a bad status. Check for errors in the server and session logs.
CAUSE: An set, revert, or save operation turned the status of the object bad.
ACTION: Examine logs for error messages. Once error is resolved, rerun the operation.
PARAMS:

ERROR: [DM_VERITY_COLL_E_DOC_INDEX_FAIL]

SEVERITY: ERROR
DESCRIPTION: SS Attempt to index new Verity doc set %s failed while updating partition %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_E_VDB_OPEN]

SEVERITY: ERROR
DESCRIPTION: SS Attempt to open Verity VDB %s failed while updating partition %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_E_NO_CONTENT]

SEVERITY: ERROR
DESCRIPTION: S Attempt to index content with non-existent id %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_E_CANT_OPEN_SESSION]

SEVERITY: ERROR
DESCRIPTION: I Cant open Vdk Session: Error code = %d.
CAUSE: Verity internal error.
ACTION: Report this error to your Documentum site representative.
PARAMS: %d – Verity error code

ERROR: [DM_VERITY_COLL_E_BAD_LOAD_HEADER]

SEVERITY: ERROR
DESCRIPTION: The verity_dump_header file had the wrong format — load failed
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_E_CANNOT_MARK_CONTENT_BAD]

SEVERITY: ERROR
DESCRIPTION: SSI Content %s with parent %s failed to save after setting the update_count attr to %d.
CAUSE: The save operation on the content failed most likely due to database error.
ACTION: Examine the database logs for any errors and inspect the content object. PARAMETERS:Content id, parent id, update_count
PARAMS:

ERROR: [DM_VERITY_COLL_E_UPDATE_DIR_BAD]

SEVERITY: ERROR
DESCRIPTION: S The update batch file is unreadable or missing. Name: %s.
CAUSE: Disk failure or bad mount.
ACTION: Check the disk and directory.
PARAMS:

ERROR: [DM_VERITY_COLL_E_TAR_FAILURE]

SEVERITY: ERROR
DESCRIPTION: SI Tar step failed during %s operation — OS error was %d
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_E_EXEC_FAIL]

SEVERITY: ERROR
DESCRIPTION: SS Command execution failure: %s. Operating system error: %s.
CAUSE: Unable to execute the command successfully
ACTION: See your system administrator.
PARAMS:

ERROR: [DM_VERITY_COLL_E_CANT_OPEN_COLLECTION_DIR]

SEVERITY: ERROR
DESCRIPTION: SI Cant open collection in directory %s: Error code = %d.
CAUSE: Internal error. Possible disk corruption or failure.
ACTION: None may be necessary, we will attempt recovery.
PARAMS:

ERROR: [DM_VERITY_COLL_E_CANT_CHANGE_DIRECTORY]

SEVERITY: ERROR
DESCRIPTION: S Failure in attempt to set working directory to %s
CAUSE: Unable to change working directory before reading Verity index
ACTION: See your system administrator
PARAMS:

ERROR: [DM_VERITY_COLL_E_LOST_PHASE2_FILE]

SEVERITY: ERROR
DESCRIPTION: S Update file %s has disappeared.
CAUSE: Internal error. Possible disk corruption or failure.
ACTION: None may be necessary, we will attempt recovery.
PARAMS:

ERROR: [DM_VERITY_COLL_E_CANT_SUBMIT_ADMIN_OPT]

SEVERITY: ERROR
DESCRIPTION: II Cant submit admin optimization on %d-th collection: Error code = %d.
CAUSE: Verity administrative error. Cant cleanup collection.
ACTION: Check the status file for other messages.
PARAMS: %d – the collection number %d – the verity error return code

ERROR: [DM_VERITY_COLL_E_DOC_SET_CREATE]

SEVERITY: ERROR
DESCRIPTION: S Attempt to create new Verity doc set failed while updating partition %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_E_CANT_STAT_CONTENT]

SEVERITY: ERROR
DESCRIPTION: SSI Content object %s identified by %s path could not be accessed OS Error is %d.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_E_MERGE_FAIL]

SEVERITY: ERROR
DESCRIPTION: SS Attempt to merge partitions %s and %s failed
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_E_CANT_CONVERT]

SEVERITY: ERROR
DESCRIPTION: SS Cant convert content %s to format %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_E_BAD_DESC_FILE]

SEVERITY: ERROR
DESCRIPTION: S Bad update descriptor file. Cant read %s.
CAUSE: Internal error. An indexing descriptor file was written with an unreadable section.
ACTION: Report this error to your Documentum site representative.
PARAMS: %s – the name of the unreadable section.

ERROR: [DM_VERITY_COLL_E_DEST_STYLE_FILE_OPEN_FAILED]

SEVERITY: ERROR
DESCRIPTION: S Could not open file %s for write
CAUSE: Check that the directory exists, and has permission to write
ACTION: Contact Documentum support if directory does not exist. PARAMETERS:File name
PARAMS:

ERROR: [DM_VERITY_COLL_E_NO_VERITY_DIR]

SEVERITY: ERROR
DESCRIPTION: Verity location directory not defined in server configuration
CAUSE: Server configuration must have a Verity location.
ACTION: Install Verity if necessary, create a location object pointing to it, and put this location object in the server config.
PARAMS:

ERROR: [DM_VERITY_COLL_E_CANT_DESTROY_PHASE1_FILE]

SEVERITY: ERROR
DESCRIPTION: SS In update phase1, when attempting to erase file %s, got os error:%s
CAUSE: OS error.
ACTION: Examine OS error string and react accordingly
PARAMS:

ERROR: [DM_VERITY_COLL_E_CANT_ACCESS_CONTENT]

SEVERITY: ERROR
DESCRIPTION: SSS The content identified by id (%s) which references the file named (%s) cannot be accessed. Operating System error: %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_E_CANT_SET_PARSE_HANDLE]

SEVERITY: ERROR
DESCRIPTION: S Cant set the Verity document parser for style %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_E_TRANSACTION_FAILURE]

SEVERITY: ERROR
DESCRIPTION: SS Could not %s transaction for %s operation
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_E_PATH_TOO_LONG]

SEVERITY: ERROR
DESCRIPTION: S The directory path %s is too long to be used by Verity
CAUSE: The path chosen for the index is too long for the Verity API
ACTION: Chose a different location with a shorter file path and retry the index creation
PARAMS:

ERROR: [DM_VERITY_COLL_E_BAD_BATCH]

SEVERITY: ERROR
DESCRIPTION: S Failure attempting to index batch with format %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_E_CANT_ACQUIRE_PHASE2_LOCK]

SEVERITY: ERROR
DESCRIPTION: S Cant acquire file lock for update phase II. Filename %s.
CAUSE: Internal error. Another server may be holding the lock.
ACTION: Verify that there is only one server running an update, then try again.
PARAMS:

ERROR: [DM_VERITY_COLL_E_LAUNCH_FAIL]

SEVERITY: ERROR
DESCRIPTION: SS Failed to launch the command: %s. Operating system error: %s.
CAUSE: Unable to lauch command successfully.
ACTION: You may run out of processes or see your system administrator.
PARAMS:

ERROR: [DM_VERITY_COLL_E_CANT_DESTROY_LAST_STATUS_OPT_FILE]

SEVERITY: ERROR
DESCRIPTION: SS During cleaning, when attempting to erase file %s, got os error:s%
CAUSE: OS Error
ACTION: Examine OS error string and reach accordingly
PARAMS:

ERROR: [DM_VERITY_COLL_E_VDB_WRITE]

SEVERITY: ERROR
DESCRIPTION: SS Attempt to write Verity VDB %s failed while updating partition %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_E_PART_UPDATE_FAIL]

SEVERITY: ERROR
DESCRIPTION: SSSS Attempt to update partition index %s failed trying to %s partitions %s and %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_E_CANT_DESTROY_PHASE2_FILE]

SEVERITY: ERROR
DESCRIPTION: SS In update phase2, when attempting to erase file %s, got os error:%s
CAUSE: OS error.
ACTION: Examine OS error string and react accordingly
PARAMS:

ERROR: [DM_VERITY_COLL_E_PHASE2_TIMED_OUT]

SEVERITY: ERROR
DESCRIPTION: I Phase 2 timed out after %d seconds. Killing it.
CAUSE: Indexing filter has looped.
ACTION: Look for Verity error messages and documents marked bad and retry.
PARAMS:

ERROR: [DM_VERITY_COLL_E_NO_FILTER]

SEVERITY: ERROR
DESCRIPTION: S No Verity filter for format %s
CAUSE: No verity_filter defined for this format.
ACTION: Modify the format, adding a verity_filter.
PARAMS:

ERROR: [DM_VERITY_COLL_E_VERITY_DELETE_ERROR]

SEVERITY: ERROR
DESCRIPTION: I Verity index delete request returned error. Code = %d.
CAUSE: Verity indexing error during delete request. Document may already have been deleted.
ACTION: Check the status file for other messages.
PARAMS: %d – the verity error return code

ERROR: [DM_VERITY_COLL_E_BAD_PHASE2_FILENAME]

SEVERITY: ERROR
DESCRIPTION: S Found badly formatted update file. Filename %s.
CAUSE: Internal error. Possible disk corruption or failure.
ACTION: None may be necessary, we will attempt recovery.
PARAMS:

ERROR: [DM_VERITY_COLL_E_CANT_CREATE_UPDATE_STATUS_FILE]

SEVERITY: ERROR
DESCRIPTION: S Cant create an update status file. Filename %s.
CAUSE: Out of space on disk, read-only filesystem or filesystem off-line, or other filesystem or disk problem.
ACTION: Look for operating system error messages.
PARAMS:

ERROR: [DM_VERITY_COLL_E_MKVDK_FAILURE]

SEVERITY: ERROR
DESCRIPTION: I mkvdk failed — OS error was %d. Please check status.last file (for fulltext update operation) or status_optimize.last file (for fulltext clean operation) for more messages.
CAUSE: OS Error.
ACTION: Examine OS error number and react accordingly
PARAMS:

ERROR: [DM_VERITY_COLL_E_CANT_OPEN_COLLECTION]

SEVERITY: ERROR
DESCRIPTION: SI Cant open collection for style %s: Error code = %d.
CAUSE: Possible filesystem offline or corrupted.
ACTION: Look for operating system error messages.
PARAMS: %s – collection subtype %d – Verity error code

ERROR: [DM_VERITY_COLL_E_WAIT_FAIL]

SEVERITY: ERROR
DESCRIPTION: SS Failed to wait for the command: %s. Operating system error: %s.
CAUSE: Unable to wait for command to finish successfully.
ACTION: See your system administrator.
PARAMS:

ERROR: [DM_VERITY_COLL_E_BAD_CONTENT]

SEVERITY: ERROR
DESCRIPTION: S Attempt to index content with id %s failed — Verity filter rejected content
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_E_ATTRIBUTE_QUERY_FAILED]

SEVERITY: ERROR
DESCRIPTION: SI The query %s to fetch indexed attribute values with batch size %d failed. Check the server and database logs for any db errors.
CAUSE: The query returned a NULL collection.
ACTION: Check the server and database logs for further errors. PARAMETERS:query string and number of contents to batch in one fetch to client
PARAMS:

ERROR: [DM_VERITY_COLL_E_NO_STATUS_FILES_DURING_UPDATE]

SEVERITY: ERROR
DESCRIPTION: An update seems to be in progress but there are no status files (either current or old).
CAUSE: Unknown error.
ACTION: Try again. If indexing problems occur, contact your Documentum site representative.
PARAMS:

ERROR: [DM_VERITY_COLL_E_CANT_SUBMIT_BULK]

SEVERITY: ERROR
DESCRIPTION: SSI Cant submit bulk update on %s for %s: Error code = %d.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_E_VDB_COMMIT]

SEVERITY: ERROR
DESCRIPTION: SS Attempt to commit changes to Verity VDB %s failed while updating partition %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_E_CANT_FETCH_PARENT]

SEVERITY: ERROR
DESCRIPTION: SS Error fetching dm_sysobject parent (%s) of dmr_content object %s will contine to look for another valid parent.
CAUSE: A content being indexed contains a reference to a sysobject parent that could not be fetched. The index code needed to fetch the parent object in order to index the content but could not. This may be the result of a parent_id value or index_parent value which points to a deleted sysobject. As long as another parent_id value can be found which points to a valid sysobject this error will not affect processing.
ACTION: Check for any other recent errors in the error log which may indicate the problem. Check the content object for consistent data.
PARAMS: %s – the object id of the sysobject which could not be fetched %s – the object id of the content object being indexed

ERROR: [DM_VERITY_COLL_E_PART2_UPDATE_FAIL]

SEVERITY: ERROR
DESCRIPTION: SSS Attempt to update partition index %s failed trying to %s partition %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_E_CANT_FETCH_CONTENT]

SEVERITY: ERROR
DESCRIPTION: S Error: cant fetch dmr_content object %s during fulltext index administration.
CAUSE: During full-text index processing, a failure occured fetching a content object to use in building the index. This content object will not be indexed.
ACTION: Check for any other recent errors in the error log which may indicate the problem.
PARAMS: %s – the object id of the content object being indexed

ERROR: [DM_VERITY_COLL_E_CANT_FIND_TYPE_INFO]

SEVERITY: ERROR
DESCRIPTION: S Cant determine ftindex attributes because internal type info not found for type: %s.
CAUSE: Internal error. Probable memory corruption.
ACTION: Report this error to your Documentum site representative.
PARAMS:

ERROR: [DM_VERITY_COLL_E_CANT_SET_COLLECTION]

SEVERITY: ERROR
DESCRIPTION: SSI Cant set collection for style %s on %s: Error code = %d.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_E_CANT_ADD_STYLE]

SEVERITY: ERROR
DESCRIPTION: SS Cant add style files to collection due to database error: %s. SQL statement: %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_E_CANT_SET_DOC_HANDLE]

SEVERITY: ERROR
DESCRIPTION: S Cant set the Verity document description for style %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_E_USE_FULL_PATHNAME]

SEVERITY: ERROR
DESCRIPTION: S The dump file (%s) must be specified by a full path name
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_E_ACTION]

SEVERITY: ERROR
DESCRIPTION: Check permission of file.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_E_TIMEOUT]

SEVERITY: ERROR
DESCRIPTION: LLS Timeout after %ld minutes attempting to index batch of size %ld of format %s
CAUSE: The indexing step took too long and was terminated. The batch will be marked as having failed.
ACTION: Attempt to retry the batch by doing a mark_for_retry and another update. If the problem is a looping or crashing filter, the subsequent update will generate another timeout.
PARAMS:

ERROR: [DM_VERITY_COLL_E_SOURCE_STYLE_FILE_OPEN_FAILED]

SEVERITY: ERROR
DESCRIPTION: S Could not open file %s for read
CAUSE: Check that the file exists.
ACTION: Contact Documentum support if file does not exist. PARAMETERS:File name
PARAMS:

ERROR: [DM_VERITY_COLL_E_DOC_NOT_INDEXED]

SEVERITY: ERROR
DESCRIPTION: SS Verity indexing failed for content %s (key %s).
CAUSE: The content may be bad, or may have caused the filter to crash or loop. Or, there may be nothing wrong with this content, just that it was indexed in a batch along with a bad content.
ACTION: Check the status file for other messages. mark_for_retry then rerun indexing with a smaller batch size.
PARAMS: %s – the object id of the content which failed %s – the verity key generated for that content

ERROR: [DM_VERITY_COLL_E_CAUSE]

SEVERITY: ERROR
DESCRIPTION: The process was unable to access the file identified by the file name.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_E_API_HANDLE_FAIL]

SEVERITY: ERROR
DESCRIPTION: S Attempt to build Verity API handle failed. Verity bin directory was %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_E_BAD_LOAD_FILE]

SEVERITY: ERROR
DESCRIPTION: S Load failed because file %s not found in index dump
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_E_CANT_CREATE_PHASE2_LOCKFILE]

SEVERITY: ERROR
DESCRIPTION: S Cant create the lock file for update phase II. Filename %s.
CAUSE: Out of space on disk, read-only filesystem or filesystem off-line, or other filesystem or disk problem.
ACTION: Look for operating system error messages.
PARAMS:

ERROR: [DM_VERITY_COLL_E_VDB_UPDATE]

SEVERITY: ERROR
DESCRIPTION: SS Attempt to update Verity VDB %s failed while updating partition %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_E_EMPTY_CONTENT]

SEVERITY: ERROR
DESCRIPTION: SS Content object %s has empty file identified by %s path.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_E_FTINDEX_DEADLOCK]

SEVERITY: ERROR
DESCRIPTION: The database is in the deadlock state, so no fulltext operations will be performed. Check for errors in the server and session logs.
CAUSE: Database error, deadlock state caused by external factors
ACTION: Examine database logs. Once error is resolved, rerun the fulltext operation.
PARAMS:

ERROR: [DM_VERITY_COLL_E_UPDATE_VERITY_INDEX_ERROR]

SEVERITY: ERROR
DESCRIPTION: I Verity indexing returned error. Code = %d.
CAUSE: Verity indexing error. Possible bad content or filter problem.
ACTION: Check the status file for other messages.
PARAMS: %d – the verity error return code

ERROR: [DM_VERITY_COLL_E_STYLE_FILE_ERROR]

SEVERITY: ERROR
DESCRIPTION: SS The line %s missing in %s file
CAUSE: The line is missing in file
ACTION: Contact Documentum support. PARAMETERS:line, File name
PARAMS:

ERROR: [DM_VERITY_COLL_E_CANT_MAKE_ROOT]

SEVERITY: ERROR
DESCRIPTION: Cant build root partition copy
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_E_CANT_MAKE_EMPTY_PARTITION]

SEVERITY: ERROR
DESCRIPTION: S Cant build empty Verity partition with name %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_E_COPY_ENC_STYLE_ARG_INVALID]

SEVERITY: ERROR
DESCRIPTION: Null arguments passed to function that adds decryption filters to style.uni file.
CAUSE: Internal error
ACTION: Contact Documentum support.
PARAMS:

ERROR: [DM_VERITY_COLL_E_NO_DIRECTORY]

SEVERITY: ERROR
DESCRIPTION: S Directory %s doesnt exist
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_E_CLEAR_PENDING_CANT_ACQUIRE_LOCK]

SEVERITY: ERROR
DESCRIPTION: S The clear pending method cant acquire the file lock for modifiying the index. Filename %s. Try again later.
CAUSE: Other fulltext activity, such as an update.
ACTION: Try again later.
PARAMS:

ERROR: [DM_VERITY_COLL_W_CANT_CONVERT]

SEVERITY: WARNING
DESCRIPTION: SS Cant convert content %s to format %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_W_NO_UPDATE_WORKDIR]

SEVERITY: WARNING
DESCRIPTION: S Directory %s does not exist. The fulltext index has probably never been updated before or does not exist.
CAUSE: The fulltext index has probably never been updated before or does not exist.
ACTION: Update the index to create a work directory.
PARAMS:

ERROR: [DM_VERITY_COLL_W_VERITY]

SEVERITY: WARNING
DESCRIPTION: S verity error/warning. message is: %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_W_NO_TYPE]

SEVERITY: WARNING
DESCRIPTION: S Cant process tdk collection because type %s was not found.
CAUSE: The type probably does not exist anymore. An orphaned content object that refers to a non-existing type may still exist.
ACTION: Run the DmClean job to remove all orphaned content objects.
PARAMS:

ERROR: [DM_VERITY_COLL_W_BAD_CONTENT]

SEVERITY: WARNING
DESCRIPTION: S Attempt to index content with id %s failed — Verity filter rejected content
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_W_NO_CONTENT]

SEVERITY: WARNING
DESCRIPTION: S Attempt to index content with non-existent id %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_W_CONTENT_OFFLINE]

SEVERITY: WARNING
DESCRIPTION: S Attempt to index offline content with id %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_W_CANNOT_PURGE_DIR]

SEVERITY: WARNING
DESCRIPTION: S During crash recovery phase, attempt to purge %s directory failed.
CAUSE: This is most likely caused by another process or resource holding possession on the directory or possibly an OS error.
ACTION: Look for OS error messages.
PARAMS:

ERROR: [DM_VERITY_COLL_W_NO_VERITY_FILE]

SEVERITY: WARNING
DESCRIPTION: No Verity Full-Text Engine messages will be logged in the status file.
CAUSE: Either the launch of the Verity Full-Text Engine (mkvdk) failed due to a probable OS resource problem, or the launch failed to create an output file containing Verity messages.
ACTION: Look for OS error messages.
PARAMS:

ERROR: [DM_VERITY_COLL_W_CANT_FIND_PHASE1_LOCKFILE]

SEVERITY: WARNING
DESCRIPTION: S Cant find the lock file for update phase I. Filename %s.
CAUSE: Unknown.
ACTION: Probably none necessary.
PARAMS:

ERROR: [DM_VERITY_COLL_W_NO_CURRENT_STATUS_FILE_DURING_UPDATE]

SEVERITY: WARNING
DESCRIPTION: An update is in progress but there is no current status file. The previous status file is returned.
CAUSE: The update may have terminated during the execution of the check_ftindex.
ACTION: Try again.
PARAMS:

ERROR: [DM_VERITY_COLL_T_UPDATE_PHASEIII_END]

SEVERITY: TRACE
DESCRIPTION: II End phase 3 (verification only) fulltext index update. Total successful docs: %d, total failed: %d.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_T_UPDATE_VERITY_INDEX_START]

SEVERITY: TRACE
DESCRIPTION: Begin Verity indexing. Verity messages (if any) begin here.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_T_UPDATE_BATCH_START]

SEVERITY: TRACE
DESCRIPTION: II Begin Verity indexing: epoch %d batch %d.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_T_UPDATE_CRASH_RECOVERY_NORMAL]

SEVERITY: TRACE
DESCRIPTION: No evidence of previous crash found.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_T_UPDATE_MAKE_BATCH_FILE_START]

SEVERITY: TRACE
DESCRIPTION: I Begin making batch file for batch %d.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_T_UPDATE_DESC_FILE]

SEVERITY: TRACE
DESCRIPTION: Contents of descriptor file follow this message:
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_T_UPDATE_GET_CONTENT_END]

SEVERITY: TRACE
DESCRIPTION: End executing sql cursor to get pending content objects.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_T_UPDATE_PHASEI_END]

SEVERITY: TRACE
DESCRIPTION: II End phase 1 fulltext index update. total good: %d total bad: %d.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_T_UPDATE_CRASH_BATCH_START]

SEVERITY: TRACE
DESCRIPTION: II Being processing crashed batch file: epoch %d batch %d.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_T_UPDATE_GET_CONTENT_START]

SEVERITY: TRACE
DESCRIPTION: Begin executing sql cursor to get pending content objects.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_T_UPDATE_DIR_SEARCH_START]

SEVERITY: TRACE
DESCRIPTION: Searching work directory.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_T_UPDATE_GET_BATCH_START]

SEVERITY: TRACE
DESCRIPTION: I Begin processing batch %d of pending contents.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_T_UPDATE_COLLECTION_END]

SEVERITY: TRACE
DESCRIPTION: SI End processing collection with object type %s at position %d.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_T_UPDATE_CRASH_BATCH_END]

SEVERITY: TRACE
DESCRIPTION: II End processing crashed batch file: epoch %d batch %d.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_T_UPDATE_PHASEI_START]

SEVERITY: TRACE
DESCRIPTION: Begin phase 1 fulltext index update.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_T_UPDATE_BATCH_DESC]

SEVERITY: TRACE
DESCRIPTION: SI Batch collection dir %s, size %d.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_T_UPDATE_VERITY_BATCH_FILE]

SEVERITY: TRACE
DESCRIPTION: Contents of Verity batch file follow this message:
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_T_UPDATE_VERITY_INDEX_END]

SEVERITY: TRACE
DESCRIPTION: S End Verity indexing. Return value: %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_T_UPDATE_GET_BATCH_END]

SEVERITY: TRACE
DESCRIPTION: I End processing batch %d of pending contents.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_T_UPDATE_PHASEII_END]

SEVERITY: TRACE
DESCRIPTION: II End phase 2 fulltext index update. Total successful docs: %d, total failed: %d.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_T_UPDATE_CRASH_RECOVERY_START]

SEVERITY: TRACE
DESCRIPTION: Begin update crash recovery phase.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_T_UPDATE_MAKE_BATCH_FILE_END]

SEVERITY: TRACE
DESCRIPTION: I End making batch file for batch %d.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_T_UPDATE_CRASH_FOUND_RUNNING_BATCH]

SEVERITY: TRACE
DESCRIPTION: IISI The UPDATE_FTINDEX method has found a running batch file (epoch=%d batch=%d) from a previous update run on fulltext index %s and will examine if a previous failure occured. Please refer to the most recent status file in the fulltext working directory to see if any objects failed indexing from the previous run. If failed objects are reported and you wish to reindex these objects, use the MARK_FOR_RETRY method with update_count=%d.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_T_UPDATE_VERIFY_DOCS_START]

SEVERITY: TRACE
DESCRIPTION: I Begin verifying contents in batch %d.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_T_UPDATE_COLLECTION_START]

SEVERITY: TRACE
DESCRIPTION: SI Begin processing collection with object type %s at position %d.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_T_UPDATE_VERIFY_DOCS_END]

SEVERITY: TRACE
DESCRIPTION: I End verifying contents in batch %d.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_T_UPDATE_PHASEII_START]

SEVERITY: TRACE
DESCRIPTION: Begin phase 2 fulltext index update.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_T_UPDATE_CRASH_RECOVERY_END]

SEVERITY: TRACE
DESCRIPTION: End update crash recovery phase.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_T_UPDATE_BATCH_END]

SEVERITY: TRACE
DESCRIPTION: II End Verity indexing: successful docs: %d, failed: %d.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_T_UPDATE_CANT_RENAME_BATCH_FILE]

SEVERITY: TRACE
DESCRIPTION: SSI The UPDATE_FTINDEX method was unable to rename batch file %s for fulltext index %s. All contents in this batch will not be indexed and are marked as failed. Please refer to the most recent status file in the fulltext working directory to see the failed objects. If failed objects are reported and you wish to reindex these objects, use the MARK_FOR_RETRY method with update_count=%d.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_T_UPDATE_PHASEIII_START]

SEVERITY: TRACE
DESCRIPTION: Begin phase 3 (verification only) fulltext index update.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_I_FTINDEX_IN_PROGRESS]

SEVERITY: INFORMATION
DESCRIPTION: I Another fulltext operation is currently in progress on this fulltext index with epoch %d.
CAUSE:
ACTION:
PARAMS:

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: