6.6-dm_content
DM_CONTENT
ERROR: [DM_CONTENT_F_SAVE_PROBLEM_MARK_ALL_SKIPPING]
SEVERITY: FATAL
DESCRIPTION: S Mark all cant save content object %s. Skipping.
CAUSE: Internal problem.
ACTION: Examine this object. It will not be indexable.
PARAMS:
ERROR: [DM_CONTENT_F_SUBCONTENT_TYPE_CONVERSION]
SEVERITY: FATAL
DESCRIPTION: I Failed to convert type dmi_subcontent to version %d.
CAUSE: Either the version stamp of the type was not set successfully or the changes done to convert the type failed.
ACTION: Examine the type. Contact documentum support if needed.
PARAMS: The version stamp of the type being converted into.
ERROR: [DM_CONTENT_F_MARK_ALL_DBERROR]
SEVERITY: FATAL
DESCRIPTION: S Mark all failed with the database error: %s
CAUSE: There is a problem with the database cursor.
ACTION: Turn on the MARK_ALL trace option and rerun the method. Also examine the database log for any error messages. $Id: dmcrypto.e,v 5.24 2003/06/17 19:36:24 ganeshv Exp $ Crypto module errors
PARAMS:
ERROR: [DM_CONTENT_F_TRANS_CREATE_PROBLEM_MARK_ALL_FAILED]
SEVERITY: FATAL
DESCRIPTION: Cant start RDBMS transaction during MARK_ALL.
CAUSE: A problem with the RDBMS.
ACTION: Check error logs.
PARAMS:
ERROR: [DM_CONTENT_F_SUBCONTENT_INIT]
SEVERITY: FATAL
DESCRIPTION: II Version stamp %d was expected to be %d.
CAUSE: The version stamp of the type from the database does not match any possible versions the type can have in the software.
ACTION: You must upgrade your DocuServer database to conform to the software that you are running. If your software and data are consistent, then report a bug. Also, Report this message and any parameters to your Documentum site representative.
PARAMS: The version stamp of the type from the database. The current version stamp of the type.
ERROR: [DM_CONTENT_F_COMMIT_PROBLEM_MARK_ALL_FAILED]
SEVERITY: FATAL
DESCRIPTION: RDBMS transaction commit failed during MARK_ALL.
CAUSE: A problem with the RDBMS.
ACTION: Check error logs.
PARAMS:
ERROR: [DM_CONTENT_E_STREAM_NO_FD]
SEVERITY: ERROR
DESCRIPTION: S Error: Could not get file descriptor from open fstream on file (%s).
CAUSE: A failure occurred from a stream call to extract the file descriptor for direct file io. This may indicate that the file was not actually open as the code assumed. Previous error messages may give more information on the exact problem.
ACTION: Check permissions to open or create the file. Check available disk space. Report this problem to Documentum Technical Support. Include any other error messages logged along with this one.
PARAMS: The name of the open file.
ERROR: [DM_CONTENT_E_NULL_STORE]
SEVERITY: ERROR
DESCRIPTION: S Storage object for content with id %s was null
CAUSE: An attempt was made to store content without setting the storage id
ACTION: Internal programming error
PARAMS: The id of the storage object
ERROR: [DM_CONTENT_E_MIGRATE_CONTENT_UNABLE_TO_VERIFY_RETENTION_BY_RETAINERS]
SEVERITY: ERROR
DESCRIPTION: S Unable to verify whether i_retain_until was set by retainers for content id (%s)
CAUSE: Most likely due to database errors
ACTION: Run the query manually on the object id
PARAMS: The object id of the content obejct
ERROR: [DM_CONTENT_E_OFFLINE_RESTORE]
SEVERITY: ERROR
DESCRIPTION: S Content is being restored to storage area %s — try later
CAUSE:
ACTION:
PARAMS:
ERROR: [DM_CONTENT_E_MIGRATE_CONTENT_INSUFFICIENT_ARGUMENTS]
SEVERITY: ERROR
DESCRIPTION: Insufficient arguments specified for content migration.
CAUSE: Insufficient arguments specified for content migration, no obvious values specified to identify the content objects to be migrated.
ACTION: Refer to the Administration Manual on MIGRATE_METHOD for argument values.
PARAMS:
ERROR: [DM_CONTENT_E_CANT_OPEN_SESSION]
SEVERITY: ERROR
DESCRIPTION: S Could not establish session to content server for docbase %s. During a content operation, an attempt was made to find the closest content server in a distributed content environment. The attempt to connect to the content server failed.
CAUSE: Could not connect to the content server.
ACTION: Check that the content server is still available.
PARAMS: %s – docbase name
ERROR: [DM_CONTENT_E_HASH_CANT_CREATE_CRYPTO_DIGEST]
SEVERITY: ERROR
DESCRIPTION: S Failed to successfully initialize the cryptographic hashing function for algorithm %s.
CAUSE: The cryptographic library hashing function did not initialize.
ACTION: Verify that trusted content services are enabled.
PARAMS:
ERROR: [DM_CONTENT_E_OPEN_FAILURE]
SEVERITY: ERROR
DESCRIPTION: SS Error opening file (%s). Operating System error: (%s).
CAUSE: Attempt to open the named file failed. The operating system error should give a better indication of the actual problem.
ACTION: Check if the indicated file exists check permissions to open or create the file.
PARAMS: The name of the file which could not be opened and a formatted OS error status.
ERROR: [DM_CONTENT_E_CLOSE_FAILURE]
SEVERITY: ERROR
DESCRIPTION: SS Error closing output file (%s). Operating System error: (%s).
CAUSE: A failure occurred while writing content from a new content file. The operating system error should give a better indication of the actual problem.
ACTION: Check available disk space.
PARAMS: The name of the new content file. OS error status.
ERROR: [DM_CONTENT_E_MIGRATE_CONTENT_INVALID_TARGET_STORE3]
SEVERITY: ERROR
DESCRIPTION: S The target store specified %s is not a supported target storage type
CAUSE: This error occurs when the target_store specified for MIGRATE_CONTENT apply method is not a supported storage type.
ACTION: Specify a target_store that is either a dm_filestore type or a dm_ca_store type or a dm_distributedstore.
PARAMS:
ERROR: [DM_CONTENT_E_MIGRATE_CONTENT_MISSING_LOG_FILE]
SEVERITY: ERROR
DESCRIPTION: If REMOVE_ORIGINAL argument is set to F (OR) SOURCE_STORE and TARGET_STORE specified (OR) QUERY is specified, you must specify LOG_FILE argument.
CAUSE: User did not specify LOG_FILE argument. User should specify a LOG_FILE argument value if both SOURCE_STORE and TARGET_STORE values are specified (OR) QUERY value is specified (OR) REMOVE_ORIGINAL argument is set to F.
ACTION: Specify a valid filename for LOG_FILE argument and retry migrate.
PARAMS:
ERROR: [DM_CONTENT_E_STREAM_COPY_FAILURE]
SEVERITY: ERROR
DESCRIPTION: SI Stream copy to content file (%s) failed at position %d.
CAUSE: A failure occurred while copying a data stream to a new content file. Previous error messages should have given more information on the nature of the problem.
ACTION: Check permissions to open or create the new file. Check available disk space.
PARAMS: The name of the new content file. How far along the operation proceeded before failing.
ERROR: [DM_CONTENT_E_READ_FAILURE]
SEVERITY: ERROR
DESCRIPTION: S Error reading content data from file or stream. Operating System error: (%s).
CAUSE: A failure occurred while reading content from an open content file or from an open data stream. The operating system error should give a better indication of the actual problem. Further context on the error (whether it was a file or stream error) will likely be indicated by the next error message.
ACTION: Check if the indicated file exists check permissions to open or create the file.
PARAMS: OS error status.
ERROR: [DM_CONTENT_E_UPDATE_OTHER_FILE_SIZE_WRONG_ARGUMENTS]
SEVERITY: ERROR
DESCRIPTION: SS Wrong arguments are specified for updating other file size. %s is not allowed when %s is specified.
CAUSE: Arguments are wrong when call UPDATE_OTHERFILE_SIZE apply method.
ACTION: Refer to admin mannual to specify correct arguments for this apply method.
PARAMS:
ERROR: [DM_CONTENT_E_SECUREWRITE_ERROR]
SEVERITY: ERROR
DESCRIPTION: SS Failure to create content file copy (%s) due to an error returned by the Secure Writer program (%s). Check the server error log for additional information logged by the Secure Writer.
CAUSE: A failure occurred during an attempt to copy a file to the common area. The server is configured to use the secure writer program for this action so the secure writer program was called to create the file, but the pclose call to obtain the program status failed.
ACTION: Check the server process error log for error messages since any messages logged by the secure writer program will go there rather than the session error log. Check for system resource shortages that may prevent the server from being able to open a pipe or fork a process. Check the existence and permissions of the Secure Writer program and the permissions of the common area directory.
PARAMS: The output file which the secure writer should have created. The operating system error status returned by the secure writer program.
ERROR: [DM_CONTENT_E_CANT_OPEN]
SEVERITY: ERROR
DESCRIPTION: S Could not open file (%s).
CAUSE:
ACTION:
PARAMS:
ERROR: [DM_CONTENT_E_DIRECT_COPY_OR_MOVE_FOR_EXTERNALSTORE]
SEVERITY: ERROR
DESCRIPTION: DIRECT_COPY and DIRECT_MOVE are mutually exclusive when migrating from an external store.
CAUSE: You specified both DIRECT_COPY and DIRECT_MOVE when migrating contents from an external store.
ACTION: Specify only one of these flags.
PARAMS:
ERROR: [DM_CONTENT_E_MIGRATE_CONTENT_ROLLBACK]
SEVERITY: ERROR
DESCRIPTION: Migration rolled back due to errors.
CAUSE: Check other messages
ACTION: fix the cause of the errors as reported by other messages in the log and retry the apply method.
PARAMS:
ERROR: [DM_CONTENT_E_NAME_CONFLICT]
SEVERITY: ERROR
DESCRIPTION: Name conflict with an existing migration job
CAUSE: Name conflict with an existing migration job
ACTION: Change the job name
PARAMS:
ERROR: [DM_CONTENT_E_MIGRATE_CONTENT_DB_ERROR]
SEVERITY: ERROR
DESCRIPTION: SSS A database error occured during migrate content, Operation is %s, Query is %s, Error from database is %s
CAUSE:
ACTION:
PARAMS:
ERROR: [DM_CONTENT_E_SOURCE_STORE_NEED_AUTHENTICATION]
SEVERITY: ERROR
DESCRIPTION: Authentication is required to access contents from the source store.
CAUSE: The source store is an external store that requires authentication, perhaps a login, but you are not authenticated.
ACTION: Log in to the external store before migrating the content either through external storage plug-in or through OS.
PARAMS:
ERROR: [DM_CONTENT_E_MIGRATE_CONTENT_INCOMPATIBLE_STORES_FOR_FULLTEXT_INDEX2]
SEVERITY: ERROR
DESCRIPTION: SISSSSSS Current store %s of page %d of parent object %s of content object %s is not compatible with the target store %s. Content object for page 0 is %s. Store %s has a dm_fulltext_index object whereas %s does not have one.
CAUSE: When migrating a content object that represents page 0 of a parent that has multiple pages, the current storage of those non-zero pages should be compatible with the target store for full-text indexing.
ACTION: Create the dm_fulltext_index object for the store that doesnt have one and retry migration.
PARAMS:
ERROR: [DM_CONTENT_E_MIGRATE_CONTENT_UNABLE_TO_SAVE_PARENT]
SEVERITY: ERROR
DESCRIPTION: SS Unable to save parent object %s of content object %s
CAUSE: A database error occured while trying to save a parent object
ACTION: Fix the cause of the database error and retry migrate
PARAMS:
ERROR: [DM_CONTENT_E_UNABLE_TO_MIGRATE_DUE_TO_EBR]
SEVERITY: ERROR
DESCRIPTION: D The content object id %s with conditional retention cannot be migrated to another CA Store.
CAUSE: Cannot migrate content from CA Store to CA store if the content object has a conditional retainer with no retention date set attached to it and remove_original is set to True in the migration arguments.
ACTION: Not Supported.
PARAMS:
ERROR: [DM_CONTENT_E_PURGE_FAILED]
SEVERITY: ERROR
DESCRIPTION: S Content purge failed because %s
CAUSE:
ACTION:
PARAMS:
ERROR: [DM_CONTENT_E_JOBNAME_REQUIRED]
SEVERITY: ERROR
DESCRIPTION: you must specify the name of the job which you want to stop
CAUSE: The JOB_NAME is missing or undefined.
ACTION: Specify the name of the job with the JOB_NAME parameter.
PARAMS:
ERROR: [DM_CONTENT_E_MISSING_PROPERTY]
SEVERITY: ERROR
DESCRIPTION: S The property file (%s) is missing some required property.
CAUSE: The property file is required to contain the following three items for each component file in the sequence: 1) file_name= 2) page_modifier= 3) parameters=
ACTION: Check the property file and make sure all required properties are supplied.
PARAMS:
ERROR: [DM_CONTENT_E_GDWM_MISSING_PARAMETERS]
SEVERITY: ERROR
DESCRIPTION: S Required parameter(s) %s missing or invalid from GET_DIST_WRITE_MAP
CAUSE: Required parameters were not supplied to the GET_DIST_WRITE_MAP server api call.
ACTION: Refer to the server documentation for the required parameters
PARAMS:
ERROR: [DM_CONTENT_E_MIGRATE_CONTENT_INVALID_USER]
SEVERITY: ERROR
DESCRIPTION: S User %s does not have super user permission
CAUSE: User does not have super user privileges to run the
ACTION:
PARAMS:
ERROR: [DM_CONTENT_E_GDCM_NO_READ_ACCESS]
SEVERITY: ERROR
DESCRIPTION: D Read Access is not permited to this user for sysobject %s
CAUSE: Read access has not been given to this user for this object.
ACTION: Use the Documentum Administrator to check the permission sessions on your types.
PARAMS:
ERROR: [DM_CONTENT_E_MIGRATE_CONTENT_NOT_A_FILESTORE]
SEVERITY: ERROR
DESCRIPTION: S %s is not a dm_filestore object
CAUSE: User specified storage object name for either SOURCE_STORE or TARGET_STORE which is not of dm_filestore type.
ACTION: Specify the argument value thats a filestore.
PARAMS:
ERROR: [DM_CONTENT_E_CANT_OPEN_OTHER]
SEVERITY: ERROR
DESCRIPTION: S Error opening resource fork for file (%s).
CAUSE: An error occurred opening the resource fork for a macintosh file.
ACTION: Check other error messages in the session log. A previous error message should indicate a specific reason for the failure.
PARAMS: %1s The name of the input file.
ERROR: [DM_CONTENT_E_CONTENT_SAVE_FAILURE]
SEVERITY: ERROR
DESCRIPTION: DS Save of content object %s failed. Reason: %s
CAUSE:
ACTION:
PARAMS:
ERROR: [DM_CONTENT_E_NEXTBLOCK_READ]
SEVERITY: ERROR
DESCRIPTION: I Error reading NextBlock data. Netwise error code = %d.
CAUSE: A failure occurred while performing a network read for a NextBlock operation. The netwise error code will give a more detailed indication of the actual problem.
ACTION: The network Administrator should check the status of their network
PARAMS: The netwise error code.
ERROR: [DM_CONTENT_E_FORMAT_NOT_INDEXABLE]
SEVERITY: ERROR
DESCRIPTION: S Content cant be indexed — format was %s
CAUSE:
ACTION:
PARAMS:
ERROR: [DM_CONTENT_E_MAC_SET_TC]
SEVERITY: ERROR
DESCRIPTION: SS Error setting Type/Creator information on a Macintosh file (%s). Operating System error: (%s).
CAUSE: A error returned from a request to set the type and creator information on a macintosh content data file.
ACTION: Check if the indicated file exists check permissions to open or write to the file.
PARAMS: %1s The name of the file which was being changed. %2s A formatted OS error status.
ERROR: [DM_CONTENT_E_REPLACE_FAILED_WORKER]
SEVERITY: ERROR
DESCRIPTION: A parallel content migration had to be restarted due to an internal error. Some content may have failed to be migrated.
CAUSE: A worker session has failed due to an internal error.
ACTION: Verify state of content being migrated, a new request may be required to complete the migration.
PARAMS:
ERROR: [DM_CONTENT_E_MIGRATE_CONTENT_UNABLE_TO_SAVE_CONTENT_OBJECT]
SEVERITY: ERROR
DESCRIPTION: S Unable to save content object %s after migration.
CAUSE: A database error occured while attempting to save the content object
ACTION: Fix the cause of the database error and retry migrate.
PARAMS:
ERROR: [DM_CONTENT_E_GDWM_NO_WRITE_LOCATIONS]
SEVERITY: ERROR
DESCRIPTION: S No write locations found for storage %s
CAUSE: There is a problem with the configuration of your docbase servers
ACTION: Determine what store(s) your content resides on and make sure that the store(s) is accessible to at least one ACS server.
PARAMS:
ERROR: [DM_CONTENT_E_CANT_START_COPY]
SEVERITY: ERROR
DESCRIPTION: S Could not start content copy into file %s
CAUSE:
ACTION:
PARAMS:
ERROR: [DM_CONTENT_E_UPDATE_OTHER_FILE_SIZE_FILE_ACCESS_ERROR]
SEVERITY: ERROR
DESCRIPTION: SS The other file %s is unaccessible. The reason is: %s.
CAUSE: The file store failed to access the other file due to some os error.
ACTION: Check the error message to find the exact cause.
PARAMS:
ERROR: [DM_CONTENT_E_GDCDS_ACS_CRYPTO_KEY_NOT_VALID]
SEVERITY: ERROR
DESCRIPTION: I The ACS Cryptographic key is not valid. Status = %d
CAUSE: The system was unable verify the Cryptographic key used with ACS Distributed Content access
ACTION: Restart your server
PARAMS:
ERROR: [DM_CONTENT_E_MIGRATE_CONTENT_INVALID_CONTENT_FILE]
SEVERITY: ERROR
DESCRIPTION: S The content file for dmr_content object %s is invalid or not found or inaccessible.
CAUSE: The content file for the specified dmr_content object is not found in the current storage.
ACTION: Check other messages for the path of the file that could not be accessed or not found. Rectify the error and re-run the MIGRATE_CONTENT method.
PARAMS:
ERROR: [DM_CONTENT_E_CANT_START_PUSH]
SEVERITY: ERROR
DESCRIPTION: D Could not begin content transfer for content object %s. A failure occurred in an attempt to store content to the docbase. The client was unable to initiate the content transfer mechanism.
CAUSE: Could not start content push operation.
ACTION: Check for other errors that give more detail on the problem.
PARAMS: %s – The target content object id.
ERROR: [DM_CONTENT_E_STREAM_COPY_FAIL]
SEVERITY: ERROR
DESCRIPTION: SI Stream copy to file %s failed at position %i
CAUSE:
ACTION:
PARAMS:
ERROR: [DM_CONTENT_E_STORAGE_UNKNOWN]
SEVERITY: ERROR
DESCRIPTION: S This problem may be caused by a dumpfile inconsistency. The load process was likely unable to locate the object which describes the storage area for content object %s in the dumpfile.
CAUSE: A failure occurred during load of a content object because the the content information was inconsistent. The Storage ID of the loaded content object was zero. This may have been caused by the dumpfile not having an object entry for the storage area in which the content resided. If this is the case then the loaded content object will have its storage area reset to null – causing this error later.
ACTION: Check the dumpfile for the existence of the storage area object. If possible check any logs from when the dump operation was performed to see if errors were reported then.
PARAMS: The object id of the content object which cannot be loaded.
ERROR: [DM_CONTENT_E_NOT_STORE]
SEVERITY: ERROR
DESCRIPTION: S Storage object with id %s does not exist
CAUSE: The storage object referenced in when storing or fetching content does not exits
ACTION: Check that the storage object should exist
PARAMS: The id of the storage object
ERROR: [DM_CONTENT_E_WRITE_FAILURE]
SEVERITY: ERROR
DESCRIPTION: SS Error writing data to content file (%s). Operating System error: (%s).
CAUSE: A failure occurred while writing content from a new content file. The operating system error should give a better indication of the actual problem.
ACTION: Check permissions to open or create the file. Check available disk space.
PARAMS: The name of the new content file. OS error status.
ERROR: [DM_CONTENT_E_MIGRATE_CONTENT_CANT_SPECIFY_SOURCE_STORE_AND_QUERY]
SEVERITY: ERROR
DESCRIPTION: Invalid arguments. Cannot specify both SOURCE_STORE and QUERY arguments.
CAUSE: User specified argument values for SOURCE_STORE as well as QUERY.
ACTION: Specify either SOURCE_STORE or the QUERY argument value and retry migrate
PARAMS:
ERROR: [DM_CONTENT_E_REPDT_FIX]
SEVERITY: ERROR
DESCRIPTION: S Error in startup consistency check for replica data_tickets. Query check: %s.
CAUSE: A error returned from a query which is used in server startup to check for replica data ticket corruption.
ACTION: The consistency check can be bypassed by creating an entry in dmi_vstamp for replica_dataticket_fix. But this should be done only if the data_tickets are known to be correct and the consistency check can be skipped.
PARAMS: %1s The query used for the consistency check.
ERROR: [DM_CONTENT_E_SOURCE_NOT_OPEN]
SEVERITY: ERROR
DESCRIPTION: Error: input source is not open.
CAUSE: An error occurred in the use of an internal buffer source. The source was unexpectedly not open. Previous error messages may give more information on the exact problem.
ACTION: Report this problem to Documentum Technical Support. Include any other error messages logged along with this one.
PARAMS: None
ERROR: [DM_CONTENT_E_SOURCE_READ_ERROR]
SEVERITY: ERROR
DESCRIPTION: Error: input source could not be read.
CAUSE: An error occurred in the use of an internal buffer source. The source could not be read. Previous error messages may give more information on the exact problem.
ACTION: Report this problem to Documentum Technical Support. Include any other error messages logged along with this one.
PARAMS: None
ERROR: [DM_CONTENT_E_MIGRATE_CONTENT_INVALID_CURRENT_STORE2]
SEVERITY: ERROR
DESCRIPTION: S Current storage for %s is not a dm_filestore or a dm_ca_store
CAUSE: User attempted to migrate a content object whose current storage is not a filestore or a dm_ca_store
ACTION: You can migrate content objects residing in a filestore or a dm_ca_store only using the MIGRATE_CONTENT apply method.
PARAMS:
ERROR: [DM_CONTENT_E_UPDATE_OTHER_FILE_SIZE_INVALID_STORAGE_NAME]
SEVERITY: ERROR
DESCRIPTION: S Storage name %s is invalid.
CAUSE: There is no storage object in the repository with the specified name.
ACTION: Specify a correct storage name in the argument.
PARAMS:
ERROR: [DM_CONTENT_E_ACS_CONFIGURATION]
SEVERITY: ERROR
DESCRIPTION: SD ACS object named %s contains an invalid id %s on svr_config_id
CAUSE: The ACS object has config_type of 1 yet the value of svr_config_id does not correctly identify a dm_server_config object.
ACTION: Set the value of svr_config_id to the current version of the dm_server_config object.
PARAMS:
ERROR: [DM_CONTENT_E_NO_PARTITION]
SEVERITY: ERROR
DESCRIPTION: SS Content with id %s marked for indexing no partition for format %s exists
CAUSE:
ACTION:
PARAMS:
ERROR: [DM_CONTENT_E_MIGRATE_CONTENT_SAME_STORE]
SEVERITY: ERROR
DESCRIPTION: SS Incorrect argument: SOURCE_STORE %s is same as TARGET_STORE %s
CAUSE: User specified the same store name for both source and target
ACTION: Specify a valid SOURCE_STORE and a different valid value for TARGET_STORE.
PARAMS:
ERROR: [DM_CONTENT_E_TRANSFER_ABORTED]
SEVERITY: ERROR
DESCRIPTION: S The content transfer %s the server was aborted by the user
CAUSE:
ACTION:
PARAMS:
ERROR: [DM_CONTENT_E_NOT_ORPHAN]
SEVERITY: ERROR
DESCRIPTION: SS %s is not an orphan subcontent object. Parent is %s
CAUSE:
ACTION:
PARAMS:
ERROR: [DM_CONTENT_E_MIGRATE_CONTENT_INVALID_CURRENT_STORE]
SEVERITY: ERROR
DESCRIPTION: S Current storage for %s is not a dm_filestore
CAUSE: User attempted to migrate a content object whose current storage is not a filestore
ACTION: You can migrate content objects residing in a filestore only using the MIGRATE_CONTENT apply method.
PARAMS:
ERROR: [DM_CONTENT_E_BAD_PAGE_NO]
SEVERITY: ERROR
DESCRIPTION: I Page number %d is invalid
CAUSE:
ACTION:
PARAMS:
ERROR: [DM_CONTENT_E_SYNC_FAILURE]
SEVERITY: ERROR
DESCRIPTION: SS Error forcing new content data to physical storage for file (%s). Operating System error: (%s).
CAUSE: A failure occurred while writing content to a new file on an fsync command. The operating system error should give a better indication of the actual problem.
ACTION: Check permissions to open or create the file. Check available disk space.
PARAMS: The name of the new content file. OS error status.
ERROR: [DM_CONTENT_E_CANT_FETCH]
SEVERITY: ERROR
DESCRIPTION: S Content in storage area %s is not available
CAUSE:
ACTION:
PARAMS:
ERROR: [DM_CONTENT_E_CANNOT_INDEX_CA_STORE_WITH_NULL_IP]
SEVERITY: ERROR
DESCRIPTION: S Content in the content addressable store %s cannot be indexed, since it contains a NULL ip address.
CAUSE: The value of a_storage_params at zeroth position indicates the IP address of the content addressable store, and it is NULL.
ACTION: Make sure that the value of a_storage_params at the zeroth postion of the content addressable store contains a valid IP address.
PARAMS:
ERROR: [DM_CONTENT_E_UPDATE_OTHER_FILE_SIZE_INVALID_CONTENT_ID]
SEVERITY: ERROR
DESCRIPTION: D %s is not a valid content id.
CAUSE: The id of the content is not a valid content id.
ACTION: Specify a valid content id in the parameter.
PARAMS:
ERROR: [DM_CONTENT_E_GDCDS_NO_ACS_CRYPTO_KEY]
SEVERITY: ERROR
DESCRIPTION: I Cannot get the ACS Cryptographic key for Distributed Content. This is expected during docbase creation and the ACS Cryptographic system will be initialized by each session as needed. This error is unexpected once docbase creation is complete. Status = %d
CAUSE: The system was unable to find or generate the Cryptographic key used with ACS Distributed Content access
ACTION: Restart your server
PARAMS:
ERROR: [DM_CONTENT_E_CREATE_CM_WORKER_SESSION]
SEVERITY: ERROR
DESCRIPTION: Creating content migration worker session fails.
CAUSE: Not enough memory or too many threads/processes
ACTION: Release memory or threads/processes
PARAMS:
ERROR: [DM_CONTENT_E_TICKET_INDEX]
SEVERITY: ERROR
DESCRIPTION: S Error creating dmr_content index on attribute %s.
CAUSE: An error occurred while creating the data or other ticket indexes on dmr_content. Indexes are created on this object for use by filescan. The indexes are cleaned up either by the completion of filescan or by server initialization. This message indicates an error occurred during the initialization of filescan when the indexes are created.
ACTION: Check server error log for further indication of the error.
PARAMS:
ERROR: [DM_CONTENT_E_GDCM_MISSING_PARAMETERS]
SEVERITY: ERROR
DESCRIPTION: Required Parameters are missing from GET_DIST_CONTENT_MAP
CAUSE: Required parameters were not supplied to the GET_DIST_CONTENT_MAP server api call.
ACTION: Refer to the server documentation for the required parameters
PARAMS:
ERROR: [DM_CONTENT_E_REMOVE_FAILED]
SEVERITY: ERROR
DESCRIPTION: S Attempt to remove directory %s failed couldnt fork process
CAUSE:
ACTION:
PARAMS:
ERROR: [DM_CONTENT_E_FILE_INFO_FAILURE]
SEVERITY: ERROR
DESCRIPTION: SS Error: failed to obtain file information for file (%s). Operating System error: (%s).
CAUSE: An error occurred attempting to obtain file information (size etc) for a file.
ACTION: Check the file name and your access to the file and the directory that contains it.
PARAMS: file and and oss error.
ERROR: [DM_CONTENT_E_GDWM_NO_WRITE_ACCESS]
SEVERITY: ERROR
DESCRIPTION: SS Write Access is not permited to user %s for storage %s
CAUSE: This user does not have permission to create objects in the docbase.
ACTION: Use the Documentum Administrator to check user_privileges for this user.
PARAMS:
ERROR: [DM_CONTENT_E_GDCM_CONTENT_NOT_ACCESSIBLE]
SEVERITY: ERROR
DESCRIPTION: Content is available for this object but it is not accessible via HTTP
CAUSE: There is a problem with the configuration of your docbase servers
ACTION: Determine what store(s) your content resides on and make sure that the store(s) is accessible to at least one ACS server.
PARAMS:
ERROR: [DM_CONTENT_E_MIGRATE_CONTENT_STORAGE_IS_A_COMPONENT]
SEVERITY: ERROR
DESCRIPTION: S Storage object %s is a component of a distributed store. Migration disallowed.
CAUSE: The storage object of a content object being migrated is a component of a distributed store. MIGRATE_CONTENT apply method does not currently support migrating such a content object.
ACTION: If you specified TARGET_STORE and/or SOURCE_STORE argument, specify the name of a dm_filestore object which is not a component of a dm_distributed_store object. If you specified the id of a dmr_content object, specify the id a dmr_content object whose storage is a dm_filestore which is not a component of a dm_distributed_store object. If you specified value for QUERY argument, make sure the DQL predicate expression does not select dmr_content objects that currently reside in a distributed store.
PARAMS:
ERROR: [DM_CONTENT_E_PUSH_CONTENT_DB_ERROR]
SEVERITY: ERROR
DESCRIPTION: SSS A database error occured during push content, Operation is %s, Query is %s, Error from database is %s
CAUSE: The likely cause is a database error.
ACTION: Use the reported database error to identify the source of the problem.
PARAMS:
ERROR: [DM_CONTENT_E_GDCM_NO_CONTENT_EXISTS]
SEVERITY: ERROR
DESCRIPTION: DISS There is no content for sysobject %s, page number %d, page modifier %s, and format %s
CAUSE: There isnt any content for this object using the page number, page modifier and format given.
ACTION: Check the object to see what content exists, and what page number, page modifier and formats are used.
PARAMS:
ERROR: [DM_CONTENT_E_TICKET_DROPINDEX]
SEVERITY: ERROR
DESCRIPTION: S Error dropping dmr_content index with dmi_index id %s.
CAUSE: An error occurred while cleaning up data and other ticket indexes on dmr_content. Indexes are created on this object for use by filescan. The indexes are cleaned up either by the completion of filescan or by server initialization. This message indicates an error occurred during this cleanup.
ACTION: Check server error log for further indication of the error.
PARAMS:
ERROR: [DM_CONTENT_E_MIGRATE_CONTENT_UNABLE_TO_UPDATE_RETAIN_UNTIL_DATE]
SEVERITY: ERROR
DESCRIPTION: SSIS Error updating i_retain_until attribute of %s while migrating content object %s, that represents page %d of %s Cause: A database error occured while updating the i_retain_until attribute.
CAUSE:
ACTION: Refer to the action associated with the reported database error
PARAMS:
ERROR: [DM_CONTENT_E_FILE_READ_FAILED]
SEVERITY: ERROR
DESCRIPTION: S Attempt to read from file %s failed
CAUSE:
ACTION:
PARAMS:
ERROR: [DM_CONTENT_E_NO_PATH_FOR_CONTENT]
SEVERITY: ERROR
DESCRIPTION: S No file path exists for content %s
CAUSE:
ACTION:
PARAMS:
ERROR: [DM_CONTENT_E_MIGRATE_CONTENT_INCOMPATIBLE_STORES_FOR_FULLTEXT_INDEX]
SEVERITY: ERROR
DESCRIPTION: SS Source store % has a dm_fulltext_index object. But the target store %s does not.
CAUSE: Storage areas must be compatible for migration.
ACTION: Create a dm_fulltext_index object for the target store.
PARAMS:
ERROR: [DM_CONTENT_E_MAC_GET_TC]
SEVERITY: ERROR
DESCRIPTION: SS Error reading Type/Creator information from a Macintosh file (%s). Operating System error: (%s).
CAUSE: A error returned from a request to get the type and creator information on a macintosh content data file.
ACTION: Check if the indicated file exists check permissions to open or read the file.
PARAMS: %1s The name of the file which was being read. %2s A formatted OS error status.
ERROR: [DM_CONTENT_E_NEW_CONTENT]
SEVERITY: ERROR
DESCRIPTION: Cant perform getcontent on a new content object
CAUSE:
ACTION:
PARAMS:
ERROR: [DM_CONTENT_E_MIGRATE_CONTENT_CANT_MIGRATE_CASTORE_PLUGIN_OBJECTS_TO_CASTORE]
SEVERITY: ERROR
DESCRIPTION: S The arguments specified for MIGRATE_CONTENT apply method is attempting to migrate a dm_plugin object used in a dm_ca_store object to a CA store. This is not allowed. To see which CA store plugin object is about to be migrated execute the following DQL statement as Administrator: %s
CAUSE: The arguments specified for MIGRATE_CONTENT apply method is attempting to migrate a dm_plugin object whose id is a value for a_plugin_id attribute of at least one dm_ca_store object, to a dm_ca_store. This is not allowed. The content for all dm_plugin objects used as CA CA store plugin must be in a dm_filestore.
ACTION: Refine the arguments specified for MIGRATE_CONTENT so that dm_plugin objects used as CA store plugin objects are excluded from being migarated to a CA store.
PARAMS:
ERROR: [DM_CONTENT_E_CONTENT_TOO_LONG2]
SEVERITY: ERROR
DESCRIPTION: LL Content (%i bytes) in turbo_store exceeds limit (%i bytes) and cannot be opened.
CAUSE: The client application is using an old/unsupported dmcl dll (dmcl32.dll or older) which cannot handle reading content that resides in turbo store and exceeds the content size limit for turbo store.
ACTION: Try to open the content using an application that uses a supported version of dmcl. Or documentum administrator can change the a_storage_type of the document object from turbo_store to file_store.
PARAMS:
ERROR: [DM_CONTENT_E_GDCDS_MISSING_PARAMETERS]
SEVERITY: ERROR
DESCRIPTION: Required Parameters are missing from GET_DISTCONT_DIGSIG
CAUSE: Required parameters were not supplied to the GET_DISTCONT_DIGSIG server api call.
ACTION: Refer to the server documentation for the required parameters
PARAMS:
ERROR: [DM_CONTENT_E_REMOVE_LOCAL_REND]
SEVERITY: ERROR
DESCRIPTION: SISS Failed to delete local rendition for %s of page number %i with format %s. Error is: %s
CAUSE:
ACTION:
PARAMS:
ERROR: [DM_CONTENT_E_CANNOT_UPDATE_CASTORE_BY_CMD]
SEVERITY: ERROR
DESCRIPTION: The target store cannot be a CA store when UPDATE_ONLY is specified.
CAUSE: You specified UPDATE_ONLY and specified a CA store as the target when migrating contents.
ACTION: Select another targer store, or do not specify UPDATE_ONLY.
PARAMS:
ERROR: [DM_CONTENT_E_FILE_COPY_FAIL]
SEVERITY: ERROR
DESCRIPTION: SSIS File copy from %s to %s failed at position %i. Operating System error: (%s).
CAUSE:
ACTION:
PARAMS:
ERROR: [DM_CONTENT_E_CANT_GET_COMMON_ROOT]
SEVERITY: ERROR
DESCRIPTION: Could not determine name of common directory
CAUSE:
ACTION:
PARAMS:
ERROR: [DM_CONTENT_E_FILE_COPY_OTHER]
SEVERITY: ERROR
DESCRIPTION: SSI File copy from (%s) to content file (%s) failed at position %d during the copy of the Macintosh Resource Fork data.
CAUSE: A failure occurred while copying a data file to a new content file. The error occurred during the processing of the resource fork portion of a macintosh content file. Previous error messages should have given more information on the nature of the problem.
ACTION: Check permissions to open or create the new file. Check available disk space.
PARAMS: The name of the source content file. The name of the new content file. How far along the operation proceeded before failing.
ERROR: [DM_CONTENT_E_NOT_SYS_ADMIN]
SEVERITY: ERROR
DESCRIPTION: SS User %s does not have sufficient permission to run %s. User must have at least system administrator permissions.
CAUSE: User does not have permission to run this method.
ACTION: Contact your system administrator or superuser to run this method.
PARAMS:
ERROR: [DM_CONTENT_E_MIGRATE_CONTENT_CHECKEDOUT_OBJECTS_PRESENT]
SEVERITY: ERROR
DESCRIPTION: S Parent(s) of content object(s) has been checked out, preventing storage migration. Run the following DQL query to find the checked out objects: %s
CAUSE: Parent sysobject has been checkedout whose content object is to be migrated to the specified store. Content object(s) of a checkedout sysobject cannot be migrated.
ACTION: Run the reported DQL query to find the sysobjects that have been checked out. Ask the users who have checked out those objects to either checkin or cancel the checkout and reissue the migration command.
PARAMS:
ERROR: [DM_CONTENT_E_TURBO_LOAD2]
SEVERITY: ERROR
DESCRIPTION: LLS Load of document content not completed due to inconsistencies in content object info. Storage ID is zero indicating turbo storage but non-turbo object content present. DataTicket %d OtherTicket %d content pos %s.
CAUSE: A failure occurred during load of a content object because the the content information was inconsistent. The Storage ID of the loaded content object was zero. This indicates a Turbo Store content. In this case the content data should be encoded in the i_contents field of the content object and there should be no content file or content data present in the dump Extra information. But for this object either there was content data present in the Extra entries or the data_ticket or other_ticket fields were non-zero. This is inconsistent with turbo store objects and may indicate that the storage id is set to zero in error.
ACTION: Record the id of the failed object and when the load is complete check the documents on which these failures occurred for correctness. They may need to be repaired or removed from the docbase. The next error message to be given should indicate the object id of the failed object this should be used to track down the failed document.
PARAMS: The content object data_ticket. The content object other_ticket. Value indicating position of content data in the dump file.
ERROR: [DM_CONTENT_E_MIGRATE_CONTENT_COMMIT_FAILED]
SEVERITY: ERROR
DESCRIPTION: A database error occured while committing transaction.
CAUSE: A database error occured during commit.
ACTION: Check the log for database error message, fix it and retry migrate.
PARAMS:
ERROR: [DM_CONTENT_E_TURBO_LOAD]
SEVERITY: ERROR
DESCRIPTION: ILL Load of document content not completed due to inconsistencies in content object info. Storage ID is zero indicating turbo storage but non-turbo object content present. DataTicket %d OtherTicket %d content pos %d.
CAUSE: A failure occurred during load of a content object because the the content information was inconsistent. The Storage ID of the loaded content object was zero. This indicates a Turbo Store content. In this case the content data should be encoded in the i_contents field of the content object and there should be no content file or content data present in the dump Extra information. But for this object either there was content data present in the Extra entries or the data_ticket or other_ticket fields were non-zero. This is inconsistent with turbo store objects and may indicate that the storage id is set to zero in error.
ACTION: Record the id of the failed object and when the load is complete check the documents on which these failures occurred for correctness. They may need to be repaired or removed from the docbase. The next error message to be given should indicate the object id of the failed object this should be used to track down the failed document.
PARAMS: The content object data_ticket. The content object other_ticket. Value indicating position of content data in the dump file.
ERROR: [DM_CONTENT_E_STREAM_COPY_SOURCE]
SEVERITY: ERROR
DESCRIPTION: Error creating internal Source wrapper for input stream.
CAUSE: An error occurred allocating an internal Buffer Source object to use when extracting data from the input stream in a CopyFile operation. The dmBufferSource call failed.
ACTION: Check other error messages in the session log. A previous error message should indicate a specific reason for the failure.
PARAMS: None
ERROR: [DM_CONTENT_E_MIGRATE_CONTENT_MIGRATION_FAILED]
SEVERITY: ERROR
DESCRIPTION: S Migration of content %s failed.
CAUSE: An error occured during content migration.
ACTION: check other error messages.
PARAMS:
ERROR: [DM_CONTENT_E_BATCH_RENDITION_MISSING_PROPERTY_TXT]
SEVERITY: ERROR
DESCRIPTION: property.txt not found in tar file for batch rendition
CAUSE: tar file for batch rendition did not contain property.txt
ACTION: add property.txt to tar file for batch rendition
PARAMS:
ERROR: [DM_CONTENT_E_CONTENT_OFFLINE]
SEVERITY: ERROR
DESCRIPTION: S Content object %s is offline
CAUSE:
ACTION:
PARAMS:
ERROR: [DM_CONTENT_E_WRONG_PROTOCOL]
SEVERITY: ERROR
DESCRIPTION: Server and client not using same Mac access protocol
CAUSE: When attempting to store or fetch content, the client specified a Mac access protocol different from what the server is using
ACTION:
PARAMS:
ERROR: [DM_CONTENT_E_CONTENT_TOO_LONG]
SEVERITY: ERROR
DESCRIPTION: L Content too long limit is %i bytes
CAUSE:
ACTION:
PARAMS:
ERROR: [DM_CONTENT_E_MIGRATE_CONTENT_DATABASE_ERROR]
SEVERITY: ERROR
DESCRIPTION: S A database error occured during content migration: %s
CAUSE: A database error occured while performing the content migration.
ACTION: Fix the cause of the database error and retry migration.
PARAMS:
ERROR: [DM_CONTENT_E_TICKET_FINDINDEX]
SEVERITY: ERROR
DESCRIPTION: Error searching for existing indexes on the dmr_content type.
CAUSE: An error occurred while checking for existing indexes on dmr_content. Indexes are created on this object for use by filescan. The indexes are cleaned up either by the completion of filescan or by server initialization. This message indicates an error occurred while checking for existing indexes during this cleanup.
ACTION: Check server error log for further indication of the error.
PARAMS:
ERROR: [DM_CONTENT_E_RESOURCE_READ]
SEVERITY: ERROR
DESCRIPTION: SS Error reading content data from Macintosh Fork for file (%s). Operating System error: (%s).
CAUSE: A failure occurred while reading content from the resource fork of an open macintosh file. The operating system error should give a good indication of the actual problem.
ACTION: Check if the indicated file exists check permissions to open or read the file.
PARAMS: %1s The name of the file which was being read. %2s A formatted OS error status.
ERROR: [DM_CONTENT_E_MIGRATE_CONTENT_UNABLE_TO_UPDATE_PARENT]
SEVERITY: ERROR
DESCRIPTION: SSS Unable to update the a_storage_type attribute of parent object %s for content object %s to %s
CAUSE: A database error occured while trying to update the attribute.
ACTION: Fix the cause of the database error and retry migrate
PARAMS:
ERROR: [DM_CONTENT_E_HASH_UPDATE_DIGEST_FAILED]
SEVERITY: ERROR
DESCRIPTION: I Failed to hash a block of data. The cryptographic library error code is %d.
CAUSE: The cryptographic library could not hash the content data.
ACTION: Verify the status of the content object that is being signed.
PARAMS:
ERROR: [DM_CONTENT_E_MIGRATE_CONTENT_INVALID_TARGET_STORE2]
SEVERITY: ERROR
DESCRIPTION: S The target store specified %s is neither a dm_filestore nor a dm_ca_store
CAUSE: This error occurs when the target_store specified for MIGRATE_CONTENT apply method is neither a dm_filestore nor a dm_ca_store.
ACTION: Specify a target_store that is either a dm_filestore type or a dm_ca_store type.
PARAMS:
ERROR: [DM_CONTENT_E_TARGET_STORE_TYPE_ERROR_FOR_EXTERNALSTORE_NONDIRECT]
SEVERITY: ERROR
DESCRIPTION: The target store must be a file store, a CA store, or a writable external store like an XML store when migrating from an external store using a plugin.
CAUSE: The target store must be a file store, a CA store, or a writable external store like an XML store when migrating contents from an external store using a plugin.
ACTION: Ther target store must be either a file store or CA store or a writable external store like XML store
PARAMS:
ERROR: [DM_CONTENT_E_MIGRATE_CONTENT_UNABLE_TO_FETCH_STORAGE_OBJECT]
SEVERITY: ERROR
DESCRIPTION: S Unable to fetch storage object %s
CAUSE: A database error occured while attempting to fetch the storage object from the database.
ACTION: Examine the other error messages and fix the cause of the database error and retry migrate.
PARAMS:
ERROR: [DM_CONTENT_E_INVALID_SOURCE_STORE_FOR_DIRECT_OPERATION]
SEVERITY: ERROR
DESCRIPTION: The source store should be either dm_extern_file or dm_extern_free when DIRECT_COPY or DIRECT_MOVE is sepcified.
CAUSE: You specified DIRECT_COPY or DIRECT_MOVE and specified a source store other than dm_extern_file or dm_extern_free.
ACTION: Either migrate the content(s) from a dm_extern_file (or dm_extern_free) store or do not specify DIRECT_COPY (or DIRECT_MOVE).
PARAMS:
ERROR: [DM_CONTENT_E_INVALID_CONTENT]
SEVERITY: ERROR
DESCRIPTION: S %s is not the object id of a valid content object
CAUSE: The id passed to the action procedure is not the id of a valid content object
ACTION: Check that the id should be valid
PARAMS: The object id
ERROR: [DM_CONTENT_E_FLUSH_FAILURE]
SEVERITY: ERROR
DESCRIPTION: SS Error flushing output stream to content file (%s). Operating System error: (%s).
CAUSE: A failure occurred while writing content to a new file on an flush command. The operating system error should give a better indication of the actual problem.
ACTION: Check permissions to open or create the file. Check available disk space.
PARAMS: The name of the new content file. OS error status.
ERROR: [DM_CONTENT_E_INVALID_TARGET_STORE_FOR_DIRECT_OPERATION]
SEVERITY: ERROR
DESCRIPTION: The target store should be either dm_filestore or dm_ca_store when DIRECT_COPY or DIRECT_MOVE is specified.
CAUSE: You specified DIRECT_COPY or DIRECT_MOVE and specified a target store other than dm_filestore or dm_ca_store.
ACTION: Either migrate the content(s) to a dm_filestore (or dm_ca_store) or do not specify DIRECT_COPY (or DIRECT_MOVE).
PARAMS:
ERROR: [DM_CONTENT_E_RESTORE_FAIL]
SEVERITY: ERROR
DESCRIPTION: SS Content could not be restored to storage area %s — method %s failed
CAUSE:
ACTION:
PARAMS:
ERROR: [DM_CONTENT_E_MIGRATE_CONTENT_CANNOT_MIGRATE_CONTENT_WITH_UNEXPIRED_RETENTION]
SEVERITY: ERROR
DESCRIPTION: SSS Cannot migrate content object %s from %s to %s because of unexpired retention
CAUSE: This error occurs when using MIGRATE_CONTENT apply method to migrate a content object out of a CA store, whose retention period has not expired.
ACTION: Do not migrate this object until its retention expires.
PARAMS:
ERROR: [DM_CONTENT_E_GDCDS_NOT_VERIFIED]
SEVERITY: ERROR
DESCRIPTION: Cannot make Digital Signature, the hash key digest did not verify
CAUSE: The hash key digest provided did not verify correctly.
ACTION: Verify that your GET_DIST_CONTENT_MAP and GET_DISTCONT_DIGSIG calls are to the same server.
PARAMS:
ERROR: [DM_CONTENT_E_UNABLE_TO_MIGRATE_TARGET_STORE_NOT_RETENTION_AWARE]
SEVERITY: ERROR
DESCRIPTION: D The content object %s cannot be migrated to the target_store
CAUSE: The target storage specified is not conditional cretention aware , and content object specifies Event Based Retention
ACTION:
PARAMS:
ERROR: [DM_CONTENT_E_BAD_FORMAT]
SEVERITY: ERROR
DESCRIPTION: S Format %s is invalid
CAUSE:
ACTION:
PARAMS:
ERROR: [DM_CONTENT_E_MIGRATE_CONTENT_TARGET_STORE_NOT_ONLINE]
SEVERITY: ERROR
DESCRIPTION: S Target store %s is not ONLINE
CAUSE: The storage name specified for TARGET_STORE argument is not currently ONLINE. Target storage must be online for migrating content.
ACTION: Execute the SET_STORAGE_STATE apply method on the storage to mark it ONLINE and then retry migrate.
PARAMS:
ERROR: [DM_CONTENT_E_FILE_COPY_SOURCE]
SEVERITY: ERROR
DESCRIPTION: S Error creating internal Source wrapper for input file (%s).
CAUSE: An error occurred allocating an internal Buffer Source object to use when extracting data from the input file in a CopyFile operation. The dmBufferSource call failed.
ACTION: Check other error messages in the session log. A previous error message should indicate a specific reason for the failure.
PARAMS: %1s The name of the input file.
ERROR: [DM_CONTENT_E_ENCODED_CONTENT_ATTRS]
SEVERITY: ERROR
DESCRIPTION: S Failed to process encoded content attributes %s
CAUSE: Unable to satisfy the content request, encoded content attributs could not be processed.
ACTION: Check for other errors that give more detail on the problem.
PARAMS:
ERROR: [DM_CONTENT_E_HASH_UNSUPPORTED_ALGORITHM]
SEVERITY: ERROR
DESCRIPTION: S The hashing algorithm %s is not supported.
CAUSE: The server does not know the requested hashing algorithm. The original implementation only accepted SHA-1.
ACTION: Verify the spelling of the algorithm name. Confirm that the server supports the desired algorithm.
PARAMS:
ERROR: [DM_CONTENT_E_DESTROY_FAILED]
SEVERITY: ERROR
DESCRIPTION: S Content destroy failed because %s
CAUSE:
ACTION:
PARAMS:
ERROR: [DM_CONTENT_E_CANT_START_PULL]
SEVERITY: ERROR
DESCRIPTION: D Could not begin content transfer for content object %s. A failure occurred in an attempt to fetch content from the docbase. The client was unable to initiate the content transfer mechanism.
CAUSE: Could not start content pull operation.
ACTION: Check for other errors that give more detail on the problem.
PARAMS: %s – The source content object id.
ERROR: [DM_CONTENT_E_MIGRATE_CONTENT_INVALID_SYSOBJECT]
SEVERITY: ERROR
DESCRIPTION: S The sysobject specified %s is not a valid sysobject
CAUSE: The specified object id for MIGRATE_CONTENT apply method is not a valid sysobject id.
ACTION: Specify a valid sysobject id and re-execute the command.
PARAMS:
ERROR: [DM_CONTENT_E_SECUREWRITE_PERM]
SEVERITY: ERROR
DESCRIPTION: SS Error: failed to set proper file permission for content file (%s). Operating System error: (%s).
CAUSE: An error occurred while the secure writer attempted to set the proper permission for the content file.
ACTION: Check the security on the target directory and your access permission.
PARAMS: None
ERROR: [DM_CONTENT_E_INDEX_PARENT_NOT_A_PARENT]
SEVERITY: ERROR
DESCRIPTION: S Content cant be indexed because specified index parent %s not a parent
CAUSE: Internal error.
ACTION:
PARAMS:
ERROR: [DM_CONTENT_E_JMS_CONFIGURATION]
SEVERITY: ERROR
DESCRIPTION: SD JMS object named %s contains an invalid id %s on svr_config_id
CAUSE: The JMS object has config_type of 1 yet the value of svr_config_id does not correctly identify a dm_server_config object.
ACTION: Set the value of svr_config_id to the current version of the dm_server_config object.
PARAMS:
ERROR: [DM_CONTENT_E_MKDIR_FAILED]
SEVERITY: ERROR
DESCRIPTION: S Cannot create temporary directory %s
CAUSE:
ACTION:
PARAMS:
ERROR: [DM_CONTENT_E_NO_OTHER]
SEVERITY: ERROR
DESCRIPTION: Other-file content requested for document which has no other-file.
CAUSE: A getfile operation was done which explicitely requested that the otherfile content be returned, but the document contains no other_ticket entry.
ACTION: Remove the request for the other-file for this document.
PARAMS: none
ERROR: [DM_CONTENT_E_GDCDS_NO_HASHKEY_GENERATED]
SEVERITY: ERROR
DESCRIPTION: I Cannot generate the Crypto HashKey for Distributed Content. Distributed ACS Access will be disabled. Status = %d
CAUSE: The system was unable to generate a hashKey for distibuted content at server startup
ACTION: Restart your server
PARAMS:
ERROR: [DM_CONTENT_E_MIGRATE_CONTENT_INVALID_STORE]
SEVERITY: ERROR
DESCRIPTION: SS Storage object %s is invalid for %s
CAUSE: Unable to fetch the storage object. This could occur if the storage object could not be fetched by the database or if the attributes of the storage object is invalid or corrupt.
ACTION: Fix the cause of the error and retry migrate.
PARAMS:
ERROR: [DM_CONTENT_E_PUSH_CONTENT_RETENTION_TOO_LARGE]
SEVERITY: ERROR
DESCRIPTION: I The retention interval %d is to large. CASE: The retention passed in push content cannot exceed 20 decimal digits.
CAUSE:
ACTION: Change the retention to a smaller value.
PARAMS:
ERROR: [DM_CONTENT_E_HASH_FINALIZE_DIGEST_FAILED]
SEVERITY: ERROR
DESCRIPTION: I Failed to complete a cryptographic hashing operation. The cryptographic library error code is %d.
CAUSE: The cryptographic library could not hash the content data.
ACTION: Verify the status of the content object that is being signed.
PARAMS:
ERROR: [DM_CONTENT_E_MIGRATE_CONTENT_UNABLE_TO_GET_RETENTION_PERIOD]
SEVERITY: ERROR
DESCRIPTION: SS Unable to get retention period for content object %s in storage %s
CAUSE: This error occurs when Content Server attempts to obtain the retention period of the content object to be migrated, whose current store is a dm_ca_store.
ACTION: Look for additional error messages from the storage subsystem and take corrective action.
PARAMS:
ERROR: [DM_CONTENT_E_DIRECT_OPERATION_FAIL_DUE_TO_OS]
SEVERITY: ERROR
DESCRIPTION: SI An operating system error occurred during direct move or copy: %s, error code: %d.
CAUSE: An operating system error occurred during the direct move or copy operation.
ACTION: Refer to the operating system documentation for more information about the error message, and for further action.
PARAMS:
ERROR: [DM_CONTENT_E_MIGRATE_CONTENT_UNABLE_TO_OPEN_LOGFILE]
SEVERITY: ERROR
DESCRIPTION: S Unable to open log file %s
CAUSE: User specified an invalid value for LOG_FILE argument or the file could not be opened due to disk error or user does not have right permission to open the specified file.
ACTION: Specify a valid filename and make sure the user context in which Content Server process is running has appropriate permission on the file path specified.
PARAMS:
ERROR: [DM_CONTENT_E_MIGRATE_CONTENT_MASTER_TIMEOUT]
SEVERITY: ERROR
DESCRIPTION: master session timeout, forcely terminate failed worker sessions
CAUSE: Some worker sessions fail
ACTION: No action is needed.
PARAMS:
ERROR: [DM_CONTENT_E_FILE_WRITE_FAILED]
SEVERITY: ERROR
DESCRIPTION: S Attempt to write to file %s failed
CAUSE:
ACTION:
PARAMS:
ERROR: [DM_CONTENT_E_UNABLE_TO_CREATE_INDEX_ON_CONTENT_HASH]
SEVERITY: ERROR
DESCRIPTION: Index creation on dmr_content.r_content_hash failed. See other error messages for the session
CAUSE:
ACTION:
PARAMS:
ERROR: [DM_CONTENT_E_MIGRATE_CONTENT]
SEVERITY: ERROR
DESCRIPTION: method
CAUSE: An error has occured during content migration. This message is currently not being used.
ACTION: Login as a user with super-user privileges and retry migrate.
PARAMS:
ERROR: [DM_CONTENT_E_XFER_NULL_HANDLE]
SEVERITY: ERROR
DESCRIPTION: S Server content transfer method %s was called by client with a null handle. Consistency check for obviously bad content transfer handle.
CAUSE: Indicates a bug in the dmcl.
ACTION: Check for other errors that may give clues to the problem.
PARAMS: %s – The type of server call made.
ERROR: [DM_CONTENT_E_UNLINK_FROM_PARENT]
SEVERITY: ERROR
DESCRIPTION: SS Failed to remove rendition object %s from its parent object %s
CAUSE:
ACTION:
PARAMS:
ERROR: [DM_CONTENT_E_MIGRATE_CONTENT_INVALID_TARGET_STORE]
SEVERITY: ERROR
DESCRIPTION: No or invalid target store specified.
CAUSE: User specified a store name for TARGET_STORE that is either invalid or does not exist in the docbase.
ACTION: Specify a valid storage object name for TARGET_STORE
PARAMS:
ERROR: [DM_CONTENT_E_MIGRATE_CONTENT_CANNOT_MIGRATE_RESOURCE_FORK_TO_CA_STORE]
SEVERITY: ERROR
DESCRIPTION: SS Cannot migrate content object %s to Content Addressable store %s since dm_ca_store does not support storing Mac Resource fork
CAUSE: This error occurs when executing the MIGRATE_CONTENT apply method to migrate a content object with Mac resource fork to a CA store.
ACTION: dm_ca_store storage type does not currently support storing mc resource forks. Leave the object in its current store.
PARAMS:
ERROR: [DM_CONTENT_E_INVALID_ARGUMENTS]
SEVERITY: ERROR
DESCRIPTION: If you specify the argument COMMAND_FILE_NAME, you should also specify UPDATE_ONLY when migrating contents from an external store.
CAUSE: The file specified by COMMAND_FILE_NAME is intended to save the commands generated when UPDATE_ONLY is specified.
ACTION: Either specify the argument UPDATE_ONLY, or remove COMMAND_FILE_NAME.
PARAMS:
ERROR: [DM_CONTENT_E_FILE_COPY_FAILURE]
SEVERITY: ERROR
DESCRIPTION: SSI File copy from (%s) to content file (%s) failed at position %d.
CAUSE: A failure occurred while copying a data file to a new content file. Previous error messages should have given more information on the nature of the problem.
ACTION: Check permissions to open or create the new file. Check available disk space.
PARAMS: The name of the source content file. The name of the new content file. How far along the operation proceeded before failing.
ERROR: [DM_CONTENT_E_ACTION]
SEVERITY: ERROR
DESCRIPTION: : The target store should be retention aware, otherwise the operation is not supported.
CAUSE:
ACTION:
PARAMS:
ERROR: [DM_CONTENT_E_NO_TEMP_FILE]
SEVERITY: ERROR
DESCRIPTION: S Cannot create temporary file in directory %s
CAUSE:
ACTION:
PARAMS:
ERROR: [DM_CONTENT_E_INVALID_SUBCONTENT]
SEVERITY: ERROR
DESCRIPTION: S %s is not a valid subcontent object
CAUSE:
ACTION:
PARAMS:
ERROR: [DM_CONTENT_E_DIRECT_MOVE_TO_FILESTORE_ONLY]
SEVERITY: ERROR
DESCRIPTION: The target store should be a dm_filestore when DIRECT_MOVE is specified.
CAUSE: You specified DIRECT_MOVE and specified a non-filestore target store.
ACTION: Either migrate the content(s) to filestore or do not specify DIRECT_MOVE.
PARAMS:
ERROR: [DM_CONTENT_E_HASH_INVALID_DIGEST_LENGTH]
SEVERITY: ERROR
DESCRIPTION: II Failed to create a hash string of the required length. Actual Length: %d Expected Length: %d
CAUSE: The hash results have an invalid length.
ACTION: Verify the result size for the requested algorithm.
PARAMS:
ERROR: [DM_CONTENT_E_SECUREWRITE_POPEN]
SEVERITY: ERROR
DESCRIPTION: SS Error executing the Secure Writer: %s. The popen() operation failed with status (%s).
CAUSE: A failure occurred during an attempt to copy a file to the common area. The server is configured to use the secure writer program for this action so the secure writer program was called to create the file, but the popen call to start the program failed.
ACTION: Check for system resource shortages that may prevent the server from being able to open a pipe or fork a process.
PARAMS: The secure writer command line. The operating system error status.
ERROR: [DM_CONTENT_E_COPY_BAD_USER]
SEVERITY: ERROR
DESCRIPTION: SSS Copy of %s to %s failed — couldnt get info for user %s
CAUSE:
ACTION:
PARAMS:
ERROR: [DM_CONTENT_E_HASH_CANT_CREATE_DATA_SOURCE]
SEVERITY: ERROR
DESCRIPTION: S Failed to read the data in content object %s.
CAUSE: Could not obtain a data source from the content object.
ACTION: Verify the state of the content object to be signed.
PARAMS:
ERROR: [DM_CONTENT_E_MIGRATE_CONTENT_CURRENT_STORE_IS_A_COMPONENT]
SEVERITY: ERROR
DESCRIPTION: SS Current store %s of content %s is a component of a distributed store
CAUSE: Current store of a content object to be migrated is a component of a distributed store. This operation is disallowed.
ACTION:
PARAMS:
ERROR: [DM_CONTENT_E_UPDATE_ONLY_SHOULD_BE_WITH_DIRECT_COPY_OR_MOVE_AND_COMMAND_FILE_NAME]
SEVERITY: ERROR
DESCRIPTION: You specified the flag, UPDATE_ONLY when migrating from an external store. You should also specify one of the following flags, DIRECT_COPY or DIRECT_MOVE, and specify a command file name.
CAUSE: You did not specify DIRECT_COPY or DIRECT_MOVE and a command file name when you specified UPDATE_ONLY and you were migrating contents from an external store.
ACTION: Specify the DIRECT_COPY or DIRECT_MOVE flag, and specify a command file name.
PARAMS:
ERROR: [DM_CONTENT_E_NO_FORMAT]
SEVERITY: ERROR
DESCRIPTION: S Content object (%s) does not have a format associated with it.
CAUSE: Either the content object is corrupted or the format object is bad.
ACTION: Verify that the content object is not corrupt and that it is associated with a valid format.
PARAMS: The object id of the content object.
ERROR: [DM_CONTENT_E_RESOURCE_OPEN]
SEVERITY: ERROR
DESCRIPTION: SS Error opening Macintosh Fork for file (%s). Operating System error: (%s).
CAUSE: Attempt to open the named file failed. The operating system error should give a good indication of the actual problem.
ACTION: Check if the indicated file exists check permissions to open or read the file.
PARAMS: %1s The name of the file which could not be opened. %2s A formatted OS error status.
ERROR: [DM_CONTENT_E_SECUREWRITE_PCLOSE]
SEVERITY: ERROR
DESCRIPTION: SS Error executing the Secure Writer: %s. The pclose() operation failed with status (%s).
CAUSE: A failure occurred during an attempt to copy a file to the common area. The server is configured to use the secure writer program for this action so the secure writer program was called to create the file, but the pclose call to obtain the program status failed.
ACTION: Check for system resource shortages that may prevent the server from being able to open a pipe or fork a process. Check the existence and permissions of the Secure Writer program and check the server error log for error messages.
PARAMS: The secure writer command line. The operating system error status.
ERROR: [DM_CONTENT_E_INVALID_TARGET_STORE_CONFIGURATION_FOR_DIRECT_OPERATION]
SEVERITY: ERROR
DESCRIPTION: The target store cannot be configured for compression, encryption, or de-duplication when migrating contents and you have specified SOURCE_DIRECT_ACCESS_OK.
CAUSE: You selected SOURCE_DIRECT_ACCESS_OK when migrating content to a store configured for compression, encryption, or de-duplication.
ACTION: Either migrate contents to a normal store, or do not specify SOURCE_DIRECT_ACCESS_OK.
PARAMS:
ERROR: [DM_CONTENT_E_MIGRATE_CONTENT_SOURCE_STORE_NOT_READONLY]
SEVERITY: ERROR
DESCRIPTION: S Source store object %s is not READONLY
CAUSE: Current or source store must be marked READONLY before content from that store could be migrated.
ACTION: Execute SET_STORAGE_STATE apply method.
PARAMS:
ERROR: [DM_CONTENT_E_MIGRATE_CONTENT_INSUFFICIENT_SYSOBJECT_PERMIT]
SEVERITY: ERROR
DESCRIPTION: SS User %s does not have enough privileges to migrate the content of sysobject %s
CAUSE: User executing the MIGRATE_CONTENT apply method does not have WRITE privilege on the specified sysobject.
ACTION: You cannot migrate content of a sysobject on which you do not have at least WRITE permission.
PARAMS:
ERROR: [DM_CONTENT_E_NO_DATABASE_CONNECTION]
SEVERITY: ERROR
DESCRIPTION: Mark all could not establish a database connection to perform necessary operations.
CAUSE: No valid database connection established.
ACTION: Check the database logs and verify that your database is running normally.
PARAMS:
ERROR: [DM_CONTENT_E_GDWM_FAILED]
SEVERITY: ERROR
DESCRIPTION: GET_DIST_WRITE_MAP failed to complete
CAUSE: Unable to satisfy the GET_DIST_WRITE_MAP request.
ACTION: Check for other errors that give more detail on the problem.
PARAMS:
ERROR: [DM_CONTENT_E_WRITE_FAILURE_READBLOCK]
SEVERITY: ERROR
DESCRIPTION: S Error writing data to content file (%s) due to a ReadBlock error.
CAUSE: A failure occurred while writing content from a new content file. The additional error associated with this error will give a more detailed indication of the problem to be correctd.
ACTION: Refer to the error returned with this error for the appropriate actions
PARAMS: The name of the new content file.
ERROR: [DM_CONTENT_E_NO_RESTORE_METHOD]
SEVERITY: ERROR
DESCRIPTION: SS Attempt to restore content to storage area %s failed — no method with name %s
CAUSE:
ACTION:
PARAMS:
ERROR: [DM_CONTENT_E_MIGRATE_CONTENT_INVALID_CONTENT]
SEVERITY: ERROR
DESCRIPTION: S %s is an invalid content object
CAUSE: Server validation of the content object to be migrated failed. This can occur if the content object could not be fetched successfully from the database or the attributes of the object are invalid or corrupt.
ACTION: Attempt to fetch the content from a different session to diagnose the actual error.
PARAMS:
ERROR: [DM_CONTENT_W_UPDATE_OTHER_FILE_SIZE_INVALID_MAX_COUNT]
SEVERITY: WARNING
DESCRIPTION: Max count should be a positive integer. By default, it will be ignored.
CAUSE: Wrong arguments for this apply method, MAX_COUNT should be greater than zero.
ACTION: Specify a positive integer or dont specify it to ignore max count.
PARAMS:
ERROR: [DM_CONTENT_W_CREATE_MARK_ALL_TRACE_FAILED]
SEVERITY: WARNING
DESCRIPTION: S Could not create trace file %s when running the MARK_ALL method. The method will continue without tracing.
CAUSE: Failed to create trace file probably due to OS error.
ACTION: Resolve any OS error preventing files from being created.
PARAMS: The path of the trace file
ERROR: [DM_CONTENT_W_LOAD_NO_CONTENT]
SEVERITY: WARNING
DESCRIPTION: S No content data for dmr_content object %s in dumpfile. Document being added with no content. Use RESTORE_CONTENT method to associate content data with this object.
CAUSE: During a dump of a content object, the content data could not be dumped. This may have been caused by: – the content object had no content data associated with it – the document was offline when the dump was made – the storage area was offline when the dump was made – the document was not accessible by the server which produced the dump. Now that the document is being loaded, since it includes no content data, no content can be loaded. The resulting document will have a dmr_content object but with a zero data_ticket, precluding any getfiles on it.
ACTION: The document can be fixed by using the RESTORE_CONTENT method to import new content data and associated it with the document.
PARAMS: The object_id of the dmr_content object being loaded.
ERROR: [DM_CONTENT_W_STOP_SEQUENTIAL_JOB]
SEVERITY: WARNING
DESCRIPTION: Unable to monitor this content migration job, it will proceed but cannot be stopped through the apply method control_migration
CAUSE: Once the Server has reached its maximum capacity for monitoring migration jobs, additional jobs cannot be stopped manually through control_migration.
ACTION: No action needs to be taken, the content migration will proceed but it will be outside the control of control_migration.
PARAMS:
ERROR: [DM_CONTENT_W_RMDIR_FAILED]
SEVERITY: WARNING
DESCRIPTION: SDS Unable to destroy temp directory (%s) created for content batch save. Content Id: %s. Reason: %s
CAUSE: Unable to destroy the temp directory created for content batch save. Some OS error occured.
ACTION: Manually destroy the directory.
PARAMS:
ERROR: [DM_CONTENT_W_INIT_CM_CONTEXT]
SEVERITY: WARNING
DESCRIPTION: Failed to initialize the content migration execution context, content will be migrated sequentially
CAUSE: Failed to initialize the content migration execution context for parallel content migration. The Server will run the content migration sequentially.
ACTION: No action is required. To take advantage of parallel migration allow any current content migration job to complete before requesting another.
PARAMS:
ERROR: [DM_CONTENT_W_DUMP_NO_CONTENT]
SEVERITY: WARNING
DESCRIPTION: SS The content data for dmr_content object %s could not be dumped. Reason: %s.
CAUSE: During a dump of a content object, the content data could not be dumped. This may have been caused by: – the content object had no content data associated with it – the document is currently offline – the storage area is currently offline – the document is not accessible by the current server – the content file could not be found or accessed This error is sometimes generated by archive or dumps used for replicating content. It occurs when a document is dumped which has previous versions which are either offline or not replicated to the current site. In these cases this warning does not indicate anything wrong with the server or docbase.
ACTION: This particular document was dumped with no content data. If loaded, the loaded document will have no content data.
PARAMS: The object_id of the dmr_content object being dumped. The reason for the inability to dump.
ERROR: [DM_CONTENT_W_UPDATE_OTHER_FILE_SIZE_FAIL_COMPUTE_OTHER_FILE_SIZE]
SEVERITY: WARNING
DESCRIPTION: D Fail to compute other file size for content %s. This content will be skipped to be updated.
CAUSE: Some error occured during computing other file size for this content. Check error logs to identify the exact cause.
ACTION: Check error logs to identify the exact cause.
PARAMS:
ERROR: [DM_CONTENT_W_CONTENT_TRUNCATED]
SEVERITY: WARNING
DESCRIPTION: L Content was truncated — only %lu bytes stored
CAUSE:
ACTION:
PARAMS:
ERROR: [DM_CONTENT_W_PARALLEL_DEGREE]
SEVERITY: WARNING
DESCRIPTION: parallel_degree shouldnt be negative
CAUSE: the given parallel_degree is negative
ACTION: set the parallel_degree positive
PARAMS:
ERROR: [DM_CONTENT_W_MIGRATE_CONTENT]
SEVERITY: WARNING
DESCRIPTION: S %s
CAUSE: A generic warning message for during content migration.
ACTION: None. All warning messages during content migration
PARAMS:
ERROR: [DM_CONTENT_W_UPDATE_OTHER_FILE_SIZE_MISSING_OTHER_FILE]
SEVERITY: WARNING
DESCRIPTION: D There is no other file for the specified dmr_content object %s.
CAUSE: No other file is attached with this content.
ACTION: Skip this content object as it doesnt require any updates.
PARAMS:
ERROR: [DM_CONTENT_W_UPDATE_OTHER_FILE_SIZE_ORPHANED_CONTENT]
SEVERITY: WARNING
DESCRIPTION: D Content %s is an orphaned content and is skipped to be updated.
CAUSE: This content is an orphaned content and has not parent object. It will be skipped to be updated.
ACTION: Skip this content object as it doesnt require any updates.
PARAMS:
ERROR: [DM_CONTENT_W_UPDATE_OTHER_FILE_SIZE_INVALID_BATCH_SIZE]
SEVERITY: WARNING
DESCRIPTION: I Batch size should be a positive integer. The default batch size %d will be used.
CAUSE: Wrong arguments for this apply method, batch size should be greater than zero.
ACTION: Specify a positive integer or dont specify a value if default is desired.
PARAMS:
ERROR: [DM_CONTENT_W_RETRIEVE_CM_CONTEXT]
SEVERITY: WARNING
DESCRIPTION: Fail to retrieve content migration execution context and we will migrate contents sequentially
CAUSE: Another session is doing the parallel content migration currently.
ACTION:
PARAMS:
ERROR: [DM_CONTENT_W_LOAD_CONTENT_ERROR]
SEVERITY: WARNING
DESCRIPTION: S Could not load content data for dmr_content object %s. Document being added with no content. Use RESTORE_CONTENT method to associate content data with this object.
CAUSE: During a load of a content object, the content data could not be written to the documents storage area. This may have been caused by: – lack of disk space – the storage area being offline or otherwise inaccessible. The resulting document will have a dmr_content object but with a zero data_ticket, precluding any getfiles on it.
ACTION: The document can be fixed by using the RESTORE_CONTENT method to import new content data and associated it with the document.
PARAMS: The object_id of the dmr_content object being loaded.
ERROR: [DM_CONTENT_W_STOP_BY_USER]
SEVERITY: WARNING
DESCRIPTION: This content migration job was stopped by user request
CAUSE: The apply method named control_migration was used to stop the content migration.
ACTION:
PARAMS:
ERROR: [DM_CONTENT_T_MERGE_3]
SEVERITY: TRACE
DESCRIPTION: S Unlinking content object: %s
CAUSE:
ACTION:
PARAMS:
ERROR: [DM_CONTENT_T_MIGRATE_CONTENT_ARGUMENTS_SPECIFIED]
SEVERITY: TRACE
DESCRIPTION: SSSSIISS Arguments specified for MIGRATE_CONTENT: OBJECT_ID = %s, TARGET_STORE = %s, SOURCE_STORE = %s, QUERY = %s, MAX_MIGRATE_COUNT = %d, BATCH_SIZE = %d, LOG_FILE= %s, REMOVE_ORIGINAL = %s
CAUSE: Just a trace message to log the arguments specified
ACTION: None.
PARAMS:
ERROR: [DM_CONTENT_T_MIGRATE_CONTENT_OBJECT_SKIPPED]
SEVERITY: TRACE
DESCRIPTION: DS Migration of content for object %s skipped. Reason %s
CAUSE:
ACTION:
PARAMS:
ERROR: [DM_CONTENT_T_MIGRATE_CONTENT_WORKER_LOGFILENAME]
SEVERITY: TRACE
DESCRIPTION: S worker log filename: %s
CAUSE:
ACTION:
PARAMS:
ERROR: [DM_CONTENT_T_COMPRESSION]
SEVERITY: TRACE
DESCRIPTION: SS Content was compressed from %s to %s bytes
CAUSE:
ACTION:
PARAMS:
ERROR: [DM_CONTENT_T_MERGE_1]
SEVERITY: TRACE
DESCRIPTION: SS Checking local renditions for content object ID=%s, parent ID=%s
CAUSE:
ACTION:
PARAMS:
ERROR: [DM_CONTENT_T_DECOMPRESSION]
SEVERITY: TRACE
DESCRIPTION: SS Content was decompressed from %s to %s bytes
CAUSE:
ACTION:
PARAMS:
ERROR: [DM_CONTENT_T_MIGRATE_CONTENT_PERF_FINAL]
SEVERITY: TRACE
DESCRIPTION: S %s
CAUSE:
ACTION:
PARAMS:
ERROR: [DM_CONTENT_T_MIGRATE_CONTENT_MIGRATION_SUCCESS]
SEVERITY: TRACE
DESCRIPTION: I Successful migration of batch (%d object(s)).
CAUSE: Indicates that the migration is successful.
ACTION: None.
PARAMS:
ERROR: [DM_CONTENT_T_MIGRATE_CONTENT_REMOVE_SKIPPED]
SEVERITY: TRACE
DESCRIPTION: SS Content file %s for content object %s is not removed. You should remove it manually.
CAUSE: Because REMOVE_ORIGINAL argument value was set to F, the content file in the source store of the content object was not removed by the apply method.
ACTION: The file must be removed manually by user. dmfilescan will attempt to remove this file.
PARAMS:
ERROR: [DM_CONTENT_T_MIGRATE_CONTENT_REACHED_MAX_COUNT]
SEVERITY: TRACE
DESCRIPTION: I Migrated maximum objects specified %d
CAUSE: The apply method has migrated the maximum number of objects specified by user. If no error has occured, the transaction is about to be committed.
ACTION: None.
PARAMS:
ERROR: [DM_CONTENT_T_MIGRATE_CONTENT]
SEVERITY: TRACE
DESCRIPTION: S %s
CAUSE: Any generic message related to content migration.
ACTION: None.
PARAMS:
ERROR: [DM_CONTENT_T_MIGRATE_CONTENT_OBJECTS_MIGRATED]
SEVERITY: TRACE
DESCRIPTION: I %d object(s) successfully migrated.
CAUSE: Indicates how many content objects were migrated successfully.
ACTION: None
PARAMS:
ERROR: [DM_CONTENT_T_MIGRATE_CONTENT_PERF_FREC]
SEVERITY: TRACE
DESCRIPTION: S %s
CAUSE:
ACTION:
PARAMS:
ERROR: [DM_CONTENT_T_MIGRATE_CONTENT_PERF_REC]
SEVERITY: TRACE
DESCRIPTION: S %s
CAUSE:
ACTION:
PARAMS:
ERROR: [DM_CONTENT_T_MIGRATE_CONTENT_MIGRATED_OBJECT]
SEVERITY: TRACE
DESCRIPTION: S Migrated content object %s
CAUSE: Trace message to indicate a content object has been migrated. Transaction has not been committed yet.
ACTION: None.
PARAMS:
ERROR: [DM_CONTENT_T_MIGRATE_CONTENT_MIGRATING_OBJECT]
SEVERITY: TRACE
DESCRIPTION: S Migrating content object %s
CAUSE: Trace message to indicate the current object being migrated.
ACTION: None.
PARAMS:
ERROR: [DM_CONTENT_T_MIGRATE_CONTENT_TOTAL_SKIPPED]
SEVERITY: TRACE
DESCRIPTION: I %d objects skipped during migration
CAUSE:
ACTION:
PARAMS:
ERROR: [DM_CONTENT_T_MERGE_2]
SEVERITY: TRACE
DESCRIPTION: S Deleting content object: %s
CAUSE:
ACTION:
PARAMS:
dm_misc: Miscellaneous Documentum Information 