IT blok - Michal Šika

kutilovo živobytí

Documentum 6.6 – chybové zprávy – část 1.

V první části výčtu chybových hlášení systému Documentum verze 6.6 od EMC si ukážeme chyby DM_ACL – DM_DIRECTORY v abecedním pořadí. Jedná se jak o ERROR tak i o WARNING chybová hlášení.
Doufám, že se vám podaří najít odpovídající řešení vašich problémů…

DM_ACL DM_API DM_ASSEMBLY
DM_AUDITTRAIL DM_CABINET DM_CCONTENT
DM_CHARTRANS DM_COMPOSITE DM_CONTAINMENT
DM_CONTENT DM_CRYPTO DM_DATA_DICT
DM_DATA_PARTITION DM_DCNFG DM_DIRECTORY

DM_ACL

ERROR: [DM_ACL_E_DESTROY_IN_USE]

SEVERITY: ERROR
DESCRIPTION: SS Failed to destroy the ACL %s in domain %s because it is in use.
CAUSE: Destroy an ACL that is in use.
ACTION: Make sure the ACL is not used by any sysobjects, users and types.
PARAMS:

ERROR: [DM_ACL_E_CANT_CHANGE_INSTANCE]

SEVERITY: ERROR
DESCRIPTION: S The ACL %s is an instance of an ACL template.
CAUSE: User tried to change an instance of an ACL template.
ACTION: Change the associated document instead so that a new internal ACL will be created.
PARAMS:

ERROR: [DM_ACL_E_NEED_NAME]

SEVERITY: ERROR
DESCRIPTION: SS Need the user name for operation %s to succeed, when setting the ACL %s.
CAUSE: The operation requires a name to proceed.
ACTION:
PARAMS:

ERROR: [DM_ACL_E_CHANGE_OBJNAME_PRIV]

SEVERITY: ERROR
DESCRIPTION: Only SUPERUSER can change object_name.
CAUSE: Non-superusers try to change ACLs object_name.
ACTION: Ask superusers to do this for you.
PARAMS:

ERROR: [DM_ACL_E_FETCH_NO_NAME]

SEVERITY: ERROR
DESCRIPTION: Failed to fetch the ACL with no name provided.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_ACL_E_USER_NOT_EXIST]

SEVERITY: ERROR
DESCRIPTION: SS The owner_name or accessor_name %s given in the ACL %s does not exist.
CAUSE: The owner_name or accessor_name given does not exist.
ACTION:
PARAMS:

ERROR: [DM_ACL_E_ACE_INVALID_PERMIT]

SEVERITY: ERROR
DESCRIPTION: SSII The Accessor Control Entry (ACE) for accessor %s, permit_type %s(%d), has an invalid permit (%d)
CAUSE: An illegal permit was specified in the ACE.
ACTION: Check the permit for the specified ACE and correct the permit.
PARAMS:

ERROR: [DM_ACL_E_READONLY_ATTR]

SEVERITY: ERROR
DESCRIPTION: SS The attribute %s of the ACL %s is read-only and not changable.
CAUSE: Try to change read-only attrs.
ACTION:
PARAMS:

ERROR: [DM_ACL_E_NEW_SYS_ACL]

SEVERITY: ERROR
DESCRIPTION: SS Failed to create an ACL %s in the system domain, because the user %s is neither SYSADMIN nor SUPERUSER.
CAUSE: Failed to create system ACLs due to low privilege.
ACTION: Ask the sysadmin/superuser to grant the privilege.
PARAMS:

ERROR: [DM_ACL_E_CANT_CHANGE_PERMITS]

SEVERITY: ERROR
DESCRIPTION: S Only the %s acl owner, superuser, or whoever has the change_permit extended permission can change permits.
CAUSE: A user, other than a superuser or sysobject owner, tried to change security permits without possessing the change_permit extended permit.
ACTION: None.
PARAMS:

ERROR: [DM_ACL_E_OLD_CLIENT_CANNOT_MODIFY_MACL_ACL]

SEVERITY: ERROR
DESCRIPTION: D The ACL with ID %s contains MACL (Mandatory Access Controls) rules and cannot be modified by an older client.
CAUSE: An ACL with MACL rules cannot be modified by an old client
ACTION: Use a newer client to modify the specified ACL.
PARAMS:

ERROR: [DM_ACL_E_ACE_NULL_APPLICATION_PERMIT]

SEVERITY: ERROR
DESCRIPTION: SSI The Accessor Control Entry (ACE) for accessor %s, permit_type %s(%d) cannot have a NULL application_permit.
CAUSE: The specified ACE cannot have a NULL application_permit.
ACTION: Ensure that the application_permit for the ACE is not NULL or that the permit_type is correct.
PARAMS:

ERROR: [DM_ACL_E_REFRESH_BAD_ALIAS_SET]

SEVERITY: ERROR
DESCRIPTION: SD The ACL instance object named %s refers to a non-existent alias set object %s.
CAUSE: The alias set object does not exist.
ACTION: Check to see if the alias set is deleted by someone else.
PARAMS:

ERROR: [DM_ACL_E_DUMP_NO_USER]

SEVERITY: ERROR
DESCRIPTION: Although dump will continue, the missing user should be created in the docbase where load is to be performed.
CAUSE: Either the owner or one of the accessors of the ACL does not exist, while the ACL object is being dumpped.
ACTION: The missing user/group object should be created manually in the docbase where load is to be performed, to pervent any malfunctions in the future.
PARAMS:

ERROR: [DM_ACL_E_CORRUPTED]

SEVERITY: ERROR
DESCRIPTION: SS The ACL %s in domain %s is found corrupted.
CAUSE: The first two ACEs are not for dm_world and dm_owner.
ACTION: Add the first two ACE manually as required.
PARAMS:

ERROR: [DM_ACL_E_PARAMETER]

SEVERITY: ERROR
DESCRIPTION: S The parameters provided for command %s are not valid.
CAUSE: The command is provided invalid parameters.
ACTION: Try again with valid parameters.
PARAMS:

ERROR: [DM_ACL_E_CANNOT_UPDATE_ACE]

SEVERITY: ERROR
DESCRIPTION: DSSI The Accessor Control Entry (ACE) in ACL with Id %s for accessor %s, permit_type %s(%d) cannot be updated.
CAUSE: Certain permit_types cannot be updated. They can only be created or deleted.
ACTION: Check the command being issued to update the ACL.
PARAMS:

ERROR: [DM_ACL_E_ILLEGAL_ACL_CLASS]

SEVERITY: ERROR
DESCRIPTION: IS The acl_class (%d) of ACL %s is illegal.
CAUSE: User has specified an illegal acl_class for the ACL Object. Currently, only the following values are allowed: 0 — regular ACL. 1 — template ACL. 2 — instance of template ACL. 3 — public ACL.
ACTION:
PARAMS:

ERROR: [DM_ACL_E_FORCE_DESTROY]

SEVERITY: ERROR
DESCRIPTION: The force flag in the destroy API command can be used only by superusers.
CAUSE: Non-superusers attempt to use the force flag (e.g. destroy,c,l,T).
ACTION: Do not turn on the force flag, if youre non-superuser.
PARAMS:

ERROR: [DM_ACL_E_DESTROY_REF_COUNT]

SEVERITY: ERROR
DESCRIPTION: SS Failed to destroy the ACL %s in domain %s because it is in use.
CAUSE: Cannot delete an ACL that is in use.
ACTION: obsolete
PARAMS:

ERROR: [DM_ACL_E_CANT_FETCH_USER]

SEVERITY: ERROR
DESCRIPTION: SS The operation to the ACL object %s failed due to failure to fetch dmUser %s and failure to check permissions.
CAUSE: Unable to fetch the updating user.
ACTION:
PARAMS:

ERROR: [DM_ACL_E_REFRESH_BAD_ACL_TEMPLATE]

SEVERITY: ERROR
DESCRIPTION: SS The ACL instance object named %s refers to a non-existent template ACL object %s.
CAUSE: The template ACL object does not exist.
ACTION: Check to see if the template ACL is deleted by someone else.
PARAMS:

ERROR: [DM_ACL_E_TRUSTED_CONTENT_SERVICES_NOT_ENABLED]

SEVERITY: ERROR
DESCRIPTION: Trusted Content Services (TCS) must be enabled to access Mandatory Access Control (MACL) functionality.
CAUSE: License for Trusted Content Services is not available. This license is necessary to access MACL functionality.
ACTION: Make sure that you have the license for Trusted Content Services.
PARAMS:

ERROR: [DM_ACL_E_ACE_XPERMIT_NOT_NULL]

SEVERITY: ERROR
DESCRIPTION: SSII The Accessor Control Entry (ACE) for accessor %s, permit_type %s(%d) has a non-null xpermit of %d.
CAUSE: The specified ACE cannot have a non-null xpermit.
ACTION: Ensure that the xpermit for the ACE is NULL (0) or that the permit_type is correct.
PARAMS:

ERROR: [DM_ACL_E_FAILED_TO_UPGRADE_ACL_INSTANCE]

SEVERITY: ERROR
DESCRIPTION: DS Could not upgrade ACL Instance with ID %s and object_name %s. The ACL Instance to ACL Template/Alias Set mapping is not complete.
CAUSE: Starting from the 5.3 Server, ACL Instance to ACL Template/Alias Set Id mapping is being moved from the object_name field to r_template_id and r_alias_set_id attributes. The server has encountered an error while completing this conversion.
ACTION: See additional error messages for more detail on why the conversion failed.
PARAMS:

ERROR: [DM_ACL_E_ACE_APPLICATION_PERMIT_NOT_NULL]

SEVERITY: ERROR
DESCRIPTION: SSIS The Accessor Control Entry (ACE) for accessor %s, permit_type %s(%d) has a non-null application_permit of %s.
CAUSE: The specified ACE cannot have a non-null application_permit.
ACTION: Ensure that the application permit for the ACE is NULL (0) or that the permit_type is correct.
PARAMS:

ERROR: [DM_ACL_E_UNIQUE_NAME]

SEVERITY: ERROR
DESCRIPTION: ACL name has to be unique in a given domain.
CAUSE: Attempt to create an ACL that has a name conflict.
ACTION: Use different object_name.
PARAMS:

ERROR: [DM_ACL_E_MOD_SYSACL]

SEVERITY: ERROR
DESCRIPTION: SS The ACL %s can only be modified by its owner %s, system admins or superusers.
CAUSE: The user is neither owner of the system ACL nor sysadmin/superusers.
ACTION: Ask sysadmin or superuser for help.
PARAMS:

ERROR: [DM_ACL_E_CANT_FETCH]

SEVERITY: ERROR
DESCRIPTION: D Cannot fetch – Invalid object ID %s
CAUSE: Could not fetch an object with the given id.
ACTION: This is probably caused by a bad ID. Or, possibly, a connection to the Documentum server could not be established.
PARAMS:

ERROR: [DM_ACL_E_ACE_APPLICATION_PERMIT_NOT_ALLOWED]

SEVERITY: ERROR
DESCRIPTION: SSI The Accessor Control Entry (ACE) for accessor %s, permit_type %s(%d), cannot have an application_permit value.
CAUSE: An application_permit value has been specified for a permit_type that does not allow it.
ACTION: Check the permit_type and application_permit value for the specified accessor.
PARAMS:

ERROR: [DM_ACL_E_OWNER_NOT_ALLOWED]

SEVERITY: ERROR
DESCRIPTION: SS Setting the owner_name of the ACL %s to %s is not allowed.
CAUSE: Try to use other user as the owner_name of the ACL.
ACTION:
PARAMS:

ERROR: [DM_ACL_E_NOT_OWNER]

SEVERITY: ERROR
DESCRIPTION: SS The ACL %s can only be modified by its owner %s or superusers.
CAUSE: The user is not the owner of the ACL and modification is not allowed.
ACTION:
PARAMS:

ERROR: [DM_ACL_E_CHANGE_NAME_PRIV]

SEVERITY: ERROR
DESCRIPTION: Changeing ACL owners name or object name requires SUPERUSER privilege.
CAUSE: Try to change ACLs owner_name and object_name without superuser privilege.
ACTION: Please ask superusers to do this for you.
PARAMS:

ERROR: [DM_ACL_E_INVALID_XPERMIT]

SEVERITY: ERROR
DESCRIPTION: IS Illegal extended permit (%d) granted for user %s.
CAUSE: An illegal extended permit was given.
ACTION:
PARAMS:

ERROR: [DM_ACL_E_INTERNAL_FETCH_TYPE_FAILED]

SEVERITY: ERROR
DESCRIPTION: SS Failed to fetch type %s during the following operation: %s
CAUSE: An attempt to fetch an ACL during an internal operation failed.
ACTION: Try the failed operation again. If the message persists, contact technical support. $Id: dmapi.e,v 5.36 2003/05/13 01:42:42 vchandra Exp $ API errors
PARAMS:

ERROR: [DM_ACL_E_ACE_INVALID_XPERMIT]

SEVERITY: ERROR
DESCRIPTION: SSII The Accessor Control Entry (ACE) for accessor %s, permit_type %s(%d), has an illegal extended permit (%d).
CAUSE: An illegal extended permit was specified in the ACE.
ACTION: Check the xpermit for the specified ACE and correct the permit.
PARAMS:

ERROR: [DM_ACL_E_INVALID_PERMIT]

SEVERITY: ERROR
DESCRIPTION: IS Illegal permit (%d) granted for user %s.
CAUSE: An illegal permit was given.
ACTION:
PARAMS:

ERROR: [DM_ACL_E_INVALID_ACE_PERMIT_TYPE]

SEVERITY: ERROR
DESCRIPTION: SI The Accessor Control Entry (ACE) for accessor %s has an invalid permit_type value of %d.
CAUSE: An invalid r_permit_type value has been specified in the specified ACE.
ACTION: Check the parameters for the specified ACE and verify that the correct parameters are being supplied.
PARAMS:

ERROR: [DM_ACL_E_CANT_FETCH_ACL]

SEVERITY: ERROR
DESCRIPTION: SS Failed to fetch the ACL %s in the domain %s.
CAUSE: Failed to fetch the specified ACL.
ACTION:
PARAMS:

ERROR: [DM_ACL_E_MISSING_ACCESSOR_LIST]

SEVERITY: ERROR
DESCRIPTION: The apply method DM_ACL_VALIDATE_REQUIRED_GROUPS requires an accessor list as in input parameter.
CAUSE: A list of accessors was not provided to the apply method
ACTION: Supply a list of accessors to the apply method
PARAMS: None

ERROR: [DM_ACL_E_INVALID_XPERMIT_NAME]

SEVERITY: ERROR
DESCRIPTION: SS There exists at least one invalid extended permission name in %s for operation %s.
CAUSE: At least one of the extended permission names provided in the list is invalid. Currently, only the following names for extended permissions are supported: (1) execute_proc (2) change_location (3) change_state (4) change_permit (5) take_owner (6) delete_object
ACTION: Only supply names in the above list.
PARAMS:

ERROR: [DM_ACL_E_BAD_STATE]

SEVERITY: ERROR
DESCRIPTION: SS The ACL %s of domain %s is in bad state.
CAUSE: The ACL is marked bad somehow.
ACTION:
PARAMS:

ERROR: [DM_ACL_E_CURSOR]

SEVERITY: ERROR
DESCRIPTION: SS The cursor %s failed. The error message from the database server is: %s.
CAUSE: Cursor failure.
ACTION:
PARAMS:

ERROR: [DM_ACL_E_ACE_INTERNAL_INVALID_PERMIT_TYPE]

SEVERITY: ERROR
DESCRIPTION: SSI The Accessor Control Entry (ACE) for accessor %s has an invalid permit_type %s(%d).
CAUSE: An invalid permit_type has been specified for the ACE.
ACTION: Typically, this is an internal error. Check the ACE.
PARAMS:

ERROR: [DM_ACL_E_NOMATCH]

SEVERITY: ERROR
DESCRIPTION: SS No ACEs matched for the name %s in the ACL %s.
CAUSE: There are no ACEs found with the name.
ACTION:
PARAMS:

ERROR: [DM_ACL_E_QUERY_EXECUTION_FAILURE]

SEVERITY: ERROR
DESCRIPTION: SS Error while trying to execute the following query: %s. Database error is %s.
CAUSE: Query execution failed.
ACTION: Check the error message from the database in order to determine the cause of the query failure.
PARAMS: The first parameter is the query that was being executed. The second parameter is the resulting error from the database.

ERROR: [DM_ACL_E_CANNOT_RESTRICT_MORE_THAN_GRANTED]

SEVERITY: ERROR
DESCRIPTION: DSII The ACL with ID %s can not restrict the permission of accessor %s to (%d) because an equal or lower permission (%d) is granted.
CAUSE: User trid to restrict the access permit of an accessor more than what has been granted to the same user in an ACL/sysobject.
ACTION: Check the access permit (permit_type = 0) and access restriction (permit_type = 3) of the user. Make sure the user is not restricted more than what has been granted to him/her.
PARAMS:

ERROR: [DM_ACL_E_CANT_UNREGISTER]

SEVERITY: ERROR
DESCRIPTION: SS Could not unregister the specified %s event for %s object.
CAUSE: The specified event could not be unregistered. Most likely bad event name specified.
ACTION: Correct the event name and try again.
PARAMS:

ERROR: [DM_ACL_E_MACL_NOT_SUPPORTED]

SEVERITY: ERROR
DESCRIPTION: The current docbase does not support MACL Security.
CAUSE: The connected docbase does not support MACL Security. The user or application has attempted to get or set MACL Security parameters.
ACTION: MACL Security rules cannot be set or retrieved from this docbase.
PARAMS:

ERROR: [DM_ACL_E_MOD_NAME_DOMAIN]

SEVERITY: ERROR
DESCRIPTION: S Changing domain or name of the ACL %s is not allowed, once the ACL is created.
CAUSE: Tried to modify the domain or object_name of the ACL.
ACTION:
PARAMS:

ERROR: [DM_ACL_E_PERMIT_TYPE_REQUIRES_GROUP]

SEVERITY: ERROR
DESCRIPTION: SSI The Accessor Control Entry (ACE) for accessor %s is invalid. The accessor for permit_type value of %s(%d) must be a valid group.
CAUSE: The specified permit_type value can only be used in conjunction with and accessor that is a valid group.
ACTION: Ensure that the permit_type is valid or that the accessor is a valid group.
PARAMS:

ERROR: [DM_ACL_E_ACE_PERMIT_NOT_NULL]

SEVERITY: ERROR
DESCRIPTION: SSII The Accessor Control Entry (ACE) for accessor %s, permit_type %s(%d) has a non-null permit of %d.
CAUSE: The specified ACE cannot have a non-null permit.
ACTION: Ensure that the permit for the ACE is NULL (0) or that the permit_type is correct.
PARAMS:

ERROR: [DM_ACL_E_CANT_CREATE_INSTANCE]

SEVERITY: ERROR
DESCRIPTION: SSS Cannot create an instance %s of template ACL %s based on alias set %s.
CAUSE: Failed to create an instance of the said template ACL. There must exist at least one alias which cant be resolved based on the said alias set.
ACTION:
PARAMS:

ERROR: [DM_ACL_F_PUB_BIT_CHANGE_FAILED]

SEVERITY: FATAL
DESCRIPTION: SS Failure changing public bits when acl %s (domain %s) changed.
CAUSE: Probable database error.
ACTION: Look for messages from the RDBMS.
PARAMS:

ERROR: [DM_ACL_F_TYPE_INIT]

SEVERITY: FATAL
DESCRIPTION: Failed to initialize type dm_acl.
CAUSE: Unknown.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_ACL_F_REFRESH_SELECT_INSTANCE]

SEVERITY: FATAL
DESCRIPTION: SS Failure retrieving instances of template ACL. Select statement is %s. DB error is %s.
CAUSE: Internal error.
ACTION: Report the problem.
PARAMS:

ERROR: [DM_ACL_F_BAD_VSTAMP]

SEVERITY: FATAL
DESCRIPTION: II Type dm_acl has a bad vstamp %d. The current vstamp for dm_acl is supposed to be %d.
CAUSE: The RDBMS table has a bad vstamp.
ACTION: Report this error to Documentum sysadmins.
PARAMS:

ERROR: [DM_ACL_F_TYPE_CONVERSION]

SEVERITY: FATAL
DESCRIPTION: I Failed to convert type dm_acl to version %d.
CAUSE: Type conversion failed.
ACTION: Report the problem.
PARAMS:

ERROR: [DM_ACL_W_RENAMED_ACCESSOR_EXISTS]

SEVERITY: WARNING
DESCRIPTION: SSS Renaming accessor_name from %s to %s for ACL %s caused the existing ACE with the same qualification being removed.
CAUSE: There already exists another ACE with the same accessor_name, permit_type, and application_permit. The problem is very likely caused by the logic of replacing dm_group with the sysobjects group_name while there is already another ACE that has the same qualification.
ACTION: Since the changes did not affect the original ACL, it shouldnt cause any problem. Otherwise, choose ACL carefully to ensure that the resulting ACL would not have the conflict while renaming an accessor name to another name.
PARAMS:

ERROR: [DM_ACL_W_ACL_INSTANCES_NEED_CONVERSION]

SEVERITY: WARNING
DESCRIPTION: Server did not convert all ACL Instances to use r_template_id and r_alias_set_id as part of the upgrade because there are too many. Administrator should manually use the apply method DM_CONVERT_ACL_INSTANCES (i.e., apply,c,NULL,DM_CONVERT_ACL_INSTANCES) after upgrade completes.
CAUSE: For performance reasons, the server will only convert up to 1000 ACL Instances as part of the upgrade. Before the remaining ACL Instances can be used they must be converted to the new format by using the apply method DM_CONVERT_ACL_INSTANCES.
ACTION: After the upgrade is complete, the Administrator should run the apply method DM_CONVERT_ACL_INSTANCES to convert the remaining ACL instances. The Administrator can query for all ACLs with acl_class = 2 to determine the total number of ACL Instances that exist.
PARAMS:

nahoru

DM_API

ERROR: [DM_API_F_CACHE_UNREADABLE]

SEVERITY: FATAL
DESCRIPTION: An unexpected internal error has occurred while reading query results from the query cache for your query.
CAUSE: The disk file containing your query results cache is unreadable.
ACTION: Report this problem to your Documentum System Administrator. You should also flush the query cache.
PARAMS:

ERROR: [DM_API_F_CACHE_CLOSE]

SEVERITY: FATAL
DESCRIPTION: An unexpected error has occurred while closing the query cache for your query.
CAUSE: This disk file containing your query results cache could not be closed for some reason.
ACTION: Report this problem to your Documentum System Administrator. You should also flush the query cache. The results displayed by your query will be complete unless other error messages have occurred.
PARAMS:

ERROR: [DM_API_F_BADRPCDLL]

SEVERITY: FATAL
DESCRIPTION: IIII You have a mismatched rpcdll.dll and dmcl.dll. rpc version: %d, rpc release: %d. Expected version: %d, expected release: %d
CAUSE: The rpcdll.dll and dmcl.dll libraries are incompatible and are different versions of the product.
ACTION: Verify the installation of rpcdll.dll and dmcl.dll and check your path for other possible dlls
PARAMS:

ERROR: [DM_API_F_CACHE_OBJECT]

SEVERITY: FATAL
DESCRIPTION: An unexpected error has occurred while loading an object from the query cache for your query.
CAUSE: An object in your query cache is not a valid object.
ACTION: Report this problem to your Documentum System Administrator. You should also flush the query cache. The results returned so far by your query may not be complete.
PARAMS:

ERROR: [DM_API_F_CACHE_MAP]

SEVERITY: FATAL
DESCRIPTION: An unexpected internal error has occurred while processing a cached query.
CAUSE: This is an internal inconsistency.
ACTION: Contact your site Documentum System Administrator. To get past this problem, try flushing the query cache and restarting your session. If that doesnt work, turn off query caching in your dmcl.ini file. $Id: dmassmbl.e,v 5.2 2003/05/12 16:34:04 nagboat Exp $ dmAssembly class errors
PARAMS:

ERROR: [DM_API_F_CACHE_READ]

SEVERITY: FATAL
DESCRIPTION: An unexpected internal error has occurred while reading query results from the query cache for your query.
CAUSE: The disk file containing your query results cache was unreadable for some reason.
ACTION: Report this problem to your Documentum System Administrator. You should also flush the query cache. The results returned so far by your query may not be complete.
PARAMS:

ERROR: [DM_API_F_INTERNAL]

SEVERITY: FATAL
DESCRIPTION: S An unexpected internal inconsistency has caused your operation to fail (%s).
CAUSE: Unknown.
ACTION: Provide this message, and its parameter, and any other recent messages from your session, and contact your Documentum site representative.
PARAMS: The parameter is an indication of where the error occurred.

ERROR: [DM_API_E_INVALID_TOKEN_SCOPE]

SEVERITY: ERROR
DESCRIPTION: S Invalid token scope (%s). It must be global or docbase.
CAUSE: wrong application token scope value is specified for gettoken.
ACTION: specify a correct application token scope value
PARAMS: S – The specified application token scope

ERROR: [DM_API_E_ISCACHED_NO_CACHE_NAME]

SEVERITY: ERROR
DESCRIPTION: A cache name must be supplied to the iscached API call.
CAUSE: You have specified a call to the iscached API call with no cache name.
ACTION: Supply a valid cache name, for example typecache.
PARAMS: None.

ERROR: [DM_API_E_MISSING_PASSWORD]

SEVERITY: ERROR
DESCRIPTION: A password must be provided.
CAUSE: A password was not provided for the API method resetpassword.
ACTION: specify a valid password
PARAMS: None

ERROR: [DM_API_E_NOT_IN_CACHE]

SEVERITY: ERROR
DESCRIPTION: S Document/object specified by %s does not exist in the cache.
CAUSE: You have specified an object id for an object which does not exist in the cache. Some API like lock requires the object to reside in cache before applying the operation.
ACTION: Fetch the object and re-try the same operation.
PARAMS: The object id.

ERROR: [DM_API_E_API_SHUTDOWN]

SEVERITY: ERROR
DESCRIPTION: S The DMCL has been disabled due to an internal error, command %s was not run. The process needs to be restarted.
CAUSE: Earlier errors of type DM_API_E_EXCEPTION or DM_API_E_EXCEPTION_ON_SESSION have occcurred.
ACTION: In its current state, the DMCL is no longer usable. The process will have to be restarted.
PARAMS: S – api command

ERROR: [DM_API_E_NO_MATCH]

SEVERITY: ERROR
DESCRIPTION: S There was no match in the docbase for the qualification: %s
CAUSE: The qualification you provided did not match any object.
ACTION: None required. If you think there really should have been a match reexamine your qualification, correct it, and resubmit it.
PARAMS: The qualification.

ERROR: [DM_API_E_ONELISTMSG]

SEVERITY: ERROR
DESCRIPTION: Cannot have multiple listmessage collections open simultaneously.
CAUSE: User tried to have more than one listmessage collection opened.
ACTION: Close the previous listmessage collection, before opening the next one.
PARAMS:

ERROR: [DM_API_E_BADSESS]

SEVERITY: ERROR
DESCRIPTION: S Bad session specifier %s, try using current.
CAUSE: You have incorrectly specified the session in your command line.
ACTION: Correct the session specification and retry the command. If you do not know what the correct session specification is, you could use current.
PARAMS: The incorrect session as specified in your command.

ERROR: [DM_API_E_NOT_SELECT]

SEVERITY: ERROR
DESCRIPTION: You have specified an unsupported statement type in a cachequery.
CAUSE: Only SELECT statements may be specified using cachequery.
ACTION: Resubmit the DQL statement using the readquery, query, or execquery method. If the statement is being run by an application, contact your Documentum System Administrator about having the application corrected.
PARAMS:

ERROR: [DM_API_E_NOLAST]

SEVERITY: ERROR
DESCRIPTION: Cannot use last for document/object id. Must fetch or create document/object first.
CAUSE: You have specified last in place of a document or object id, but no object is active.
ACTION: Specify the object id explicitly in your command and retry.
PARAMS: None.

ERROR: [DM_API_E_CANNOT_FETCH_POLICY]

SEVERITY: ERROR
DESCRIPTION: D Cannot fetch a business policy with object id %s.
CAUSE: A business policy object with the supplied id could not be found.
ACTION: Specify a valid business policy object id.
PARAMS: The parameter is the business policy object id that was supplied.

ERROR: [DM_API_E_NOPASSWORD]

SEVERITY: ERROR
DESCRIPTION: There is no password argument specified.
CAUSE: You have not specified the password which is required to electronically sign off an object.
ACTION: Please specify the valid password of the user who is signing off the object.
PARAMS:

ERROR: [DM_API_E_BADSTAMP]

SEVERITY: ERROR
DESCRIPTION: S Bad queue stamp specifier for queue %s.
CAUSE: Your command did not specify a stamp.
ACTION: The stamp is the unique identifier for the object you wish to dequeue. It must be specified on this command.
PARAMS: The name of the queue.

ERROR: [DM_API_E_MUSTBE_NEXT]

SEVERITY: ERROR
DESCRIPTION: You must specify next as the state name to promote to.
CAUSE: This is to reserve a field for Promote API to easily expand into state network model. Currently, next is only aceptable state, which simply means the next state of the current state.:wq
ACTION:
PARAMS:

ERROR: [DM_API_E_DOCBASE_SCOPE_ID]

SEVERITY: ERROR
DESCRIPTION: L Could not connect to docbase. Docbase id %d could not be found.
CAUSE: The request failed due to an unknown docbase name in the scope setting. Unless the requested command has a scope argument the scope is derived from the sessionconfigs docbase_scope attribute.
ACTION: Check the request to see if the scope argument is valid. If it is, verify that the requested docbase is available. Check that the application is using a docbroker that the requested server projects to. Try connecting to the docbase directly through the connect api or login.
PARAMS: %1s – the docbase id being searched for

ERROR: [DM_API_E_UNKNOWN_SECURE_FLAG]

SEVERITY: ERROR
DESCRIPTION: S Unknown secure connect flag %s is specified.
CAUSE: Unknown secure connect flag specified. Valid secure connect flags are secure, native, try_secure_first and try_native_first.
ACTION: specify a valid secure connect flag.
PARAMS: Secure connect flag specified.

ERROR: [DM_API_E_INVALID_TYPE_FOR_METHOD]

SEVERITY: ERROR
DESCRIPTION: SSS Cannot perform %s method on supplied object of id (%s) since it is not of type (%s).
CAUSE: The specified operation not supported on this type of sysobject.
ACTION: None.
PARAMS:

ERROR: [DM_API_E_NOCACHE]

SEVERITY: ERROR
DESCRIPTION: Internal error, cache is missing.
CAUSE: This is a very unlikely event. Your internal object cache has been destroyed.
ACTION: This is not recoverable. You must restart your session.
PARAMS: None.

ERROR: [DM_API_E_QUERY_FAIL]

SEVERITY: ERROR
DESCRIPTION: S Query failed: %s
CAUSE: Your query failed. Either you specified the query incorrectly on the command line, or the query executed, but failed to return a query results collection. This may be a query that was run on behalf of a non-query method that you have invoked. It may be that a qualification that you have provided (for the ID or RETRIEVE methods, for example) was in error.
ACTION: Examine the rest of the error messages on your sessions message queue. If there are no other messages, then the query was incorrectly specified on the command line. Examine your command line and make the necessary corrections. If there are additional messages, they will explain what the cause of the failure was, and what to do about it.
PARAMS: The query.

ERROR: [DM_API_E_FLUSH_DD_CACHE_NO_KEY]

SEVERITY: ERROR
DESCRIPTION: A cache key must be supplied to the flush API call when ddcache is specified.
CAUSE: You have specified a call to the flush API for the ddcache without specifying a cache key. The cache key indicates for which type the Data Dictionary information should be flushed.
ACTION: Supply a key that is the name of an object type.
PARAMS: None.

ERROR: [DM_API_E_SCHD_POLICY_NO_STATE]

SEVERITY: ERROR
DESCRIPTION: A scheduled policy event requires a state name specified.
CAUSE: User tries to schedule a policy event (promote, demote, suspend, resume) without providing a source (or target) state name/position.
ACTION: Supply a source or target state name/position.
PARAMS:

ERROR: [DM_API_E_NO_COLLECTION]

SEVERITY: ERROR
DESCRIPTION: There are no more available collection object for the current session.
CAUSE: User has used all available collection. Current limit is 10 per session.
ACTION: Close some unused collections.
PARAMS:

ERROR: [DM_API_E_NOTASKNUM]

SEVERITY: ERROR
DESCRIPTION: No task number specified during router operations.
CAUSE: You have not specified a task number during a router operation. (i.e. forward, reverse, …)
ACTION: Specify the task number during this router operation.
PARAMS:

ERROR: [DM_API_E_BAD_POSITION]

SEVERITY: ERROR
DESCRIPTION: S Invalid position argument (%s) to seek method
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_API_E_NODEVNAME]

SEVERITY: ERROR
DESCRIPTION: S No device name was given for command %s.
CAUSE: The device name is required for this command.
ACTION: Correct the command to specify the device name.
PARAMS: The command as specified.

ERROR: [DM_API_E_NOTYPE]

SEVERITY: ERROR
DESCRIPTION: S Type name %s is not a valid type.
CAUSE: The specified typename is not valid.
ACTION: If this is a typename that you have specified explicitly on a command line, ensure that the type exists, correct the command and retry. Otherwise, this is a type that a command requires internally, and it does not exist. This may be an internal problem. Report this error to your Documentum site representative.
PARAMS: The name of the type as passed to the API.

ERROR: [DM_API_E_CANT_WITH_OPEN_TRAN]

SEVERITY: ERROR
DESCRIPTION: SD You cannot perform %s operation since there is an open transaction in this session %s.
CAUSE: Since attach,promote,demote,suspend,continue all inlvolve some form of procedure execution in which the sysobject changes are committed. This is to prevent hanging/save failure from happening.
ACTION:
PARAMS:

ERROR: [DM_API_E_NOFOLDID]

SEVERITY: ERROR
DESCRIPTION: No folder id given for a link/unlink command.
CAUSE: The folder id is required for link and unlink.
ACTION: Correct the command to specify a folder id.
PARAMS: None.

ERROR: [DM_API_E_NOSESS]

SEVERITY: ERROR
DESCRIPTION: No session is currently active.
CAUSE: You are not connected with a session.
ACTION: Your session may have been dropped due to inactivity. You must start up another session.
PARAMS: None.

ERROR: [DM_API_E_ERROR]

SEVERITY: ERROR
DESCRIPTION: General internal error: API has failed.
CAUSE: Unknown internal problem.
ACTION: This error is unrecoverable. Report this error message, and any other recent error messages from your session, to your Documentum site representative.
PARAMS: None.

ERROR: [DM_API_E_BAD_EXTENSION_FOR_BATCH]

SEVERITY: ERROR
DESCRIPTION: SS The extension of the input file, %s, is not allowed for %s in batch mode.
CAUSE: We currently only support tar format file with extension tar in batch addrendition.
ACTION: We only support tar format file in batch addrendition. You have to specify a tarred file with extension tar.
PARAMS: file name and name of the API.

ERROR: [DM_API_E_BAD_DIRECTION]

SEVERITY: ERROR
DESCRIPTION: S An improper direction (%s) was specified in a seek.
CAUSE: Direction specification in a seek must be one of C, B, E
ACTION: Use a valid direction specification
PARAMS: The direction specification that was supplied.

ERROR: [DM_API_E_COMMAND_OBSOLETE]

SEVERITY: ERROR
DESCRIPTION: S The API command %s is no longer supported.
CAUSE: An obsolete API command has requested.
ACTION: The application should be modified to no longer depend on the obsolete command.
PARAMS: The command requested.

ERROR: [DM_API_E_NO_REMOTE_POLICY]

SEVERITY: ERROR
DESCRIPTION: L You cannot attach to a non-local business policy object from docase id %d.
CAUSE: The policy object id is either a bogus one or is foreign.
ACTION:
PARAMS:

ERROR: [DM_API_E_MISS_PACKAGE_TYPE]

SEVERITY: ERROR
DESCRIPTION: Parameter, package type, is missing.
CAUSE: Parameter, package type, was not specified.
ACTION: Specify package type.
PARAMS:

ERROR: [DM_API_E_NOPRIORITY]

SEVERITY: ERROR
DESCRIPTION: S No priority specified for routing.
CAUSE:
ACTION:
PARAMS: None.

ERROR: [DM_API_E_BADID]

SEVERITY: ERROR
DESCRIPTION: S Bad ID given: %s
CAUSE: You have specified an invalid id.
ACTION: Retry with a valid id definition.
PARAMS:

ERROR: [DM_API_E_MISSING_CONTAINMENT_TYPE]

SEVERITY: ERROR
DESCRIPTION: S A containment desc of %s was supplied but its corresponding containment type is missing.
CAUSE: The containment type must be supplied if the containment description is supplied.
ACTION: Supply the corresponding containment type.
PARAMS:

ERROR: [DM_API_E_NO_USER]

SEVERITY: ERROR
DESCRIPTION: Need to specifiy an user.
CAUSE: Need to specifiy a user as the performer.
ACTION: Specify an user name.
PARAMS:

ERROR: [DM_API_E_BADCMD]

SEVERITY: ERROR
DESCRIPTION: S Bad API command %s
CAUSE: An API command has been incorrectly formed.
ACTION: If the parameter is , make sure that no spaces precede your specified command in the command line. Otherwise, check to be sure that the command you have specified is a valid API command. Reformulate and retry your command.
PARAMS: The command as specified, or .

ERROR: [DM_API_E_DOCBASE_SCOPE]

SEVERITY: ERROR
DESCRIPTION: S Could not connect to docbase. Docbase %s could not be found.
CAUSE: The request failed due to an unknown docbase name in the scope setting. Unless the requested command has a scope argument the scope is derived from the sessionconfigs docbase_scope attribute.
ACTION: Verify that the requested docbase is available. Check that the application is using a docbroker that the requested server projects to. Try connecting to the docbase directly through the connect api or login.
PARAMS: %1s – the user-specified docbase name

ERROR: [DM_API_E_NOSCOPE]

SEVERITY: ERROR
DESCRIPTION: The required scope argument is missing.
CAUSE: The request failed due to an invalid docbase scope argument.
ACTION: Modify request to include scope value.
PARAMS: None

ERROR: [DM_API_E_NO_FILE]

SEVERITY: ERROR
DESCRIPTION: S No file name given for command %s.
CAUSE: A file name is required for this command.
ACTION: Correct the command to specify a file name.
PARAMS: The command as specified

ERROR: [DM_API_E_NODBPASSWD]

SEVERITY: ERROR
DESCRIPTION: No database password provided for a connection.
CAUSE: The fourth argument has not been provided for a connect statement.
ACTION: Provide a complete connect statement.
PARAMS:

ERROR: [DM_API_E_INVALID_ARG_APPLY]

SEVERITY: ERROR
DESCRIPTION: SSS Invalid value (%s) for the %s argument of %s apply method.
CAUSE: Invalid value for an argument of an apply method.
ACTION: Specify a valid value for the argument.
PARAMS:

ERROR: [DM_API_E_NO_ACL_SOURCE]

SEVERITY: ERROR
DESCRIPTION: The ACL inheritance source is missing.
CAUSE: The inheritance source of useacl cmd is missing.
ACTION:
PARAMS:

ERROR: [DM_API_E_NO_CACHE_NAME]

SEVERITY: ERROR
DESCRIPTION: The name of the global cache to be flushed is missing.
CAUSE: The name of the global cache to be flushed is missing from the flushglobalcache method.
ACTION: Provide the cache name in the flushglobalcache method. Currently, only user cache is allowed.
PARAMS:

ERROR: [DM_API_E_EXIST]

SEVERITY: ERROR
DESCRIPTION: S Document/object specified by %s does not exist.
CAUSE: You have specified an object id for an object which does not exist.
ACTION: Ensure that you are specifying the correct object id. Remember that you save a new object, it gets a new id. If there are additional error messages on your session, they may contain information which is helpful as well.
PARAMS: The object id.

ERROR: [DM_API_E_MISS_PACKAGE_NAME]

SEVERITY: ERROR
DESCRIPTION: Parameter, package name, is missing.
CAUSE: Parameter, package name, was not specified.
ACTION: Specify package name.
PARAMS:

ERROR: [DM_API_E_INVALID_TICKET_SCOPE]

SEVERITY: ERROR
DESCRIPTION: S Invalid login ticket scope (%s). It must be global, docbase, or server.
CAUSE: wrong login ticket scope value is specified for getlogin.
ACTION: specify a correct login ticket scope value
PARAMS: S – The specified login ticket scope

ERROR: [DM_API_E_MISS_LINK_NAME]

SEVERITY: ERROR
DESCRIPTION: Missing parameter link name.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_API_E_FLUSH_DD_CACHE_BAD_KEY]

SEVERITY: ERROR
DESCRIPTION: S A cache key (%s) was supplied to the flush ddcache API call that is not the name of a type.
CAUSE: The cache key you specified is not the name of a type.
ACTION: Supply a key that is the name of an object type.
PARAMS: None.

ERROR: [DM_API_E_NOPERMIT]

SEVERITY: ERROR
DESCRIPTION: The accessor permit is missing.
CAUSE: Accessor permit is missing from the cmd line.
ACTION: Provide the accessor permit.
PARAMS:

ERROR: [DM_API_E_EXPECT_BOOL]

SEVERITY: ERROR
DESCRIPTION: ISS A null or boolean value was expected for positional parameter %d. Bad value: %s. This parameter specifies %s.
CAUSE: The command expected to parse a boolean or no value at all. Boolean arguments can take the form: t, T, f, F, true, false, TRUE, FALSE
ACTION:
PARAMS:

ERROR: [DM_API_E_NULL_TICKET]

SEVERITY: ERROR
DESCRIPTION: A login ticket must be provided.
CAUSE: Missing login ticket argument for the API method dumploginticket
ACTION: Specify a login ticket
PARAMS: None

ERROR: [DM_API_E_POLICY_STATE_NOT_FOUND]

SEVERITY: ERROR
DESCRIPTION: DS The business policy with object id %s does not have a state named %s.
CAUSE: The supplied state name could not be found in the given business policy.
ACTION: Specify a valid state name for the business policy.
PARAMS: The first parameter is the business policy object id that was supplied. The second parameter is the state name supplied.

ERROR: [DM_API_E_FACILITY_UNKNOWN]

SEVERITY: ERROR
DESCRIPTION: S The specified facility (%s) is not a valid trace facility.
CAUSE: The command specified an invalid facility name.
ACTION: Check command syntax – check that facility name is upper case.
PARAMS: %1s – the user-specified facility name

ERROR: [DM_API_E_NO_PERMIT_TYPE]

SEVERITY: ERROR
DESCRIPTION: No value for permit_type was specified.
CAUSE: No permit_type value was specified in the API
ACTION: Check the API syntax and ensure that a permit_type value is specified
PARAMS:

ERROR: [DM_API_E_BAD_ARGS]

SEVERITY: ERROR
DESCRIPTION: SS Invalid or insufficient arguments for %s for %s API
CAUSE: User did not specify valid values for required argument while executing the specified API.
ACTION: Specify value for required arguments and retry.
PARAMS: S – argument name(s) S – API Name.

ERROR: [DM_API_E_INVALID_MACHINE_ONLY]

SEVERITY: ERROR
DESCRIPTION: S Invalid machine_only parameter value (%s). It must be T or t.
CAUSE: Wrong machine_only parameter value is specified for gettokn.
ACTION: Specify a correct value for machine_only.
PARAMS: S – The specified value for machine_only parameter

ERROR: [DM_API_E_NOTYPE2]

SEVERITY: ERROR
DESCRIPTION: No type was specified.
CAUSE: You have specified a command for which the type must be specified.
ACTION: Add the type to your command, and retry.
PARAMS: None.

ERROR: [DM_API_E_NOOSPASSWD]

SEVERITY: ERROR
DESCRIPTION: No operating system password has been provided for a connection.
CAUSE: The third argument has not been provided for a connect statement.
ACTION: Provide a complete connect statement.
PARAMS:

ERROR: [DM_API_E_MISS_INPUT_PORT_NAME]

SEVERITY: ERROR
DESCRIPTION: The parameter, input port name, is missing.
CAUSE: Parameter, input port name, is required for the command.
ACTION: Specify the input port name in the command.
PARAMS:

ERROR: [DM_API_E_MISS_ACTIVITY_DEF_ID]

SEVERITY: ERROR
DESCRIPTION: Missing parameter activity definition id.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_API_E_NOEVENTNAME]

SEVERITY: ERROR
DESCRIPTION: No event name specified during register/unregister operations.
CAUSE: You have not specified an event name during event register/unregister operation.
ACTION: Specify the event name.
PARAMS:

ERROR: [DM_API_E_DEQUEUE_FAIL]

SEVERITY: ERROR
DESCRIPTION: S Dequeue operation on queue item %s failed
CAUSE: The requested dequeue failed during server execution.
ACTION: There will be additional error messages queued on your session. Those error messages will contain information on why this operation failed. Follow the suggested actions in those error messages to correct this problem.
PARAMS: The name of the queue.

ERROR: [DM_API_E_FLUSH_BAD_ARG]

SEVERITY: ERROR
DESCRIPTION: S The flush method had an unsupported cache name argument: %s.
CAUSE: A flush method was invoked with a cachename argument that is not supported. Currently only querycache is supported.
ACTION: Change the cachename argument to a supported cachename and retry.
PARAMS:

ERROR: [DM_API_E_DESCRIBE_TABOWNER]

SEVERITY: ERROR
DESCRIPTION: To execute this describe table operation against the current server you must supply the table owner name in the command (ie. describe table owner_name.table_name).
CAUSE: The server to which the application is connected does not support the describe table command on system tables (beginning with dm). The application is likely connected to an older server which cannot process the requested action.
ACTION: If possible upgrade the server to resolve the problem. Otherwise issue the owner name along with the table name in the describe command.
PARAMS: None

ERROR: [DM_API_E_DOCBASE_NOT_ALLOWED]

SEVERITY: ERROR
DESCRIPTION: S You cannot specify a docbase name (%s) if you use a session in authenticate API.
CAUSE: If a session is specified in the authenticate API, no docbase name should be used.
ACTION: Verify your argument of authenticate API to meet this requirement.
PARAMS: S – Docbase name.

ERROR: [DM_API_E_BADATTRSTATE]

SEVERITY: ERROR
DESCRIPTION: SS Attribute name %s for policy has incorrect value %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_API_E_FLUSH_REGISTRY_CACHE_NO_KEY]

SEVERITY: ERROR
DESCRIPTION: A cache key must be supplied to the flush API call when registrycache is specified.
CAUSE: You have specified a call to the flush API for the registrycache without specifying a cache key. The cache key indicates for which type the in memory registry information should be flushed.
ACTION: Supply a key that is the name of an object type.
PARAMS: None.

ERROR: [DM_API_E_BADSCOPE]

SEVERITY: ERROR
DESCRIPTION: S Docbase scope identifier (%s) is not valid.
CAUSE: The request failed due to an invalid docbase scope argument. The scope value is specified directly on some commands (eg getconnection takes a scope argument) – and is otherwise picked up from the sessionconfigs docbase_scope attribute.
ACTION: Change the scope value – either on the command line or in the sessionconfig docbase_scope field – to be a legal scope value.
PARAMS: %1s – the user-specified scope value

ERROR: [DM_API_E_MISS_ACT_NAME]

SEVERITY: ERROR
DESCRIPTION: The parameter, activity name, is missing.
CAUSE: Parameter, activity name, is required for the command.
ACTION: Specify the activity name in the command.
PARAMS:

ERROR: [DM_API_E_BADDATE]

SEVERITY: ERROR
DESCRIPTION: SS You have specified an unrecognized date representation %s based on format %s
CAUSE: The date representation shown does not conform to the date formats that Documentum recognizes, or the date is not in the valid date range. Dates prior to the year 1970 may not be specified.
ACTION: Correct the date.
PARAMS: The incorrectly specified date.

ERROR: [DM_API_E_ACCESS]

SEVERITY: ERROR
DESCRIPTION: S Document/object specified by %s cannot be accessed.
CAUSE: You have specified an object id for an object which cannot be accessed.
ACTION: Ensure that you are specifying the correct object id. Remember that you save a new object, it gets a new id. If there are additional error messages on your session, they may contain information which is helpful as well.
PARAMS: The object id.

ERROR: [DM_API_E_MISS_DEST_PORT]

SEVERITY: ERROR
DESCRIPTION: Missing parameter destination port.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_API_E_EXCEPTION]

SEVERITY: ERROR
DESCRIPTION: S An unexpected error has caused the current command to be aborted. A detailed description of the error can be found in %s.
CAUSE: An unknown error has caused a memory access violation.
ACTION: Provide this message, and the contents of the error report file, and contact your Documentum site representative.
PARAMS: S – pathname to error file dmcl_err_pid__

ERROR: [DM_API_E_NOUSERNAME]

SEVERITY: ERROR
DESCRIPTION: No user name have been provided for a connection.
CAUSE: The second argument has not been provided for a connect statement.
ACTION: Provide a complete connect statement.
PARAMS:

ERROR: [DM_API_E_BAD_PAGE_MODIFIER]

SEVERITY: ERROR
DESCRIPTION: S The page_modifier, %s, is reserved for internal use.
CAUSE: The page_modifier specified by user is reserved for internal use.
ACTION: We have reserved dm_batch in page_modifier in order to process addrendition in batch mode. You have to specify a different value for the page_modifier
PARAMS: The page_modifier.

ERROR: [DM_API_E_OUT_OF_MEMORY]

SEVERITY: ERROR
DESCRIPTION: There is not enough memory for creating the object.
CAUSE: System needs more memory
ACTION: Add more memory or reduce the system workload
PARAMS: None

ERROR: [DM_API_E_CANNOT_FETCH_REMOTE_POLICY]

SEVERITY: ERROR
DESCRIPTION: D Cannot fetch a remote business policy with object id %s.
CAUSE: A business policy object with the supplied id could not be found.
ACTION: Verify your access to the remote docbase. Specify a valid business policy object id.
PARAMS: The parameter is the business policy object id that was supplied.

ERROR: [DM_API_E_NOQUERY]

SEVERITY: ERROR
DESCRIPTION: No query has been run. Cannot use a query collection id.
CAUSE: You are attempting to look up an object and its typed based on a query collection which has not had a query run yet.
ACTION: Run a query first.
PARAMS: None.

ERROR: [DM_API_E_CONFIGURATION]

SEVERITY: ERROR
DESCRIPTION: SS The value %s is not a valid setting for %s in the dmcl.ini initialization file.
CAUSE: An invalid parameter value was specified in the dmcl.ini API initialization file.
ACTION: Read the description of the parameter in the dmclfull.ini file.
PARAMS: The parameter value and the parameter name from the dmcl.ini.

ERROR: [DM_API_E_BOOLEAN_FLAG]

SEVERITY: ERROR
DESCRIPTION: S The value %s is not valid. The boolean flag is either T or F.
CAUSE: The value of the boolean flag in the command needs to be either T or F.
ACTION: Change the value of the boolean flag and try again.
PARAMS:

ERROR: [DM_API_E_COMMAND_NOT_SUPPORTED]

SEVERITY: ERROR
DESCRIPTION: SS Server version (%s) does not support the method (%s).
CAUSE: Pre-5.3 Content Server does not support the API the method.
ACTION: Do not use the method with pre-53 Content Server.
PARAMS: S – target server version string S – command name

ERROR: [DM_API_E_ISCACHED_NO_CACHE_KEY]

SEVERITY: ERROR
DESCRIPTION: A cache key must be supplied to the iscached API call.
CAUSE: You have specified a call to the iscached API call with no cache key. The cache key indicates what to look for in the named cache.
ACTION: Supply a key that is appropriate for the named cache.
PARAMS: The parameter is the name of the cache.

ERROR: [DM_API_E_PUBLISH_DD_MISSING_PARAMETER]

SEVERITY: ERROR
DESCRIPTION: When calling the publish_dd api, the 1st parameter (locale) is optional. The 2nd parameter (type_name) is optional, but must be present if the 3rd parameter (attribute) is specified.
CAUSE: The syntax was incorrect on the publish_dd api call.
ACTION: The api call takes 3 parameters, locale name, type name, and attribute name. All 3 are optional, but if the attribute name is present, the type name must also be present.
PARAMS:

ERROR: [DM_API_E_NO_APPLICATION_PERMIT]

SEVERITY: ERROR
DESCRIPTION: The application_permit value was not specified.
CAUSE: The application_permit value is missing.
ACTION: Specify the application_permit value
PARAMS:

ERROR: [DM_API_E_BADDATATYPE]

SEVERITY: ERROR
DESCRIPTION: S Bad datatype or value conversion for attribute %s.
CAUSE: You have specified an attribute, along with a datatype or a value. The datatype was not a valid docuserver datatype, or the value was incompatible with the datatype of the specified attribute.
ACTION: Correct the command as appropriate and retry.
PARAMS: The name of the attribute.

ERROR: [DM_API_E_BADATTRINDX]

SEVERITY: ERROR
DESCRIPTION: SI Attribute name %s for document/object has incorrect index %d
CAUSE: Attribute name was supplied with an incorrect index.
ACTION: Check to make sure that the index is within bounds of the current number of attributes.
PARAMS: None.

ERROR: [DM_API_E_GETHOSTBYNAME_FAILED]

SEVERITY: ERROR
DESCRIPTION: OS Error has occurred in gethostbyname() or gethostbname_r(). Retry could resolve the issue.
CAUSE: Due to some threading issues in Unix gethostbyname() or gethostbyname_r() may return NULL
ACTION: Abort DMCL client creation. Client Application (DFC/WDK) can retry.
PARAMS:

ERROR: [DM_API_E_NO_EVENT_NAME]

SEVERITY: ERROR
DESCRIPTION: S No event name given for command %s.
CAUSE: An event name is required for this command.
ACTION: Correct the command to specify an event name.
PARAMS: The command as specified.

ERROR: [DM_API_E_BADSEVERITY]

SEVERITY: ERROR
DESCRIPTION: S Bad severity level given: %s
CAUSE: You have specified an invalid severity level.
ACTION: Retry with a valid severity level (0 ~ 4).
PARAMS:

ERROR: [DM_API_E_MUSTBE_BASE_PREV]

SEVERITY: ERROR
DESCRIPTION: You must specify base or previous as the state name to demote to.
CAUSE: This is to reserver a field for Demote API to easily expand into state network model. Currently, base means demoting to base base state previous means demoting to the original state.
ACTION:
PARAMS:

ERROR: [DM_API_E_INVALID_PERMIT]

SEVERITY: ERROR
DESCRIPTION: I An invalid accessor_permit value of %d was specified.
CAUSE: An invalid accessor_permit value was specified.
ACTION: Specify a valid accessor_permit value
PARAMS:

ERROR: [DM_API_E_CANT_UPDATE]

SEVERITY: ERROR
DESCRIPTION: S Cannot Save/Check-in object <%s> because the object is marked invalid. This is most likely due to an error from a prior operation performed on the object.
CAUSE: One or more operations has failed during this update. Consult the following error message(s) for more help.
ACTION: Try again after fixing previous problems.
PARAMS:

ERROR: [DM_API_E_NODOCBASE]

SEVERITY: ERROR
DESCRIPTION: No document base has been provided for a connection.
CAUSE: The first argument has not been provided for a connect statement.
ACTION: Provide a complete connect statement.
PARAMS:

ERROR: [DM_API_E_NO_UL_SUPPORT]

SEVERITY: ERROR
DESCRIPTION: The server does not support NT Unified Logon.
CAUSE: The server is not running under NT or the old docbroker is running
ACTION: Make sure the server and the docbroker support NT Unified Logon
PARAMS:

ERROR: [DM_API_E_INVALID_INPUT]

SEVERITY: ERROR
DESCRIPTION: S Input string (%s) must have prefix DM_TICKET= or DM_TOKEN.
CAUSE: The input string is neither a login ticket nor an application access control token.
ACTION: Specifiy a valid login ticket or application access control token.
PARAMS: the input string.

ERROR: [DM_API_E_MISS_SRC_PORT]

SEVERITY: ERROR
DESCRIPTION: Missing parameter source port.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_API_E_INVALID_FORCE_AUTH]

SEVERITY: ERROR
DESCRIPTION: S Invalid value (%s) for connect argument force_authenticate. It must be T, t, F, or f.
CAUSE: Invalid value for connect argument force_authenticate
ACTION: Specify a valid value for connect argument force_authenticate
PARAMS:

ERROR: [DM_API_E_NOPOLIID]

SEVERITY: ERROR
DESCRIPTION: you need to specify a valid policy object while doing an Attach.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_API_E_STATE_WITH_NO_POLICY]

SEVERITY: ERROR
DESCRIPTION: S The state name parameter (%s) to the type api cannot be supplied without a business policy object id.
CAUSE: The business policy id was omitted or NULL.
ACTION: Specify a valid business policy id if a state name is used.
PARAMS: The parameter is the state name that was supplied.

ERROR: [DM_API_E_INVALID_TIMEOUT]

SEVERITY: ERROR
DESCRIPTION: S Invalid timeout parameter value (%s). It must be a valid integer.
CAUSE: Wrong timeout parameter value is specified for getlogin/gettoken.
ACTION: Specify a correct value for timeout
PARAMS: S – The specified value for timeout parameter

ERROR: [DM_API_E_NO_XPERMIT]

SEVERITY: ERROR
DESCRIPTION: The accessor_xpermit value was not specified.
CAUSE: The accessor_xpermit value is missing.
ACTION: Specify the accessor_xpermit value
PARAMS:

ERROR: [DM_API_E_CANT_WITHOUT_OPEN_TRAN]

SEVERITY: ERROR
DESCRIPTION: S You cannot perform %s operation without an open transaction in this session.
CAUSE: The specified operation needs to be run under an open transaction.
ACTION: Issue a begintran before running the specified operation.
PARAMS:

ERROR: [DM_API_E_MISS_ROUTE_ID]

SEVERITY: ERROR
DESCRIPTION: The parameter route case identifier is missing.
CAUSE: The route case identifier parameter is missing.
ACTION: Specify a route case identifier.
PARAMS:

ERROR: [DM_API_E_MISS_DEST_ACTIVITY]

SEVERITY: ERROR
DESCRIPTION: Missing parameter destination activity.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_API_E_METHOD_NOT_APPLICABLE]

SEVERITY: ERROR
DESCRIPTION: SS The method %s is not applicable to type %s.
CAUSE: The attempted operation is not supported by the type.
ACTION: Use the method supported by the type instead.
PARAMS: S – method name S – type name

ERROR: [DM_API_E_NO_PAGE_MODIFIER_FOR_BATCH]

SEVERITY: ERROR
DESCRIPTION: SS The page_modifier, %s, is not allowed for %s in batch mode.
CAUSE: The page_modifier isnt allowed when processing the operation in batch mode.
ACTION: Either set the batch_flag to false or remove the page_modifier in the operation.
PARAMS: The page_modifier and API name of the operation.

ERROR: [DM_API_E_MISS_ROUTE_COND]

SEVERITY: ERROR
DESCRIPTION: The parameter route condition is missing.
CAUSE: The route condition parameter is missing.
ACTION: Specify a route condition.
PARAMS:

ERROR: [DM_API_E_BADQUERY]

SEVERITY: ERROR
DESCRIPTION: S No query has been run for command %s.
CAUSE: You have specified next or close on a null query result collection.
ACTION: You probably ran a query that failed and returned a null collection. Check the error messages for your session they should provide an explanation as to why your query failed. Correct your query and run it again. Check to be sure you get a collection back before issuing a next or close command.
PARAMS: The command specified.

ERROR: [DM_API_E_NONAME]

SEVERITY: ERROR
DESCRIPTION: The accessor name is missing.
CAUSE: Accessor name is missing from the cmd line.
ACTION: Provide the accessor name.
PARAMS:

ERROR: [DM_API_E_DISTTRANS_UNSUPPORTED]

SEVERITY: ERROR
DESCRIPTION: It is disallowed to update through a reference or a replica while a user transaction is open.
CAUSE: The distributed transaction is disallowed in this release.
ACTION: Check if begintrans has been issued and only update through a reference or a replica outside of the transaction.
PARAMS:

ERROR: [DM_API_E_AUTH_CMD_NOT_SUPPORTED]

SEVERITY: ERROR
DESCRIPTION: S The target server of version (%s) does not support authenticate command.
CAUSE: Pre-5.2 server does not support API command authenticate.
ACTION: Use other command such as connect to authenticate user.
PARAMS: S – target server version string

ERROR: [DM_API_E_EXCEPTION_ON_SESSION]

SEVERITY: ERROR
DESCRIPTION: SS An unexpected error has caused the command %s to be aborted. The session and all associated subconnections have been disabled. A detailed description of the error can be found in %s.
CAUSE: An unknown error has caused a memory access violation.
ACTION: Provide this message, and the contents of the error report file, and contact your Documentum site representative.
PARAMS: S – api command S – pathname to error file dmcl_err_pid__

ERROR: [DM_API_E_BAD_TYPE]

SEVERITY: ERROR
DESCRIPTION: DS The object, %s, is not type, %s.
CAUSE: The object and type specified do not agree.
ACTION: Check the existence of the objct or the type of the object.
PARAMS: D – object ID S – type

ERROR: [DM_API_E_MISS_ACTIVITY_NAME]

SEVERITY: ERROR
DESCRIPTION: Missing parameter activity name.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_API_E_DECODING_FAILED]

SEVERITY: ERROR
DESCRIPTION: SS Decoding %s (%s) failed.
CAUSE: The given login ticket or applicatiob access control token is corrupted.
ACTION: Make sure the specified login ticket or token is valid.
PARAMS: the first parameter tells whether this is login ticket or token. The second parameter is the login ticket or token.

ERROR: [DM_API_E_NOID]

SEVERITY: ERROR
DESCRIPTION: S No id given for command %s.
CAUSE: An object id is required for this command.
ACTION: Correct the command to specify an object id.
PARAMS: The command as specified.

ERROR: [DM_API_E_ISCACHED_BAD_CACHE_NAME]

SEVERITY: ERROR
DESCRIPTION: S %s is not a valid cache name for the iscached API call.
CAUSE: You have specified a call to the iscached API call with an invalid cache name.
ACTION: Supply a valid cache name, for example typecache.
PARAMS: None.

ERROR: [DM_API_E_VDMPATH_SORTBY]

SEVERITY: ERROR
DESCRIPTION: S %s is not a valid attribute to sort by
CAUSE: The attribute specified in the sort by parameter is not allowed.
ACTION: Choose a different attribute by which to exclude multiple versions of components in the path.
PARAMS:

ERROR: [DM_API_E_UNRECOGNIZED_PARAMETER]

SEVERITY: ERROR
DESCRIPTION: S An unrecongized parameter with value %s was specified. Check the API syntax and the parameter and try again.
CAUSE: An unrecognized parameter was encountered in the API statement.
ACTION: Check the parameter and API syntax and try again.
PARAMS:

ERROR: [DM_API_E_CANT_SEEK]

SEVERITY: ERROR
DESCRIPTION: Cant perform a seek operation for this content
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_API_E_CHECK_ACTIVITY]

SEVERITY: ERROR
DESCRIPTION: Paramter check activity is invalid.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_API_E_FLUSH_NO_ARG]

SEVERITY: ERROR
DESCRIPTION: The flush method had a missing required cachename argument.
CAUSE: A flush method was invoked without the required cachename arguement.
ACTION: Add the cachename argument (currently only querycache is supported) and retry.
PARAMS:

ERROR: [DM_API_E_BADFILE_FORMAT]

SEVERITY: ERROR
DESCRIPTION: S File format for file %s is either incorrect or missing.
CAUSE: The file format for a method that adds a new file to a document is either missing or incorrect.
ACTION: Insure that the file format has been specified. Make sure that the file format matches those listed in dm_format objects.
PARAMS: The file that is being added.

ERROR: [DM_API_E_UPDATE_BAD_ATTR]

SEVERITY: ERROR
DESCRIPTION: S The attribute %s is not updateable.
CAUSE: The attribute you are attempting to set is not an updateable attribute.
ACTION: Internal and readonly attributes are not updateable. Remove the reference(s) to attribute(s) beginning with i_ or _r, from your update or create object statement.
PARAMS:

ERROR: [DM_API_E_ACTION]

SEVERITY: ERROR
DESCRIPTION: specify TRUE/FALSE or do not specify anything
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_API_E_NOFOLDER]

SEVERITY: ERROR
DESCRIPTION: S Folder with the path %s does not exist.
CAUSE: You have tried to fetch a folder that does not exist.
ACTION: Double check the path that you specified and ensure that it is correct. The folder may have been deleted. Also check any other error messages queued on your session to see if they also reference this folder.
PARAMS: The path name specified in the command.

ERROR: [DM_API_E_BADOBJ]

SEVERITY: ERROR
DESCRIPTION: S Command %s returned an invalid document/object id.
CAUSE: Your command has returned an invalid (null) object id.
ACTION: The command should have generated other error messages which will explain the cause for this failure. Check the rest of the message queue, and follow whatever actions are suggested in the other error messages.
PARAMS: The command, as specified.

ERROR: [DM_API_E_MISS_SRC_ACTIVITY]

SEVERITY: ERROR
DESCRIPTION: Missing parameter source activity.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_API_E_INVALID_SINGLE_USE]

SEVERITY: ERROR
DESCRIPTION: S Invalid single_use parameter value (%s). It must be T, t, F, or f.
CAUSE: Wrong single_use parameter value is specified for getlogin.
ACTION: Specify a correct value for single_use parameter.
PARAMS: S – The specified value for single_use parameter

ERROR: [DM_API_E_SAVE_TYPE]

SEVERITY: ERROR
DESCRIPTION: S The internal type, %s, can not be saved.
CAUSE: Internal types cant be saved.
ACTION: create and save a non-internal type.
PARAMS: S – type name

ERROR: [DM_API_E_NOLABEL]

SEVERITY: ERROR
DESCRIPTION: No version label specified during appendcomp/insertcomp operations.
CAUSE: You have not specified a version label during appendcomp or insertcomp operation.
ACTION: Specify the version label during the appendcomp or insertcomp operation.
PARAMS:

ERROR: [DM_API_E_CAUSE]

SEVERITY: ERROR
DESCRIPTION: an invalid value for check activity was specified or parameter check activity should not be specified.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_API_E_POLICY_WITH_NO_STATE]

SEVERITY: ERROR
DESCRIPTION: D If a business policy id (%s) is used in the type api, a valid state name must be supplied.
CAUSE: The state name was omitted.
ACTION: Specify a valid state name for the business policy object.
PARAMS: The parameter is the business policy object id that was supplied.

ERROR: [DM_API_E_WRONG_CACHE_NAME]

SEVERITY: ERROR
DESCRIPTION: S The global cache %s is not supported in flushglobalcache method.
CAUSE: The name of the global cache to be flushed is not supported in the flushglobalcache method.
ACTION: Currently, only user cache is allowed.
PARAMS:

ERROR: [DM_API_E_DYNAMIC_GROUP_UPDATE]

SEVERITY: ERROR
DESCRIPTION: The dynamic_groups field can be updated only by append and remove operations.
CAUSE: The session config field dynamic_groups is used to control the set of dynamic groups that the current session is involved in. Changing the set of dynamic groups is done by removing or appending groups from dynamic_groups list. The list does not allow manipulation by other operations: set, insert, truncate.
ACTION: Use the documented operations for manipulating the dynamic_groups list.
PARAMS:

ERROR: [DM_API_E_NOMESSAGE]

SEVERITY: ERROR
DESCRIPTION: S No messsage specified for routing.
CAUSE:
ACTION:
PARAMS: None.

ERROR: [DM_API_E_BADATTRNAME]

SEVERITY: ERROR
DESCRIPTION: S Bad attribute name %s for document/object.
CAUSE: An incorrect attribute name was supplied with the API command.
ACTION: Use a correct attribute name. Insure that no spaces have been placed between comma delimiters.
PARAMS: None.

ERROR: [DM_API_E_DOWNREV_SERVER_VER]

SEVERITY: ERROR
DESCRIPTION: SSSS The docbase (%s) has version (%s) which does not support the operation (%s). This operation requires a server of at least version (%s)
CAUSE: You can only connect to a docbase with a higher version.
ACTION:
PARAMS:

ERROR: [DM_API_E_SESSION_DISABLED]

SEVERITY: ERROR
DESCRIPTION: The session was disabled on an exception, only getmessage and disconnect are allowed on a disabled session.
CAUSE: An earlier error of type DM_API_E_EXCEPTION_ON_SESSION has been reported on this session.
ACTION: Use the disconnect command to end the session.
PARAMS:

ERROR: [DM_API_E_MISSING_CONTAINMENT_DESC]

SEVERITY: ERROR
DESCRIPTION: S A containment type of %s was supplied but its corresponding containment description is missing.
CAUSE: The containment description must be supplied if the containment type is supplied.
ACTION: Supply the corresponding containment description.
PARAMS:

ERROR: [DM_API_E_INVALID_PERMIT_TYPE]

SEVERITY: ERROR
DESCRIPTION: S An unrecognized permit_type value of %s was specified. Please check the value and try again.
CAUSE: An unrecognized value for permit_type was specified.
ACTION: Check the value supplied for permit_type and retry the API statement.
PARAMS:

ERROR: [DM_API_E_OPERATION_UNSUPPORTED]

SEVERITY: ERROR
DESCRIPTION: SS This %s operation cannot be performed because the server does not support the %s method. There is an incompatibility between your client library (DMCL) and the current Documentum server.
CAUSE: The server to which the application is connected does not support a method call used by the DMCL in the current command. The application is likely connected to an older server which cannot process the requested action.
ACTION: If possible upgrade the server to resolve the problem.
PARAMS: The command as specified and the unsupported METHOD call.

ERROR: [DM_API_E_NO_SERVERMAP]

SEVERITY: ERROR
DESCRIPTION: No server map information from docbroker.
CAUSE: The docbroker is not running or the server is not running
ACTION: Check with your dmadmin for help
PARAMS:

ERROR: [DM_API_E_BADQUEUE]

SEVERITY: ERROR
DESCRIPTION: No queue name has been given.
CAUSE: You have issued a dequeue command without specifying a queue name.
ACTION: Correct the command line to include the queue name.
PARAMS: None.

ERROR: [DM_API_E_POSITIONAL_PARAM_MISSING]

SEVERITY: ERROR
DESCRIPTION: IS The required positional parameter, %d, was not supplied. Please provide a value for %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_API_E_NO_SESSION]

SEVERITY: ERROR
DESCRIPTION: There are no more available sessions.
CAUSE: User has used all available sessions. Current limit is 10 per application.
ACTION: Close some unused sessions in your application.
PARAMS:

ERROR: [DM_API_E_MISS_STATE_POS]

SEVERITY: ERROR
DESCRIPTION: The movestate API requires both old and new positions be specified.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_API_W_NO_VALUE]

SEVERITY: WARNING
DESCRIPTION: S There are no values in the repeating attribute %s.
CAUSE: You have requested a value from the repeating attribute, but no values have been set for this attribute. The _count value for this attribute is zero.
ACTION: None required. This message is informational. In general, the repeating attributes _count value should be checked before values are requested. _count tells you how many values the repeating attribute contains, so that you can retrieve all of them.
PARAMS:

ERROR: [DM_API_W_NO_MATCH]

SEVERITY: WARNING
DESCRIPTION: S There was no match in the docbase for the qualification: %s
CAUSE: The qualification you provided did not match any object.
ACTION: None required. If you think there really should have been a match reexamine your qualification, correct it, and resubmit it.
PARAMS: The qualification.

ERROR: [DM_API_W_CACHE_FLUSH]

SEVERITY: WARNING
DESCRIPTION: Unable to flush query cache.
CAUSE: Query caching is disabled for your session or docbase. Unable to flush the cache.
ACTION: Query caching must be enabled, either by your System Administrator setting the effective_date in the Docbase Config, or through your dmcl.ini.
PARAMS:

ERROR: [DM_API_W_SERVER_NEED_RESTART]

SEVERITY: WARNING
DESCRIPTION: S Changes made by the apply method %s will not take effect until Content Server is restarted.
CAUSE: Content server needs to restart after certain APPLY method being executed. Such apply method includes only DEFAULT_RETENTION_ATTR for now.
ACTION: An Admin user needs to restart the content server.
PARAMS:

ERROR: [DM_API_W_EXTRA_PARAMETER]

SEVERITY: WARNING
DESCRIPTION: S The extra parameter, %s, is only allowed for date attribute.
CAUSE: You have provided an extra parameter in the Set, Append, Insert API for non-date attribute.
ACTION: Remove the extra parameter.
PARAMS:

ERROR: [DM_API_W_OLDTYPE]

SEVERITY: WARNING
DESCRIPTION: S Type name %s should no longer be used in the creation of objects.
CAUSE: An old type has been used document, cabinet, folder.
ACTION: In the future, use dm_document, dm_cabinet, dm_folder.
PARAMS: None.

ERROR: [DM_API_W_CONTAINMENT_FEATURES_NOT_SUPPORTED]

SEVERITY: WARNING
DESCRIPTION: SSSS The docbase (%s) has version (%s) which does not support setting containment_type and containment_desc attributes in the operation (%s). These features require a server of at least version (%s)
CAUSE: You can only set containment_type and containment_desc attributes in a 4.1 or later server
ACTION: Use a newer server if you wish to set the containment_type and containment_desc attributes.
PARAMS: docbase, old server version, api operation, minimum server version required.

ERROR: [DM_API_I_OPTION_USAGE]

SEVERITY: INFORMATION
DESCRIPTION: SS This option is currently (%s). You need system administrators privilege to turn on -o flags. You can turn on[/off] this option by issueing an api command: apply,,NULL,SET_OPTIONS,OPTION,S,%s, VALUE,B,T[/F]
CAUSE: Instruction to turn on/off -o option
ACTION: None.
PARAMS:

ERROR: [DM_API_I_SPECIAL_FACILITY_USAGE]

SEVERITY: INFORMATION
DESCRIPTION: S You can turn on/off (%s) trace facility by issueing an api command:apply,c,NULL,MODIFY_TRACE,SYBSYSTEM,S,fulltext,VALUE,S,{all,document,verity,none}
CAUSE: Instruction to turn on trace for this facility on the server side
ACTION: None.
PARAMS:

ERROR: [DM_API_I_FACILITY_USAGE]

SEVERITY: INFORMATION
DESCRIPTION: SS You can turn on (%s) trace facility by issueing an api command:trace,,,apilogfile,%s. You can turn off this facility by using the same api with severity_level set to 0.
CAUSE: Instruction to turn on trace for this facility on the server side
ACTION: None.
PARAMS:

ERROR: [DM_API_I_FACILITY_NOT_AVAILABLE]

SEVERITY: INFORMATION
DESCRIPTION: S Current facility (%s) does not have trace
CAUSE: the information of the facility
ACTION: None.
PARAMS:

ERROR: [DM_API_I_SQL_TRACE_USAGE]

SEVERITY: INFORMATION
DESCRIPTION: S SQL Trace is currently (%s). The api command to turn on[/off] SQL trace is: trace,,1[/0],,SQL_TRACE
CAUSE: this is the instruction for session based sql trace.
ACTION: none.
PARAMS:

nahoru

DM_ASSEMBLY

ERROR: [DM_ASSEMBLY_F_LENGTH_WIDEN_FAILED]

SEVERITY: FATAL
DESCRIPTION: SII Failed to increase the length of the attribute (%s) from %d to %d.
CAUSE: For unknown reason, type conversion failed.
ACTION: Check if there are any database errors or problems. Report the problem to Documentum Support. Audit Trail errors ** Documentum DocuServer ** Confidential Property of Documentum, Inc. ** (c) Copyright Documentum, Inc., 1991-2000 ** All rights reserved. **
PARAMS:

ERROR: [DM_ASSEMBLY_F_INIT3]

SEVERITY: FATAL
DESCRIPTION: The type manager returned an error storing the dmAssembly type.
CAUSE: Unknown.
ACTION: Look at the error logged by the type manager. Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_ASSEMBLY_F_INIT1]

SEVERITY: FATAL
DESCRIPTION: The dmAssembly type was found in the database without a version stamp.
CAUSE: Unknown.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_ASSEMBLY_F_TYPE_CONVERSION]

SEVERITY: FATAL
DESCRIPTION: I Failed to convert type dm_assembly to version %d.
CAUSE: For unknown reason, type conversion failed.
ACTION: Report the problem to Documentum Support.
PARAMS:

ERROR: [DM_ASSEMBLY_F_INIT2]

SEVERITY: FATAL
DESCRIPTION: II Version stamp %d was expected to be %d.
CAUSE: The version stamp that the dmAssembly object software expected was different from the actual version stamp in the database.
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:

ERROR: [DM_ASSEMBLY_E_CANT_FETCH_INVALID_ID]

SEVERITY: ERROR
DESCRIPTION: D Cannot fetch an assembly – Invalid object ID %s
CAUSE: Could not fetch an object with the given id.
ACTION: This is probably caused by a bad ID. Or, possibly, a connection to the Documentum server could not be established.
PARAMS:

ERROR: [DM_ASSEMBLY_E_NEED_PRIV_FOR_CHANGE]

SEVERITY: ERROR
DESCRIPTION: SS The current user %s has insufficient privileges to save or destroy %s assembly.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_ASSEMBLY_E_INVALID_COMPONENT]

SEVERITY: ERROR
DESCRIPTION: D Invalid component id %s specified.
CAUSE: An invalid component id is specified.
ACTION: Change the component id to a valid id.
PARAMS:

ERROR: [DM_ASSEMBLY_E_NEED_PRIV2_FOR_CHANGE]

SEVERITY: ERROR
DESCRIPTION: SSSS The current user %s has insufficient privileges to save or destroy %s assembly since %s %s is protected.
CAUSE: A user with insufficient privileges tried to save or destroy an assembly object.
ACTION: See your sysadmin.
PARAMS:

ERROR: [DM_ASSEMBLY_E_INVALID_COMP_MATCH]

SEVERITY: ERROR
DESCRIPTION: DD Specified chronicle id %s does not match the chronicle id of %s.
CAUSE: specified chroncile id of the component does not match the chronicle id from the docbase for the given component.
ACTION: Change the component chronicle id to a valid chronicle id of the component.
PARAMS:

ERROR: [DM_ASSEMBLY_E_INVALID_PARENT]

SEVERITY: ERROR
DESCRIPTION: D Invalid parent id %s specified.
CAUSE: An invalid parent id is specified.
ACTION: Change the parent id to a valid id.
PARAMS:

ERROR: [DM_ASSEMBLY_E_INVALID_COMP_CHRON]

SEVERITY: ERROR
DESCRIPTION: D Invalid component chronicle id %s specified.
CAUSE: An invalid component chronicle id is specified.
ACTION: Change the component chronicle id to a valid id.
PARAMS:

nahoru

DM_AUDITTRAIL

ERROR: [DM_AUDITTRAIL_F_TYPE_INIT]

SEVERITY: FATAL
DESCRIPTION: S Failed to initialize type %s.
CAUSE: Unknown.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_AUDITTRAIL_F_BAD_VSTAMP]

SEVERITY: FATAL
DESCRIPTION: II Type dm_audittrail has a bad vstamp %d. The current vstamp for dm_audittrail is supposed to be %d.
CAUSE: The RDBMS table has a bad vstamp.
ACTION: Report this error to Documentum sysadmins.
PARAMS:

ERROR: [DM_AUDITTRAIL_F_TYPE_CONVERSION]

SEVERITY: FATAL
DESCRIPTION: I Failed to convert type dm_audittrail to version %d.
CAUSE: For unknown reason, type conversion failed.
ACTION: Report the problem to Documentum Support.
PARAMS:

ERROR: [DM_AUDITTRAIL_F_RPC_CALL]

SEVERITY: FATAL
DESCRIPTION: S Failed to run the RPC call %s.
CAUSE: For unknown reason, the RPC call failed.
ACTION: Report the problem to Documentum Support. $Id: dmbroker.e,v 5.5 2002/07/25 22:50:01 ling Exp $
PARAMS:

ERROR: [DM_AUDITTRAIL_E_NO_SIGNATURE]

SEVERITY: ERROR
DESCRIPTION: D Audit record (%s) has not been signed.
CAUSE: The audit record has not been signed.
ACTION: Make sure that the audit record is signed.
PARAMS: D – Audit trail object id.

ERROR: [DM_AUDITTRAIL_E_AUDIT_DOCBASE_WIDE_NOT_ALLOW_EXTRA]

SEVERITY: ERROR
DESCRIPTION: S You are not allowed to specify extra values, %s, when docbase-wide event is audited.
CAUSE: When auditing docbase-isDocbasewide events (i.e., object_id is NULL), it is not allowed to specify any values after the event_name.
ACTION: Remove the extra parameter after event_name
PARAMS:

ERROR: [DM_AUDITTRAIL_E_CANT_AUDIT]

SEVERITY: ERROR
DESCRIPTION: SS Could not audit the specified %s event for %s document/object.
CAUSE: The specified event could not be audited. Most likely bad event name specified or object doesnt exist in docbase.
ACTION: Check the event name and try again.
PARAMS:

ERROR: [DM_AUDITTRAIL_E_AUDIT_OBJ_NOT_ALLOW_EXTRA]

SEVERITY: ERROR
DESCRIPTION: SSSS When auditing an object, no values can be provided for the following arguments: audit_subtypes (%s), controlling_app (%s), policy_id (%s), and state_name (%s)
CAUSE: When auditing an object, it is not allowed to specify any values for audit_subtypes, controlling_app, policy_id, and state_name parameters.
ACTION: Remove the invalid values from the audit api.
PARAMS:

ERROR: [DM_AUDITTRAIL_E_AUDIT_DEFAULT_NOT_ALLOWED]

SEVERITY: ERROR
DESCRIPTION: S The keyword default for policy is only allowed when the event name is (%s).
CAUSE: You can use the keyword default to specify the default policy associated with the type for auditing event. However, it is only allowed when the event name is dm_attach.
ACTION: Either specify a valid event name or a valid policy id.
PARAMS:

ERROR: [DM_AUDITTRAIL_E_CURSOR_FAIL]

SEVERITY: ERROR
DESCRIPTION: SS The following query %s generated the following database %s error
CAUSE: Used for internal purpose.
ACTION: Report to your sys admin.
PARAMS:

ERROR: [DM_AUDITTRAIL_E_AUDIT_NEED_CONFIG_AUDIT]

SEVERITY: ERROR
DESCRIPTION: SS The current user (%s) needs to have config audit privilege to audit the %s event.
CAUSE: Must have config audit privilege to audit an event
ACTION: Consult your system administrator.
PARAMS:

ERROR: [DM_AUDITTRAIL_E_DBERROR]

SEVERITY: ERROR
DESCRIPTION: SSSS AuditTrail was unable to perform %s on %s for event %s.nDatabase error:n%s
CAUSE: AuditTrail was attempting a database operation which failed.
ACTION: Ensure that all is well with the underlying database tables. Check the dmi_registry_s table.
PARAMS:

ERROR: [DM_AUDITTRAIL_E_AUDIT_ALREADY_AUDITED]

SEVERITY: ERROR
DESCRIPTION: SS Event %s on object %s is already being audited.
CAUSE: The object already has the requested event audited
ACTION: No need to audit the event twice
PARAMS:

ERROR: [DM_AUDITTRAIL_E_NOT_AUDITED]

SEVERITY: ERROR
DESCRIPTION: SS Event %s is not audited for object %s.
CAUSE: Specified event is not audited
ACTION: Check to see if either the event or the sysobj ID is invalid.
PARAMS:

ERROR: [DM_AUDITTRAIL_E_SIGNATURE_CREATE_FAIL]

SEVERITY: ERROR
DESCRIPTION: Server failed to generate audit signature.
CAUSE: An error occured while creating audit signature.
ACTION: Contact Documentm Tech Support.
PARAMS:

ERROR: [DM_AUDITTRAIL_E_NO_BROWSE_ACCESS]

SEVERITY: ERROR
DESCRIPTION: SD The user (%s) does not have browse access to the audittrail record with ID %s. CAUSE:You do not have browse access to this audittrail record. Superusers and users with VIEW AUDIT privilege can view any audit trail record. Other users need to be either the owner or with at least BROWSE permit in order to acces the record. ACTION:See your System Administrator or the owner of the sysobject.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_AUDITTRAIL_E_NO_AUTH_DESTROY]

SEVERITY: ERROR
DESCRIPTION: S The current user (%s) must have purge audit privilege to destroy an audit trail.
CAUSE: User does not have the right privleges to destroy an audit trail object.
ACTION: Destroy the object as a user with the purge audit privilege.
PARAMS:

ERROR: [DM_AUDITTRAIL_E_CANT_UNAUDIT]

SEVERITY: ERROR
DESCRIPTION: SS Could not unaudit the specified %s event for %s document/object.
CAUSE: The specified event could not be unaudited. Most likely bad event name specified.
ACTION: Check the event name and try again.
PARAMS:

ERROR: [DM_AUDITTRAIL_E_MISSING_ARG]

SEVERITY: ERROR
DESCRIPTION: SS The method %s is missing argument for %s.
CAUSE: Argument is missing for the method.
ACTION: Make sure that all required arguments are correctly specified.
PARAMS: S – name of the method. S – name of the missing argument.

ERROR: [DM_AUDITTRAIL_E_AUDIT_NOT_ALLOW_STATE_NAME]

SEVERITY: ERROR
DESCRIPTION: S It is not allowed to specify state_name (%s) if lifecycle id is not specified.
CAUSE: It is allowed to specify policy state name only if a policy id is specifed.
ACTION: Either specify a policy id or remove policy state name.
PARAMS:

ERROR: [DM_AUDITTRAIL_E_INCREASE_LENGTH]

SEVERITY: ERROR
DESCRIPTION: SII Failed to increase the size of %s from %d to %d.
CAUSE: Unknown.
ACTION: Report this error to Documentum sysadmins.
PARAMS:

ERROR: [DM_AUDITTRAIL_E_INVALID_STATE_NAME]

SEVERITY: ERROR
DESCRIPTION: SD There is no state named %s in lifecycle with ID %s.
CAUSE: The state name is invalid.
ACTION: Make sure that the state name exists in the specified lifecycle.
PARAMS:

ERROR: [DM_AUDITTRAIL_E_NO_DEFAULT_POLICY]

SEVERITY: ERROR
DESCRIPTION: SS %s failed because the type (%s) does not have a default policy.
CAUSE: You tried to use default to specify a policy for auditing. But, the relevant type doesnt have a default policy.
ACTION: You can user DQL ALTER TYPE statement to associate a default policy to a type.
PARAMS:

ERROR: [DM_AUDITTRAIL_E_EVENT_NOT_AUDITABLE_FOR_TYPE]

SEVERITY: ERROR
DESCRIPTION: SS The event %s is not auditable for the type %s.
CAUSE: The event is not auditable for this type.
ACTION: Specify a valid event for this type.
PARAMS: S – user specified audit event name S – user specified type name

ERROR: [DM_AUDITTRAIL_E_UNAUDIT_NEED_CONFIG_AUDIT]

SEVERITY: ERROR
DESCRIPTION: SS The current user (%s) needs to have config audit privilege to unaudit the %s event.
CAUSE: Must have config audit privileges to unaudit an event
ACTION: Consult your system administrator.
PARAMS:

ERROR: [DM_AUDITTRAIL_E_ONLY_INSTALL_OWNER]

SEVERITY: ERROR
DESCRIPTION: SS Only a docbase install owner can perform %s operation on audit policy.
CAUSE: Non install owner tried to CREATE/UPDATE/DELETE the audit policy
ACTION: Login as Docbase Install owner and try again.
PARAMS:

ERROR: [DM_AUDITTRAIL_E_CANT_MODIFY]

SEVERITY: ERROR
DESCRIPTION: D You can not modify any existing AuditTrail object %s.
CAUSE: The AuditTrail object has been previously saved. It cannot be saved again by anyone.
ACTION: Do not attempt to modify an AuditTrail object. Only one save action is allowed on it.
PARAMS:

ERROR: [DM_AUDITTRAIL_E_INVALID_POLICY_ID]

SEVERITY: ERROR
DESCRIPTION: D Lifecycle with ID %s does not exist.
CAUSE: The policy id is invalid.
ACTION: Check the specified policy id. Make sure it is pointing to a valid policy object.
PARAMS:

ERROR: [DM_AUDITTRAIL_E_UNAUDIT_NO_EVENT]

SEVERITY: ERROR
DESCRIPTION: No Event Specified for unaudit.
CAUSE: The user forgot to specify an event for unaudit
ACTION: Specify a valid event name
PARAMS:

ERROR: [DM_AUDITTRAIL_E_UNAUDIT_INVALID_EVENT]

SEVERITY: ERROR
DESCRIPTION: S Event %s is not a valid system event.
CAUSE: The user specified an invalid event name for unaudit
ACTION: Specify a valid event name
PARAMS:

ERROR: [DM_AUDITTRAIL_E_CANT_FETCH]

SEVERITY: ERROR
DESCRIPTION: D Cannot fetch – Invalid object ID %s.
CAUSE: Could not fetch an object with the given id.
ACTION: This is probably caused by a bad ID. Or, possibly, a connection to the Documentum server could not be established.
PARAMS:

ERROR: [DM_AUDITTRAIL_E_SIGNATURE_MISMATCH]

SEVERITY: ERROR
DESCRIPTION: D Audit record (%s) has failed the audit signature verification.
CAUSE: The audit record has been changed.
ACTION: Check database log on who changed the object.
PARAMS: D – Audit trail object id.

ERROR: [DM_AUDITTRAIL_E_CANT_AUDIT_UNLESS_MATERIALIZED]

SEVERITY: ERROR
DESCRIPTION: SS Could not audit the specified %s event for %s because it is an un-materialized lightweight object.
CAUSE: It is not allowed to register a lightweight object for auditing before it is materialized
ACTION: Materialize the lightweight object and try again.
PARAMS:

ERROR: [DM_AUDITTRAIL_E_NO_PURGE_POLICY]

SEVERITY: ERROR
DESCRIPTION: SD The current user (%s) does not have a purge policy to destroy an AuditTrail object (%s)
CAUSE: Current session user does not belong to the purge policy, which satisfy the deleting audit record.
ACTION: Add a purge policy for deleting audit record or delete the satisfy purge policy for current record. —————————————————————–
PARAMS:

ERROR: [DM_AUDITTRAIL_E_AUDIT_ALL_NOT_ALLOW_EXTRA]

SEVERITY: ERROR
DESCRIPTION: S You are not allowed to specify extra values, for example, %s, when auditing all events.
CAUSE: When auditing all events (i.e., event_name is all), it is not allowed to specify any values after the audit_subtypes parameter.
ACTION: Specify a valid event name
PARAMS:

ERROR: [DM_AUDITTRAIL_E_INVALID_ARG]

SEVERITY: ERROR
DESCRIPTION: SSS The method %s has invalid value (%s) for argument %s.
CAUSE: Argument has invalid value.
ACTION: Make sure that all required arguments are correctly specified.
PARAMS: S – name of the method. S – value of the arguemnt. S – name of the argument.

ERROR: [DM_AUDITTRAIL_E_UNAUDIT_NEED_TO_BE_SUPERUSER]

SEVERITY: ERROR
DESCRIPTION: SS The current user (%s) needs to have superuser privileges to unaudit the %s event.
CAUSE: Must have Superuser privileges to unaudit an event
ACTION: Consult your system administrator.
PARAMS:

ERROR: [DM_AUDITTRAIL_E_AUDIT_INVALID_EVENT]

SEVERITY: ERROR
DESCRIPTION: S Event %s is not a valid system event.
CAUSE: The user specified an invalid event name for audit
ACTION: Specify a valid event name
PARAMS:

ERROR: [DM_AUDITTRAIL_E_SIGNATURE_TOO_LONG]

SEVERITY: ERROR
DESCRIPTION: II The internal gernerated audit signature is too long (%d). It cannot exceed the size of %d.
CAUSE: An internal error caused the size to be too large.
ACTION: Contact Documentm Tech Support.
PARAMS: I – Actual string size of the audit signature. I – Allowed string size.

ERROR: [DM_AUDITTRAIL_E_AUDIT_NO_EVENT]

SEVERITY: ERROR
DESCRIPTION: No Event Specified for audit.
CAUSE: The user forgot to specify an event for audit
ACTION: Specify a valid event name
PARAMS:

ERROR: [DM_AUDITTRAIL_E_AUDIT_NEED_AT_LEAST_SYSADMIN]

SEVERITY: ERROR
DESCRIPTION: SS The current user (%s) needs to have at least sysadmin privileges to audit the %s event.
CAUSE: Must have at least SysAdmin privileges to audit an event
ACTION: Consult your system administrator.
PARAMS:

ERROR: [DM_AUDITTRAIL_E_EVENT_NAME_NOT_ALLOWED]

SEVERITY: ERROR
DESCRIPTION: SS Event %s is not allowed in %s.
CAUSE: The user specified an invalid event name for audit or unaudit. It is very likely the specified event name is either dm_audit or dm_unaudit since we dont allow user to audit/unaudit them because they are always audited.
ACTION: Specify other event name.
PARAMS:

ERROR: [DM_AUDITTRAIL_E_OUT_OF_RANGE]

SEVERITY: ERROR
DESCRIPTION: ISII The index (%d) of the attribute %s should be between %d and %d.
CAUSE: The attribue value is out of range.
ACTION: Set the attribute to a value as suggested and retry the operation.
PARAMS: I – the specified index S – attribute name I – the lower bound I – the upper bound

ERROR: [DM_AUDITTRAIL_E_INSUFFICIENT_PRIV]

SEVERITY: ERROR
DESCRIPTION: SSS The user (%s) needs %s privilege for the operation %s.
CAUSE: User does not have the necessary privilege for the operation.
ACTION: Make sure that user has the required privilege for the operation.
PARAMS: S – User name. S – Required privilege. S – Operation/Method name.

ERROR: [DM_AUDITTRAIL_E_OBJ_NO_SIGNATURE]

SEVERITY: ERROR
DESCRIPTION: DS The Object (%s) has not been digitally signed. No audit record is generated for the event %s.
CAUSE: Object has to be digitally signed before an audit record can be generated for this event.
ACTION: Make sure that the object is digitally signed.
PARAMS: D – Object ID. S – name of the event.

ERROR: [DM_AUDITTRAIL_E_CANT_FIND_OBJ]

SEVERITY: ERROR
DESCRIPTION: SS Could not find the object, name or event %s for id %s.
CAUSE: The object identified by the id could not be found for that event.
ACTION: Check the id to make sure that it is a valid sysobject.
PARAMS:

ERROR: [DM_AUDITTRAIL_E_AUDIT_ATTR_NOT_EXISTS]

SEVERITY: ERROR
DESCRIPTION: SSS You try to audit event (%s) with an non-existent attribute (%s) in the list (%s).
CAUSE: When auditing an object, all attributes specified in the list must be present in the type.
ACTION: Remove the invalid values from the attribute list.
PARAMS:

ERROR: [DM_AUDITTRAIL_E_AUDIT_GROUP_NOT_ALLOW_EXTRA]

SEVERITY: ERROR
DESCRIPTION: SSSS No value is allowed to specify in controlling_app (%s), policy_id (%s), and state_name (%s) for event (%s).
CAUSE: When auditing certain events, it is not allowed to specify any values for controlling_app, policy_id, and state_name parameters.
ACTION: Remove the invalid values from the audit api.
PARAMS:

ERROR: [DM_AUDITTRAIL_W_EXCEED_ROW_SIZE]

SEVERITY: WARNING
DESCRIPTION: The attribute_list_old property is created with a short lengh because the ability to audit old property values is not enabled due to a database page size limitation.
CAUSE: The max row size (page size) is less than 8K consequently, the attribute_list_old property is created with a short length (1 char).
ACTION: Use a max row size (page size) of at least 8K. —————————————————————–
PARAMS:

nahoru

DM_CABINET

ERROR: [DM_CABINET_F_INIT3]

SEVERITY: FATAL
DESCRIPTION: The type manager returned an error storing the dmCabinet type.
CAUSE: Unknown.
ACTION: Look at the error logged by the type manager. Report this message and any parameters to your Documentum site representative. Common Content Facility errors
PARAMS:

ERROR: [DM_CABINET_F_INIT1]

SEVERITY: FATAL
DESCRIPTION: The dmCabinet type was found in the database without a version stamp.
CAUSE: Unknown.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_CABINET_F_INIT2]

SEVERITY: FATAL
DESCRIPTION: II Version stamp %d was expected to be %d.
CAUSE: The version stamp that the dmCabinet object software expected was different from the actual version stamp in the database.
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:

ERROR: [DM_CABINET_E_NEED_PRIV_FOR_CHANGE]

SEVERITY: ERROR
DESCRIPTION: SS The current user %s has insufficient privileges to save or destroy %s cabinet.
CAUSE: A user with insufficient privileges tried to save or destroy a cabinet object.
ACTION: See your sysadmin.
PARAMS:

nahoru

DM_CCONTENT

ERROR: [DM_CCONTENT_E_NO_LOCAL_AREA]

SEVERITY: ERROR
DESCRIPTION: The Local Content Area could not be initialized due to the inability to lookup a default Working Directory to use for Getfile requests.
CAUSE: The client specified to use the default local area however the dmcl is unable to get a Working Directory value from the operating system.
ACTION: The client should either specify a local content area explicitly or use the server common area for nameless getfile requests.
PARAMS:

ERROR: [DM_CCONTENT_E_REMOVE_FILE]

SEVERITY: ERROR
DESCRIPTION: SS Error destroying a file. Error occurred on remove of file (%s) with Operating System error (%s).
CAUSE: Possibly the directory does not exist or is not accessible. Possibly permissions on the file or parent directory prevent deletion. Operating System error should give further details.
ACTION: See your sysadmin.
PARAMS:

ERROR: [DM_CCONTENT_E_LOCAL_AREA_DEFAULT]

SEVERITY: ERROR
DESCRIPTION: SS The default Local Location for this client (%s) does not exist or cannot be accessed. This prevents fetching document contents. The Operating System error was (%s).
CAUSE: The default Local Location could not be accessed. Possibly permissions on the local working directory prevent its use.
ACTION: Check the working directory permissions and if needed redefine the Local area to an accessible device.
PARAMS:

ERROR: [DM_CCONTENT_E_CHECK_LONG]

SEVERITY: ERROR
DESCRIPTION: SS Error accessing directory %s. While determining file system support for long file names the following Operating System error occurred: %s. When using the Client Local area, the client API library checks to see if the underlying file system supports long file name before fetching content files onto the local disk. This error indicates a failure checking long file name. This will cause the Getfile request to fail.
CAUSE: Possibly the content area directory has been removed or is no longer accessible. The Operating System error should give further details.
ACTION: See your sysadmin.
PARAMS:

ERROR: [DM_CCONTENT_E_DISKFULL_LIMIT]

SEVERITY: ERROR
DESCRIPTION: SSLII Insufficient disk space exists to create a file of size %s bytes in directory %s. Free Bytes Remaining: %dK. Current Disk Usage: %d percent. Diskfull Limit: %d percent.
CAUSE: The disk pointed to by the Local Content Area has exceeded the Diskfull limit threshold established for the session.
ACTION: New diskspace must be made available. Purging the content area is recommended.
PARAMS:

ERROR: [DM_CCONTENT_E_CREATE_DIRECTORY]

SEVERITY: ERROR
DESCRIPTION: SS Creation of file system directory (%s) for session content area failed. Operating System error was (%s). One of the subdirectories of the Session Temporary Content Area (Local or Common) could not be created in initialization for a Getfile request. The Getfile request will fail.
CAUSE: Possibly the parent directory does not exist or is not accessible. Possibly the permissions on the parent directory prevent creation. Operating System error should give further details.
ACTION: See your sysadmin.
PARAMS:

ERROR: [DM_CCONTENT_E_LOCAL_AREA_NOTFOUND]

SEVERITY: ERROR
DESCRIPTION: SSS The Client configuration setting for the Local Location specifies a directory (%s) that does not exist or cannot be accessed. Using the Default Local Content Area (%s). The Operating System error was (%s).
CAUSE: The client configuration specified a Local location definition that was not accessible by the client. Possibly the disk it is defined to is not mounted or does not exist. Possibly permissions on the device prevent its use.
ACTION: Check the Local Location setting for correctness.
PARAMS:

ERROR: [DM_CCONTENT_E_LCOPY_AMBIGUOUS]

SEVERITY: ERROR
DESCRIPTION: Both the use_local_always and use_local_on_copy options were enabled for this client. These flags are mutually exclusive. Use_local_on_copy cannot be specified unless use_local_always is unset.
CAUSE: The use_local_on_copy option specifies that the local area should be used only when a file copy is required on getfile requests. If the file can be fetched by just returning a link or a direct filename pointer then the option specifies that nfs filenames be returned. This option requires that NFS access be enabled.
ACTION: If the client has nfs access to the server common area then set the nfs_enabled option to TRUE for this client. Otherwise turn off the use_local_on_copy option.
PARAMS:

ERROR: [DM_CCONTENT_E_DIRECTORY_ACCESS]

SEVERITY: ERROR
DESCRIPTION: SS Cannot use the Local Content Area due to the inability to access the session content directory (%s). The Operating System error was (%s).
CAUSE: The Local area directory was found to not exist or not be accessible. Possibly the client working directory cannot be accessed. Possibly the Local Location has been set to an non-existent directory. Possibly it was removed out from under the client session.
ACTION: Make sure the Local Location is defined to an accessible directory.
PARAMS:

ERROR: [DM_CCONTENT_E_REMOVE_DIRECTORY]

SEVERITY: ERROR
DESCRIPTION: SS Error destroying a directory or its contents. Error occurred on remove of directory (%s) with Operating System error (%s).
CAUSE: Possibly the directory does not exist or is not accessible. Possibly the permissions on the parent directory, a subdirectory or a file within prevent deletion. Operating System error should give further details.
ACTION: See your sysadmin.
PARAMS:

ERROR: [DM_CCONTENT_E_PERMS3]

SEVERITY: ERROR
DESCRIPTION: S The Local Content Area root (%s) and its docbase and hostname subdirectories should be made publicly updatable as well as the dir.lck files inside.
CAUSE: The Local Content Area could not be initialized because the current session did not have permission to either create a subdirectory in in the local area or to acquire a lock on an existing directory. The objects in the local area are normally created to be publicly accessible but it is possible for the user to run with a network filesystem umask which overrides our attempt to make file files public. When this occurs then the user which creates the local area (it is created automatically on first access) will be the only one with permission to use it. This is only a problem if the same local area root is shared by multiple users.
ACTION: A system admin should modify the permissions of the local area root directory along with its docbase and hostname subdirectories and any dir.lck files therein. Once this is done the local area should remain accessible by all users.
PARAMS:

ERROR: [DM_CCONTENT_E_LOCK_FILECREATE]

SEVERITY: ERROR
DESCRIPTION: SS Error creating file (%s) in order to lock the Session Temporary Content Directory for use on the first Getfile request. Operating System error was (%s). When using the Client Local area, the client API library places a lock on the Local Area content directory to prevent cleanup processing from deleting its content files. The lock is taken on the first access to the content area (the 1st nameless getfile request). This error indicates that the .lock file used for this procedure could not be taken preventing initialization of the Local area. The Getfile request will fail.
CAUSE: Possibly the parent directory does not exist or is not accessible. Possibly the permissions on the parent directory prevent creation. Operating System error should give further details.
ACTION: See your sysadmin.
PARAMS:

ERROR: [DM_CCONTENT_E_BAD_CONFIG_VALUE]

SEVERITY: ERROR
DESCRIPTION: SLI The setting for the configuration parameter (%s) is not a legal value: %d. Using default value of %d.
CAUSE: The value is out of range.
ACTION: Set the value to a legal value.
PARAMS:

ERROR: [DM_CCONTENT_E_NO_COMMON]

SEVERITY: ERROR
DESCRIPTION: A Nameless Getfile request was made to a server which does not have Common Area access. The Client should be configured to use its Local Content Area.
CAUSE: A client session executed a nameless getfile request against a server which does not allow Common Area access. It should be the case that the client session would have seen this and always done content tunneling into the client local area. Obviously something broke.
ACTION: Set up the client to use the local area (set USE_LOCAL = True).
PARAMS:

ERROR: [DM_CCONTENT_E_CHECK_DISKSPACE]

SEVERITY: ERROR
DESCRIPTION: SS Error attempting to check for available disk space in the Session Temporary Content Area during a Getfile operation. Space check on directory (%s) failed with Operating System error (%s). When using the Client Local area, the client API library checks for available disk space before fetching content files onto the local disk. This error indicates a failure checking disk space. This will cause the Getfile request to fail.
CAUSE: Possibly the content area directory has been removed or is no longer accessible. The Operating System error should give further details.
ACTION: See your sysadmin.
PARAMS:

ERROR: [DM_CCONTENT_E_READ_DIRECTORY]

SEVERITY: ERROR
DESCRIPTION: SS Error reading directory contents of directory (%s). Operating System error (%s).
CAUSE: Possibly the directory does not exist or is not accessible. Possibly permissions on the directory prevent reading. Operating System error should give further details.
ACTION: See your sysadmin.
PARAMS:

ERROR: [DM_CCONTENT_E_LOCK_REQUEST]

SEVERITY: ERROR
DESCRIPTION: SIS Error requesting file lock on filename (%s) in order to lock the Session Temporary Content Directory for use on the first Getfile request. Lock_wait %i. Operating System error was (%s). When using the Client Local area, the client API library places a lock on the Local Area content directory to prevent cleanup processing from deleting its content files. The lock is taken on the first access to the content area (the 1st nameless getfile request). This error indicates that a file lock could not be acquired on the .lock file used for this procedure preventing initialization of the Local area. The Getfile request will fail.
CAUSE: Possibly the operating system is out of file or lock resources. Possibly permissions prevent the opening of the .lock file or the taking of locks resources. Operating System error should give further details.
ACTION: See your sysadmin.
PARAMS:

ERROR: [DM_CCONTENT_E_PERMS1]

SEVERITY: ERROR
DESCRIPTION: S The Local Content Area cannot be initialized because the session does not have permission to make updates in the Root Local Area (%s). The Local Area root and its immediate subdirectories should allow public write access.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_CCONTENT_E_PATH_TOO_LONG]

SEVERITY: ERROR
DESCRIPTION: SI Cannot create file in directory %s as the resulting path/filename would exceed the system limitation of %d bytes.
CAUSE: The path to the content area is too long, preventing the system from being able to create a short enough filename such that the combination of the path/filename fits within the system limits of a legal pathname. The content area path must allow room for at least 11- byte filenames.
ACTION: Set or change the local_path field in the dmcl.ini to use a new content area with a shorter directory path.
PARAMS:

ERROR: [DM_CCONTENT_E_LCOPY_NONFS]

SEVERITY: ERROR
DESCRIPTION: The use_local_on_copy option requires that the client be nfs enabled. Since the nfs_enabled option for this client is not set to TRUE the local area protocols must default to use_local_always.
CAUSE: The use_local_on_copy option specifies that the local area should be used only when a file copy is required on getfile requests. If the file can be fetched by just returning a link or a direct filename pointer then the option specifies that nfs filenames be returned. This option requires that NFS access be enabled.
ACTION: If the client has nfs access to the server common area then set the nfs_enabled option to TRUE for this client. Otherwise turn off the use_local_on_copy option.
PARAMS:

ERROR: [DM_CCONTENT_E_PERMS2]

SEVERITY: ERROR
DESCRIPTION: If the local root is shared by multiple users then in some cases the user environment can prevent the Local Area from being created with proper permissions (the user may use a umask which disallows creating public files).
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_CCONTENT_E_NO_UNIQUE]

SEVERITY: ERROR
DESCRIPTION: SIS Unable to generate a unique file name. While creating a file for the sysobject %s with hint %d the maximum number of collisions was exceeded. The file name generated was %s
CAUSE: A client session executed a nameless getfile request against a sysobject on a content can not find a unique file name on the content area. The client session probably has retrieved the same content object many times.
ACTION: Re-connect the session and try again.
PARAMS:

ERROR: [DM_CCONTENT_E_LOCK_RELEASE]

SEVERITY: ERROR
DESCRIPTION: SS Error releasing file lock on filename (%s) in order to unlock the Session Temporary Content Directory at session exit. Operating System error was (%s). When using the Client Local area, the client API library places a lock on the Local Area content directory to prevent cleanup processing from deleting its content files. The lock is released at session exit to allow cleanup handling to become available. This error indicates that the file lock which should have been acquired on the .lock file during use of the Local Area could not be released. Session end processing will proceed normally in the hopes that the error will not cause any later problems. If the error is an indication that the lock is not actually held then no damage is done. If the lock is held but not released, then it will be released anyway if the client process is terminated. Otherwise cleanup for orphaned clients will not be done automatically until this client process terminates.
CAUSE: Possibly the file lock was never actually acquired. Operating System error should give further details.
ACTION: See your sysadmin and check for any previously reported errors.
PARAMS:

ERROR: [DM_CCONTENT_W_PURGE_CONTENTS]

SEVERITY: WARNING
DESCRIPTION: SS Error occurred during purge operation on temporary content area (%s). Not all files could be removed. Operating System error was (%s).
CAUSE: Possibly the content area directory has been removed or is no longer accessible. Previous error messages may give more information.
ACTION: If warning occurs frequently, see your sysadmin.
PARAMS:

ERROR: [DM_CCONTENT_W_APICONFIG_VALUE]

SEVERITY: WARNING
DESCRIPTION: S The Client configuration setting for %s in the dmcl.ini file specifies an invalid value. Overriding this setting with its default value.
CAUSE: The client configuration specified a Local Area option value that was not valid.
ACTION: Check the dmcl.ini settings for correctness.
PARAMS:

ERROR: [DM_CCONTENT_W_DISKFULL_WARN]

SEVERITY: WARNING
DESCRIPTION: SLII Diskfull warning threshold exceeded in content area %s. Free Bytes Remaining: %dK. Current Disk Usage: %d percent. Diskfull Limit: %d percent.
CAUSE: The disk pointed to by the Local Content Area has exceeded the Diskfull warning threshold established for the session.
ACTION: If diskspace is not made available (purging the content area is recommended) then the device may eventually run out of space.
PARAMS:

ERROR: [DM_CCONTENT_W_APICONFIG_PATH]

SEVERITY: WARNING
DESCRIPTION: S The configuration setting for the local_path in the dmcl.ini file specifies a directory (%s) that does not exist or cannot be accessed. Overriding this setting with its default local area.
CAUSE: The client configuration specified a Local location definition that was not accessible by the client. Possibly the disk it is defined to is not mounted or does not exist. Possibly permissions on the device prevent its use.
ACTION: Check the Local Path setting for correctness.
PARAMS:

ERROR: [DM_CCONTENT_W_CLEANUP_ERROR]

SEVERITY: WARNING
DESCRIPTION: S During session exit errors were encountered cleaning up the session content directory (%s). These files will be automatically cleaned up the next time you connect. When using the Local or Common area, cleanup of fetched content files is performed automatically when the session exits. This message is given if an error is encountered during cleanup processing. It is a warning only, indicating that cleanup may not have been complete.
CAUSE: Possibly the content area directory has been removed or is no longer accessible. Previous error messages may give more information.
ACTION: If warning occurs frequently, see your sysadmin.
PARAMS:

ERROR: [DM_CCONTENT_I_AUTO_PURGE]

SEVERITY: INFORMATION
DESCRIPTION: S Local Content Area (%s) was purged automatically as the Diskfull Warning threshold was exceeded during a getfile request. When the LOCAL_PURGE_ON_DISKFULL option is set then purging occurs automatically whenever the diskfull percentage rises above the warning limit.
CAUSE:
ACTION:
PARAMS:

nahoru

DM_COMPOSITE

ERROR: [DM_COMPOSITE_F_INIT3]

SEVERITY: FATAL
DESCRIPTION: The type manager returned an error storing the dm_composite type.
CAUSE: Unknown.
ACTION: Look at the error logged by the type manager. Report this message and any parameters to your Documentum Site Representative.
PARAMS:

ERROR: [DM_COMPOSITE_F_INIT1]

SEVERITY: FATAL
DESCRIPTION: The dm_composite type was found in the database without a version stamp.
CAUSE: Unknown.
ACTION: Report this message and any parameters to your Documentum Site Representative.
PARAMS:

ERROR: [DM_COMPOSITE_F_INIT2]

SEVERITY: FATAL
DESCRIPTION: II Version stamp %d was expected to be %d.
CAUSE: The version stamp that the dm_composite object software expected was different from the actual version stamp in the database.
ACTION: You must upgrade your Documentum docbase to conform to the software that you are running. If your software and data are consistent, then report this message and any parameters to your Documentum Site Representative.
PARAMS:

ERROR: [DM_COMPOSITE_F_INT1]

SEVERITY: FATAL
DESCRIPTION: S The following database query could not be executed: %s.
CAUSE: Inconsistency between the server and the composite type.
ACTION: Look at the error logged by the database. Report this message and any parameters to your Documentum Site Representative. Content Facility errors (c) Copyright Documentum, Inc., 1991 – 1995. All rights reserved
PARAMS:

ERROR: [DM_COMPOSITE_E_ALREADY_LINKED]

SEVERITY: ERROR
DESCRIPTION: SD The %s sysobject is already linked to the composite with ID %s.
CAUSE: You just linked a composite that has been linked before. Most likely the sysobject in question is erroneous.
ACTION: No action is required. The requested link operation is denied.
PARAMS:

ERROR: [DM_COMPOSITE_E_COMPN_DOC]

SEVERITY: ERROR
DESCRIPTION: D The component with %s id cannot be added since components of this composite must all be documents.
CAUSE: You tried to insert or append a component in a composite that does not match the previous component types. At each level a given composite is homogeneous. (i.e., it either contains all composites or all documents).
ACTION: Reissue the append or insert with the appropriate type. If you need to insert a composite into a composite containing documents, or a document into a composite containing composites, you may have to create dummy composites to restructure the composite hierarchy.
PARAMS:

ERROR: [DM_COMPOSITE_E_INVALID_CHECKIN]

SEVERITY: ERROR
DESCRIPTION: SS Invalid version label %s specified for composite %s checkin.
CAUSE: A user specified composite version label different than CURRENT. Currently, only CURRENT version of a composite can be checked in.
ACTION: Change version label to CURRENT and try checking in again.
PARAMS:

ERROR: [DM_COMPOSITE_E_CIRC_LINK]

SEVERITY: ERROR
DESCRIPTION: S Cannot create circular links for composite with path name %s.
CAUSE: New linkages in this composite have caused circularity of composite containment.
ACTION: Remove the unwanted links and try again.
PARAMS:

ERROR: [DM_COMPOSITE_E_CANT_DESTROY]

SEVERITY: ERROR
DESCRIPTION: S Cannot destroy composite with path name %s since it is not empty.
CAUSE: You tried to destroy a non-empty composite.
ACTION: A composite must be empty before destruction.
PARAMS:

ERROR: [DM_COMPOSITE_E_PATH_EXISTS]

SEVERITY: ERROR
DESCRIPTION: SS Cannot save (or link) %s composite with path name %s because one already exists.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_COMPOSITE_E_CANT_COMPUTE_DESC]

SEVERITY: ERROR
DESCRIPTION: S Cannot compute child composites for %s composite.
CAUSE: Most likely security violation. ACTION:consult the previous error messages.
ACTION:
PARAMS:

ERROR: [DM_COMPOSITE_E_INVALID_PATH]

SEVERITY: ERROR
DESCRIPTION: S Cannot fetch composite with path name %s.
CAUSE: You tried to fetch a composite with a non-existent path name.
ACTION: Retry the operation with a valid path name.
PARAMS:

ERROR: [DM_COMPOSITE_E_CANT_SAVE_NO_LINK]

SEVERITY: ERROR
DESCRIPTION: S Cannot save composite with object_name %s – composites must be linked.
CAUSE: You tried to save a composite without any linkages. Your default composite or the composite that you tried to link may be bad.
ACTION: All composites must have one linkage. Link this composite to another composite and try again.
PARAMS:

ERROR: [DM_COMPOSITE_E_NO_COMPONENT]

SEVERITY: ERROR
DESCRIPTION: IS Cannot find the component at position %d in composite %s.
CAUSE: object_names of all contained composites within the same composite must be unique.
ACTION: Remove the linkage that caused this problem.
PARAMS:

ERROR: [DM_COMPOSITE_E_COMPN_COMPS]

SEVERITY: ERROR
DESCRIPTION: D The component with %s id cannot be added since components of this composite must all be composites.
CAUSE: You tried to insert or append a component into a composite that does not match the previous component types. At each level a given composite is homogeneous. (i.e., it either contains all composites or all documents).
ACTION: Reissue the append or insert with the appropriate type. If you need to insert a composite into a composite containing documents, or a document into a composite containing composites, you may have to create dummy composites to restructure the composite hierarchy.
PARAMS:

ERROR: [DM_COMPOSITE_E_TOO_MANY_LEVELS]

SEVERITY: ERROR
DESCRIPTION: SSI Cannot link %s composite to %s composite since the level of nesting is passed the limit (%d).
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_COMPOSITE_E_CANT_CHANGE_NAME]

SEVERITY: ERROR
DESCRIPTION: Cannot change a composite name.
CAUSE: You tried to change the object_name attribute of an existing composite. This is not a supported operation.
ACTION: No action is required. The requested save operation is not carried.
PARAMS:

ERROR: [DM_COMPOSITE_E_INVALID_COMP]

SEVERITY: ERROR
DESCRIPTION: D The component identified by %s is of invalid type.
CAUSE: All composite components must be either documents or composites (or subtypes of dm_document or dm_composite).
ACTION: Reissue the appendcomp, insertcomp with the appropriate object type.
PARAMS:

ERROR: [DM_COMPOSITE_E_CANT_DELETE_LINK]

SEVERITY: ERROR
DESCRIPTION: SS Cannot delete sysobject %s from composite with path name %s.
CAUSE: Your unlink operation between the sysobject and composite has failed. Most likely the sysobject in question is erroneous.
ACTION: No action is required. The requested link operation is denied.
PARAMS:

ERROR: [DM_COMPOSITE_E_INVALID_COMPL]

SEVERITY: ERROR
DESCRIPTION: SD Invalid component label %s for %s component.
CAUSE: Currently, only CURRENT label is accepted with composite components.
ACTION: Retry with the valid label.
PARAMS:

ERROR: [DM_COMPOSITE_E_NONEXISTENT_COMPN]

SEVERITY: ERROR
DESCRIPTION: DS Nonexistent component %s ID for %s composite.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_COMPOSITE_E_INVALID_LABEL]

SEVERITY: ERROR
DESCRIPTION: SS Version label %s must exist in %s composite.
CAUSE: A user tried to append or insert a component to a static version of a composite. These operations can be performed on a composite with CURRENT version label.
ACTION: Use the dynamic version of the composite with append or insert component operations.
PARAMS:

ERROR: [DM_COMPOSITE_E_CANT_ADD_LINK]

SEVERITY: ERROR
DESCRIPTION: SS Cannot add sysobject %s to composite with path name %s.
CAUSE: Your linkage between the sysobject and composite has failed.
ACTION: No action is required. The requested link operation is denied.
PARAMS:

ERROR: [DM_COMPOSITE_E_CANT_DROP_CHILDL]

SEVERITY: ERROR
DESCRIPTION: SD No link established between composite with path name %s and ancestor composite with ID %s.
CAUSE: You tried to drop a non-existent ancestor. This may have happened when trying to update the composite explosion during a removecomp operation. If this error message is reported, it indicates that the child composites are not accurate to indicate the ancestor relationship with a given composite at the right position, If so, either the children information has been altered incorrectly or someone has tampered with the database.
ACTION: If this error condition occurs then the composite information is inaccurate. The only action which can be done at this time is to recreate the child composites.
PARAMS:

ERROR: [DM_COMPOSITE_E_BAD_ORDER]

SEVERITY: ERROR
DESCRIPTION: L Invalid order number %d specified. Must be positive and non-zero.
CAUSE: You have specified a negative or zero order number during insertcomp or removecomp operation. Order numbers must be positive. The order number zero is resevered for the composite itself.
ACTION: Specify a positive order number with the insertcomp or removecomp operation.
PARAMS:

ERROR: [DM_COMPOSITE_E_CANT_DROP_LINK]

SEVERITY: ERROR
DESCRIPTION: SD No link exists between composite with path name %s and sysobject with ID %s.
CAUSE: You tried to drop a non-existent linkage.
ACTION: No action is required. The requested unlink operation is denied.
PARAMS:

ERROR: [DM_COMPOSITE_E_MUST_HAVE_NAME]

SEVERITY: ERROR
DESCRIPTION: A new composite must have an object_name.
CAUSE: All composites must have an object_name during creation.
ACTION: Set object_name attribute and try to save again.
PARAMS:

nahoru

DM_CONTAINMENT

ERROR: [DM_CONTAINMENT_F_INIT3]

SEVERITY: FATAL
DESCRIPTION: The type manager returned an error storing the dmContainment type.
CAUSE: Unknown.
ACTION: Look at the error logged by the type manager. Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_CONTAINMENT_F_INIT4]

SEVERITY: FATAL
DESCRIPTION: The type manager returned an error converting the dm_containment type.
CAUSE: Unknown.
ACTION: Look at the error message logged by the type manager. Report this message and any parameters to your Documentum Site Representative.
PARAMS:

ERROR: [DM_CONTAINMENT_F_INIT1]

SEVERITY: FATAL
DESCRIPTION: The dmContainment type was found in the database without a version stamp.
CAUSE: Unknown.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_CONTAINMENT_F_TYPE_CONVERSION]

SEVERITY: FATAL
DESCRIPTION: I Failed to convert type dm_containment to version %d.
CAUSE: Type conversion failed.
ACTION: Report the problem. $Id: dmcompos.e,v 5.0 1998/01/10 02:07:31 sol_ora Exp $ dmComposite class errors
PARAMS:

ERROR: [DM_CONTAINMENT_F_INIT2]

SEVERITY: FATAL
DESCRIPTION: II Version stamp %d was expected to be %d.
CAUSE: The version stamp that the dmContainment object software expected was different from the actual version stamp in the database.
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:

ERROR: [DM_CONTAINMENT_F_INT1]

SEVERITY: FATAL
DESCRIPTION: S The following database query %s could not be executed.
CAUSE: Inconsistency between the server and the sysobject type.
ACTION: Look at the error logged by the database. Report this message and any parameters to your Documentum Site
PARAMS:

ERROR: [DM_CONTAINMENT_E_UPDATE_FAIL]

SEVERITY: ERROR
DESCRIPTION: SS Database update on the following table %s generated the following database %s error.
CAUSE: Used for internal purpose.
ACTION: Report to your sys admin.
PARAMS:

ERROR: [DM_CONTAINMENT_E_BAD_PARAM]

SEVERITY: ERROR
DESCRIPTION: S Invalid object id %s specified.
CAUSE: Used for internal purpose.
ACTION: Report to Docuemtum.
PARAMS:

ERROR: [DM_CONTAINMENT_E_NEED_PRIV_FOR_CHANGE]

SEVERITY: ERROR
DESCRIPTION: SS The current user %s has insufficient privileges to save or destroy %s containment.
CAUSE: A user with insufficient privileges tried to save or destroy a containment object.
ACTION: See your sysadmin.
PARAMS:

ERROR: [DM_CONTAINMENT_E_INVALID_COMPONENT]

SEVERITY: ERROR
DESCRIPTION: D Component object with id %s does not exist.
CAUSE: The component could be destroyed by another user.
ACTION: Please make sure that the chosen component object is still in the docbase.
PARAMS:

ERROR: [DM_CONTAINMENT_E_CANT_FETCH]

SEVERITY: ERROR
DESCRIPTION: D Cannot fetch – Invalid object ID %s
CAUSE: Could not fetch an object with the given id.
ACTION: This is probably caused by a bad ID. Or, possibly, a connection to the Documentum server could not be established.
PARAMS:

ERROR: [DM_CONTAINMENT_E_FETCH_FAIL]

SEVERITY: ERROR
DESCRIPTION: SS Database fetching on the following table %s generated the following database %s error.
CAUSE: Used for internal purpose.
ACTION: Report to your sys admin.
PARAMS:

ERROR: [DM_CONTAINMENT_E_CURSOR_FAIL]

SEVERITY: ERROR
DESCRIPTION: SS The following query %s generated the following database %s error
CAUSE: Used for internal purpose.
ACTION: Report to your sys admin.
PARAMS:

nahoru

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:

nahoru

DM_CRYPTO

ERROR: [DM_CRYPTO_E_DECRYPTPASS_FAILED]

SEVERITY: ERROR
DESCRIPTION: Failed to decrypt password
CAUSE: The password could not be decrypted.
ACTION: Report this message and error number to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_REMOTE_SERVERS_FAILED]

SEVERITY: ERROR
DESCRIPTION: Failed to retrieve list of remote servers
CAUSE: The list .
ACTION: Report this message and error number to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_STORAGE_AREA_CANNOT_BE_ENCRYPTED_STORAGE_TYPE]

SEVERITY: ERROR
DESCRIPTION: Only file stores can be encrypted.
CAUSE: The crypto_mode attribute was non-zero during creation of a storage area that is not a file store.
ACTION: Make sure that the crypto_mode attribute is not set for the storage area.
PARAMS:

ERROR: [DM_CRYPTO_E_ENCRYPTPASS_FAILED]

SEVERITY: ERROR
DESCRIPTION: Failed to encrypt password
CAUSE: The password could not be encrypted.
ACTION: Report this message and error number to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_NULL_CN]

SEVERITY: ERROR
DESCRIPTION: A null common name was detected when creating a certificate
CAUSE: When checking the input to certificate creation a null common name was detected.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_PASSWORDS_DO_NOT_MATCH]

SEVERITY: ERROR
DESCRIPTION: Passwords do not match.
CAUSE: Passwords entered do not match.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_NULL_KEY_FILE_LOCATION]

SEVERITY: ERROR
DESCRIPTION: NULL key file location encountered.
CAUSE: The operation needs a valid key file location.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_NULL_FSK]

SEVERITY: ERROR
DESCRIPTION: NULL Filestore KEY (FSK) passed.
CAUSE: NULL FSK was passed to a function expecting a valid one.
ACTION: Report this message and error number to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_NO_PASSWORD_PRESENT_IN_FILE_TO_ENCRYPT]

SEVERITY: ERROR
DESCRIPTION: S A password was not found in file %s to encrypt.
CAUSE: The file is probably empty.
ACTION: Check that the file is present, and if so it is not empty and a valid password is present in the file.
PARAMS: – S – File name

ERROR: [DM_CRYPTO_E_KEYSTORE_ALREADY_INITIALIZED_WITH_DIFFERENT_LOCATION]

SEVERITY: ERROR
DESCRIPTION: S Key store at location %s has already been initialized..
CAUSE: A key store has already been initialized.
ACTION: None.
PARAMS: Key store location

ERROR: [DM_CRYPTO_E_DEFAULT_PASSPHRASE_CREATION_FAILED]

SEVERITY: ERROR
DESCRIPTION: Creation of default passphrase failed
CAUSE: This is an internal error and must be reported to your Documentum site representative.
ACTION: Report this message and internal error number to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_KEYSTORE_NOT_INITIALIZED]

SEVERITY: ERROR
DESCRIPTION: A key store has not been initialized yet.
CAUSE: An operation is being attempted on a key store before initializing the key store.
ACTION: Make sure that the key store has been initializd before attempting to perform an operation using the key store.
PARAMS:

ERROR: [DM_CRYPTO_E_CORRUPT_AEK_OR_PASSPHRASE_MISMATCH]

SEVERITY: ERROR
DESCRIPTION: AEK could not be read from the file
CAUSE: Either the AEK is corrupt or the AEK was not encrypted using the given password.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_PARAMS_ALREADY_INITIALIZED]

SEVERITY: ERROR
DESCRIPTION: Crypto parameters have already been initialized
CAUSE: Crypto parameters that have been initialized are being initialized again.
ACTION: Report this message and error number to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_KEY_PAIR_NOT_NULL_DURING_CERT_CREATION]

SEVERITY: ERROR
DESCRIPTION: A key pair was found to be non null when expected to be null.
CAUSE: An operation sequencing error occurred while function performing cryptographic operation.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_INVALID_AEK_IN_AEKSTORE_DM]

SEVERITY: ERROR
DESCRIPTION: Invalid AEK present in the Documentum AEK store.
CAUSE: An invalid AEK was found in the Documentum AEK store.
ACTION: Report this message and error number to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_NULL_SERIAL_NUMBER]

SEVERITY: ERROR
DESCRIPTION: A null serial number was detected when creating a certificate
CAUSE: When checking the input to certificate creation a null serial number was detected.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_CREATE_EVENT_FAILED]

SEVERITY: ERROR
DESCRIPTION: Creation of an event object on windows failed
CAUSE: Either the resource are not available, or the event name is being used some other resource already.
ACTION: Report this message and internal error number to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_CONNECT_FAILED]

SEVERITY: ERROR
DESCRIPTION: Failed to connect to server
CAUSE: Failed to connect to server.
ACTION: Report this message and error number to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_DIRECTORY_CREATION_FAILED]

SEVERITY: ERROR
DESCRIPTION: Could not create key store directory.
CAUSE: Either the key store directory is already present, or permission not available to remove directory.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_CANT_CREATE_CRYPTO_OBJECTS]

SEVERITY: ERROR
DESCRIPTION: SI File store key creation for storage area %s failed. Internal error – %d.
CAUSE: Creation of a file store key for a storage area failed.
ACTION: Report this message and internal error number to your Documentum site representative.
PARAMS: S – Storage Area Name I – Low level error

ERROR: [DM_CRYPTO_E_INSERT_CERT_IN_LIST_FAILED]

SEVERITY: ERROR
DESCRIPTION: The number of certificates/keys in a list does not match the number inserted into a key store
CAUSE: The list of certificates or the key store is invalid.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_TEMPORARY_FILE_DELETE_FAILED]

SEVERITY: ERROR
DESCRIPTION: A temporary file cound not be deleted
CAUSE: Possibly the file is in use or the permissions do not allow it to be deleted.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_INVALID_HEX_NUMBER]

SEVERITY: ERROR
DESCRIPTION: An invalid hex number was passed to a function.
CAUSE: An invalid hex number was passed to a function.
ACTION: Report this message to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_DECRYPTION_ALREADY_FINALIZED]

SEVERITY: ERROR
DESCRIPTION: Decryption has already been finalized.
CAUSE: Internal error.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_INVALID_TEXT_FOR_DECRYPTION]

SEVERITY: ERROR
DESCRIPTION: The string to be decrypted is invalid.
CAUSE: Either the string was not encrypted or was not encrypted using the encrypttext method or does not have the DM_ENCR_TEXT= prefix.
ACTION: Make sure that the string was encrypted using the encrypttext method, and if so has the DM_ENCR_TEXT= prefix.
PARAMS:

ERROR: [DM_CRYPTO_E_DIRECTORY_READ_ERROR]

SEVERITY: ERROR
DESCRIPTION: S Could not read directory – %s
CAUSE: Either the key store directory is not present, or permission not available to remove directory.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS: – S – Name of directory that is being scanned

ERROR: [DM_CRYPTO_E_CIPHER_ALREADY_INITIALIZED]

SEVERITY: ERROR
DESCRIPTION: A cipher has already been initialized
CAUSE: A cipher that has already been initialized is being initialized again.
ACTION: Report this message and error number to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_NO_LOCAL_COMPONENT_STORE]

SEVERITY: ERROR
DESCRIPTION: No local component store for server
CAUSE: A server in the distributed configuration does not have any local component store.
ACTION: Refer to the documentation for how to setup a single distributed docbase.
PARAMS:

ERROR: [DM_CRYPTO_E_FILE_RENAME_FAILED]

SEVERITY: ERROR
DESCRIPTION: SS The file %s could not be renamed to %s.
CAUSE: Either the file is not present, or the directory does not have WRITE permission.
ACTION: Ensure that the file is present, and set the correct permissions on the directory.
PARAMS: Source File name Destination File name

ERROR: [DM_CRYPTO_E_MULTIPLE_LINES_IN_PASSWORD_FILE]

SEVERITY: ERROR
DESCRIPTION: The password in file cannot be encrypted. Only single line password files can be encrypted using this utility.
CAUSE: The file contains multiple line. Only single line password files can be encrypted using this utility.
ACTION: Make sure that file does not contain multiple lines. Size of password cannot exceed 128 bytes.
PARAMS:

ERROR: [DM_CRYPTO_E_PASSWORD_LENGTH_IN_FILE_EXCEEDS_MAX_SIZE]

SEVERITY: ERROR
DESCRIPTION: Password length in file exceeds maximum allowed size of 128 bytes.
CAUSE: Length password present in the first line of a file exceeds 128 bytes.
ACTION: Make sure that the length of password does not exceed 128 bytes.
PARAMS:

ERROR: [DM_CRYPTO_E_SP_ENCRYPTED_DATA_INVALID]

SEVERITY: ERROR
DESCRIPTION: Invalid encrypted data.
CAUSE: Data decrypted by system password is invalid.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_NULL_ALGORITHM_OBJECT]

SEVERITY: ERROR
DESCRIPTION: Null algorithm object encountered while performing a cryptographic operation
CAUSE: A NULL algorithm object was found during initialization.
ACTION: Report this message and error number to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_NULL_DBK]

SEVERITY: ERROR
DESCRIPTION: NULL Docbase Key (DBK) passed.
CAUSE: NULL DBK passed to a function expecting a valid one.
ACTION: Report this message and error number to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_DELETE_CERT_IN_LIST_FAILED]

SEVERITY: ERROR
DESCRIPTION: The number of certificates/keys in a list does not match the number deleted from a key store
CAUSE: The list of certificates or the key store is invalid.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_UPDATE_CONTENT_REPL_JOB_FAILED]

SEVERITY: ERROR
DESCRIPTION: Failed to update local dm_ContentReplication job
CAUSE: The dm_ContentReplication job for the local server could not be updated.
ACTION: See trace file for more information.
PARAMS:

ERROR: [DM_CRYPTO_E_SHM_ATTACH_FAILED]

SEVERITY: ERROR
DESCRIPTION: Attaching to a shared memory segment failed.
CAUSE: Attaching to a shared memory segment failed.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_NULL_PASSWORD]

SEVERITY: ERROR
DESCRIPTION: A NULL password was passed to function expecting a valid one.
CAUSE: A NULL password was passed to function expecting a valid one.
ACTION: Report this message and error number to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_DIRECTORY_REMOVAL_FAILED]

SEVERITY: ERROR
DESCRIPTION: Could not remove key store directory.
CAUSE: Either the directory is not present, or permission not available to read directory.
ACTION: Make sure the directory exists, and if so it has read permission.
PARAMS:

ERROR: [DM_CRYPTO_E_ALREADY_INITIALIZED]

SEVERITY: ERROR
DESCRIPTION: A Crypto object has already been initialized
CAUSE: A Crypto object that has initialized is being initialized again.
ACTION: Report this message and error number to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_INVALID_AEK_IN_AEKSTORE_SHM]

SEVERITY: ERROR
DESCRIPTION: Invalid AEK in the Documentum AEK shared memory segment.
CAUSE: An invalid AEK was found in the Documentum AEK shared memory segment.
ACTION: Report this message and error number to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_CONTENT_ENCRYPTION_FAILED]

SEVERITY: ERROR
DESCRIPTION: I Content encryption failed. Internal error – %d
CAUSE: Content encryption failed.
ACTION: Report this message and internal error number to your Documentum site representative.
PARAMS: – I – Internal error.

ERROR: [DM_CRYPTO_E_ILL_FORMED]

SEVERITY: ERROR
DESCRIPTION: An object is not completely formed.
CAUSE: An object has not been completely formed.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_NO_LOCAL_CONTENT_REPL_JOB]

SEVERITY: ERROR
DESCRIPTION: Failed to find local dm_ContentReplication job
CAUSE: The dm_ContentReplication job for the local server does not exist.
ACTION: You must probably run the utility toolset.ebs on the local server.
PARAMS:

ERROR: [DM_CRYPTO_E_CANT_WRITE]

SEVERITY: ERROR
DESCRIPTION: SS Unable to write to file: (%s). Operating System Error: (%s)
CAUSE: Cannot write to the conversion file indicated.
ACTION: Make sure that the directory exists and has write permission.
PARAMS: – S – File name – S – Storage area name

ERROR: [DM_CRYPTO_E_INIT_CERT_OBJECT_FAILED]

SEVERITY: ERROR
DESCRIPTION: The RSA function C_InitializeCertC failed to initialize the certificate object.
CAUSE: Internal RSA library error.
ACTION: Please turn on -ocrypto_trace, restart the content server and collect the server log after reproducing the issue and send it to Documentum Technical Support. Data Dictionary Facility errors ** Documentum DocuServer ** Confidential Property of Documentum, Inc. ** (c) Copyright Documentum, Inc., 1991-1999 ** All rights reserved. **
PARAMS:

ERROR: [DM_CRYPTO_E_PASSWORD_MISMATCH]

SEVERITY: ERROR
DESCRIPTION: There was a mismatch with the current key store password
CAUSE: When verifying the key store password a mismatch was detected.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_FILE_OPEN_FOR_WRITE_FAILED]

SEVERITY: ERROR
DESCRIPTION: S The file %s could not opened for write.
CAUSE: Either the file is not present, or the permissions on the file is not set for WRITE.
ACTION: Make sure that the file is present, and the permissions on the file is set for WRITE.
PARAMS: – S – File name

ERROR: [DM_CRYPTO_E_INVALID_PRIVATE_KEY]

SEVERITY: ERROR
DESCRIPTION: An invalid private key of an asymmetric key pair was detected
CAUSE: The private key failed an integrity check based on the key identifier.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_PASSPHRASE_DOES_NOT_MATCH]

SEVERITY: ERROR
DESCRIPTION: Entered passphrase does not match the one in the shared memory segment.
CAUSE: The passphrase given does not match the one stored in the shared mmeory segment.
ACTION: Make sure that you have supplied the correct passphrase.
PARAMS:

ERROR: [DM_CRYPTO_E_KEY_STORE_ALREADY_EXISTS]

SEVERITY: ERROR
DESCRIPTION: A key store already exists.
CAUSE: Attempt was made to create a key store where one already exists.
ACTION: Check if the key store files are already present.
PARAMS:

ERROR: [DM_CRYPTO_E_MISMATCHED_DIGEST_ALGORITHM]

SEVERITY: ERROR
DESCRIPTION: Digest algorithm does not match.
CAUSE: Algorithm used while signing data is different from the one used during verification.
ACTION: Report this message and internal error number to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_NULL_CODING_OBJECT]

SEVERITY: ERROR
DESCRIPTION: NULL encoding object found
CAUSE: NULL encoding object was passed to a function expecting a valid one.
ACTION: Report this message and error number to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_INVALID_CERTIFICATE]

SEVERITY: ERROR
DESCRIPTION: An invalid certificate was detected
CAUSE: The certificate has an invalid field or failed an integrity check.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_DM_AEKSTORE_INSTANCE_EXISTS]

SEVERITY: ERROR
DESCRIPTION: The Documentum AEK store object already exists
CAUSE: An instance of the documentum AEK store object already exists. An attempt is made to create another one.
ACTION: Report this message and error number to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_SHM_READ_FAILED]

SEVERITY: ERROR
DESCRIPTION: Read from a shared memory segment failed.
CAUSE: Read from a shared memory segment failed.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_DMCL_INIT_FAILED]

SEVERITY: ERROR
DESCRIPTION: Failed to initialize DMCL
CAUSE: The Documentum Client Library could not be initialized.
ACTION: Report this message and error number to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_DUPLICATE_CERTS]

SEVERITY: ERROR
DESCRIPTION: Multiple certificates present for same serial number.
CAUSE: Multiple certificates present for same serial number. This is an internal error.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_HASH_KEY_INVALID]

SEVERITY: ERROR
DESCRIPTION: A hash key was found to be null or invalid.
CAUSE: A hash operation that requires a key found the key to be null or invalid.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_INVALID_ARGUMENT]

SEVERITY: ERROR
DESCRIPTION: Invalid arguments. Check Usage
CAUSE: Invalid arguments were passed to this utility. Check Usage.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_ENCRYPTION_ALREADY_FINALIZED]

SEVERITY: ERROR
DESCRIPTION: Encryption has already been finalized.
CAUSE: Internal error.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_CREATE_CONTENTREPL_FILE_FAILED]

SEVERITY: ERROR
DESCRIPTION: Failed to create content replication file
CAUSE: The content replication file ContentRepl.cnt could not be created.
ACTION: Report this message and error number to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_SHM_DOES_NOT_EXIST]

SEVERITY: ERROR
DESCRIPTION: The shared memory segment keyed by a specific ID does not exists.
CAUSE: The shared memory segment was probably not created in the first place.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_CONTENT_DECRYPTION_FAILED]

SEVERITY: ERROR
DESCRIPTION: I Content decryption failed. Internal error – %d
CAUSE: Content decryption failed.
ACTION: Report this message and internal error number to your Documentum site representative.
PARAMS: – I – Internal error.

ERROR: [DM_CRYPTO_E_CERT_FIELDS_NOT_NULL_DURING_CERT_CREATION]

SEVERITY: ERROR
DESCRIPTION: The public key certificate fields were found to be non null when expected to be null.
CAUSE: An operation sequencing error occurred while function performing cryptographic operation.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_NULL_KEY_DATA]

SEVERITY: ERROR
DESCRIPTION: NULL key data found during key generation process
CAUSE: NULL key data was specified during key generation process.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_NULL_CERT_FIELD]

SEVERITY: ERROR
DESCRIPTION: A NULL certificate fields object was detected
CAUSE: A certificate object is in an uninitialized state.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_INVALID_FEDERATION_PASSWORD_FILE]

SEVERITY: ERROR
DESCRIPTION: S An invalid federation.cnt file was found for docbase %s
CAUSE: An invalid federation.cnt file was found for docbase %s.
ACTION: Make sure that the docbase contains a valid federation.cnt file.
PARAMS: – S – Docbase name

ERROR: [DM_CRYPTO_E_NULL_KEYSTORE_NAME]

SEVERITY: ERROR
DESCRIPTION: A null key store name was passed when creating a key store
CAUSE: When checking the input to key store creation a null name was detected.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_INVALID_PASSPHRASE_IN_STORE]

SEVERITY: ERROR
DESCRIPTION: Invalid passphrase is present in the store.
CAUSE: An invalid passphrase was found in the Documentum passphrase store.
ACTION: Report this message and error number to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_NULL_ORGANIZATION_UNIT]

SEVERITY: ERROR
DESCRIPTION: A null pointer to an organization unit string was passed to a function performing cryptographic operation.
CAUSE: A null pointer was passed to a function performing cryptographic operation.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_INVALID_OPERATION]

SEVERITY: ERROR
DESCRIPTION: This is not a valid operation for this cipher type
CAUSE: An operation was attempted that is invalid for this cipher type.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_INVALID_KEY_FOR_SHM]

SEVERITY: ERROR
DESCRIPTION: Invalid key for shared memory segment
CAUSE: A NUL or empty key has been specified as the key for a shared memory segment.
ACTION: Report this message and error number to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_BUFFER_SIZE_EXCEEDS_MAX_SHM_SIZE]

SEVERITY: ERROR
DESCRIPTION: Buffer size exceeds maximum allowable shared memory segment size.
CAUSE: Buffer size exceeds maximum allowable shared memory segment size.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_FETCH_CERT_FAILED]

SEVERITY: ERROR
DESCRIPTION: Error while fetching a certificate.
CAUSE: A certificate fetch failed. Maybe the certificate was deleted.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_NO_PASSWORD_ENTERED]

SEVERITY: ERROR
DESCRIPTION: No password was entered.
CAUSE: No password was entered.
ACTION: Enter a password when prompted.
PARAMS:

ERROR: [DM_CRYPTO_E_DM_SYSPASSSTORE_INSTANCE_EXISTS]

SEVERITY: ERROR
DESCRIPTION: The Documentum system password store object already exists
CAUSE: An instance of the documentum password store object already exists. An attempt is made to create another one.
ACTION: Report this message and error number to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_DOCBASE_NAME_MISSING]

SEVERITY: ERROR
DESCRIPTION: Docbase name missing while trying to open/create a key store.
CAUSE: Docbase name missing while trying to open/create a key store
ACTION: Pass a valid docbase name while opening/creating a content server key store.
PARAMS:

ERROR: [DM_CRYPTO_E_NULL_LOCATION]

SEVERITY: ERROR
DESCRIPTION: NULL AEK file name encountered .
CAUSE: A NULL AEK file name was passed to a method expecting a valid one.
ACTION: Make sure you pass a valid AEK file name.
PARAMS:

ERROR: [DM_CRYPTO_E_MAKE_SOURCE_FAILED]

SEVERITY: ERROR
DESCRIPTION: SS A failure occurred while performing an operation on file %s belonging to storage area %s
CAUSE: Either the file is not a valid one, or the storage area is invalid.
ACTION: Make sure that the file and storage area are valid.
PARAMS: – S – File name – S – Storage area name

ERROR: [DM_CRYPTO_E_DIRECTORY_CHANGE_PERMISSION_FAILED]

SEVERITY: ERROR
DESCRIPTION: Failed to change key store directory permission to 0755.
CAUSE: Either the key store directory is not present, or permission not available to remove directory.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_NULL_CIPHER_OBJECT]

SEVERITY: ERROR
DESCRIPTION: Null cipher object encountered while performing a cryptographic operation
CAUSE: A NULL cipher object was found during initialization.
ACTION: Report this message and error number to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_KEYSTORE_PUT_ERROR]

SEVERITY: ERROR
DESCRIPTION: An error was encountered when writing to the database used to store cryptographic keys
CAUSE: The database table does not exist, the folder for keys does not exist, or security does not allow write access.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_LOCATION_NOT_FOUND]

SEVERITY: ERROR
DESCRIPTION: Location not found to open/create key store. Make sure that you have passed in a valid location or the docbase name or specify environment variable DM_CRYPTO_HOME.
CAUSE: Either a location or docbase name or EM_CRYPTO_HOME environment variable must be specified to open/create a key store.
ACTION: Either pass the location or the docbase name or specify environment variable DM_CRYPTO_HOME while creating/opening the key store.
PARAMS:

ERROR: [DM_CRYPTO_E_NO_MORE_MEMORY]

SEVERITY: ERROR
DESCRIPTION: Not enough memory to allocate object.
CAUSE: System running out of memory.
ACTION: Make sure that the system has enough memory and restart process.
PARAMS:

ERROR: [DM_CRYPTO_E_INVALID_KEYPAIR]

SEVERITY: ERROR
DESCRIPTION: A NULL An invalid asymmetric key pair was detected
CAUSE: An encrypt, decrypt, or signature test of the key pair has failed.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_INVALID_FILE_NAME]

SEVERITY: ERROR
DESCRIPTION: A valid file name must be passed.
CAUSE: Pass a NULL or valid file name.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_NULL_PREFIX]

SEVERITY: ERROR
DESCRIPTION: NULL prefix passed.
CAUSE: NULL prefix was passed to a function expecting a valid one.
ACTION: Report this message and error number to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_NULL_AEK]

SEVERITY: ERROR
DESCRIPTION: NULL AEK passed.
CAUSE: NULL AEK was passed to a function expecting a valid one.
ACTION: Report this message and error number to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_DECRYPTTEXT_FAILED]

SEVERITY: ERROR
DESCRIPTION: Failed to decrypt string
CAUSE: The string could not be decrypted.
ACTION: Report this message and error number to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_CERTIFICATE_OBJECT_NULL]

SEVERITY: ERROR
DESCRIPTION: A null pointer to a public key certificate object was found in a function performing cryptographic operation.
CAUSE: A null pointer was found in a function performing cryptographic operation.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_NULL_KEY_LIST]

SEVERITY: ERROR
DESCRIPTION: A NULL key list was passed while deleting private keys from key store.
CAUSE: A NULL key list was passed while deleting private keys from key store. Internal error.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_DOCUMENTUM_ENV_MISSING]

SEVERITY: ERROR
DESCRIPTION: Environment variable DOCUMENTUM is not available.
CAUSE: The environment variable DOCUMENTUM is not available to open/create a key store.
ACTION: Set the environment variable DOCUMENTUM to point to the key store location.
PARAMS:

ERROR: [DM_CRYPTO_E_INVALID_CIPHER_MODE]

SEVERITY: ERROR
DESCRIPTION: Invalid cipher object was encountered while performing a cryptographic operation
CAUSE: An invalid cipher object was found while performing a cryptographic operation.
ACTION: Report this message and error number to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_NULL_ORGANIZATION]

SEVERITY: ERROR
DESCRIPTION: A null pointer to an organization string was passed to a function performing cryptographic operation.
CAUSE: A null pointer was passed to a function performing cryptographic operation.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_NULL_TEXT]

SEVERITY: ERROR
DESCRIPTION: A NULL string was passed to function expecting a valid one.
CAUSE: A NULL string was passed to function expecting a valid one.
ACTION: Report this message and error number to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_INVALID_SIGNATURE_DATA]

SEVERITY: ERROR
DESCRIPTION: The signature data could not be converted into a valid object
CAUSE: The signature data does not correspond to the valid object or is corrupted..
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_INVALID_DIGEST_LENGTH]

SEVERITY: ERROR
DESCRIPTION: Length of data to be digested is not valid.
CAUSE: Either the algorithm used for message digestion is incorrect or the digest object has not been initialized.
ACTION: Report this message and internal error number to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_NOT_ALL_OBJECTS_DELETED]

SEVERITY: ERROR
DESCRIPTION: Not all objects deleted based on input.
CAUSE: Not all expected objects deleted from key store.
ACTION: Report this message and error number to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_STRING_NOT_ENCRYPTED_USING_THIS_METHOD]

SEVERITY: ERROR
DESCRIPTION: The string was not encrypted using the complementary method with which it is being decrypted
CAUSE: A string encrypted using a method is not being decrypted using its complementary decryption method.
ACTION: Please use the correct correct method to decrypt the string .
PARAMS:

ERROR: [DM_CRYPTO_E_NULL_KEYSTORE_PASSWORD]

SEVERITY: ERROR
DESCRIPTION: A null keystore password was passed when creating a key store
CAUSE: When checking the input to key store creation a null password was detected.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_START_VALIDITY_GREATER_THAN_END_VALIDITY]

SEVERITY: ERROR
DESCRIPTION: The start validity date is after the end validity date for a public key certificate.
CAUSE: Invalid start and end validity dates were passed to a function performing cryptographic operation.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_NULL_BUFFER_RECEIVED_FROM_SOURCE]

SEVERITY: ERROR
DESCRIPTION: NULL buffer received from underlying source.
CAUSE: NULL buffer received from underlying source. Internal error.
ACTION: Report this message and error number to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_NO_SYSTEM_CRYPTO_KEYS_FOLDER]

SEVERITY: ERROR
DESCRIPTION: The /System/Cryptographic/Keys folder does not exist
CAUSE: The /System/Cryptographic/Keys should exist but does not
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_FILE_OPEN_FOR_READ_FAILED]

SEVERITY: ERROR
DESCRIPTION: S The file %s could not opened for read.
CAUSE: Either the file is not present, or the permissions on the file is not set for READ.
ACTION: Make sure that the file is present, and the permissions on the file is set for READ.
PARAMS: – S – File name

ERROR: [DM_CRYPTO_E_NULL_FEK]

SEVERITY: ERROR
DESCRIPTION: NULL File Encryption Key (FEK) passed.
CAUSE: NULL FEK was passed to a function expecting a valid one.
ACTION: Report this message and error number to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_CERT_PRIVATE_KEY_COUNT_MISMATCH]

SEVERITY: ERROR
DESCRIPTION: The number of certificates and private keys do not match
CAUSE: When inserting private keys and certs into a store the number of each does not match.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_PBE_STREAM_ALREADY_INITIALIZED]

SEVERITY: ERROR
DESCRIPTION: Password Based Encryption stream has already been initialized
CAUSE: Password Based Encryption parameters that have been initialized are being initialized again.
ACTION: Report this message and error number to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_NOT_INITIALIZED]

SEVERITY: ERROR
DESCRIPTION: A cryptographic object has not been initialized yet.
CAUSE: A cryptographic object has not been initialized yet..
ACTION: Report this message and error number to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_INVALID_KEY_TYPE]

SEVERITY: ERROR
DESCRIPTION: An invalid key type was specified.
CAUSE: An invalid key type was specified. Valid ones are PUBLIC and PRIVATE.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_BOOT_PROCESS_CREATION_FAILED]

SEVERITY: ERROR
DESCRIPTION: Could not create boot process.
CAUSE: Could not create boot process. Check user permission.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_PASSWORD_NOT_ENCRYPTED_USING_THIS_METHOD]

SEVERITY: ERROR
DESCRIPTION: The password was not encrypted using the complementary method with which it is being decrypted
CAUSE: A password encrypted using a method is not being decrypted using its complementary decryption method.
ACTION: Please use the correct correct method to decrypt the string .
PARAMS:

ERROR: [DM_CRYPTO_E_PASSWORD_DECRYPTION_FAILED]

SEVERITY: ERROR
DESCRIPTION: SI Decryption of password present in file %s failed, status – %d
CAUSE: The private key used to decrypt the password is wrong or is not present.
ACTION: Report this message and error number to your Documentum site representative.
PARAMS: – S – File name where password is present – I – Low level error code

ERROR: [DM_CRYPTO_E_LIST_COUNT_MISMATCH]

SEVERITY: ERROR
DESCRIPTION: The number of certificates in a list does not match the number of entries in the list
CAUSE: The list of certificates is invalid.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_INVALID_PASSWORD_FOR_DECRYPTION]

SEVERITY: ERROR
DESCRIPTION: The password to be decrypted is invalid.
CAUSE: Either the string was not encrypted or was not encrypted using the encryptpass method or does not have the DM_ENCR_PASS= prefix.
ACTION: Make sure that the string was encrypted using the encryptpass method, and if so has the DM_ENCR_PASS= prefix.
PARAMS:

ERROR: [DM_CRYPTO_E_SHM_ACCESS_DENIED]

SEVERITY: ERROR
DESCRIPTION: Access to a shared memory segment is denied.
CAUSE: You probably do not have permission to acces the shared memory segment.
ACTION: Make sure that you have the right permission to access the shared memory segment.
PARAMS:

ERROR: [DM_CRYPTO_E_ENCRYPTTEXT_FAILED]

SEVERITY: ERROR
DESCRIPTION: Failed to encrypt string
CAUSE: The string could not be encrypted.
ACTION: Report this message and error number to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_CANT_FETCH_CRYPTO_OBJECTS]

SEVERITY: ERROR
DESCRIPTION: SI The Filestore Key associated with the storage area %s could not be retrieved. Internal error – %d.
CAUSE: Retrieval of the fhe Filestore Key associated with the storage area failed.
ACTION: Report this message and internal error number to your Documentum site representative.
PARAMS: S – Storage Area Name I – Low level error

ERROR: [DM_CRYPTO_E_NULL_DATA]

SEVERITY: ERROR
DESCRIPTION: NULL data passed to a function performing cryptographic operation.
CAUSE: A NULL or zero length buffer was passed to be decrypted or decrypted.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_SHM_WRITE_FAILED]

SEVERITY: ERROR
DESCRIPTION: Write to a shared memory segment failed.
CAUSE: Write to a shared memory segment failed.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_NULL_BUFFER_DURING_CONTENT_DECRYPTION]

SEVERITY: ERROR
DESCRIPTION: NULL buffer was encountered during content decryption.
CAUSE: NULL buffer was encountered during content decryption. Internal error.
ACTION: Report this message and error number to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_INVALID_KEY_FOR_STORE]

SEVERITY: ERROR
DESCRIPTION: Invalid cyrptographic key associated with the storage area
CAUSE: The cryptographic key does not belong to the storage area.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_TRUSTED_CONTENT_SERVICES_NOT_ENABLED]

SEVERITY: ERROR
DESCRIPTION: Trusted content services must be enabled to perform the operation.
CAUSE: License for Trusted Content Services is not available.
ACTION: Make sure that you have the licnse for Trusted Content Services.
PARAMS:

ERROR: [DM_CRYPTO_E_KEY_IDENTIFIER_MISMATCH]

SEVERITY: ERROR
DESCRIPTION: The key identifier associated with a cryptographic key is incorrect
CAUSE: There is an inconsistency in the database used to store cryptographic keys.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_INITCRYPTODB_FAILED]

SEVERITY: ERROR
DESCRIPTION: Failed to initialize crypto database
CAUSE: The crypto database could not be initialized.
ACTION: Report this message and error number to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_NULL_OBJECT_TO_ENCRYPT_TEXT]

SEVERITY: ERROR
DESCRIPTION: NULL crypto objects were encountered while encrypting text
CAUSE: NULL crypto objects were encountered while encrypting text.
ACTION: Report this message and error number to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_NULL_GLOBAL_CONTEXT_OBJECT]

SEVERITY: ERROR
DESCRIPTION: S NULL global context object found.
CAUSE: The global context object has not been initialized yet.
ACTION: Report this message and error number to your Documentum site representative.
PARAMS: S – Storage Area Name

ERROR: [DM_CRYPTO_E_SHM_REMOVE_FAILED]

SEVERITY: ERROR
DESCRIPTION: Removal of a shared memory segment failed.
CAUSE: Removal of a shared memory segment failed.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_INVALID_OBJECT_FROM_SERIALIZED_DATA]

SEVERITY: ERROR
DESCRIPTION: The serialized data could not be converted into a valid object
CAUSE: The serialized data does not correspond to the object being formed or is corrupted..
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_OLD_AND_NEW_PASSWORD_NULL]

SEVERITY: ERROR
DESCRIPTION: Both old and new password cannot be passed as NULL.
CAUSE: The change password functionality encountered a NULL old and new password.
ACTION: Report this message and any parameters to your Documentum site representative. Check if the key store files are present.
PARAMS:

ERROR: [DM_CRYPTO_E_NULL_PARAMS_OBJECT]

SEVERITY: ERROR
DESCRIPTION: During a parameter object initialization, a NULL parameter object was found
CAUSE: A NULL parameter object was found during initialization.
ACTION: Report this message and error number to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_OBJECT_NOT_FOUND]

SEVERITY: ERROR
DESCRIPTION: Expected cryptographic object not found in key store.
CAUSE: Internal error or object deleted from key store.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_E_SHM_CREATE_FAILED]

SEVERITY: ERROR
DESCRIPTION: Creation of a shared memory segment failed.
CAUSE: Creation of a shared memory segment failed.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_CRYPTO_F_KEYSTORE_INIT]

SEVERITY: FATAL
DESCRIPTION: SI Failed to initialize keystore at %s. Internal error – %d
CAUSE: Failed to initialize key store. Check if key store exists at specified location.
ACTION: Report this message and any parameters to your Documentum site representative. Check if the key store files are present.
PARAMS: S – Key store location

ERROR: [DM_CRYPTO_F_KEYSTORE_LOCATION]

SEVERITY: FATAL
DESCRIPTION: Failed to find key store location. Internal error – %d.
CAUSE: Key store location could not be found. Check if key store exists at key store location.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS: I – Internal error.

ERROR: [DM_CRYPTO_W_SCAN_DIR_NO_MORE_FILES]

SEVERITY: WARNING
DESCRIPTION: S No more files were found while scanning directory – %s
CAUSE: All files in the directory have been scanned.
ACTION: None
PARAMS: – S – Name of directory that is being scanned

ERROR: [DM_CRYPTO_W_DATA_ALREADY_ENCRYPTED]

SEVERITY: WARNING
DESCRIPTION: Encrypted data cannot be encrypted again.
CAUSE: Encrypted data is being encrypted again.
ACTION: Do not attempt to encrypt already encrypted data.
PARAMS:

ERROR: [DM_CRYPTO_W_KEYSTORE_ALREADY_INITIALIZED]

SEVERITY: WARNING
DESCRIPTION: S Key store has already been initialized. Key store location – %s.
CAUSE: A key store has already been initialized.
ACTION: None.
PARAMS: – S – Key store location

nahoru

DM_DATA_DICT

ERROR: [DM_DATA_DICT_F_CANNOT_FIND_ATTRIBUTE_FOR_TYPE]

SEVERITY: FATAL
DESCRIPTION: SS Attribute %s does not exist in type %s.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: The first parameter is the name of the attribute. The second parameter is the name of the type.

ERROR: [DM_DATA_DICT_F_INTERNAL_ERROR]

SEVERITY: FATAL
DESCRIPTION: S A Data Dictionary internal error occurred: (%s).
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: The parameter is a text description of the internal error.

ERROR: [DM_DATA_DICT_F_DD_TYPE_INFO_TYPE_INIT]

SEVERITY: FATAL
DESCRIPTION: S Failed to initialize type %s.
CAUSE: Unknown.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS: The parameter is the type name

ERROR: [DM_DATA_DICT_F_CANNOT_CLONE_VALUE_ASSIST]

SEVERITY: FATAL
DESCRIPTION: D Cannot clone the dm_value_assist object with object id %s.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: The parameter is the object id of the dm_value_assist object.

ERROR: [DM_DATA_DICT_F_VALUE_QUERY_BAD_VSTAMP]

SEVERITY: FATAL
DESCRIPTION: II Type dm_value_query has a bad vstamp %d. The current vstamp for dm_value_query is supposed to be %d.
CAUSE: The RDBMS table has a bad vstamp.
ACTION: Report this error to Documentum sysadmins.
PARAMS:

ERROR: [DM_DATA_DICT_F_CANNOT_EXPUNGE_COMPUTED_EXPRESSION]

SEVERITY: FATAL
DESCRIPTION: DI Cannot expunge the computed expression with object id %s at position %d.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: The first parameter is the object id of the dm_expression object. The second parameter is the (zero-based) position of the expression.

ERROR: [DM_DATA_DICT_F_BAD_DD_ATTRIBUTE_TREATMENT]

SEVERITY: FATAL
DESCRIPTION: SI The Data Dictionary attribute %s has a bad attribute treatment value (%d).
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: The first parameter is the name of the Data Dictionary attribute. The second parameter is the internal attribute treatment value.

ERROR: [DM_DATA_DICT_F_BAD_DD_DEFAULT_VALUE_TYPE]

SEVERITY: FATAL
DESCRIPTION: SI The Data Dictionary attribute %s is of the wrong type (%d) to have a default value.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: The first parameter is the name of the Data Dictionary attribute. The second parameter is the internal attribute type code.

ERROR: [DM_DATA_DICT_F_DD_COMMON_INFO_TYPE_INIT]

SEVERITY: FATAL
DESCRIPTION: S Failed to initialize type %s.
CAUSE: Unknown.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS: The parameter is the type name

ERROR: [DM_DATA_DICT_F_EXPR_CODE_TYPE_INIT]

SEVERITY: FATAL
DESCRIPTION: S Failed to initialize type %s.
CAUSE: Unknown.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_DATA_DICT_F_DISPLAY_CONFIG_BAD_VSTAMP]

SEVERITY: FATAL
DESCRIPTION: II Type dm_display_config has a bad vstamp %d. The current vstamp for dm_display_config is supposed to be %d.
CAUSE: The RDBMS table has a bad vstamp.
ACTION: Report this error to Documentum sysadmins.
PARAMS:

ERROR: [DM_DATA_DICT_F_CANNOT_SAVE_POLICY]

SEVERITY: FATAL
DESCRIPTION: DS Could not save changes to business policy %s for state %s.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: The parameter is the object id of the dm_aggr_domain object.

ERROR: [DM_DATA_DICT_F_AGGR_DOMAIN_NO_TYPE]

SEVERITY: FATAL
DESCRIPTION: D There is no edit_type for the aggregate domain with object id %s.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: The parameter is the object id of the aggregate domain object.

ERROR: [DM_DATA_DICT_F_CANNOT_CLONE_DEFAULT_COMPUTED_EXPRESSION]

SEVERITY: FATAL
DESCRIPTION: D Cannot clone the default computed dm_expression object with object id %s.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: The parameter is the object id of the dm_expression object.

ERROR: [DM_DATA_DICT_F_CANNOT_EXPUNGE_SCOPE_CONFIG]

SEVERITY: FATAL
DESCRIPTION: DI Cannot expunge the dm_scope_config object with object id %s at position %d.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: The first parameter is the object id of the dm_scope_config object. The second parameter is the (zero-based) position of the scope_config attribute.

ERROR: [DM_DATA_DICT_F_CANNOT_CLONE_COND_COMPUTED_EXPR]

SEVERITY: FATAL
DESCRIPTION: D Cannot clone the cond computed dm_expression object with object id %s.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: The parameter is the object id of the dm_expression object.

ERROR: [DM_DATA_DICT_F_CANNOT_EXPUNGE_DD_OBJECT_FOR_OVERRIDE]

SEVERITY: FATAL
DESCRIPTION: D Cannot expunge the object with id %s during an override operation.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: The parameter is the id of the object.

ERROR: [DM_DATA_DICT_F_CANNOT_CLONE_COND_VALUE_ASSIST]

SEVERITY: FATAL
DESCRIPTION: D Cannot clone the cond value assistance dm_expresion object with object id %s.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: The parameter is the object id of the dm_expression object.

ERROR: [DM_DATA_DICT_F_CANNOT_EXPUNGE_DOMAIN_FOR_ATTR]

SEVERITY: FATAL
DESCRIPTION: S Cannot expunge the domain object for attribute %s.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: The parameter is the name of the attribute associated with the domain.

ERROR: [DM_DATA_DICT_F_ROUTINE_ID_MISMATCH]

SEVERITY: FATAL
DESCRIPTION: DD Two different routine_id objects were specified for generated expression source code: %s and %s.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: The first parameter is the object id of the first generated source sysobject. The second parameter is the object id of the second generated source sysobject.

ERROR: [DM_DATA_DICT_F_CANNOT_CLONE_NLS_DD_INFO]

SEVERITY: FATAL
DESCRIPTION: D Cannot clone the dm_nls_dd_info object with object id %s.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: The parameter is the object id of the dm_nls_dd_info object.

ERROR: [DM_DATA_DICT_F_AGGR_DOMAIN_BAD_ATTR_LENGTH]

SEVERITY: FATAL
DESCRIPTION: SIS String attribute %s has an invalid length (%d) in type %s.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: The first parameter is the name of the attribute. The second parameter is the invalid length. The third parameter is the name of object type.

ERROR: [DM_DATA_DICT_F_FOREIGN_KEY_TYPE_INIT]

SEVERITY: FATAL
DESCRIPTION: S Failed to initialize type %s.
CAUSE: Unknown.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_DATA_DICT_F_CANNOT_CLONE_DD_INFO]

SEVERITY: FATAL
DESCRIPTION: D Cannot clone the dm_dd_info object with object id %s.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: The parameter is the object id of the dm_dd_info object.

ERROR: [DM_DATA_DICT_F_NULL_DOMAIN_POINTER]

SEVERITY: FATAL
DESCRIPTION: The domain pointer for a dm_dd_info object is NULL.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: None.

ERROR: [DM_DATA_DICT_F_CANNOT_EXPUNGE_DEFAULT_VALUE]

SEVERITY: FATAL
DESCRIPTION: DI Cannot expunge the default value expression with object id %s at position %d.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: The first parameter is the object id of the dm_expression object. The second parameter is the (zero-based) position of the expression.

ERROR: [DM_DATA_DICT_F_VALUE_ASSIST_TYPE_INIT]

SEVERITY: FATAL
DESCRIPTION: S Failed to initialize type %s.
CAUSE: Unknown.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_DATA_DICT_F_NULL_DEFAULT_ID]

SEVERITY: FATAL
DESCRIPTION: The default_id attribute is NULL for this dm_cond_id_expr object.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: None.

ERROR: [DM_DATA_DICT_F_CANNOT_CLONE_DEFAULT_VALUE_ASSIST]

SEVERITY: FATAL
DESCRIPTION: D Cannot clone the default dm_value_assist object with object_id %s.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: The parameter is the object id of the dm_value_assist object.

ERROR: [DM_DATA_DICT_F_DOMAIN_TYPE_INIT]

SEVERITY: FATAL
DESCRIPTION: S Failed to initialize type %s.
CAUSE: Unknown.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_DATA_DICT_F_VALUE_QUERY_TYPE_INIT]

SEVERITY: FATAL
DESCRIPTION: S Failed to initialize type %s.
CAUSE: Unknown.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_DATA_DICT_F_CANNOT_EXPUNGE_AGGR_DOMAIN]

SEVERITY: FATAL
DESCRIPTION: D Cannot expunge the dm_aggr_domain object with object id %s.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: The parameter is the object id of the dm_aggr_domain object.

ERROR: [DM_DATA_DICT_F_CANNOT_FETCH_KEY]

SEVERITY: FATAL
DESCRIPTION: D The key specified with object id %s does not exist.
CAUSE: No dm_key object exists with the given id.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: The parameter is the object id.

ERROR: [DM_DATA_DICT_F_STORE_STATE_OVERRIDE_FAILED]

SEVERITY: FATAL
DESCRIPTION: DS Could not set the override_id while updating the type for business policy id %s, state %s.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: The parameter is the object id of the dm_aggr_domain object.

ERROR: [DM_DATA_DICT_F_DISPLAY_CONFIG_TYPE_INIT]

SEVERITY: FATAL
DESCRIPTION: S Failed to initialize type %s.
CAUSE: Unknown.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_DATA_DICT_F_CANNOT_FETCH_DD_INFO_FOR_ATTRIBUTE]

SEVERITY: FATAL
DESCRIPTION: DSS Cannot fetch the dm_dd_info object with id %s for attribute %s of type %s.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: The first parameter is the object id of the dm_dd_info object. The second parameter is the name of the attribute. The third parameter is the name of the type.

ERROR: [DM_DATA_DICT_F_DD_INFO_BAD_VSTAMP]

SEVERITY: FATAL
DESCRIPTION: II Type dm_dd_info has a bad vstamp %d. The current vstamp for dm_dd_info is supposed to be %d.
CAUSE: The RDBMS table has a bad vstamp.
ACTION: Report this error to Documentum sysadmins.
PARAMS:

ERROR: [DM_DATA_DICT_F_DD_COMMON_INFO_BAD_VSTAMP]

SEVERITY: FATAL
DESCRIPTION: II Type dmi_dd_common_info has a bad vstamp %d. The current vstamp for dmi_dd_common_info is supposed to be %d.
CAUSE: The RDBMS table has a bad vstamp.
ACTION: Report this error to Documentum sysadmins.
PARAMS: The first parameter is the current vstamp The second parameter is what the stamp should be.

ERROR: [DM_DATA_DICT_F_SCOPE_CONFIG_TYPE_INIT]

SEVERITY: FATAL
DESCRIPTION: S Failed to initialize type %s.
CAUSE: Unknown.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_DATA_DICT_F_FOREIGN_KEY_BAD_VSTAMP]

SEVERITY: FATAL
DESCRIPTION: II Type dm_foreign_key has a bad vstamp %d. The current vstamp for dm_foreign_key is supposed to be %d.
CAUSE: The RDBMS table has a bad vstamp.
ACTION: Report this error to Documentum sysadmins.
PARAMS:

ERROR: [DM_DATA_DICT_F_KEY_TYPE_INIT]

SEVERITY: FATAL
DESCRIPTION: S Failed to initialize type %s.
CAUSE: Unknown.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_DATA_DICT_F_CANNOT_EXPUNGE_DEFAULT_COMPUTED_EXPRESSION]

SEVERITY: FATAL
DESCRIPTION: D Cannot expunge the default computed expression with object id %s.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: The parameter is the object id of the dm_expression object.

ERROR: [DM_DATA_DICT_F_VALUE_LIST_TYPE_INIT]

SEVERITY: FATAL
DESCRIPTION: S Failed to initialize type %s.
CAUSE: Unknown.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_DATA_DICT_F_ABORT_FAILURE]

SEVERITY: FATAL
DESCRIPTION: S Could not set the transaction state to ABORT while updating type %s.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: The parameter is the object id of the dm_aggr_domain object.

ERROR: [DM_DATA_DICT_F_CLONE_FOREIGN_KEY]

SEVERITY: FATAL
DESCRIPTION: D Attempt to clone a foreign key for the dm_dd_info object with object id %s.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: The parameter is the object id of the dm_dd_info object.

ERROR: [DM_DATA_DICT_F_AGGR_DOMAIN_NO_TYPE_INFO]

SEVERITY: FATAL
DESCRIPTION: DD Could not fetch the type info object with object id %s for the aggregate domain with object id %s.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: The first parameter is the object id of the dmi_type_info object that could not be fetched. The second parameter is the object id of the aggregate domain object.

ERROR: [DM_DATA_DICT_F_CANNOT_FETCH_DD_OBJECT_FOR_OVERRIDE]

SEVERITY: FATAL
DESCRIPTION: D Cannot fetch the object with id %s during an override operation.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: The parameter is the id of the object.

ERROR: [DM_DATA_DICT_F_CLONE_UNIQUE_KEY]

SEVERITY: FATAL
DESCRIPTION: D Attempt to clone a unique key for the dm_dd_info object with object id %s.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: The parameter is the object id of the dm_dd_info object.

ERROR: [DM_DATA_DICT_F_NLS_DD_INFO_BAD_VSTAMP]

SEVERITY: FATAL
DESCRIPTION: II Type dm_nls_dd_info has a bad vstamp %d. The current vstamp for dm_nls_dd_info is supposed to be %d.
CAUSE: The RDBMS table has a bad vstamp.
ACTION: Report this error to Documentum sysadmins.
PARAMS:

ERROR: [DM_DATA_DICT_F_AGGR_DOMAIN_TYPE_INIT]

SEVERITY: FATAL
DESCRIPTION: S Failed to initialize type %s.
CAUSE: Unknown.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_DATA_DICT_F_COMMIT_FAILURE]

SEVERITY: FATAL
DESCRIPTION: S Could not commit Data Dictionary updates for type %s.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: The parameter is the object id of the dm_aggr_domain object.

ERROR: [DM_DATA_DICT_F_CANNOT_EXPUNGE_PRIMARY_KEY]

SEVERITY: FATAL
DESCRIPTION: D Cannot expunge the primary key with object id %s.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: The parameter is the object id of the dm_unique_key object.

ERROR: [DM_DATA_DICT_F_CANNOT_GET_TYPE_INFO_FOR_TYPE]

SEVERITY: FATAL
DESCRIPTION: S Cannot get the type info object for type %s.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: The parameter is the name of the type.

ERROR: [DM_DATA_DICT_F_DD_ATTR_INFO_BAD_VSTAMP]

SEVERITY: FATAL
DESCRIPTION: II Type dmi_dd_attr_info has a bad vstamp %d. The current vstamp for dmi_dd_attr_info is supposed to be %d.
CAUSE: The RDBMS table has a bad vstamp.
ACTION: Report this error to Documentum sysadmins.
PARAMS: The first parameter is the current vstamp The second parameter is what the stamp should be.

ERROR: [DM_DATA_DICT_F_CANNOT_CLONE_COMPUTED_EXPRESSION]

SEVERITY: FATAL
DESCRIPTION: D Cannot clone the computed dm_expression object with object id %s.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: The parameter is the object id of the dm_expression object.

ERROR: [DM_DATA_DICT_F_CANNOT_GET_NLS_DD_INFO_TYPE]

SEVERITY: FATAL
DESCRIPTION: Could not get the dm_nls_dd_info type.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: None.

ERROR: [DM_DATA_DICT_F_TYPE_UNDO_FAILURE]

SEVERITY: FATAL
DESCRIPTION: S Could not undo type updates for type %s.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: The parameter is the object id of the dm_aggr_domain object.

ERROR: [DM_DATA_DICT_F_NLS_DD_INFO_TYPE_INIT]

SEVERITY: FATAL
DESCRIPTION: S Failed to initialize type %s.
CAUSE: Unknown.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_DATA_DICT_F_VALUE_FUNC_BAD_VSTAMP]

SEVERITY: FATAL
DESCRIPTION: II Type dm_value_func has a bad vstamp %d. The current vstamp for dm_value_func is supposed to be %d.
CAUSE: The RDBMS table has a bad vstamp.
ACTION: Report this error to Documentum sysadmins.
PARAMS:

ERROR: [DM_DATA_DICT_F_GET_ATTR_TYPE_FAILURE]

SEVERITY: FATAL
DESCRIPTION: SS Cannot get attribute type for type %s attribute %s.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: The first parameter is the name of the type. The second parameter is the name of the attribute.

ERROR: [DM_DATA_DICT_F_CANNOT_EXPUNGE_VALUE_ASSIST]

SEVERITY: FATAL
DESCRIPTION: DI Cannot expunge the value assistance with object id %s at position %d.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: The first parameter is the object id of the dm_value_assist object. The second parameter is the (zero-based) position of the value assistance.

ERROR: [DM_DATA_DICT_F_EXPR_CODE_BAD_VSTAMP]

SEVERITY: FATAL
DESCRIPTION: II Type dmi_expr_code has a bad vstamp %d. The current vstamp for dmi_expr_code is supposed to be %d.
CAUSE: The RDBMS table has a bad vstamp.
ACTION: Report this error to Documentum sysadmins.
PARAMS:

ERROR: [DM_DATA_DICT_F_CANNOT_FETCH_NLS_DD_INFO_FOR_ATTRIBUTE]

SEVERITY: FATAL
DESCRIPTION: DSS Cannot fetch the dm_nls_dd_info object with id %s for attribute %s of type %s.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: The first parameter is the object id of the dm_nls_dd_info object. The second parameter is the name of the attribute. The third parameter is the name of the type.

ERROR: [DM_DATA_DICT_F_CANNOT_CLONE_DOMAIN_FOR_ATTR]

SEVERITY: FATAL
DESCRIPTION: S Cannot clone the domain object for attribute %s.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: The parameter is the name of the attribute associated with the domain.

ERROR: [DM_DATA_DICT_F_CLONE_PRIMARY_KEY]

SEVERITY: FATAL
DESCRIPTION: D Attempt to clone a primary key for the dm_dd_info object with object id %s.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: The parameter is the object id of the dm_dd_info object.

ERROR: [DM_DATA_DICT_F_CANNOT_FETCH_DD_INFO_FOR_TYPE]

SEVERITY: FATAL
DESCRIPTION: DS Cannot fetch the dm_dd_info object with id %s for type %s.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: The first parameter is the object id of the dm_dd_info object. The second parameter is the name of the type.

ERROR: [DM_DATA_DICT_F_AGGR_DOMAIN_BAD_VSTAMP]

SEVERITY: FATAL
DESCRIPTION: II Type dm_aggr_domain has a bad vstamp %d. The current vstamp for dm_aggr_domain is supposed to be %d.
CAUSE: The RDBMS table has a bad vstamp.
ACTION: Report this error to Documentum sysadmins.
PARAMS:

ERROR: [DM_DATA_DICT_F_VALUE_LIST_BAD_VSTAMP]

SEVERITY: FATAL
DESCRIPTION: II Type dm_value_list has a bad vstamp %d. The current vstamp for dm_value_list is supposed to be %d.
CAUSE: The RDBMS table has a bad vstamp.
ACTION: Report this error to Documentum sysadmins.
PARAMS:

ERROR: [DM_DATA_DICT_F_CANNOT_EXPUNGE_DEFAULT_VALUE_ASSIST]

SEVERITY: FATAL
DESCRIPTION: D Cannot expunge the default value assistance with object id %s.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: The parameter is the object id of the dm_value_assist object.

ERROR: [DM_DATA_DICT_F_CANNOT_EXPUNGE_COND_VALUE_ASSIST]

SEVERITY: FATAL
DESCRIPTION: D Cannot expunge the cond value assist expression with object id %s.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: The parameter is the object id of the dm_cond_id_expr object.

ERROR: [DM_DATA_DICT_F_BAD_PRIMITIVE_TYPE_CODE]

SEVERITY: FATAL
DESCRIPTION: I Unknown primitive type code: (%d).
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: The parameter is the internal primitive type code.

ERROR: [DM_DATA_DICT_F_AGGR_DOMAIN_BAD_ATTR_LISTS]

SEVERITY: FATAL
DESCRIPTION: III The attribute lists lengths for the aggregate domain are corrupted. Attr_name has %d values, attr_domain_name has %d values, and attr_domain_id has %d values.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: The first parameter is the number of overridden attribute names. The second parameter is the number of corresponding domain names. The third parameter is the number of corresponding domain object ids.

ERROR: [DM_DATA_DICT_F_CANNOT_EXPUNGE_NLS_DD_INFO]

SEVERITY: FATAL
DESCRIPTION: D Cannot expunge the dm_nls_dd_info object with object id %s.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: The parameter is the object id of the dm_nls_dd_info object.

ERROR: [DM_DATA_DICT_F_CANNOT_FETCH_AGGR_DOMAIN_FOR_TYPE]

SEVERITY: FATAL
DESCRIPTION: DS Cannot fetch the aggregate domain with object id %s for type %s.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: The first parameter is the object id of the aggregate domain object. The second parameter is the name of the type.

ERROR: [DM_DATA_DICT_F_CANNOT_EXPUNGE_VAL_CONSTRAINT]

SEVERITY: FATAL
DESCRIPTION: DI Cannot expunge the val_constraint expression with object id %s at position %d.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: The first parameter is the object id of the dm_expression object. The second parameter is the (zero-based) position of the expression.

ERROR: [DM_DATA_DICT_F_CANNOT_EXPUNGE_DD_INFO]

SEVERITY: FATAL
DESCRIPTION: D Cannot expunge the dm_dd_info object with object id %s.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: The parameter is the object id of the dm_dd_info object.

ERROR: [DM_DATA_DICT_F_CANNOT_GET_DD_INFO_TYPE]

SEVERITY: FATAL
DESCRIPTION: Could not get the dm_dd_info type.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: None.

ERROR: [DM_DATA_DICT_F_NO_ATTRIBUTE_INFO_FOR_NAME]

SEVERITY: FATAL
DESCRIPTION: SS The Data Dictionary has no information for attribute %s of Data Dictionary type %s.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: The first parameter is the name of the Data Dictionary attribute. The second parameter is the name of the Data Dictionary type.

ERROR: [DM_DATA_DICT_F_NULL_GENERATED_SOURCE_FILE]

SEVERITY: FATAL
DESCRIPTION: The generated_source_file pointer for an aggr domain object is NULL.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: None.

ERROR: [DM_DATA_DICT_F_NULL_DOMAIN_ID_FOR_ATTRIBUTE]

SEVERITY: FATAL
DESCRIPTION: SS The domain id for attribute %s of type %s is NULL.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: The first parameter is the name of the attribute. The second parameter is the name of the type.

ERROR: [DM_DATA_DICT_F_AGGR_DOMAIN_NULL_CODE_OBJECT_ID]

SEVERITY: FATAL
DESCRIPTION: The object id of the code object is NULL.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: None.

ERROR: [DM_DATA_DICT_F_DD_TYPE_INFO_BAD_VSTAMP]

SEVERITY: FATAL
DESCRIPTION: II Type dmi_dd_type_info has a bad vstamp %d. The current vstamp for dmi_dd_type_info is supposed to be %d.
CAUSE: The RDBMS table has a bad vstamp.
ACTION: Report this error to Documentum sysadmins.
PARAMS: The first parameter is the current vstamp The second parameter is what the stamp should be.

ERROR: [DM_DATA_DICT_F_UNIQUE_KEY_TYPE_INIT]

SEVERITY: FATAL
DESCRIPTION: S Failed to initialize type %s.
CAUSE: Unknown.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_DATA_DICT_F_CANNOT_CLONE_VAL_CONSTRAINT]

SEVERITY: FATAL
DESCRIPTION: D Cannot clone the validation constraint dm_expression object with object id %s.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: The parameter is the object id of the dm_expression object.

ERROR: [DM_DATA_DICT_F_CANNOT_EXPUNGE_UNIQUE_KEY]

SEVERITY: FATAL
DESCRIPTION: DI Cannot expunge the unique key with object id %s at position %d.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: The first parameter is the object id of the dm_unique_key object. The second parameter is the (zero-based) position of the expression.

ERROR: [DM_DATA_DICT_F_CANNOT_FETCH_DD_INFO]

SEVERITY: FATAL
DESCRIPTION: Could not fetch a dm_dd_info object.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: None.

ERROR: [DM_DATA_DICT_F_BAD_POLICY_ID_AND_VERSION]

SEVERITY: FATAL
DESCRIPTION: DS Bad default policy id (%s) and version label (%s) combination.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: The first parameter is the object id of the default business policy. The second parameter is the version label of the policy.

ERROR: [DM_DATA_DICT_F_CANNOT_EXPUNGE_CODE_OBJECT_FOR_ATTR_DOMAIN]

SEVERITY: FATAL
DESCRIPTION: D Cannot expunge the dmi_expr_code object with object id %s.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: The parameter is the object id of the dmi_expr_code object.

ERROR: [DM_DATA_DICT_F_UNIQUE_KEY_BAD_VSTAMP]

SEVERITY: FATAL
DESCRIPTION: II Type dm_unique_key has a bad vstamp %d. The current vstamp for dm_unique_key is supposed to be %d.
CAUSE: The RDBMS table has a bad vstamp.
ACTION: Report this error to Documentum sysadmins.
PARAMS:

ERROR: [DM_DATA_DICT_F_SET_NULL_UPDATE_BAD_TYPE]

SEVERITY: FATAL
DESCRIPTION: SI Update NULL for attribute %s using unknown primitive type code (%d).
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: The first parameter is the name of the attribute. The second parameter is the internal primitive type code.

ERROR: [DM_DATA_DICT_F_CANNOT_GET_OBJECT_MANAGER]

SEVERITY: FATAL
DESCRIPTION: Could not get Persistent Object Manager.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: None.

ERROR: [DM_DATA_DICT_F_VALUE_FUNC_TYPE_INIT]

SEVERITY: FATAL
DESCRIPTION: S Failed to initialize type %s.
CAUSE: Unknown.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_DATA_DICT_F_SYNCHRONIZE_WITH_TYPE_FAILED]

SEVERITY: FATAL
DESCRIPTION: DS Failure synchronizing dm_aggr_domain %s with type %s.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: The first parameter is the name of the type. The second parameter is the name of the attribute.

ERROR: [DM_DATA_DICT_F_DD_INFO_TYPE_INIT]

SEVERITY: FATAL
DESCRIPTION: S Failed to initialize type %s.
CAUSE: Unknown.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_DATA_DICT_F_SCOPE_CONFIG_BAD_VSTAMP]

SEVERITY: FATAL
DESCRIPTION: II Type dm_scope_config has a bad vstamp %d. The current vstamp for dm_scope_config is supposed to be %d.
CAUSE: The RDBMS table has a bad vstamp.
ACTION: Report this error to Documentum sysadmins.
PARAMS:

ERROR: [DM_DATA_DICT_F_CANNOT_EXPUNGE_COND_COMPUTED_EXPR]

SEVERITY: FATAL
DESCRIPTION: D Cannot expunge the cond computed expr expression with object id %s.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: The parameter is the object id of the dm_cond_id_expr object.

ERROR: [DM_DATA_DICT_F_CANNOT_FETCH_DD_FOLDER]

SEVERITY: FATAL
DESCRIPTION: SD Cannot fetch the Data Dictionary system folder %s with ID %s.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: The first parameter is the folder path of the Data Dictionary folder. The second parameter is the object id of the Data Dictionary folder.

ERROR: [DM_DATA_DICT_F_CANNOT_GET_GLOBAL_CONTEXT]

SEVERITY: FATAL
DESCRIPTION: Could not get Global Context Object.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: None.

ERROR: [DM_DATA_DICT_F_MISSING_VALUE_ASSIST_PARENT_ID]

SEVERITY: FATAL
DESCRIPTION: D Value assistance object %s has no parent_id set.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: The parameter is the object id of the value assistance object.

ERROR: [DM_DATA_DICT_F_CANNOT_EXPUNGE_FOREIGN_KEY]

SEVERITY: FATAL
DESCRIPTION: DI Cannot expunge the foreign key with object id %s at position %d.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: The first parameter is the object id of the dm_foreign_key object. The second parameter is the (zero-based) position of the expression.

ERROR: [DM_DATA_DICT_F_VALUE_ASSIST_BAD_VSTAMP]

SEVERITY: FATAL
DESCRIPTION: II Type dm_value_assist has a bad vstamp %d. The current vstamp for dm_value_assist is supposed to be %d.
CAUSE: The RDBMS table has a bad vstamp.
ACTION: Report this error to Documentum sysadmins.
PARAMS:

ERROR: [DM_DATA_DICT_F_CANT_FETCH_DOMAIN]

SEVERITY: FATAL
DESCRIPTION: DS Cannot fetch the domain object with object id %s for attribute %s
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: The first parameter is the object id of the domain that could not be fetched. The second parameter is the name of the corresponding attribute.

ERROR: [DM_DATA_DICT_F_CANNOT_FETCH_NLS_DD_INFO_FOR_TYPE]

SEVERITY: FATAL
DESCRIPTION: DS Cannot fetch the dm_nls_dd_info object with id %s for type %s.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: The first parameter is the object id of the dm_nls_dd_info object. The second parameter is the name of the type.

ERROR: [DM_DATA_DICT_F_SAVE_FAILED_AFTER_SYNCHRONIZE]

SEVERITY: FATAL
DESCRIPTION: DS Failure saving after synchronizing dm_aggr_domain %s with type %s.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: The first parameter is the name of the type. The second parameter is the name of the attribute.

ERROR: [DM_DATA_DICT_F_AGGR_DOMAIN_WRONG_NUMBER_CODE_OBJECTS]

SEVERITY: FATAL
DESCRIPTION: II There should be %d code object(s) for this aggregate domain, found %d.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: The first parameter is the number of code objects expected. The second parameter is the number of code objects found.

ERROR: [DM_DATA_DICT_F_KEY_BAD_VSTAMP]

SEVERITY: FATAL
DESCRIPTION: II Type dm_key has a bad vstamp %d. The current vstamp for dm_key is supposed to be %d.
CAUSE: The RDBMS table has a bad vstamp.
ACTION: Report this error to Documentum sysadmins.
PARAMS:

ERROR: [DM_DATA_DICT_F_DOMAIN_BAD_VSTAMP]

SEVERITY: FATAL
DESCRIPTION: II Type dm_domain has a bad vstamp %d. The current vstamp for dm_domain is supposed to be %d.
CAUSE: The RDBMS table has a bad vstamp.
ACTION: Report this error to Documentum sysadmins.
PARAMS:

ERROR: [DM_DATA_DICT_F_AGGR_DOMAIN_EDIT_TYPE_NOT_SET]

SEVERITY: FATAL
DESCRIPTION: D The internal pointer to the type being edited is not set in dm_aggr_domain %s.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: The parameter is the object id of the dm_aggr_domain object.

ERROR: [DM_DATA_DICT_F_DD_ATTR_INFO_TYPE_INIT]

SEVERITY: FATAL
DESCRIPTION: S Failed to initialize type %s.
CAUSE: Unknown.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS: The parameter is the type name

ERROR: [DM_DATA_DICT_F_CANNOT_CLONE_DOMAIN]

SEVERITY: FATAL
DESCRIPTION: D Cannot clone the dm_domain object with object id %s.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: The parameter is the object id of the dm_domain object.

ERROR: [DM_DATA_DICT_F_AGGR_DOMAIN_BAD_ATTR_TYPE]

SEVERITY: FATAL
DESCRIPTION: SS Cannot get attribute type for attribute %s of type %s.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: The first parameter is the name of the attribute. The second parameter is the name of object type.

ERROR: [DM_DATA_DICT_F_CANNOT_FETCH_DOMAIN_FOR_ATTRIBUTE]

SEVERITY: FATAL
DESCRIPTION: DSS Cannot fetch the dm_domain object with object id %s for attribute %s of type %s.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: The first parameter is the object id of the domain object. The second parameter is the name of the attribute. The third parameter is the name of the type.

ERROR: [DM_DATA_DICT_F_CANNOT_CLONE_DEFAULT_VALUE]

SEVERITY: FATAL
DESCRIPTION: D Cannot clone the default value dm_expresion object with object id %s.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: The parameter is the object id of the dm_expression object.

ERROR: [DM_DATA_DICT_F_CANNOT_GET_DOCBASE_DATA]

SEVERITY: FATAL
DESCRIPTION: Could not get Docbase Data Object.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: None.

ERROR: [DM_DATA_DICT_F_CANNOT_FIND_DD_FOLDER]

SEVERITY: FATAL
DESCRIPTION: S Cannot find the Data Dictionary system folder %s.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: The first parameter is the folder path of the Data Dictionary folder.

ERROR: [DM_DATA_DICT_F_NULL_AGGR_DOMAIN_POINTER]

SEVERITY: FATAL
DESCRIPTION: The aggr_domain pointer for a domain object is NULL.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: None.

ERROR: [DM_DATA_DICT_F_AGGR_DOMAIN_CANNOT_FETCH_CODE_OBJECT]

SEVERITY: FATAL
DESCRIPTION: D Cannot fetch the expression code SysObject with object id %s.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: The parameter is the object id of the code object that cannot be fetched.

ERROR: [DM_DATA_DICT_F_UNEXPECTED_ATTRIBUTE_TYPE]

SEVERITY: FATAL
DESCRIPTION: SI Attribute %s has an unexpected data type (%d).
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: The first parameter is the name of the Data Dictionary attribute. The second parameter is the internal type code.

ERROR: [DM_DATA_DICT_F_UNEXPECTED_DOMAIN_ID_IN_ATTR_DOMAIN_ID_LIST]

SEVERITY: FATAL
DESCRIPTION: DSD For aggr domain %s, the attr_domain_id for attribute %s was found to be %s.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: The parameter is the name of the attribute associated with the domain.

ERROR: [DM_DATA_DICT_F_CANNOT_FETCH_FOREIGN_KEY]

SEVERITY: FATAL
DESCRIPTION: D The foreign key specified with object id %s does not exist.
CAUSE: No dm_foreign_key object exists with the given id.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: The parameter is the object id.

ERROR: [DM_DATA_DICT_F_CANNOT_EXPUNGE_DISPLAY_CONFIG]

SEVERITY: FATAL
DESCRIPTION: DI Cannot expunge the dm_display_config object with object id %s at position %d.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: The first parameter is the object id of the dm_display_config object. The second parameter is the (zero-based) position of the display_config attribute.

ERROR: [DM_DATA_DICT_F_STORE_OVERRIDE_FAILED]

SEVERITY: FATAL
DESCRIPTION: S Could not set the override_id while updating type %s.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: The parameter is the object id of the dm_aggr_domain object.

ERROR: [DM_DATA_DICT_F_CANNOT_FETCH_NLS_DD_INFO]

SEVERITY: FATAL
DESCRIPTION: Could not fetch a dm_nls_dd_info object.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: None.

ERROR: [DM_DATA_DICT_F_INCONSISTENT_CODE_OBJECT]

SEVERITY: FATAL
DESCRIPTION: D The code object pointer for dm_aggr_domain %s is inconsistent.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representative.
PARAMS: The parameter is the object id of the dm_aggr_domain object.

ERROR: [DM_DATA_DICT_E_CANNOT_MODIFY_THIS_ATTR]

SEVERITY: ERROR
DESCRIPTION: S The attribute %s cannot be modified.
CAUSE: An attribute was specified in a Data Dictionary update modifier that is not user-modifiable.
ACTION: Do not attempt to modify this attribute.
PARAMS: The parameter is the attribute name.

ERROR: [DM_DATA_DICT_E_BAD_TYPE_FOR_KEY]

SEVERITY: ERROR
DESCRIPTION: SD The type_name (%s) specified for key %s is not a valid type name.
CAUSE: The type_name for a dm_key or dm_foreign_key object is not the name of a valid type.
ACTION: Use a valid type name.
PARAMS: The first parameter is the name of the type. The second parameter is the object id of the key object.

ERROR: [DM_DATA_DICT_E_REMOVE_UPDATE_FAILED]

SEVERITY: ERROR
DESCRIPTION: SI Could not REMOVE from attribute %s at position %d.
CAUSE: An attempt to REMOVE from the given attribute at the given position failed.
ACTION: Specify a legal attribute, value and position.
PARAMS: The first parameter is the attribute name. The second parameter is the position index.

ERROR: [DM_DATA_DICT_E_DD_HANDLE_STATE_NAME_TOO_LONG]

SEVERITY: ERROR
DESCRIPTION: S The business policy state name portion of the Data Dictionary handle %s is too long.
CAUSE: The business policy state named in the data dictionary handle is too long.
ACTION: Use a valid state name for the given business policy.
PARAMS: The parameter is the Data Dictionary handle.

ERROR: [DM_DATA_DICT_E_SINGLE_AND_REPEATING_IN_KEY]

SEVERITY: ERROR
DESCRIPTION: DSSS The key with object id %s for type %s contains at least one single-valued attribute (%s) and at least one repeating attribute (%s).
CAUSE: You have attempted to define a unique, foreign, or primary key containing a mixture of single-valued and repeating attributes.
ACTION: You may not mix the two in any key.
PARAMS: The first parameter is the object id of the key object. The second parameter is the name of the type that defines the attributes. The third parameter is the name of a single-valued attribute in the key. The fourth parameter is the name of a repeating attribute in the key.

ERROR: [DM_DATA_DICT_E_NO_DB_CONNECTION]

SEVERITY: ERROR
DESCRIPTION: S There was no database connection passed %s
CAUSE: The database connection parameter was not passed to the function.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS: The function which the missing database connection was detected.

ERROR: [DM_DATA_DICT_E_INSERT_UPDATE_FAILED]

SEVERITY: ERROR
DESCRIPTION: SI Could not INSERT into attribute %s at position %d.
CAUSE: An attempt to INSERT into the given attribute at the given position failed.
ACTION: Specify a legal attribute, value and position.
PARAMS: The first parameter is the attribute name. The second parameter is the position index.

ERROR: [DM_DATA_DICT_E_NAMED_DOMAIN_NOT_SUPPORTED]

SEVERITY: ERROR
DESCRIPTION: S Named domain objects are not supported. The name of the domain is %s.
CAUSE: A domain was encountered that had its domain_name attribute set.
ACTION: Only anonymous (un-named) domains are currently supported.
PARAMS: The parameter is the name of the domain.

ERROR: [DM_DATA_DICT_E_DD_INFO_CANT_FETCH]

SEVERITY: ERROR
DESCRIPTION: D Cannot fetch – Invalid object ID %s.
CAUSE: Could not fetch an object with the given id.
ACTION: This is probably caused by a bad ID. Or, possibly, a connection to the Documentum server could not be established.
PARAMS:

ERROR: [DM_DATA_DICT_E_CURSOR_ERROR]

SEVERITY: ERROR
DESCRIPTION: S A database error has occurred during the creation of a cursor (%s).
CAUSE: A SQL statement that queries the Documentum schema has failed. This error message indicates that a failure occurred during the parsing of the generated SQL statement by the underlying RDBMS.
ACTION: The error message from the RDBMS is shown in the message. Use that error message to figure out what has happened.
PARAMS: The parameter contains the text of the error message generated by the RDBMS.

ERROR: [DM_DATA_DICT_E_INVALID_SCOPE_CONFIG]

SEVERITY: ERROR
DESCRIPTION: D The dm_scope_config object with ID %s is invalid. See additional error messages for details.
CAUSE: The dm_scope_config object is invalid
ACTION: Look at the additional error messages reported for more information
PARAMS: The first parameter is the object id of the dm_scope_config object.

ERROR: [DM_DATA_DICT_E_CANT_CREATE_EXPR_CODE_TEMP_FILE]

SEVERITY: ERROR
DESCRIPTION: S The following error occurred trying to create a temporary file for expression code: %s.
CAUSE: A file error occurred trying to create the temporary file used to hold generated expression code.
ACTION: This depends on the file error code provided.
PARAMS: The parameter is the file error message.

ERROR: [DM_DATA_DICT_E_UPDATE_BOOLEAN_NULL]

SEVERITY: ERROR
DESCRIPTION: SI An attempt was made to update the BOOLEAN attribute %s with the value %d (currently used as a NULL marker) which will cause the parents value to be inherited. If this is desired use the keyword NULL.
CAUSE: An update was attempted directly using the NULL Boolean value.
ACTION: Use the keyword NULL.
PARAMS: The first parameter is the name of the BOOLEAN attribute being updated. The second parameter is the value used.

ERROR: [DM_DATA_DICT_E_MARK_PUBLISH_IN_PROGRESS]

SEVERITY: ERROR
DESCRIPTION: SS The server was trying to update the publish_in_progress flag for an entry of %s with locale %s in the dd_publish_log and failed.
CAUSE: Unknown.
ACTION: Go to the database and execute the statement: — SELECT * FROM dd_publish_log where publish_in_progress = 1 — If the row return corresponds to the entry in the error log, the command has succeeded. Please contact your Documentum site representative.
PARAMS: The first parameter is the dmDDHandle. This contains the type name, the attribute name, business policy and state name. The second parameter is the nls_key (the locale of the data dictionary information)

ERROR: [DM_DATA_DICT_E_DUPLICATE_VALUE_LIST_ENTRY]

SEVERITY: ERROR
DESCRIPTION: SII The list value assistance contains the value %s at position %d and at position %d.
CAUSE: A duplicate value was supplied in list value assistance.
ACTION: Remove one of the duplicates.
PARAMS: The first parameter is the duplicated value. The second parameter is the position of the first occurrence. The second parameter is the position of the second occurrence.

ERROR: [DM_DATA_DICT_E_EXPR_CODE_TEMP_FILE_WRITE_ERROR]

SEVERITY: ERROR
DESCRIPTION: S The following error occurred while writing to a temporary file for expression code: %s.
CAUSE: A file I/O error occurred trying to write the temporary file used to hold generated expression code.
ACTION: This depends on the file error code provided.
PARAMS: The parameter is the file I/O error message.

ERROR: [DM_DATA_DICT_E_DUPLICATE_SEARCH_OP_VALUE]

SEVERITY: ERROR
DESCRIPTION: SIII The search operator attribute %s contains the value %d at position %d and at position %d.
CAUSE: The search operator contains duplicate values.
ACTION: Remove one of the duplicates.
PARAMS: The first parameter is the attribute name. The second parameter is the duplicated value. The third parameter is the repeating attribute index of the first occurrence. The fourth parameter is the repeating attribute index of the second occurrence.

ERROR: [DM_DATA_DICT_E_COMPUTING_DEPENDENCIES_IN_DATA_DICTIONARY_LOG]

SEVERITY: ERROR
DESCRIPTION: SS An error occured while adding entries to the data dictionary log table named dd_publish_log. Information was being added relating to %s with locale %s
CAUSE: Unknown. The server was inserting the subtypes of the aforementioned type and attribute combination to the log but failed.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS: The first parameter is the dmDDHandle. This contains the type name, the attribute name, business policy and state name. The second parameter is the nls_key (the locale of the data dictionary information)

ERROR: [DM_DATA_DICT_E_DD_HANDLE_TYPE_NAME_MISSING]

SEVERITY: ERROR
DESCRIPTION: S The type name portion of the Data Dictionary handle %s is missing.
CAUSE: The type named in the data dictionary handle is missing.
ACTION: Use a valid type name.
PARAMS: The parameter is the Data Dictionary handle.

ERROR: [DM_DATA_DICT_E_BAD_BOOLEAN_VALUE]

SEVERITY: ERROR
DESCRIPTION: S The value %s is not a valid BOOLEAN value (must be TRUE (1) or FALSE (0)).
CAUSE: A non-Boolean value was specified in a context where a Boolean is required.
ACTION: Specify a legal Boolean value (TRUE (1) or FALSE (0)).
PARAMS: The parameter is the value.

ERROR: [DM_DATA_DICT_E_MIXED_ATTR_LEVELS_FOR_KEY]

SEVERITY: ERROR
DESCRIPTION: DSSS The key (%s) for type %s references some attributes defined in type %s and some attributes defined in type %s.
CAUSE: The dm_key or dm_foreign_key references attributes that are defined in different types.
ACTION: All of the attribute names must be defined at the same level in the type hierarchy.
PARAMS: The first parameter is the object id of the key object. The second parameter is the name of the type. The third parameter is the type defining part of the attribute names. The forth parameter is the type defining the rest of the attribute names.

ERROR: [DM_DATA_DICT_E_CANNOT_FETCH_POLICY]

SEVERITY: ERROR
DESCRIPTION: D The business policy specified with object id %s does not exist.
CAUSE: No dm_policy object exists with the given id.
ACTION: Specify the id of a business policy object.
PARAMS: The parameter is the object id.

ERROR: [DM_DATA_DICT_E_OVERRIDE_UNKNOWN_ATTR]

SEVERITY: ERROR
DESCRIPTION: S The attribute %s does not exist in the Data Dictionary.
CAUSE: An attempt was made to override an attribute that does not exist in the Data Dictionary.
ACTION: Use the name of the correct Data Dictionary attribute.
PARAMS: The parameter is the name of the attribute.

ERROR: [DM_DATA_DICT_E_UNIQUE_KEY_CANT_FETCH]

SEVERITY: ERROR
DESCRIPTION: D Cannot fetch – Invalid object ID %s.
CAUSE: Could not fetch an object with the given id.
ACTION: This is probably caused by a bad ID. Or, possibly, a connection to the Documentum server could not be established.
PARAMS:

ERROR: [DM_DATA_DICT_E_VALUE_ASSIST_CANT_FETCH]

SEVERITY: ERROR
DESCRIPTION: D Cannot fetch – Invalid object ID %s.
CAUSE: Could not fetch an object with the given id.
ACTION: This is probably caused by a bad ID. Or, possibly, a connection to the Documentum server could not be established.
PARAMS:

ERROR: [DM_DATA_DICT_E_STATE_NAME_TOO_LONG]

SEVERITY: ERROR
DESCRIPTION: SI Business Policy state_name %s is too long. Maximum length is %d.
CAUSE: A state_name was specified that is too long.
ACTION: Shorten the state name.
PARAMS: The first parameter is the name of the state specified. The second parameter is the maximum Data Dictionary state name length.

ERROR: [DM_DATA_DICT_E_BAD_POLICY_ID_TAG]

SEVERITY: ERROR
DESCRIPTION: D The object id specifed for the default business policy %s is not the id of a dm_policy object.
CAUSE: The indicated object id is not the id of a business policy object.
ACTION: Specify the id of a business policy object.
PARAMS: The parameter is the object id.

ERROR: [DM_DATA_DICT_E_INVALID_ATTR_FOR_ATTR_CONSTRAINT_EXPRESSION]

SEVERITY: ERROR
DESCRIPTION: SS A constraint expression for attribute %s references another attribute (%s). Only type level constraints can reference multiple attributes.
CAUSE: A constraint expression specified at the attribute level references other attributes than the attribute for which it was specified.
ACTION: Move the constraint to the type level, or remove the other attributes.
PARAMS: The first parameter is the name of the attribute. The second parameter is the name of the other attribute found.

ERROR: [DM_DATA_DICT_E_DUPLICATE_FOREIGN_KEY]

SEVERITY: ERROR
DESCRIPTION: SS Type %s has multiple foreign keys based on just the attribute %s. One at the type level, and one at the attribute level.
CAUSE: You have specified multiple foreign keys with the single attribute indicated.
ACTION: Remove one of the duplicates.
PARAMS: The first parameter is the name of the type. The second parameter is the name of the offending attribute.

ERROR: [DM_DATA_DICT_E_DD_HANDLE_TYPE_NAME_TOO_LONG]

SEVERITY: ERROR
DESCRIPTION: S The type name portion of the Data Dictionary handle %s is too long.
CAUSE: The type named in the data dictionary handle is too long.
ACTION: Use a valid type name.
PARAMS: The parameter is the Data Dictionary handle.

ERROR: [DM_DATA_DICT_E_CODE_GENERATION_FAILURE]

SEVERITY: ERROR
DESCRIPTION: D Could not generate source or code for the dm_aggr_domain with object id %s.
CAUSE: Source or object code could not be generated for the expressions for the given dm_aggr_domain.
ACTION: Check the syntax and semantic correctness of the expressions.
PARAMS: The parameter is the object id of the dm_aggr_domain object.

ERROR: [DM_DATA_DICT_E_TRUNCATE_UPDATE_FAILED]

SEVERITY: ERROR
DESCRIPTION: SI Could not TRUNCATE attribute %s at position %d.
CAUSE: An attempt to TRUNCATE the given attribute at the given position failed.
ACTION: Specify a legal attribute, value and position.
PARAMS: The first parameter is the attribute name. The second parameter is the position index.

ERROR: [DM_DATA_DICT_E_DOMAIN_UNABLE_TO_NAME_DEFAULT_LOCALE]

SEVERITY: ERROR
DESCRIPTION: S The Data Dictionary encountered an error while trying to name the default locale (nls_key) in the dm_domain objects. The error from the database is %s
CAUSE: The Data Dictionary encountered a database error while trying to name the default locale (nls_key).
ACTION: Refer to the reported database error in order to determine what action should be taken.
PARAMS: The parameter is the error message from the database.

ERROR: [DM_DATA_DICT_E_BAD_DEF_VALUE_LENGTH]

SEVERITY: ERROR
DESCRIPTION: I The value of the def_value_length attribute (%d) must be >= 0.
CAUSE: A negative value was supplied for def_value_length.
ACTION: Supply a legal value.
PARAMS: The parameter is the def_value_length value.

ERROR: [DM_DATA_DICT_E_DD_HANDLE_POLICY_ID_MISSING]

SEVERITY: ERROR
DESCRIPTION: S The policy id portion of the Data Dictionary handle %s is missing.
CAUSE: The policy id in the data dictionary handle is missing.
ACTION: Use a valid business policy id.
PARAMS: The parameter is the Data Dictionary handle.

ERROR: [DM_DATA_DICT_E_BAD_ATTR_FOR_KEY]

SEVERITY: ERROR
DESCRIPTION: DSS The key (%s) for type %s references a non-existent attribute %s.
CAUSE: The dm_key or dm_foreign_key object references an attribute that does not exist for the type.
ACTION: Use a valid attribute.
PARAMS: The first parameter is the object id of the key object. The second parameter is the name of the type. The third parameter is the name of the non-existent attribute.

ERROR: [DM_DATA_DICT_E_EXPRESSION_IS_WRONG_TYPE]

SEVERITY: ERROR
DESCRIPTION: SS Expression or literal is wrong type. Expected %s, found %s.
CAUSE: You have specified an expression or literal of the wrong type.
ACTION: Supply an expression or literal of the expected type.
PARAMS: The first parameter is the expected type. The second parameter is the actual type of the literal or expression.

ERROR: [DM_DATA_DICT_E_DD_HANDLE_POLICY_STATE_NOT_FOUND]

SEVERITY: ERROR
DESCRIPTION: DSS The policy with object id %s named in the Data Dictionary handle %s does not have a state named %s.
CAUSE: The business policy state given in the Data Dictionary handle does not exist.
ACTION: Use a valid business policy state name.
PARAMS: The first parameter is the object id of the business policy. The second parameter is the Data Dictionary handle. The third parameter is the name of the business policy state.

ERROR: [DM_DATA_DICT_E_QUERY_EXECUTION_FAILURE]

SEVERITY: ERROR
DESCRIPTION: SS The Data Dictionary encountered an error while trying to execute the following query: %s. Database error was %s.
CAUSE: Query execution failed.
ACTION: Check the error message from the database in order to determine the cause of the query failure.
PARAMS: The first parameter is the query that was being executed. The second parameter is the resulting error from the database.

ERROR: [DM_DATA_DICT_E_DUPLICATE_COMPONENT_CLASSIFIER]

SEVERITY: ERROR
DESCRIPTION: SII The component classifier %s is duplicated at position %d and position %d.
CAUSE: A component classifier is repeated in the COMPONENTS list.
ACTION: Remove the duplicate.
PARAMS: The first parameter is the duplicated classifier. The second parameter is the (0-based) position of the first occurrence. The third parameter is the (0-based) position of the second occurrence.

ERROR: [DM_DATA_DICT_E_BAD_ATTR_FOR_TYPE]

SEVERITY: ERROR
DESCRIPTION: S The attribute %s can only be supplied for an attribute, not for a type.
CAUSE: The indicated attribute cannot be supplied for a type.
ACTION: Remove the indicated information.
PARAMS: The parameter is the offending Data Dictionary attribute.

ERROR: [DM_DATA_DICT_E_INVALID_TYPE_NAME]

SEVERITY: ERROR
DESCRIPTION: S An invalid type_name %s was specified.
CAUSE: An invalid type_name was specified
ACTION: Correct the type_name and retry the operation.
PARAMS: The parameter contains the name of the type_name that is invalid.

ERROR: [DM_DATA_DICT_E_NAMED_SUPER_DOMAIN_NOT_SUPPORTED]

SEVERITY: ERROR
DESCRIPTION: S Named super domain objects are not supported. The name of the super domain is %s.
CAUSE: A domain was encountered that had a named super domain.
ACTION: Only anonymous (un-named) domains are currently supported.
PARAMS: The parameter is the name of the super domain.

ERROR: [DM_DATA_DICT_E_UPDATE_STATEMENT]

SEVERITY: ERROR
DESCRIPTION: SS The Data Dictionary encountered an error while trying to execute the following query: %s. Database error was %s.
CAUSE: An update query failed.
ACTION: Check the error message from the database in order to determine the cause of the query failure. If the error is a rollback segment or transaction log segment error, the database may not have enough space to rollback the update statement in the case of a failure. In this case, please see your DBA about either freeing space in the rollback segement/transaction log. One may also modify the update statement to limit the number of affected rows. Instead of running a single query which may not be feasible, one can split the update statement to process a fraction of the table, commit the transaction and then continue updating the table piece by piece. Please contact Documentum for details.
PARAMS: The first parameter is the query that was being executed. The second parameter is the resulting error from the database.

ERROR: [DM_DATA_DICT_E_NLS_DD_INFO_CANT_FETCH]

SEVERITY: ERROR
DESCRIPTION: D Cannot fetch – Invalid object ID %s.
CAUSE: Could not fetch an object with the given id.
ACTION: This is probably caused by a bad ID. Or, possibly, a connection to the Documentum server could not be established.
PARAMS:

ERROR: [DM_DATA_DICT_E_BAD_REPEATING_PSEUDO_BOOLEAN_VALUE]

SEVERITY: ERROR
DESCRIPTION: SIIII The value of attribute %s[%d] should be in the range %d to %d, but was %d.
CAUSE: The value is out of range.
ACTION: Supply a value in the indicated range.
PARAMS: The first parameter is the attribute name. The second parameter is the repeating attribute index. The third parameter is the lower range bound. The fourth parameter is the upper range bound. The fifit parameter is the actual value.

ERROR: [DM_DATA_DICT_E_BAD_ENFORCEMENT_VALUE]

SEVERITY: ERROR
DESCRIPTION: SIII The value of attribute %s should be in the range %d to %d, but was %d.
CAUSE: The value is out of range.
ACTION: Supply a value in the indicated range.
PARAMS: The first parameter is the attribute name. The second parameter is the lower range bound. The third parameter is the upper range bound. The fourth parameter is the actual value.

ERROR: [DM_DATA_DICT_E_CANNOT_FETCH_EXPRESSION_OBJECT_FOR_ATTRIBUTE]

SEVERITY: ERROR
DESCRIPTION: DS Cannot fetch the expression with object id %s for attribute %s.
CAUSE: The expression with the given id does not exist.
ACTION: Supply a valid object id.
PARAMS: The first parameter is object id of the expression object. The second parameter is the attribute name.

ERROR: [DM_DATA_DICT_E_MISMATCHED_ATTRIBUTE_VALUES]

SEVERITY: ERROR
DESCRIPTION: SDSS The %s object with ID %s has mismatched attribute value counts for related attributes %s and %s.
CAUSE: The specified attributes are supposed to have a one-to-one mapping, however the attribute value counts are different.
ACTION: Ensure that both attribute values are properly matched up.
PARAMS: The first parameter is the object type. The second parameter is the object ID. The third parameter is the first attribute in the one-to-one mapping The fourth parameter is the second attribute in the one-to-one mapping

ERROR: [DM_DATA_DICT_E_DOMAIN_CANT_FETCH]

SEVERITY: ERROR
DESCRIPTION: D Cannot fetch – Invalid object ID %s.
CAUSE: Could not fetch an object with the given id.
ACTION: This is probably caused by a bad ID. Or, possibly, a connection to the Documentum server could not be established.
PARAMS:

ERROR: [DM_DATA_DICT_E_NAMED_VALUE_ASSISTANCE_NOT_SUPPORTED]

SEVERITY: ERROR
DESCRIPTION: S A value assistance object with an object name of %s was found. Named value assistance objects are not supported.
CAUSE: The value assistance object has an object_name supplied.
ACTION: Remove the object_name.
PARAMS: The parameter is the object_name of the value assistance object.

ERROR: [DM_DATA_DICT_E_SET_UPDATE_FAILED]

SEVERITY: ERROR
DESCRIPTION: SI Could not SET attribute %s at position %d.
CAUSE: An attempt to SET the given attribute at the given position failed.
ACTION: Specify a legal attribute, value and position.
PARAMS: The first parameter is the attribute name. The second parameter is the position index.

ERROR: [DM_DATA_DICT_E_BAD_ID_VALUE]

SEVERITY: ERROR
DESCRIPTION: S The value %s is not a valid ID value.
CAUSE: A non-ID value was specified in a context where an object ID is required.
ACTION: Specify a legal object id.
PARAMS: The parameter is the value.

ERROR: [DM_DATA_DICT_E_REQUIRED_ATTRIBUTE]

SEVERITY: ERROR
DESCRIPTION: SDS The %s object with ID %s must have an value for attribute %s.
CAUSE: The attribute value for the specified attribute is NULL.
ACTION: The specified attribute must be set to a non-NULL value for this type.
PARAMS: The first parameter is the type of the object. The second parameter is the object ID. The third parameter is the name of the required attribute.

ERROR: [DM_DATA_DICT_E_DD_HANDLE_TYPE_NOT_FOUND]

SEVERITY: ERROR
DESCRIPTION: SS The type %s named in the Data Dictionary handle %s does not exist.
CAUSE: The type portion of the Data Dictionary handle names a non-existent type.
ACTION: Use a valid type name.
PARAMS: The first parameter is the name of the type. The second parameter is the Data Dictionary handle.

ERROR: [DM_DATA_DICT_E_BAD_POLICY_LABEL]

SEVERITY: ERROR
DESCRIPTION: DS The business policy specified with object id %s does not have a version with the label %s.
CAUSE: A version label was specified that does not exist for the object.
ACTION: Specify a valid version label.
PARAMS: The first parameter is the object id. The second parameter is the version label.

ERROR: [DM_DATA_DICT_E_DISPLAY_CONFIG_NOT_VALID_FOR_TYPE]

SEVERITY: ERROR
DESCRIPTION: DSS The dm_display_config object with ID %s is not valid for type %s The dm_display_config object can only be associated with %s type or one of its subtypes.
CAUSE: The dm_display_config object is not valid for the given type.
ACTION: Check the attribute_source of the dm_display_config object and ensure that it is either the same as attribute_source or a subtype of attribute_source.
PARAMS: The first parameter is the object id of the dm_display_config object The second parameter is the type that this object was validated against.

ERROR: [DM_DATA_DICT_E_NO_ATTRS_FOR_KEY]

SEVERITY: ERROR
DESCRIPTION: DS The key (%s) for type %s has no attributes.
CAUSE: The dm_key or dm_foreign_key object has an empty key_attributes list.
ACTION: Specify at least one attribute on which to base the key.
PARAMS: The first parameter is the object id of the key object. The second parameter is the name of the type.

ERROR: [DM_DATA_DICT_E_COULD_NOT_SAVE_DATA_DICTIONARY_CHANGES]

SEVERITY: ERROR
DESCRIPTION: SS The server could not save changes to the database tables in a transaction. The data dictionary information being changed was for %s, locale %s
CAUSE: The database tables are corrupted, or they are locked in some way to prevent committing the transaction. For some reason, db changes cannot be committed.
ACTION: Report this message and any parameters to your Documentum site representative. Look at the dmi_dd_common_info_s table in your database to see if information exists about the type you are trying to retrieve. See if there are any locks held, or other transactions running.
PARAMS: The first parameter is the function where the save is occurring. The second parameter is the dmDDHandle. This contains the type name, the attribute name, business policy and state name. The third parameter is the nls_key (the locale of the data dictionary information)

ERROR: [DM_DATA_DICT_E_DISPLAY_CONFIG_CANT_FETCH]

SEVERITY: ERROR
DESCRIPTION: D Cannot fetch – Invalid object ID %s.
CAUSE: Could not fetch an object with the given id.
ACTION: This is probably caused by a bad ID. Or, possibly, a connection to the Documentum server could not be established.
PARAMS:

ERROR: [DM_DATA_DICT_E_DUPLICATE_PRIMARY_KEY]

SEVERITY: ERROR
DESCRIPTION: S Type %s has more than one primary key.
CAUSE: You have specified multiple primary keys for the indicated type.
ACTION: A type cannot specify multiple primary keys.
PARAMS: The parameter is the name of the type.

ERROR: [DM_DATA_DICT_E_SCOPE_CONFIG_NOT_VALID_FOR_TYPE]

SEVERITY: ERROR
DESCRIPTION: DS The dm_scope_config object with ID %s is not valid for type %s. See additional messages for more detail.
CAUSE: The dm_scope_config object is not valid for the given type.
ACTION: Check the additional error messages for more detail.
PARAMS: The first parameter is the object id of the dm_scope_config object The second parameter is the type that this object was validated against.

ERROR: [DM_DATA_DICT_E_FIND_DATA_DICTIONARY_OBJECT_IN_DB]

SEVERITY: ERROR
DESCRIPTION: SSS While trying to retrieve data dictionary information about %s with locale %s, the following database cursor error was returned: %s
CAUSE: Unknown. Perhaps the database tables are locked.
ACTION: Report this message and any parameters to your Documentum site representative. Try to see if you can manually query the dmi_dd_common_info_s, dmi_dd_common_info_r, dmi_dd_type_info_s, dmi_dd_type_info_r, dmi_dd_attr_info_s, or dmi_dd_attr_info_r tables.
PARAMS: The first parameter is the dmDDHandle. This contains the type name, the attribute name, business policy and state name. The second parameter is the nls_key (the locale of the data dictionary information) The third parameter is the error from the database cursor.

ERROR: [DM_DATA_DICT_E_RESYNC_NEEDED]

SEVERITY: ERROR
DESCRIPTION: The server is dealing with an out of sync data dictionary object.
CAUSE: The resync needed flag in the published data dictionary is set to True if that object in the Data Dictionary needs updating. The server was either trying to remove published Data Dictionary information which was out of date, or it was trying to mark Data Dictionary information as out of date.
ACTION: Contact your Documentum site representative.
PARAMS:

ERROR: [DM_DATA_DICT_E_VALUE_FUNC_CANT_FETCH]

SEVERITY: ERROR
DESCRIPTION: D Cannot fetch – Invalid object ID %s.
CAUSE: Could not fetch an object with the given id.
ACTION: This is probably caused by a bad ID. Or, possibly, a connection to the Documentum server could not be established.
PARAMS:

ERROR: [DM_DATA_DICT_E_REPLICA_VALIDATION_FAILURE]

SEVERITY: ERROR
DESCRIPTION: The Data Dictionary encountered an error during the validation of Data Dictionary replica objects
CAUSE: The Data Dictionary encountered an error during the validation of replica objects. Validation typically occurs to ensure that the replica Data Dictionary information for a type or policy does not refer to non-existent attributes in the target docbase.
ACTION: Refer to the additional error messages for more details on the failure.
PARAMS: None

ERROR: [DM_DATA_DICT_E_COULD_NOT_PUBLISH_DATA_DICTIONARY_INFORMATION]

SEVERITY: ERROR
DESCRIPTION: SS The Data Dictionary was unable to publish information for %s, locale %s, an error occured.
CAUSE: The Data Dictionary encountered an error while trying to publish information. Additional error information should have been reported.
ACTION: Gather error messages and any parameters and report them to your Documentum site representative. Look at the dmi_dd_common_info_s table in your database to see if information exists about the type you are trying to retrieve.
PARAMS: The first parameter is the dmDDHandle. This contains the type name, the attribute name, business policy and state name. The second parameter is the nls_key (the locale of the data dictionary information)

ERROR: [DM_DATA_DICT_E_APPEND_UPDATE_FAILED]

SEVERITY: ERROR
DESCRIPTION: S Could not APPEND to attribute %s.
CAUSE: An attempt to APPEND to the given attribute failed.
ACTION: Specify a legal attribute and value.
PARAMS: The first parameter is the attribute name.

ERROR: [DM_DATA_DICT_E_AGGR_DOMAIN_BAD_ATTR_NAME]

SEVERITY: ERROR
DESCRIPTION: SS Attribute %s does not exist for type %s.
CAUSE: The attribute does not exist for the type.
ACTION: Correct the attribute name.
PARAMS: The first parameter is the name of the attribute. The second parameter is the name of the type.

ERROR: [DM_DATA_DICT_E_DUPLICATE_CATEGORY_LIST_ENTRY]

SEVERITY: ERROR
DESCRIPTION: SII The category_list entry %s is duplicated at position %d and position %d.
CAUSE: A data string is repeated in the CATEGORY LIST.
ACTION: Remove the duplicate.
PARAMS: The first parameter is the duplicated data string. The second parameter is the (0-based) position of the first occurrence. The third parameter is the (0-based) position of the second occurrence.

ERROR: [DM_DATA_DICT_E_BAD_ATTR_NAME_IN_MESSAGE]

SEVERITY: ERROR
DESCRIPTION: SS A parameterized error message referenced the value of an attribute $value(%s) that does not exist in type %s.
CAUSE: The attribute name referenced as a substitution parameter in the error message does not exist in the type.
ACTION: Correct the attribute name.
PARAMS: The first parameter is the name of the attribute. The second parameter is the name of the type.

ERROR: [DM_DATA_DICT_E_BAD_VALUE_ESTIMATE]

SEVERITY: ERROR
DESCRIPTION: I Value estimate (%d) for value assistance cannot be negative.
CAUSE: A negative value was specified for the value estimate for value assistance.
ACTION: Use a value greater than 0 or NULL.
PARAMS: The parameter is the negative value.

ERROR: [DM_DATA_DICT_E_CLEANUP_OBJECT_ERROR]

SEVERITY: ERROR
DESCRIPTION: SDS An error occurred while running the data dictionary cleanup method. Operation: %s. Object ID: %s. Details: %s.
CAUSE: An error, most likely related to the database, occurred.
ACTION: Try again in case of a database error. If it occurs again, contact technical support.
PARAMS: The first parameter indicates what was being done when the error occurred. The second parameter is the ID of the object being processed. The third parameter is additional information about the error.

ERROR: [DM_DATA_DICT_E_POLICY_STATE_NOT_FOUND]

SEVERITY: ERROR
DESCRIPTION: DS The policy with object id %s does not have a state named %s.
CAUSE: The business policy state given does not exist.
ACTION: Use a valid business policy state name.
PARAMS: The first parameter is the object id of the business policy. The second parameter is the name of the business policy state.

ERROR: [DM_DATA_DICT_E_UPDATE_STRING_NULL]

SEVERITY: ERROR
DESCRIPTION: SS An attempt was made to update the STRING attribute %s with the value %s (currently used as a NULL marker) which will cause the parents value to be inherited. If this is desired use the keyword NULL.
CAUSE: An update was attempted directly using the NULL string value.
ACTION: Use the keyword NULL.
PARAMS: The first parameter is the name of the STRING attribute being updated. The second parameter is the value used.

ERROR: [DM_DATA_DICT_E_KEY_CANT_FETCH]

SEVERITY: ERROR
DESCRIPTION: D Cannot fetch – Invalid object ID %s.
CAUSE: Could not fetch an object with the given id.
ACTION: This is probably caused by a bad ID. Or, possibly, a connection to the Documentum server could not be established.
PARAMS:

ERROR: [DM_DATA_DICT_E_DUPLICATE_VALUE]

SEVERITY: ERROR
DESCRIPTION: SDSSII The %s object with ID %s has a duplicate values for attribute %s of %s at positions %d and %d.
CAUSE: The attribute for the specified object has duplicate values. Duplicate values for this attribute are not allowed.
ACTION: Ensure that there are no duplicate values in the specified attribute of the object.
PARAMS: The first parameter is the object_type The second parameter is the object ID. The third parameter is the attribute name. The fourth parameter is the duplicate value. The fifth and sixth parameters are the duplicate attribute value indices.

ERROR: [DM_DATA_DICT_E_MISSING_FORMAT_TAG]

SEVERITY: ERROR
DESCRIPTION: S A format pattern (%s) was supplied without a format tag.
CAUSE: If a format pattern is specified, a format tag must also be specified.
ACTION: Supply a format tag.
PARAMS: The parameter is the format pattern.

ERROR: [DM_DATA_DICT_E_REPLICA_VALIDATION_FAILED]

SEVERITY: ERROR
DESCRIPTION: SD The replica %s object with ID %s could not be validated against one or more types in the target docbase.
CAUSE: The Data Dictionary encountered an error during the validation of replica objects. Validation typically occurs to ensure that the replica Data Dictionary information for a type or policy does not refer to non-existent attributes in the target docbase.
ACTION: Refer to the additional error messages for more details on the failure.
PARAMS: The first parameter is the object type of the replica object. The second parameter is the object ID of the replica object.

ERROR: [DM_DATA_DICT_E_TYPE_NOT_VALID_FOR_POLICY]

SEVERITY: ERROR
DESCRIPTION: SD The type %s is not a valid type for the policy with object id %s.
CAUSE: The type is not a valid type for the policy supplied.
ACTION: Verify that one of the following is true: 1) The type is an included_type of the policy 2) A supertype of the type is an included type of the policy and the include_subtypes flag of the policy object is TRUE.
PARAMS: The first parameter is the type name. The second parameter is the object id of the policy.

ERROR: [DM_DATA_DICT_E_ALLOWED_SEARCH_OPS_NULL]

SEVERITY: ERROR
DESCRIPTION: SS The allowed search operators attribute %s cannot be NULL if the default search op attribute %s is set.
CAUSE: The allowed search ops attribute is NULL. It must be set if you specified a default search op.
ACTION: Set the allowed search ops attribute.
PARAMS: The first parameter is the attribute name for allowed search ops. The second parameter is the attribute name for default search op.

ERROR: [DM_DATA_DICT_E_POLICY_STATE_FOR_OVERRIDE_NOT_FOUND]

SEVERITY: ERROR
DESCRIPTION: DD The business policy state was not found for the data dictionary override was not found. The dm_aggr_domain id is %s and the dm_policy id is %s.
CAUSE: The data dictionary dm_aggr_domain objects parent_id indicates that it is associated with a policy override. However, the corresponding policy object does not have a matching type_override_id in it.
ACTION: Contact your Documentum Administrator with the information contained within the error message.
PARAMS: The first parameter is the object id of the dm_aggr_domain object. The second parameter is the object id of the dm_policy object.

ERROR: [DM_DATA_DICT_E_INSUFFICIENT_PRIVILEGES]

SEVERITY: ERROR
DESCRIPTION: S The docbase user %s has insufficient privileges for the desired operation. The user must be a super user.
CAUSE: The docbase user does not have sufficient privileges for the operation.
ACTION: Either use another user, or make the user a superuser.
PARAMS: The first parameter is the docbase user name.

ERROR: [DM_DATA_DICT_E_DD_HANDLE_ATTR_NAME_MISSING]

SEVERITY: ERROR
DESCRIPTION: S The attribute name portion of the Data Dictionary handle %s is missing.
CAUSE: The attribute name in the data dictionary handle is missing.
ACTION: Use a valid attribute name for the given type.
PARAMS: The parameter is the Data Dictionary handle.

ERROR: [DM_DATA_DICT_E_DEPENDENCY_ATTR_NOT_FOUND]

SEVERITY: ERROR
DESCRIPTION: SS Attribute %s was specified in a DEPENDENCY LIST clause for type %s but does not exist in the type.
CAUSE: An invalid attribute name was specified in a DEPENDENCY LIST clause.
ACTION: Specify a legal attribute name.
PARAMS: The first parameter is the name of the attribute specified. The second parameter is the name of the type.

ERROR: [DM_DATA_DICT_E_DD_ATTR_INFO_CANT_FETCH]

SEVERITY: ERROR
DESCRIPTION: D Cannot fetch – Invalid object ID %s.
CAUSE: Could not fetch an object with the given id.
ACTION: This is probably caused by a bad ID. Or, possibly, a connection to the Documentum server could not be established.
PARAMS: The parameter is the object id.

ERROR: [DM_DATA_DICT_E_DD_HANDLE_STATE_NAME_MISSING]

SEVERITY: ERROR
DESCRIPTION: S The business policy state name portion of the Data Dictionary handle %s is missing.
CAUSE: The state name in the data dictionary handle is missing. This is required if a business policy id is provided.
ACTION: Use a valid state name for the given business policy.
PARAMS: The parameter is the Data Dictionary handle.

ERROR: [DM_DATA_DICT_E_ATTR_NAME_TOO_LONG]

SEVERITY: ERROR
DESCRIPTION: SI Attribute name %s is too long. Maximum length is %d.
CAUSE: An attribute name was specified that is too long.
ACTION: Shorten the attribute name.
PARAMS: The first parameter is the name of the attribute specified. The second parameter is the maximum Data Dictionary attribute name length.

ERROR: [DM_DATA_DICT_E_DD_TYPE_INFO_CANT_FETCH]

SEVERITY: ERROR
DESCRIPTION: D Cannot fetch – Invalid object ID %s.
CAUSE: Could not fetch an object with the given id.
ACTION: This is probably caused by a bad ID. Or, possibly, a connection to the Documentum server could not be established.
PARAMS: The parameter is the object id.

ERROR: [DM_DATA_DICT_E_DUP_ATTR_FOR_KEY]

SEVERITY: ERROR
DESCRIPTION: DSS The key (%s) for type %s duplicates the attribute %s.
CAUSE: The dm_key or dm_foreign_key object has a duplicate attribute in its attributes list.
ACTION: Remove the duplicate.
PARAMS: The first parameter is the object id of the key object. The second parameter is the name of the type. The third parameter is the name of the duplicated attribute.

ERROR: [DM_DATA_DICT_E_BAD_SEARCH_OP_VALUE]

SEVERITY: ERROR
DESCRIPTION: SIII The value of attribute %s should be in the range %d to %d, but was %d.
CAUSE: The value is out of range.
ACTION: Supply a value in the indicated range.
PARAMS: The first parameter is the attribute name. The second parameter is the lower range bound. The third parameter is the upper range bound. The fourth parameter is the actual value.

ERROR: [DM_DATA_DICT_E_BAD_DOUBLE_VALUE]

SEVERITY: ERROR
DESCRIPTION: S The value %s is not a valid DOUBLE value.
CAUSE: A non-DOUBLE value was specified in a context where a DOUBLE is required.
ACTION: Specify a legal DOUBLE value.
PARAMS: The parameter is the value.

ERROR: [DM_DATA_DICT_E_DEFAULT_FOR_SYSTEM_READ_ONLY_ATTRIBUTE]

SEVERITY: ERROR
DESCRIPTION: SS You cannot specify a DEFAULT value for attribute %s in type %s because it is a system read only attribute.
CAUSE: You have attempted to specify a DEFAULT value for an attribute whose name begins with r_.
ACTION: Remove the DEFAULT value clause.
PARAMS: The first parameter is the name of the attribute. The second parameter is the name of the type.

ERROR: [DM_DATA_DICT_E_EXAMPLE]

SEVERITY: ERROR
DESCRIPTION: S ALTER TYPE: You have insufficient privilege to ADD or DROP attributes from a Documentum base type (%s).
CAUSE: Your alter type statement specified a Documentum base type. Only a superuser may alter the base types, and then only if requested to do so as part of a Documentum release script. Any type which has a name beginning with the letters dm is a Documentum base type.
ACTION: None.
PARAMS: The typename as specified in the alter type statement.

ERROR: [DM_DATA_DICT_E_TYPE_NOT_FOUND]

SEVERITY: ERROR
DESCRIPTION: SDS The type %s referenced in object with ID %s, attribute %s was not found.
CAUSE: The specified type does not exist.
ACTION: Verify that the correct type was set in the attribute of the object
PARAMS: The first parameter is the type name The second parameter is the object that referenced the type. The third parameter is the attribute name that the non-existent type is specified in.

ERROR: [DM_DATA_DICT_E_BAD_REPEATING_ENFORCEMENT_VALUE]

SEVERITY: ERROR
DESCRIPTION: SIIII The value of attribute %s[%d] should be in the range %d to %d, but was %d.
CAUSE: The value is out of range.
ACTION: Supply a value in the indicated range.
PARAMS: The first parameter is the attribute name. The second parameter is the repeating attribute index. The third parameter is the lower range bound. The fourth parameter is the upper range bound. The fifit parameter is the actual value.

ERROR: [DM_DATA_DICT_E_COULD_NOT_DROP_PUBLISHED_DATA_DICTIONARY_INFO]

SEVERITY: ERROR
DESCRIPTION: SS Unable to remove Data dictionary information about %s with locale %s.
CAUSE: Unknown. Perhaps the database tables are locked.
ACTION: Report this message and any parameters to your Documentum site representative. Try to see if you can manually query the dmi_dd_common_info_s, dmi_dd_common_info_r, dmi_dd_type_info_s, dmi_dd_type_info_r, dmi_dd_attr_info_s, or dmi_dd_attr_info_r tables.
PARAMS: The first parameter is the dmDDHandle. This contains the type name, the attribute name, business policy and state name. The second parameter is the nls_key (the locale of the data dictionary information)

ERROR: [DM_DATA_DICT_E_COULD_NOT_EXPUNGE_PUBLISHED_DATA_DICTIONARY_OBJECT]

SEVERITY: ERROR
DESCRIPTION: SSD An error occured while attemping to remove an object of type dmi_dd_type_info or dmi_dd_attr_info from the docbase. The object referred to %s with locale %s. The r_object_id was %s
CAUSE: Unknown. The server tried to remove the object from the docbase but failed. A database error may have occured.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS: The first parameter is the dmDDHandle. This contains the type name, the attribute name, business policy and state name. The second parameter is the nls_key (the locale of the data dictionary information) The third paremeter is the object id of the object being expunged.

ERROR: [DM_DATA_DICT_E_DUPLICATE_UNIQUE_KEY]

SEVERITY: ERROR
DESCRIPTION: SS Type %s has multiple unique keys consisting of just the attribute %s. One at the type level, and one at the attribute level.
CAUSE: You have specified multiple unique keys with the single attribute indicated.
ACTION: Remove one of the duplicates.
PARAMS: The first parameter is the name of the type. The second parameter is the name of the offending attribute.

ERROR: [DM_DATA_DICT_E_DEFAULT_FOR_BUSINESS_POLICY_STATE]

SEVERITY: ERROR
DESCRIPTION: SS You cannot specify a DEFAULT value for attribute %s in type %s that is specific to a particular Business Policy state.
CAUSE: You have attempted to specify a DEFAULT value that is specific to a Business Policy state. Since objects are created before being put in Business Policy states, the DEFAULT value would be meaningless.
ACTION: Remove the DEFAULT value clause.
PARAMS: The first parameter is the name of the attribute. The second parameter is the name of the type.

ERROR: [DM_DATA_DICT_E_NULL_REPEATING_EXPRESSION_VALUE]

SEVERITY: ERROR
DESCRIPTION: SI The value of expression attribute %s[%d] is the NULL object id.
CAUSE: A NULL object id is not allowed here.
ACTION: Supply a valid object id.
PARAMS: The first parameter is the attribute name. The second parameter is the repeating attribute index.

ERROR: [DM_DATA_DICT_E_BAD_ESCAPE_CHARACTER_IN_MESSAGE]

SEVERITY: ERROR
DESCRIPTION: SS The substitution parameter escape character (%s) was not used correctly in error message: %s.
CAUSE: The substitution parameter marker $ was not followed by a legal value.
ACTION: Use $value(attr_name) with no extra white space.
PARAMS: The first parameter is the parameter escape character. The second parameter is the error message text.

ERROR: [DM_DATA_DICT_E_CANNOT_SET_IGNORE_IMMUTABLE_FALSE]

SEVERITY: ERROR
DESCRIPTION: SS You cannot set ignore_immutable to FALSE for %s attribute %s. It is required by the system to be TRUE.
CAUSE: You have attempted to change ignore_immutable to FALSE for an attribute that the system depends on having ignore_immutable TRUE.
ACTION: Do not try to change ignore_immutable to FALSE for this attribute.
PARAMS: The first parameter is the type name. The second parameter is the attribute name.

ERROR: [DM_DATA_DICT_E_EXPR_CODE_CANT_FETCH]

SEVERITY: ERROR
DESCRIPTION: D Cannot fetch – Invalid object ID %s.
CAUSE: Could not fetch an object with the given id.
ACTION: This is probably caused by a bad ID. Or, possibly, a connection to the Documentum server could not be established.
PARAMS:

ERROR: [DM_DATA_DICT_E_DUPLICATE_DEPENDENCY_ATTR]

SEVERITY: ERROR
DESCRIPTION: SS Attribute %s was specified more than once in a DEPENDENCY LIST clause for type %s.
CAUSE: A duplicate attribute name was specified in a DEPENDENCY LIST clause.
ACTION: Remove the duplicates.
PARAMS: The first parameter is the name of the attribute specified. The second parameter is the name of the type.

ERROR: [DM_DATA_DICT_E_PARAM_NOT_TERMINATED]

SEVERITY: ERROR
DESCRIPTION: SS A substitution parameter was not terminated correctly with %s in error message: %s.
CAUSE: A substitution parameter marked with $ was not correctly formed.
ACTION: Use $value(attr_name) with no extra white space.
PARAMS: The first parameter is the expected terminator. The second parameter is the error message text.

ERROR: [DM_DATA_DICT_E_ILLEGAL_REPEATING_IN_KEY]

SEVERITY: ERROR
DESCRIPTION: DSS The key with object id %s for type %s contains at least one repeating attribute (%s). Neither a primary key, nor the parent key in a foreign key can contain repeating attributes.
CAUSE: You have attempted to define a primary key or a parent key in a foreign key that contains a repeating attribute.
ACTION: These key types cannot contain repeating attributes.
PARAMS: The first parameter is the object id of the key object. The second parameter is the name of the type that defines the attributes. The third parameter is the name of a repeating attribute in the key.

ERROR: [DM_DATA_DICT_E_BAD_PSEUDO_BOOLEAN_VALUE]

SEVERITY: ERROR
DESCRIPTION: SIII The value of attribute %s should be in the range %d to %d, but was %d.
CAUSE: The value is out of range.
ACTION: Supply a value in the indicated range.
PARAMS: The first parameter is the attribute name. The second parameter is the lower range bound. The third parameter is the upper range bound. The fourth parameter is the actual value.

ERROR: [DM_DATA_DICT_E_ERROR_GENERATING_EXPRESSION_SOURCE]

SEVERITY: ERROR
DESCRIPTION: DS An error was encountered generating the source code for expression object %s for Data Dictionary attribute %s.
CAUSE: A problem (reported in a separate message) prevented expression source generation.
ACTION: Correct the problem that was reported separately.
PARAMS: The first parameter is the object id of the expression object. The second parameter is the attribute name.

ERROR: [DM_DATA_DICT_E_DD_HANDLE_WRONG_FIRST_CHAR]

SEVERITY: ERROR
DESCRIPTION: S The Data Dictionary handle %s is invalid because it does not begin with t.
CAUSE: The Data Dictionary handle is mal-formed.
ACTION: Use a valid Data Dictionary handle.
PARAMS: The parameter is the Data Dictionary handle.

ERROR: [DM_DATA_DICT_E_SCOPE_CONFIG_CANT_FETCH]

SEVERITY: ERROR
DESCRIPTION: D Cannot fetch – Invalid object ID %s.
CAUSE: Could not fetch an object with the given id.
ACTION: This is probably caused by a bad ID. Or, possibly, a connection to the Documentum server could not be established.
PARAMS:

ERROR: [DM_DATA_DICT_E_MISSING_FORMAT_PATTERN]

SEVERITY: ERROR
DESCRIPTION: I A format tag (%d) was supplied without a format pattern.
CAUSE: If a format tag is specified, a format pattern must also be specified.
ACTION: Supply a format pattern.
PARAMS: The parameter is the format tag.

ERROR: [DM_DATA_DICT_E_TYPE_MISSING]

SEVERITY: ERROR
DESCRIPTION: S The type %s referred by the aggregate domain was not found.
CAUSE: During loading, the type referred by the aggregate domain object was missing.
ACTION: The aggregate domain object was not loaded.
PARAMS: Name of the type.

ERROR: [DM_DATA_DICT_E_DEFAULT_FOR_SYSTEM_INTERNAL_ATTRIBUTE]

SEVERITY: ERROR
DESCRIPTION: SS You cannot specify a DEFAULT value for attribute %s in type %s because it is a system internal attribute.
CAUSE: You have attempted to specify a DEFAULT value for an attribute whose name begins with i_.
ACTION: Remove the DEFAULT value clause.
PARAMS: The first parameter is the name of the attribute. The second parameter is the name of the type.

ERROR: [DM_DATA_DICT_E_DD_COMMON_INFO_CANT_FETCH]

SEVERITY: ERROR
DESCRIPTION: D Cannot fetch – Invalid object ID %s.
CAUSE: Could not fetch an object with the given id.
ACTION: This is probably caused by a bad ID. Or, possibly, a connection to the Documentum server could not be established.
PARAMS: The parameter is the object id.

ERROR: [DM_DATA_DICT_E_BAD_CONSTRAINT_CHECKER_VALUE]

SEVERITY: ERROR
DESCRIPTION: SIII The value of attribute %s should be in the range %d to %d, but was %d.
CAUSE: The value is out of range.
ACTION: Supply a value in the indicated range.
PARAMS: The first parameter is the attribute name. The second parameter is the lower range bound. The third parameter is the upper range bound. The fourth parameter is the actual value.

ERROR: [DM_DATA_DICT_E_DD_HANDLE_ATTR_NOT_FOUND]

SEVERITY: ERROR
DESCRIPTION: SSS The attribute %s named in the Data Dictionary handle %s does not exist in type %s.
CAUSE: The attribute named in the Data Dictionary handle does not exist in the given type.
ACTION: Use a valid attribute name for the given type.
PARAMS: The first parameter is the attribute name. The second parameter is the Data Dictionary handle. The third parameter is type name.

ERROR: [DM_DATA_DICT_E_BAD_REPEATING_CONSTRAINT_CHECKER_VALUE]

SEVERITY: ERROR
DESCRIPTION: SIIII The value of attribute %s[%d] should be in the range %d to %d, but was %d.
CAUSE: The value is out of range.
ACTION: Supply a value in the indicated range.
PARAMS: The first parameter is the attribute name. The second parameter is the repeating attribute index. The third parameter is the lower range bound. The fourth parameter is the upper range bound. The fifit parameter is the actual value.

ERROR: [DM_DATA_DICT_E_BAD_INTEGER_VALUE]

SEVERITY: ERROR
DESCRIPTION: S The value %s is not a valid INTEGER value.
CAUSE: A non-integer value was specified in a context where an integer is required.
ACTION: Specify a legal integer value.
PARAMS: The parameter is the value.

ERROR: [DM_DATA_DICT_E_TYPE_CANNOT_HAVE_DEFAULT_VALUE]

SEVERITY: ERROR
DESCRIPTION: S You cannot specify a DEFAULT value for any attribute of the system type %s.
CAUSE: You have attempted to specify a DEFAULT value for one of the special system types that is not allowed to have DEFAULT values for its attributes.
ACTION: Remove the DEFAULT value clause.
PARAMS: The parameter is the name of the type.

ERROR: [DM_DATA_DICT_E_CANNOT_FETCH_OBJECT_FOR_DEFAULT_ID]

SEVERITY: ERROR
DESCRIPTION: D Cannot fetch the object with object id %s for the default_id attribute.
CAUSE: The object could not be fetched.
ACTION: Make sure the object exists.
PARAMS: The parameter is the object id of the default object.

ERROR: [DM_DATA_DICT_E_DD_HANDLE_POLICY_ID_TOO_LONG]

SEVERITY: ERROR
DESCRIPTION: S The policy id portion of the Data Dictionary handle %s is too long.
CAUSE: The policy id in the data dictionary handle is too long.
ACTION: Use a valid business policy id.
PARAMS: The parameter is the Data Dictionary handle.

ERROR: [DM_DATA_DICT_E_DD_HANDLE_TYPE_NOT_VALID_FOR_POLICY]

SEVERITY: ERROR
DESCRIPTION: SSD The type %s named in the Data Dictionary handle %s is not a valid type for the policy with object id %s.
CAUSE: The type named in the Data Dictionary handle is not a valid type for the policy supplied.
ACTION: Verify that one of the following is true: 1) The type named in the handle is an included_type of the policy 2) A supertype of the type named in the handle is an included type of the policy and the include_subtypes flag of the policy object is TRUE.
PARAMS: The first parameter is the type name. The second parameter is the Data Dictionary handle. The third parameter is the object id of the policy.

ERROR: [DM_DATA_DICT_E_CLEANUP_ERROR]

SEVERITY: ERROR
DESCRIPTION: SS An error occurred while running the data dictionary cleanup method. Operation: %s. Details: %s.
CAUSE: An error, most likely related to the database, occurred.
ACTION: Try again in case of a database error. If it occurs again, contact technical support.
PARAMS: The first parameter indicates what was being done when the error occurred. The second parameter is additional information about the error.

ERROR: [DM_DATA_DICT_E_CANT_DESTROY_EXPR_CODE_TEMP_FILE]

SEVERITY: ERROR
DESCRIPTION: S The following error occurred trying to destroy a temporary file for expression code: %s.
CAUSE: A file error occurred trying to destroy the temporary file used to hold generated expression code.
ACTION: This depends on the file error code provided.
PARAMS: The parameter is the file error message.

ERROR: [DM_DATA_DICT_E_BAD_DEFAULT_SEARCH_OP]

SEVERITY: ERROR
DESCRIPTION: SIS The default search operator attribute %s contains the value %d which is not in the list of allowed search operators (%s).
CAUSE: The default search operator is not a legal operator for the attribute.
ACTION: Change the default search operator to a legal operator for the attribute.
PARAMS: The first parameter is the attribute name. The second parameter is the default search operator value. The third parameter is the name of the allowed search operators attribute.

ERROR: [DM_DATA_DICT_E_FKEY_ATTR_LISTS_DIFFERENT_LENGTHS]

SEVERITY: ERROR
DESCRIPTION: DSISI In the foreign key (%s) for type %s the child attribute list contains %d attributes, but the parent type %s attribute list contains %d attributes.
CAUSE: The dm_foreign_key has a child attribute list with a different length than the parent attribute list.
ACTION: Make the attribute lists the same length.
PARAMS: The first parameter is the object id of the key object. The second parameter is the name of the child type. The third parameter is the length of the child attribute list. The forth parameter is the name of the parent type. The fifth parameter is the length of the parent attribute list.

ERROR: [DM_DATA_DICT_E_TYPE_CANNOT_HAVE_EXPRESSION]

SEVERITY: ERROR
DESCRIPTION: S You cannot specify an expression for the system type %s.
CAUSE: You have attempted to specify an expression for one of the special system types that is not allowed to use expressions.
ACTION: Remove the expression.
PARAMS: The parameter is the name of the type.

ERROR: [DM_DATA_DICT_E_REMOVING_DATA_DICTIONARY_OBJECTS_FOR_ATTRIBUTE]

SEVERITY: ERROR
DESCRIPTION: SSS An error occured while trying to remove published data dictionary information for type %s, attribute %s, and locale %s
CAUSE: The server was trying to remove published Data Dictionary information about the type and all of its attributes. The objects it was trying to remove are either of type dmi_dd_type_info or dmi_dd_attr_info
ACTION: Contact your Documentum site representative.
PARAMS: The first parameter name of the type being removed The second parameter is the name of the attribute being removed. The third parameter is the nls_key (the locale of the data dictionary information)

ERROR: [DM_DATA_DICT_E_DEFAULT_SEARCH_OP_NULL]

SEVERITY: ERROR
DESCRIPTION: SS The default search op attribute %s cannot be NULL if the allowed_search_ops attribute %s is set.
CAUSE: The default search op attribute is NULL. It must be set if you specified the allowed search ops.
ACTION: Set the default search op attribute.
PARAMS: The first parameter is the attribute name for default search op. The second parameter is the attribute name for allowed search ops.

ERROR: [DM_DATA_DICT_E_DUPLICATE_MAP_DATA_STRING]

SEVERITY: ERROR
DESCRIPTION: SII The mapping table data string %s is duplicated at position %d and position %d.
CAUSE: A data string is repeated in the MAPPING TABLE.
ACTION: Remove the duplicate.
PARAMS: The first parameter is the duplicated data string. The second parameter is the (0-based) position of the first occurrence. The third parameter is the (0-based) position of the second occurrence.

ERROR: [DM_DATA_DICT_E_CANNOT_EXPUNGE_REFERENCED_OBJECT]

SEVERITY: ERROR
DESCRIPTION: SDD The %s object with ID %s cannot be expunged because it is referenced by object with ID %s.
CAUSE: The object cannot be expunged because it is referened by another object.
ACTION: Remove all references to the object that is to be expunged first.
PARAMS: The first parameter is the type of the object being expunged. The second parameter is the object ID of the object being expunged. The third parameter is the object ID of the referencing object.

ERROR: [DM_DATA_DICT_E_VALUE_QUERY_CANT_FETCH]

SEVERITY: ERROR
DESCRIPTION: D Cannot fetch – Invalid object ID %s.
CAUSE: Could not fetch an object with the given id.
ACTION: This is probably caused by a bad ID. Or, possibly, a connection to the Documentum server could not be established.
PARAMS:

ERROR: [DM_DATA_DICT_E_UNABLE_TO_PUBLISH_INFO]

SEVERITY: ERROR
DESCRIPTION: SS An error occured while trying to publish data dictionary information for handle %s, locale %s
CAUSE: The Data Dictionary was unable to publish information for the specified handle.
ACTION: Contact your Documentum site representative.
PARAMS: The first parameter is the dd_handle. The second parameter is the nls_key (the locale of the data dictionary information)

ERROR: [DM_DATA_DICT_E_DD_HANDLE_EXTRA_CHARACTERS]

SEVERITY: ERROR
DESCRIPTION: S The Data Dictionary handle %s contains extra characters at the end.
CAUSE: The Data Dictionary handle has extra characters at the end.
ACTION: Remove the extra characters.
PARAMS: The parameter is the Data Dictionary handle.

ERROR: [DM_DATA_DICT_E_VALUE_LIST_CANT_FETCH]

SEVERITY: ERROR
DESCRIPTION: D Cannot fetch – Invalid object ID %s.
CAUSE: Could not fetch an object with the given id.
ACTION: This is probably caused by a bad ID. Or, possibly, a connection to the Documentum server could not be established.
PARAMS:

ERROR: [DM_DATA_DICT_E_BAD_STRING_VALUE]

SEVERITY: ERROR
DESCRIPTION: S The value %s is not a valid STRING value.
CAUSE: A non-STRING value was specified in a context where a STRING is required.
ACTION: Specify a legal STRING value.
PARAMS: The parameter is the value.

ERROR: [DM_DATA_DICT_E_MAX_RETRY_COUNT_EXCEEDED]

SEVERITY: ERROR
DESCRIPTION: I The Data Dictionary operation has exceeded the max retry count of %d. The operation has aborted due to too many errors.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DATA_DICT_E_BAD_REPEATING_LIFECYCLE_VALUE]

SEVERITY: ERROR
DESCRIPTION: SIIII The value of attribute %s[%d] should be in the range %d to %d, but was %d.
CAUSE: The value is out of range.
ACTION: Supply a value in the indicated range.
PARAMS: The first parameter is the attribute name. The second parameter is the repeating attribute index. The third parameter is the lower range bound. The fourth parameter is the upper range bound. The fifit parameter is the actual value.

ERROR: [DM_DATA_DICT_E_COULD_NOT_LOG_DATA_DICTIONARY_CHANGES]

SEVERITY: ERROR
DESCRIPTION: SS An error was encountered while trying to log changes to data dictionary information for %s, locale %s.
CAUSE: The Data Dictionary was unable to update the log for the data dictionary changes. Perhaps the database tables are corrupted.
ACTION: Report this message and any parameters to your Documentum site representative. Look at the dmi_dd_common_info_s table in your database to see if information exists about the type you are trying to retrieve. Look at the dd_publish_log table as well.
PARAMS: The first parameter is the dmDDHandle. This contains the type name, the attribute name, business policy and state name. The second parameter is the nls_key (the locale of the data dictionary information)

ERROR: [DM_DATA_DICT_E_BAD_ATTR_FOR_ATTRIBUTE]

SEVERITY: ERROR
DESCRIPTION: S The attribute %s can only be supplied for a type, not for an attribute of a type.
CAUSE: The indicated attribute cannot be supplied for an attribute of a type.
ACTION: Remove the indicated information.
PARAMS: The parameter is the offending Data Dictionary attribute.

ERROR: [DM_DATA_DICT_E_NOT_A_VALID_DATA_DICTIONARY_LOCALE]

SEVERITY: ERROR
DESCRIPTION: S The locale %s is not a valid Data Dictionary Locale.
CAUSE: A locale has been specified that does not exist within the Data Dictionary.
ACTION: Check the dd_locales attribute in the dm_docbase_config object to see a list of valid Data Dictionary locales. Specify a valid Data Dictionary locale.
PARAMS: The first parameter is the invalid locale that was specified.

ERROR: [DM_DATA_DICT_E_INVALID_DD_BUILTIN_VALUE_SPECIFICATION]

SEVERITY: ERROR
DESCRIPTION: IS An invalid builtin function %d was specified for attribute %s.
CAUSE: This is an internal error. The data dictionary should not have allowed the user to setup a a value specification with an invalid builtin function.
ACTION: Report this error to your Documentum System Administrator
PARAMS: The first parameter is the builtin tag that was supplied for the value specification. The second parameter is the attribute for which the invalid builtin function was specified.

ERROR: [DM_DATA_DICT_E_REMOVING_DATA_DICTIONARY_OBJECTS_FOR_TYPE]

SEVERITY: ERROR
DESCRIPTION: SS An error occured while trying to remove published data dictionary information for type %s, locale %s
CAUSE: The server was trying to remove published Data Dictionary information about the type and all of its attributes. The objects it was trying to remove are either of type dmi_dd_type_info or dmi_dd_attr_info
ACTION: Contact your Documentum site representative.
PARAMS: The first parameter name of the type being removed The second parameter is the nls_key (the locale of the data dictionary information)

ERROR: [DM_DATA_DICT_E_DISPLAY_CONFIG_INVALID_ATTRIBUTE_NAME]

SEVERITY: ERROR
DESCRIPTION: DSS The dm_display_config object with ID %s has an attribute_name entry %s that does not exist in the attribute_source type %s
CAUSE: The dm_display_config object references an attribute in the attribute_name repeating attribute that does not exist in the attribute_source type.
ACTION: Ensure that the dm_display_config object references valid attributes in the attribute_source type or that the attribute_source is correct.
PARAMS: The first parameter is the object ID of the dm_display_config object. The second parameter is the name of the invalid attribute. The third parameter is the name of the attribute source.

ERROR: [DM_DATA_DICT_E_UPDATE_INTEGER_NULL]

SEVERITY: ERROR
DESCRIPTION: SI An attempt was made to update the INTEGER attribute %s with the value %d (currently used as a NULL marker) which will cause the parents value to be inherited. If this is desired use the keyword NULL.
CAUSE: An update was attempted directly using the NULL integer value.
ACTION: Use the keyword NULL.
PARAMS: The first parameter is the name of the INTEGER attribute being updated. The second parameter is the value used.

ERROR: [DM_DATA_DICT_E_BAD_LIFECYCLE_VALUE]

SEVERITY: ERROR
DESCRIPTION: SIII The value of attribute %s should be in the range %d to %d, but was %d.
CAUSE: The value is out of range.
ACTION: Supply a value in the indicated range.
PARAMS: The first parameter is the attribute name. The second parameter is the lower range bound. The third parameter is the upper range bound. The fourth parameter is the actual value.

ERROR: [DM_DATA_DICT_E_INVALID_ATTRIBUTE_NAME]

SEVERITY: ERROR
DESCRIPTION: SS An invalid attribute %s for type_name %s was specified.
CAUSE: An invalid attribute name was specified
ACTION: Correct the attribute name and retry the operation.
PARAMS: The parameter contains the name of the attribute that is invalid as well as the type_name it was supposed to belong to.

ERROR: [DM_DATA_DICT_E_FOREIGN_KEY_CANT_FETCH]

SEVERITY: ERROR
DESCRIPTION: D Cannot fetch – Invalid object ID %s.
CAUSE: Could not fetch an object with the given id.
ACTION: This is probably caused by a bad ID. Or, possibly, a connection to the Documentum server could not be established.
PARAMS:

ERROR: [DM_DATA_DICT_E_UPDATE_TYPE_MISMATCH]

SEVERITY: ERROR
DESCRIPTION: SSS An attempt was made to update attribute %s (of type %s) with a value of type %s.
CAUSE: An update was attempted with a value of the wrong data type.
ACTION: Correct the type of the value.
PARAMS: The first parameter is the name of the attribute being updated. The second parameter is the actual type of that attribute. The third parameter is the type of the value.

ERROR: [DM_DATA_DICT_E_SYNCHRONIZE_WITH_TYPE_FAILED]

SEVERITY: ERROR
DESCRIPTION: SDS The server was unable to synchronize the %s object with ID %s with the type %s.
CAUSE: The server encountered a failure while trying to synchronize the specified object with the type in the docbase. Generally, the server must synchronize an object when it is either loaded or replicated from another docbase.
ACTION: Additional errors should be displayed with more details regarding the failure.
PARAMS: The first parameter is the object type. The second parameter is the ID of the object. The third parameter is the type the server tried to synchronize with.

ERROR: [DM_DATA_DICT_E_DD_HANDLE_POLICY_NOT_FOUND]

SEVERITY: ERROR
DESCRIPTION: DS The policy with object id %s named in the Data Dictionary handle %s does not exist.
CAUSE: The business policy object id given in the Data Dictionary handle does not exist.
ACTION: Use a valid business policy id.
PARAMS: The first parameter is the object id of the business policy. The second parameter is the Data Dictionary handle.

ERROR: [DM_DATA_DICT_E_PUBLISHING_FROM_DD_PUBLISH_LOG]

SEVERITY: ERROR
DESCRIPTION: An error occured while trying to update Data Dictionary information from the dd_publish_log
CAUSE: Unknown. The server is going through each entry of the dd_publish_log, dropping corresponding data dictionary information and recreating it. An error has occured during the process.
ACTION: Please contact your Documentum site representative.
PARAMS:

ERROR: [DM_DATA_DICT_E_UNABLE_TO_ADD_EXTENDED_ATTRIBUTES_TO_DMI_DD_TYPE_INFO]

SEVERITY: ERROR
DESCRIPTION: S The Data Dictionary was unable to add extended attributes to the dmi_dd_type_info object with handle %s
CAUSE: The Data Dictionary was trying to add extended attributes to the dmi_dd_type_info object and encountered a failure. These attributes are most likely from the referenced types dm_type and dmi_type_info object.
ACTION: Additional error messages should have been reported. Gather up additional error messages and contact your Documentum Administrator.
PARAMS: The first parameter is the dd_handle for the dmi_dd_type_info object.

ERROR: [DM_DATA_DICT_E_UNABLE_TO_REMOVE_DATA_DICTIONARY_LOG_ENTRY]

SEVERITY: ERROR
DESCRIPTION: SS An error occured while removing log entry about %s and locale: %s from the data dictionary log (dd_publish_log)
CAUSE: The Data Dictionary encountered an error while removing a log entry from the dd_publish_log. The information for the specified dd_handle has already been published.
ACTION: Look at the appropriate object in dmi_dd_type_info or dmi_dd_attr_info and verify that the resync_needed flag is false. If it is false, you can manually remove the entry in the dd_publish_log where publish_in_progress = 1. Please contact your Documentum site representative if you are unsure how to proceed.
PARAMS: The first parameter is the dmDDHandle. This contains the type name, the attribute name, business policy and state name. The second parameter is the nls_key (the locale of the data dictionary information)

ERROR: [DM_DATA_DICT_E_DD_HANDLE_ATTR_NAME_TOO_LONG]

SEVERITY: ERROR
DESCRIPTION: S The attribute name portion of the Data Dictionary handle %s is too long.
CAUSE: The attribute named in the data dictionary handle is too long.
ACTION: Use a valid attribute name for the given type.
PARAMS: The parameter is the Data Dictionary handle.

ERROR: [DM_DATA_DICT_E_COMMIT_EXTERNAL_TRANSACTION]

SEVERITY: ERROR
DESCRIPTION: S Committing the Data Dictionary changes for type %s would commit an explicit open transaction.
CAUSE: A CREATE/ALTER/DROP type operation was attempted that involved Data Dictionary information with an explicit transaction open.
ACTION: Move the type operation outside of the explicit transaction.
PARAMS: The parameter is the name of the type.

ERROR: [DM_DATA_DICT_E_BAD_DATE_VALUE]

SEVERITY: ERROR
DESCRIPTION: SS The value %s is not a valid DATE/TIME value using the format %s.
CAUSE: A non-DATE/TIME value was specified in a context where a DATE/TIME is required.
ACTION: Specify a legal DATE/TIME value.
PARAMS: The first parameter is the value. The second parameter is the expected DATE/TIME format.

ERROR: [DM_DATA_DICT_E_DD_HANDLE_BAD_POLICY_ID]

SEVERITY: ERROR
DESCRIPTION: S The policy id portion of the Data Dictionary handle %s is not a valid object id.
CAUSE: The policy id in the data dictionary handle is not a well-formed object id.
ACTION: Use a valid business policy id.
PARAMS: The parameter is the Data Dictionary handle.

ERROR: [DM_DATA_DICT_E_DATA_DICTIONARY_OBJECT_ERROR]

SEVERITY: ERROR
DESCRIPTION: SSS The data dictionary information for the type %s, locale %s and r_object_id (%s) was not retrieved correctly.
CAUSE: The database tables for the object may be locked or contain inaccurate information.
ACTION: Report this message and any parameters to your Documentum site representative. Look at the dmi_dd_common_info_s table in your database to see if information exists about the type you are trying to retrieve.
PARAMS: The first parameter is the dmDDHandle. This contains the type name, the attribute name, business policy and state name. The second parameter is the nls_key (the locale of the data dictionary information) The third parameter is what is the bad object id

ERROR: [DM_DATA_DICT_E_AGGR_DOMAIN_CANT_FETCH]

SEVERITY: ERROR
DESCRIPTION: D Cannot fetch – Invalid object ID %s.
CAUSE: Could not fetch an object with the given id.
ACTION: This is probably caused by a bad ID. Or, possibly, a connection to the Documentum server could not be established.
PARAMS:

ERROR: [DM_DATA_DICT_E_FKEY_ATTR_TYPE_MISMATCH]

SEVERITY: ERROR
DESCRIPTION: DSSSSSS In the foreign key (%s) for type %s the child attribute %s is of type %s, but the parent type %s attribute %s is of type %s.
CAUSE: The attributes at corresponding positions in the child attribute list and the parent attribute list for a foreign key are of different types.
ACTION: Make the attributes agree in data type.
PARAMS: The first parameter is the object id of the key object. The second parameter is the name of the child type. The third parameter is the child attribute name. The forth parameter is the child attribute data type. The fifth parameter is the name of the parent type. The sixth parameter is the parent attribute name. The seventh parameter is the parent attribute data type.

ERROR: [DM_DATA_DICT_E_UPDATE_ID_NULL]

SEVERITY: ERROR
DESCRIPTION: SD An attempt was made to update the ID attribute %s with the value %s (currently used as a NULL marker) which will cause the parents value to be inherited. If this is desired use the keyword NULL.
CAUSE: An update was attempted directly using the NULL ID value.
ACTION: Use the keyword NULL.
PARAMS: The first parameter is the name of the ID attribute being updated. The second parameter is the value used.

ERROR: [DM_DATA_DICT_E_REPLICA_LOAD_FAILURE]

SEVERITY: ERROR
DESCRIPTION: The Data Dictionary encountered an error during the load of Data Dictionary replica objects
CAUSE: The Data Dictionary encountered an error during the load of replica objects
ACTION: Refer to the additional error messages for more details on the failure.
PARAMS: None

ERROR: [DM_DATA_DICT_W_EXPUNGE_VALUE_ASSIST_CANT_FETCH]

SEVERITY: WARNING
DESCRIPTION: D Could not fetch the dm_value_assist object with ID %s during an expunge operation.
CAUSE: Could not fetch an object with the given id.
ACTION: None necessary. The expunge operation continued.
PARAMS: The parameter is the object id.

ERROR: [DM_DATA_DICT_W_EXPUNGE_AGGR_DOMAIN_CANT_FETCH]

SEVERITY: WARNING
DESCRIPTION: D Could not fetch the dm_aggr_domain object with ID %s during an expunge operation.
CAUSE: Could not fetch an object with the given id.
ACTION: None necessary. The expunge operation continued.
PARAMS: The parameter is the object id.

ERROR: [DM_DATA_DICT_W_EXPUNGE_VALUE_QUERY_CANT_FETCH]

SEVERITY: WARNING
DESCRIPTION: D Could not fetch the dm_value_query object with ID %s during an expunge operation.
CAUSE: Could not fetch an object with the given id.
ACTION: None necessary. The expunge operation continued.
PARAMS: The parameter is the object id.

ERROR: [DM_DATA_DICT_W_EXPUNGE_VALUE_LIST_CANT_FETCH]

SEVERITY: WARNING
DESCRIPTION: D Could not fetch the dm_value_list object with ID %s during an expunge operation.
CAUSE: Could not fetch an object with the given id.
ACTION: None necessary. The expunge operation continued.
PARAMS: The parameter is the object id.

ERROR: [DM_DATA_DICT_W_EXPUNGE_EXPR_CODE_CANT_FETCH]

SEVERITY: WARNING
DESCRIPTION: D Could not fetch the dmi_expr_code object with ID %s during an expunge operation.
CAUSE: Could not fetch an object with the given id.
ACTION: None necessary. The expunge operation continued.
PARAMS: The parameter is the object id.

ERROR: [DM_DATA_DICT_W_EXPUNGE_DOMAIN_CANT_FETCH]

SEVERITY: WARNING
DESCRIPTION: D Could not fetch the dm_domain object with ID %s during an expunge operation.
CAUSE: Could not fetch an object with the given id.
ACTION: None necessary. The expunge operation continued.
PARAMS: The parameter is the object id.

ERROR: [DM_DATA_DICT_W_REPLICA_PRIMARY_KEY_INCONSISTENCY]

SEVERITY: WARNING
DESCRIPTION: The Replicated Data Dictionary information for %s has a primary key constraint with id %s that references one or more invalid attributes.
CAUSE: During the validation of replicated Data Dictionary information, a primary key constraint that references one or more non-existent attributes. This typically occurs when type definitions in the source and target docbase do not match.
ACTION: It is recommended that type definitions in distributed docbases match. It is possible that some Data Dictionary information will not make sense when the type definitions do not match.
PARAMS: The first parameter is the data dictionary handle. The second parameter is the id of the primary key constraint object.

ERROR: [DM_DATA_DICT_W_EXPUNGE_FOREIGN_KEY_CANT_FETCH]

SEVERITY: WARNING
DESCRIPTION: D Could not fetch the dm_foreign_key object with ID %s during an expunge operation.
CAUSE: Could not fetch an object with the given id.
ACTION: None necessary. The expunge operation continued.
PARAMS: The parameter is the object id.

ERROR: [DM_DATA_DICT_W_EXPUNGE_UNIQUE_KEY_CANT_FETCH]

SEVERITY: WARNING
DESCRIPTION: D Could not fetch the dm_key object with ID %s during an expunge operation.
CAUSE: Could not fetch an object with the given id.
ACTION: None necessary. The expunge operation continued.
PARAMS: The parameter is the object id.

ERROR: [DM_DATA_DICT_W_REPLICA_DISPLAY_CONFIG_NONEXISTENT_ATTRIBUTE]

SEVERITY: WARNING
DESCRIPTION: DSS The Replica dm_display_config object with ID %s, attribute_source %s, reference a non-existent attribute %s.
CAUSE: During the validation of a replicated dm_display_config object, the Data Dictionary encountered a non-existent attribute in a dm_display_config object. This typically occurs when type definitions in the source and target docbase do not match.
ACTION: It is recommended that type definitions in distributed docbases match. It is possible that some Data Dictionary information will not make sense when the type definitions do not match.
PARAMS: The first parameter is the object ID of the dm_display_config object The second parameter is the attribute_source for the object The third parameter is the non-existent attribute

ERROR: [DM_DATA_DICT_W_REPLICA_VALUE_ASSISTANCE_INCONSISTENCY]

SEVERITY: WARNING
DESCRIPTION: The Replicated Data Dictionary information for %s has a conditional value assistance with id %s that references one or more invalid attributes.
CAUSE: During the validation of replicated Data Dictionary information, a conditional value assistance that references one or more non-existent attributes. This typically occurs when type definitions in the source and target docbase do not match.
ACTION: It is recommended that type definitions in distributed docbases match. It is possible that some Data Dictionary information will not make sense when the type definitions do not match.
PARAMS: The first parameter is the data dictionary handle. The second parameter is the id of the conditional value assistance.

ERROR: [DM_DATA_DICT_W_EXPUNGE_VALUE_FUNC_CANT_FETCH]

SEVERITY: WARNING
DESCRIPTION: D Could not fetch the dm_value_func object with ID %s during an expunge operation.
CAUSE: Could not fetch an object with the given id.
ACTION: None necessary. The expunge operation continued.
PARAMS: The parameter is the object id.

ERROR: [DM_DATA_DICT_W_EXPUNGE_CANT_FETCH]

SEVERITY: WARNING
DESCRIPTION: SD Could not fetch the %s object with ID %s during an expunge operation.
CAUSE: Could not fetch an object with the given id.
ACTION: None necessary. The expunge operation continued.
PARAMS: The parameter is the object id.

ERROR: [DM_DATA_DICT_W_EXPUNGE_DD_INFO_CANT_FETCH]

SEVERITY: WARNING
DESCRIPTION: D Could not fetch the dm_dd_info object with ID %s during an expunge operation.
CAUSE: Could not fetch an object with the given id.
ACTION: None necessary. The expunge operation continued.
PARAMS: The parameter is the object id.

ERROR: [DM_DATA_DICT_W_EXPUNGE_NLS_DD_INFO_CANT_FETCH]

SEVERITY: WARNING
DESCRIPTION: D Could not fetch the dm_nls_dd_info object with ID %s during an expunge operation.
CAUSE: Could not fetch an object with the given id.
ACTION: None necessary. The expunge operation continued.
PARAMS: The parameter is the object id.

ERROR: [DM_DATA_DICT_W_REPLICA_FOREIGN_KEY_INCONSISTENCY]

SEVERITY: WARNING
DESCRIPTION: The Replicated Data Dictionary information for %s has a foreign key constraint with id %s that references one or more invalid attributes.
CAUSE: During the validation of replicated Data Dictionary information, a foreign key constraint that references one or more non-existent attributes. This typically occurs when type definitions in the source and target docbase do not match.
ACTION: It is recommended that type definitions in distributed docbases match. It is possible that some Data Dictionary information will not make sense when the type definitions do not match.
PARAMS: The first parameter is the data dictionary handle. The second parameter is the id of the foreign key constraint object.

ERROR: [DM_DATA_DICT_W_REPLICA_COND_COMPUTED_EXPR_INCONSISTENCY]

SEVERITY: WARNING
DESCRIPTION: The Replicated Data Dictionary information for %s has a conditional computed expression with id %s that references one or more invalid attributes.
CAUSE: During the validation of replicated Data Dictionary information, a conditional computed expression that references one or more non-existent attributes. This typically occurs when type definitions in the source and target docbase do not match.
ACTION: It is recommended that type definitions in distributed docbases match. It is possible that some Data Dictionary information will not make sense when the type definitions do not match.
PARAMS: The first parameter is the data dictionary handle. The second parameter is the id of the conditional computed expression.

ERROR: [DM_DATA_DICT_W_REPLICA_DEFAULT_VALUE_INCONSISTENCY]

SEVERITY: WARNING
DESCRIPTION: SSD The Replicated Data Dictionary information for %s has a default value with id %s that references one or more invalid attributes.
CAUSE: During the validation of replicated Data Dictionary information, a default value that references one or more non-existent attributes. This typically occurs when type definitions in the source and target docbase do not match.
ACTION: It is recommended that type definitions in distributed docbases match. It is possible that some Data Dictionary information will not make sense when the type definitions do not match.
PARAMS: The first parameter is the data dictionary handle. The second parameter is the id of the default value expression.

ERROR: [DM_DATA_DICT_W_REPLICA_UNIQUE_KEY_INCONSISTENCY]

SEVERITY: WARNING
DESCRIPTION: The Replicated Data Dictionary information for %s has a unique key constraint with id %s that references one or more invalid attributes.
CAUSE: During the validation of replicated Data Dictionary information, a unique key constraint that references one or more non-existent attributes. This typically occurs when type definitions in the source and target docbase do not match.
ACTION: It is recommended that type definitions in distributed docbases match. It is possible that some Data Dictionary information will not make sense when the type definitions do not match.
PARAMS: The first parameter is the data dictionary handle. The second parameter is the id of the unique key constraint object.

ERROR: [DM_DATA_DICT_W_EXPUNGE_KEY_CANT_FETCH]

SEVERITY: WARNING
DESCRIPTION: D Could not fetch the dm_key object with ID %s during an expunge operation.
CAUSE: Could not fetch an object with the given id.
ACTION: None necessary. The expunge operation continued.
PARAMS: The parameter is the object id.

ERROR: [DM_DATA_DICT_W_REPLICA_REFERENCES_NONEXISTENT_ATTRIBUTE]

SEVERITY: WARNING
DESCRIPTION: SS The Replicated Data Dictionary information for %s references a non-existent attribute %s. This typically indicates that the type definitions in the source and target docbase do not match.
CAUSE: During the validation of replicated Data Dictionary information, references to one or more non-existent attributes were found. This typically occurs when type definitons in the source and target docbase do not match.
ACTION: It is recommended that type definitions in distributed docbases match. It is possible that some Data Dictionary information will not make sense when the type definitions do not match.
PARAMS: The first parameter is the data dictionary handle The second parameter is the non-existent attribute that is referenced

ERROR: [DM_DATA_DICT_W_REPLICA_VAL_CONSTRAINT_INCONSISTENCY]

SEVERITY: WARNING
DESCRIPTION: The Replicated Data Dictionary information for %s has a value constraint with id %s that references one or more invalid attributes.
CAUSE: During the validation of replicated Data Dictionary information, a value constraint that references one or more non-existent attributes. This typically occurs when type definitions in the source and target docbase do not match.
ACTION: It is recommended that type definitions in distributed docbases match. It is possible that some Data Dictionary information will not make sense when the type definitions do not match.
PARAMS: The first parameter is the data dictionary handle. The second parameter is the id of the value constraint object.

ERROR: [DM_DATA_DICT_I_PUBLISH]

SEVERITY: INFORMATION
DESCRIPTION: SS The Data Dictionary is publishing information for %s, in locale %s.
CAUSE: This is an informational message used when tracing is turned on for specific Data Dictionary operations.
ACTION: None PARAMTERS: The first parameter is the virtual identifier for the object being published The second parameter is the language for which the information is being published.
PARAMS:

ERROR: [DM_DATA_DICT_I_CLEANUP_TRACE_PROBLEM]

SEVERITY: INFORMATION
DESCRIPTION: DSDS Object %s of type %s refers to non-existent object %s in field %s. Reference will be removed.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DATA_DICT_I_CLEANUP_TRACE_GENERIC]

SEVERITY: INFORMATION
DESCRIPTION: SS Type: %s. Message: %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DATA_DICT_I_AGGR_DOMAIN_FIXUP]

SEVERITY: INFORMATION
DESCRIPTION: D The Data Dictionary is fixing up the aggrdomain object with id %s
CAUSE: The Data Dictionary is fixing up the aggrdomain object automatically due to some inconsistency. No user intervention is required
ACTION:
PARAMS:

nahoru

DM_DATA_PARTITION

ERROR: [DM_DATA_PARTITION_E_TYPE_NOT_PARTITIONED]

SEVERITY: ERROR
DESCRIPTION: S Type %s is not partitioned.
CAUSE: You tried apply partition operations or tried querying a type that is not yet partitioned.
ACTION: You can only apply partition operations or query a partitioned type.
PARAMS: Type name.

ERROR: [DM_DATA_PARTITION_E_INCORRECT_ARGUMENT]

SEVERITY: ERROR
DESCRIPTION: SS You cannot specify parameter %s for operation %s of GENERATE_PARTITION_SCHEME_SQL apply method.
CAUSE: You have specified incorrect parameters for an operation of the GENERATE_PARTITION_SCHEME_SQL apply method.
ACTION: Remove the unexpected parameters.
PARAMS: parameter name and operation name.

ERROR: [DM_DATA_PARTITION_E_SWITCHIN_TABLE_NOT_EXIST]

SEVERITY: ERROR
DESCRIPTION: The table to be switched in doesnt exist
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DATA_PARTITION_E_DUPLICATE_PARTITION_NAME]

SEVERITY: ERROR
DESCRIPTION: Partition names should be unique for dm_partition_scheme object. PARAMETER: None
CAUSE: You provide duplicate partition names to the dm_partition_scheme object.
ACTION: Make sure that the partition_names of this dm_partition_scheme object are unique.
PARAMS:

ERROR: [DM_DATA_PARTITION_E_REGTABLE_ALREADY_PARTITIONED]

SEVERITY: ERROR
DESCRIPTION: S Table %s is already partitioned.
CAUSE: You tried to partition a table that is already partitioned.
ACTION: You can only partition a nonpartitioned table.
PARAMS:

ERROR: [DM_DATA_PARTITION_E_ALL_PARTITIONED]

SEVERITY: ERROR
DESCRIPTION: All partitionable types are already partitioned. PARAMETER: None
CAUSE: You tried to execute the db_partition operation of the GENERATE_PARTITION_SCHEME_SQL apply method, but all partitionable types have already been partitioned.
ACTION: None
PARAMS:

ERROR: [DM_DATA_PARTITION_E_ACL_CANNOT_UPDATE_PARTITION]

SEVERITY: ERROR
DESCRIPTION: S You cannot update i_partition internal attribute for external dm_acl object %s. PARAMETER: object name of the dm_acl object.
CAUSE: You have tried to update the internal attribute i_partition of an external dm_acl object.
ACTION: Dont try to do this. It is not allowed.
PARAMS:

ERROR: [DM_DATA_PARTITION_E_CANT_PARTITION_TYPE_TABLE]

SEVERITY: ERROR
DESCRIPTION: SS Table %s is an internal table for type %s. PARAMETER: Table name & type name.
CAUSE: You have attempted to apply partition functions to internal tables created for documentum type.
ACTION: You should partition the type, instead of its internal tables.
PARAMS:

ERROR: [DM_DATA_PARTITION_E_MISSING_SOURCE_NAME]

SEVERITY: ERROR
DESCRIPTION: Value of SOURCE_NAME parameter cannot be empty.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DATA_PARTITION_E_TYPE_ALREADY_PARTITIONED]

SEVERITY: ERROR
DESCRIPTION: S Type %s is already partitioned.
CAUSE: You tried to partition a type that is already partitioned.
ACTION: You can only partition a nonpartitioned type.
PARAMS:

ERROR: [DM_DATA_PARTITION_E_MISSING_OWNER_NAME]

SEVERITY: ERROR
DESCRIPTION: S When applying DB_PARTITION to registered table %s, its owner_name is missing. PARAMETER: Name of the register table to be DB_PARTITIONed.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DATA_PARTITION_E_DEPRECATE_OPERATION]

SEVERITY: ERROR
DESCRIPTION: The apply method GENTERATE_PARTITION_SCHEME_SQL is deprecated, please use PARTITION_OPERATION instead. PARAMETER: None.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DATA_PARTITION_E_EMPTY_TYPE_NAME]

SEVERITY: ERROR
DESCRIPTION: When applying DB_PARTITION to type, type name cannot be empty. PARAMETER: None
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DATA_PARTITION_E_SOURCE_NAME_INVALID]

SEVERITY: ERROR
DESCRIPTION: S The source name argument: %s is invalid.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DATA_PARTITION_E_DOCBASE_NOT_PARTITIONED]

SEVERITY: ERROR
DESCRIPTION: The docbase is not partitioned. PARAMETER: None
CAUSE: You have tried to generate a script to partition an individual type but the docbase is not partitioned yet.
ACTION: You need to partition the docbase first.
PARAMS:

ERROR: [DM_DATA_PARTITION_E_MISSING_TEMP_TABLE_SUFFIX]

SEVERITY: ERROR
DESCRIPTION: Value of TEMP_TABLE_SUFFIX parameter cannot be empty.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DATA_PARTITION_E_INVALID_ARGUMENTS]

SEVERITY: ERROR
DESCRIPTION: SS You can not specify both %s and %s for GENERATE_PARTITION_SCHEME_SQL apply method.
CAUSE: You have specified both exclusive parameters such as TYPE_NAME and TABLE_NAME, TYPE_NAME and OWNER_NAME in the GENERATE_PARTITION_SCHEME_SQL apply method.
ACTION: Should only specify one of them.
PARAMS:

ERROR: [DM_DATA_PARTITION_E_MUST_BE_SUPERMOST_TYPE]

SEVERITY: ERROR
DESCRIPTION: SS Operation %s for the GENERATE_PARTITION_SCHEME_SQL apply method can only be applied to super-most type, but type %s is not one.
CAUSE: You may have provided a subtype for the DB_PARTITION/ADD_PARTITION operation in the GENERATE_PARTITION_SCHEME_SQL apply method.
ACTION: Only provide a supermost type for these operations.
PARAMS: Operation name and type name.

ERROR: [DM_DATA_PARTITION_E_FAIL_EXECUTE_SCRIPT]

SEVERITY: ERROR
DESCRIPTION: S Fail to execute the script, may have not enough priviledge, please first run the command: Grant Create Any Table to %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DATA_PARTITION_E_TABLE_ALREADY_PARTITIONED]

SEVERITY: ERROR
DESCRIPTION: SS The table %s is already partitioned with scheme object %s. PARAMETER: Name of the table and name of scheme object.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DATA_PARTITION_E_NO_OBJNAME_FOR_SCHEME]

SEVERITY: ERROR
DESCRIPTION: There is no object_name for the scheme object. PARAMETER: None
CAUSE: When you try to save a dm_partition_scheme object, its object_name attribute is NULL.
ACTION: You should provide object_name for the dm_partition_scheme object.
PARAMS:

ERROR: [DM_DATA_PARTITION_E_ACTION]

SEVERITY: ERROR
DESCRIPTION: Provide same counts of value for the above three repeating attributes.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DATA_PARTITION_E_TYPE_NOT_FOUND]

SEVERITY: ERROR
DESCRIPTION: SS The type %s is not found which is registered with partition scheme %s. PARAMETER: Name of the type and scheme object.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DATA_PARTITION_E_WRONG_ARGUMENT_COUNT]

SEVERITY: ERROR
DESCRIPTION: S The counts of arguments: partition_name, range, tablespace are incorrect for operation %s. PARAMETER: Name of operation.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DATA_PARTITION_E_MISSING_TABLE_OR_TYPE]

SEVERITY: ERROR
DESCRIPTION: S Operation %s for the GENERATE_PARTITION_SCHEME_SQL apply method requires a table/type. PARAMETER: Table name or type name.
CAUSE: You did not provide a table name or type name which is requireed for the operation.
ACTION: Add a table name or type name in the command to apply the operation.
PARAMS:

ERROR: [DM_DATA_PARTITION_E_PARTITION_NOT_EMPTY]

SEVERITY: ERROR
DESCRIPTION: The partition to be switched into isnt empty
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DATA_PARTITION_E_UNKNOWN_OPERATION]

SEVERITY: ERROR
DESCRIPTION: S Operation %s is not recognized for GENERATE_PARTITION_SCHEME_SQL apply method.
CAUSE: An unknown operation is passed for the GENERATE_PARTITION_SCHEME_SQL apply method.
ACTION: Valid operations are db_partition, add_partition, exchange_partition. PARAMETER: Subcommand that is passed to the apply method.
PARAMS:

ERROR: [DM_DATA_PARTITION_E_NO_SCHEME]

SEVERITY: ERROR
DESCRIPTION: S Partition scheme object is not found with object_name %s. PARAMETER: Object_name for dm_partition_scheme.
CAUSE: You are trying to do parition process on a non-existed scheme object.
ACTION: Make sure there is a partition schemem object with the provided object_name.
PARAMS:

ERROR: [DM_DATA_PARTITION_E_SCHEME_IS_NOT_VALIDATED]

SEVERITY: ERROR
DESCRIPTION: S The Partition Scheme %s is not validated
CAUSE: The Partition Schemes is_validated attribute is false
ACTION: Validate the partition scheme
PARAMS:

ERROR: [DM_DATA_PARTITION_E_CANNOT_SET_SCHEME_OWNERNAME]

SEVERITY: ERROR
DESCRIPTION: dm_partition_schemes owner_name cannot be set explicitly by you. PARAMETER: None
CAUSE: When you create a dm_partition_scheme object, you provide a value for owner_name attribute.
ACTION: Do not provide value for attribute owner_name, Content Server will use the current user as its value.
PARAMS:

ERROR: [DM_DATA_PARTITION_E_ADD_PARTITION_RANGE]

SEVERITY: ERROR
DESCRIPTION: I The range %d you specified to ADD_PARTITION is smaller than the last range of the scheme object. PARAMETER: Value of the up range.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DATA_PARTITION_E_REGTABLE_NOT_PARTITIONED]

SEVERITY: ERROR
DESCRIPTION: S Table %s is not partitioned.
CAUSE: You tried apply partition operations to a table that is not yet partitioned.
ACTION: You can only apply partition operations to a partitioned table.
PARAMS: Table name.

ERROR: [DM_DATA_PARTITION_E_DELETE_PARTITION_WRONG]

SEVERITY: ERROR
DESCRIPTION: SS The partition %s you want to delete is not the last partition in scheme object %s. PARAMETER: Name of the partition you want to delete.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DATA_PARTITION_E_SPLIT_PARTITION_RANGE]

SEVERITY: ERROR
DESCRIPTION: I The range %d you specified to SPLIT_PARTITIOM is larger than the last range of the scheme object. PARAMETER: Value of the up range.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DATA_PARTITION_E_PENDING_PARTITION_PROCESS]

SEVERITY: ERROR
DESCRIPTION: S There is a pending off-line partition process registered with scheme object %s, please run the generated sql script before any operation on this scheme object. PARAMETER: Name of the scheme object.
CAUSE: A pending off-line process is not finished before the current partition process.
ACTION: Run the generated sql script of the pending process before the current partition process.
PARAMS:

ERROR: [DM_DATA_PARTITION_E_SUBTYPE_CANNT_ENABLE_PARTITION]

SEVERITY: ERROR
DESCRIPTION: S You can only enable partition for a super type. Type %s is not a super type. PARAMETER: Type name.
CAUSE: You tried to execute alter type … enable partition DQL query against a subtype. This is not allowed.
ACTION: You can only execute this statement against a super type.
PARAMS:

ERROR: [DM_DATA_PARTITION_E_SCHEME_PART_INFO_CNT_MISMATCH]

SEVERITY: ERROR
DESCRIPTION: You should provide same count of partition_up_range, partition_file_group, and partition_name. PARAMETER: None
CAUSE: When creating a dm_partition_scheme object, the counts for repeating attributes partition_up_range, partition_file_group, and partition_name is not same.
ACTION:
PARAMS:

ERROR: [DM_DATA_PARTITION_E_INVALID_TABLE_NAME]

SEVERITY: ERROR
DESCRIPTION: S the table name %s is not valid
CAUSE: The table name is invalid
ACTION: Provide a valid table name
PARAMS:

ERROR: [DM_DATA_PARTITION_E_MERGE_PARTITION_WRONG]

SEVERITY: ERROR
DESCRIPTION: SS The partition %s you want to merge is not found or is the last partition in scheme object %s. PARAMETER: Name of the partition you want to merge.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DATA_PARTITION_E_SCHEME_OBJECT_HAS_UNSORTED_RANGES]

SEVERITY: ERROR
DESCRIPTION: The up ranges of dm_partition_scheme object is unsorted. PARAMETER: None
CAUSE: You provide unsorted partition_up_range values for dm_partition_scheme object.
ACTION: Sorting the up ranges before you provide them to the dm_partition_scheme object.
PARAMS:

ERROR: [DM_DATA_PARTITION_E_TYPE_ALREADY_PARTITIONED_EX]

SEVERITY: ERROR
DESCRIPTION: SS The type %s is already partitioned with scheme object %s. PARAMETER: Name of the type and name of scheme object.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DATA_PARTITION_E_EMPTY_PARTITION_SCHEME]

SEVERITY: ERROR
DESCRIPTION: SS The operation %s can not be applied on the empty partition scheme %s. PARAMETER: Name of the operation and name of the partition scheme object.
CAUSE: ACTION:
ACTION:
PARAMS:

ERROR: [DM_DATA_PARTITION_E_TABLE_NOT_EMPTY]

SEVERITY: ERROR
DESCRIPTION: The table to be switched into isnt empty
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DATA_PARTITION_E_DUPLICATE_SCHEME_OBJECT]

SEVERITY: ERROR
DESCRIPTION: You are trying to create or update a dm_partition_scheme object with the same object_name of an existed ojbect. PARAMETER: None
CAUSE: When trying saving a dm_partition_scheme object, there is already an object with the same object_name there.
ACTION: Make sure that the object_name of this dm_partition_scheme object is unique.
PARAMS:

ERROR: [DM_DATA_PARTITION_E_MISSING_TABLESPACE]

SEVERITY: ERROR
DESCRIPTION: S Value of TABLESPACE parameter cannot be empty for operation %s of the GENERATE_PARTITION_SCHEME_SQL apply method. PARAMETER: Operation name.
CAUSE: You tried to execute the db_partition/add_partition operation of the GENERATE_PARTITION_SCHEME_SQL apply method without giving tablespace parameter.
ACTION: You need to specify the tablespace parameter.
PARAMS:

ERROR: [DM_DATA_PARTITION_E_EMPTY_PARTITION_NAME]

SEVERITY: ERROR
DESCRIPTION: Partition names can not be empty. PARAMETER: None
CAUSE: You provide an empty partition name for a partition.
ACTION: Make sure there is no empty partition name in your RPC parameters.
PARAMS:

ERROR: [DM_DATA_PARTITION_E_TABLE_NAME_OWNER_COUNT_MISMATCH]

SEVERITY: ERROR
DESCRIPTION: The counts of argument table_name and table_owner are not the same. PARAMETER: None
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DATA_PARTITION_E_NO_SUCH_PARTITION]

SEVERITY: ERROR
DESCRIPTION: SS The partition %s you specified is not found in the partition scheme %s. PARAMETER: Name of the partition you want to process and name of the partition scheme object.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DATA_PARTITION_E_NOT_ENOUGH_PRIVILEDGE_FOR_CREATE_SCHEME]

SEVERITY: ERROR
DESCRIPTION: You do not have enough priviledge for creating dm_partition_scheme object, only SysAdmin/Superuser can do it. PARAMETER: None
CAUSE: A non-SysAdmin/non-Superuser tried to create a dm_partition_scheme object.
ACTION: Make sure that you have at least SysAdmin priviledge to create dm_partition_scheme object.
PARAMS:

ERROR: [DM_DATA_PARTITION_E_CAN_ONLY_UPDATE_OBJECT_NAME_FOR_SCHEME]

SEVERITY: ERROR
DESCRIPTION: You can only update dm_partition_scheme object by changing its object_name. PARAMETER: None
CAUSE: You update dm_partition_scheme object by changing its attributes other than object_name.
ACTION: Make sure only attribute object_name being updated before you update dm_partition_scheme object.
PARAMS:

ERROR: [DM_DATA_PARTITION_E_EMPTY_TABLE_NAME]

SEVERITY: ERROR
DESCRIPTION: When applying DB_PARTITION to registered table, table name cannot be empty. PARAMETER: None
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DATA_PARTITION_E_NO_PARTITION_COLUMN_IN_REGTABLE]

SEVERITY: ERROR
DESCRIPTION: S Table %s does not have i_partition column.
CAUSE: You have tried to execute data partition related method on a table without the i_partition column.
ACTION: You need to have i_partition column in order to execute data partition related method on a table.
PARAMS: Table name or type name.

ERROR: [DM_DATA_PARTITION_E_NO_TYPE_AND_TABLE]

SEVERITY: ERROR
DESCRIPTION: There is no type or table arguments for DB_PARTITION process. PARAMETER: None
CAUSE: Youre trying to do DB_PARTITION without providing any type_name or table_name.
ACTION: Provide some type_name or table_name.
PARAMS:

ERROR: [DM_DATA_PARTITION_E_PARTITION_NOT_FOUND]

SEVERITY: ERROR
DESCRIPTION: S The partition %s is not found
CAUSE: The partition is not found
ACTION: create the partition or use an existing partition
PARAMS:

ERROR: [DM_DATA_PARTITION_E_LAST_PARTITION_DEPRECATE]

SEVERITY: ERROR
DESCRIPTION: The parameter LAST_PARTITION was deprecated! PARAMETER: None
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DATA_PARTITION_W_APPLY_SCHME_MULTITIMES]

SEVERITY: WARNING
DESCRIPTION: SS Type or table %s are already partitioned with scheme %s.
CAUSE:
ACTION:
PARAMS: Name of the type (or table) and the partition scheme object.

ERROR: [DM_DATA_PARTITION_W_MERGE_FIRST_PARTITION]

SEVERITY: WARNING
DESCRIPTION: SS The partition %s you want to merge is the first partition in scheme object %s. PARAMETER: Name of the partition you want to merge.
CAUSE:
ACTION:
PARAMS:

nahoru

DM_DCNFG

ERROR: [DM_DCNFG_F_CLIENTRIGHTS_BAD_VSTAMP]

SEVERITY: FATAL
DESCRIPTION: II Version stamp %d was expected to be %d.
CAUSE: The version stamp that the dm_client_rights facility expected was different from the actual version stamp in the database.
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:

ERROR: [DM_DCNFG_F_CLIENTRIGHTS_STORE_TYPE]

SEVERITY: FATAL
DESCRIPTION: Error creating dm_client_rights type.
CAUSE: Internal error during docbase creation or upgrade.
ACTION: Check server log for other error messages providing more detail.
PARAMS:

ERROR: [DM_DCNFG_F_INIT3]

SEVERITY: FATAL
DESCRIPTION: The type manager returned an error storing the docbase_config type.
CAUSE: Unknown.
ACTION: Look at the error logged by the type manager. Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_DCNFG_F_CLIENTREG_BAD_VSTAMP]

SEVERITY: FATAL
DESCRIPTION: II Version stamp %d was expected to be %d.
CAUSE: The version stamp that the dm_client_registration facility expected was different from the actual version stamp in the database.
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:

ERROR: [DM_DCNFG_F_INIT2]

SEVERITY: FATAL
DESCRIPTION: II Version stamp %d was expected to be %d.
CAUSE: The version stamp that the docbase_config object software expected was different from the actual version stamp in the database.
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:

ERROR: [DM_DCNFG_F_INT1]

SEVERITY: FATAL
DESCRIPTION: S The following database query %s could not be executed.
CAUSE: Inconsistency between the server and the docbase_config type.
ACTION: Look at the error logged by the database. Report this message and any parameters to your Documentum Site Representative.
PARAMS:

ERROR: [DM_DCNFG_F_FEDERATION_BAD_VSTAMP]

SEVERITY: FATAL
DESCRIPTION: II Version stamp %d was expected to be %d.
CAUSE: The version stamp that the dm_federation object software expected was different from the actual version stamp in the database.
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:

ERROR: [DM_DCNFG_F_INIT1]

SEVERITY: FATAL
DESCRIPTION: The docbase_config type was found in the database without a version stamp.
CAUSE: Unknown.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_DCNFG_F_INIT4]

SEVERITY: FATAL
DESCRIPTION: The type manager returned an error converting the dm_docbase_config type.
CAUSE: Unknown.
ACTION: Look at the error message logged by the type manager. Report this message and any parameters to your Documentum Site Representative.
PARAMS:

ERROR: [DM_DCNFG_F_CLIENTREG_STORE_TYPE]

SEVERITY: FATAL
DESCRIPTION: Error creating dm_client_registration type.
CAUSE: Internal error during docbase creation or upgrade.
ACTION: Check server log for other error messages providing more detail.
PARAMS:

ERROR: [DM_DCNFG_F_FEDERATION_STORE_TYPE]

SEVERITY: FATAL
DESCRIPTION: The type manager returned an error storing the dm_federation type.
CAUSE: Unknown.
ACTION: Look at the error logged by the type manager. Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_DCNFG_F_UPGRADE65]

SEVERITY: FATAL
DESCRIPTION: Type manager is unable to upgrade dm_docbase_config type to version 6.5.
CAUSE: Unknown.
ACTION: Look at the error message logged by the type manager. Report this message and any parameters to your Documentum Site Representative. $Id: dmdump.e,v 5.10 2003/04/18 18:46:34 strellis Exp $ dmDump class errors
PARAMS:

ERROR: [DM_DCNFG_E_INVALID_MODULE_NAME]

SEVERITY: ERROR
DESCRIPTION: The number of values for module_name does not match the number of values for module_mode. These two attributes are one to one mappings and must have the same number of values.
CAUSE: module_name and module_mode have different number of values
ACTION: Ensure that both attributes have the same number of values and that the values in module_name correspond to the the values in module_mode.
PARAMS: None

ERROR: [DM_DCNFG_E_CANT_FETCH_INVALID_ID]

SEVERITY: ERROR
DESCRIPTION: D Cannot fetch a docbase_config – Invalid object ID %s
CAUSE: Could not fetch an object with the given id.
ACTION: This is probably caused by a bad ID. Or, possibly, a connection to the Documentum server could not be established.
PARAMS:

ERROR: [DM_DCNFG_E_NEED_SU_FOR_FED_CHANGE]

SEVERITY: ERROR
DESCRIPTION: SS The current user (%s) needs to have superuser privilege to save or destroy %s dm_federation object.
CAUSE: Must have Superuser privilege to save or destroy dm_federation objects.
ACTION: Consult your system administrator.
PARAMS:

ERROR: [DM_DCNFG_E_UPDATE_MIN_OWNER_PERMIT]

SEVERITY: ERROR
DESCRIPTION: I You have specified an invalid value (%d) for the minimum owner permit.
CAUSE: You tried to set the minimum_owner_permit field of dm_docbase_config to a value that is not allowed. PARAMETER: The minimum owner permit must be set to a valid integer value. See the documentation for details.
ACTION: Use an allowed value and try again.
PARAMS:

ERROR: [DM_DCNFG_E_PKCERT_KEYID]

SEVERITY: ERROR
DESCRIPTION: I Error building key identifier for certificate value. Error code: %d.
CAUSE: Certificate objects must have a valid certificate_value field.
ACTION: Create object with valid certificate_value.
PARAMS:

ERROR: [DM_DCNFG_E_INVALID_CLIENT_VERSION]

SEVERITY: ERROR
DESCRIPTION: S The value (%s) specified for docbase_config object attribute oldest_client_version is invalid.
CAUSE: The value specified attribute oldest_client_version is invalid. Probably one of component values is out of range
ACTION: Specify a valid value for attribute oldest_client_version.
PARAMS: The specified value.

ERROR: [DM_DCNFG_E_SET_OLDEST_CLIENT_VERSION_FIRST]

SEVERITY: ERROR
DESCRIPTION: The docbase_config object attribute oldest_client_version has to be set before setting attribute check_client_version to T.
CAUSE: Docbase_config object attribute oldest_client_version has not been set when setting attribute check_client_version to T.
ACTION: Set a proper value for docbase_config attribute oldest_client_version first.
PARAMS: None.

ERROR: [DM_DCNFG_E_CANT_SAVE]

SEVERITY: ERROR
DESCRIPTION: S Cannot save %s docbase_config.
CAUSE: One or more operations has failed during this save. Consult the following error message(s) for more help.
ACTION: Try again after fixing previous problems.
PARAMS:

ERROR: [DM_DCNFG_E_CANT_CHANGE_TO_ACL]

SEVERITY: ERROR
DESCRIPTION: S Can not change security mode from %s to ACL since ACL conversion has not been performed. Execute dm_convertto_acl to do the conversion.
CAUSE: The user tried to change security mode from non-ACL mode to ACL mode when the i_stamp is 0.
ACTION: System only allows security mode to be changed from non-ACL to ACL mode, not the other way around. A docbase is in ACL mode only when the following two conditions are satisfied: (1) the security_mode of its docbase config object is acl, and (2) the i_stamp of the dmi_vstamp object is greater than 0. Once, the security mode can only set to acl when the i_stamp is greater than 0.
PARAMS:

ERROR: [DM_DCNFG_E_INVALID_VALUE_FOR_MAX_AUTH_ATTEMPT]

SEVERITY: ERROR
DESCRIPTION: I The docbase_config object has an invalid max_auth_attempt value of %d. It must be an integer greater than or equal to zero.
CAUSE: The docbase_config object has a negative value for max_auth_attempt.
ACTION: Correct the value of the max_auth_attempt attribute. It must be a positive integer.
PARAMS: The parameter is the value supplied for max_auth_attempt

ERROR: [DM_DCNFG_E_INVALID_SECURITY]

SEVERITY: ERROR
DESCRIPTION: S Invalid security mode %s found in dm_docbase_config.
CAUSE: The user tried to specify an invalid security mode.
ACTION: Specify a valid security mode: none, document, cabinet, combined
PARAMS:

ERROR: [DM_DCNFG_E_PKCERT_NO_PRIV]

SEVERITY: ERROR
DESCRIPTION: S User %s does not have permission to create this dm_public_key_certificate object.
CAUSE: Some certificate objects require privilege for creation.
ACTION: User with appropriate privilege must create the object.
PARAMS:

ERROR: [DM_DCNFG_E_RIGHTS_NOT_AUTHENTICATED]

SEVERITY: ERROR
DESCRIPTION: S Client %s was not authenticated and cannot host privileged roles.
CAUSE: A protected role was asserted in an application that was not or could not be authenticated at the time this session was established.
ACTION: Check if client application is listed in the docbase rights database.
PARAMS:

ERROR: [DM_DCNFG_E_CLIENTRIGHTS_NO_PRIV]

SEVERITY: ERROR
DESCRIPTION: S User %s does not have permission to create this dm_client_rights object.
CAUSE: Client rights objects require privilege for creation.
ACTION: User with appropriate privilege must create the object.
PARAMS:

ERROR: [DM_DCNFG_E_PKCERT_ILLEGAL_VALUE]

SEVERITY: ERROR
DESCRIPTION: SS The value %s is not legal for field %s of dm_public_key_certificate.
CAUSE: An attempt was made to create a dm_public_key_certificate object with an illegal value for a required field.
ACTION: Correct the data value for the specified field.
PARAMS:

ERROR: [DM_DCNFG_E_CLIENTRIGHTS_ILLEGAL_VALUE]

SEVERITY: ERROR
DESCRIPTION: SS The value %s is not legal for field %s of dm_client_rights.
CAUSE: An attempt was made to create a dm_client_rights object with an illegal value for a required field.
ACTION: Correct the data value for the specified field.
PARAMS:

ERROR: [DM_DCNFG_E_CLIENTREG_NOT_UNIQUE]

SEVERITY: ERROR
DESCRIPTION: SS Object value (%s) not unique in field %s. Conflicts with existing object.
CAUSE: Registry entries must be unique in certain fields and an attempt was made to create a non-unique value.
ACTION: Create object with unqiue identifiers.
PARAMS:

ERROR: [DM_DCNFG_E_CANNOT_UPDATE_PARTITION_STATUS]

SEVERITY: ERROR
DESCRIPTION: Direct update on r_partition_status attribute in dm_docbase_config object is not allowed.
CAUSE: You tried to update the r_partition_status for a dm_docbase_config object
ACTION: The value of r_partition_status is for read only. The value of this attribute is maintained by Content Server.
PARAMS:

ERROR: [DM_DCNFG_E_CANT_CHANGE_MACP]

SEVERITY: ERROR
DESCRIPTION: SS Can not change mac access protocol from %s to %s.
CAUSE: User try to change mac access protocol.
ACTION: Mac access protocl can not be modified once set.
PARAMS:

ERROR: [DM_DCNFG_E_RIGHTS_NOT_AUTHORIZED]

SEVERITY: ERROR
DESCRIPTION: SS Client %s is not authorized to use role %s.
CAUSE: A protected role was asserted in an application that has not been authorized to use the role.
ACTION: Check if client application is listed in the docbase rights database. Check if client application has this role listed in the allowed_roles list of its dm_client_rights object.
PARAMS:

ERROR: [DM_DCNFG_E_PKCERT_NOT_UNIQUE]

SEVERITY: ERROR
DESCRIPTION: SS Object value (%s) not unique in field %s. Conflicts with existing object.
CAUSE: Certificate objects must be unique in certain fields and an attempt was made to create a non-unique value.
ACTION: Create object with unqiue identifiers.
PARAMS:

ERROR: [DM_DCNFG_E_MACL_REQUIRES_TRUSTED_CONTENT_SERVICES]

SEVERITY: ERROR
DESCRIPTION: In order to turn on Mandatory Access Control (MACL) functionality, you must have a Trusted Content Services (TCS) license.
CAUSE: TCS must be enabled for MACL functionality
ACTION: Obtain a TCS License key and then turn on MACL functionality. PARAMETETERS: None
PARAMS:

ERROR: [DM_DCNFG_E_PKCERT_FORMAT]

SEVERITY: ERROR
DESCRIPTION: I The certificate value is not of a format understood by the server. Error code: %d.
CAUSE: Certificate objects must have a valid certificate_value field.
ACTION: Create object with valid certificate_value.
PARAMS:

ERROR: [DM_DCNFG_E_CANT_DESTROY_FEDERATION]

SEVERITY: ERROR
DESCRIPTION: S Cannot destroy dm_federation identified by %s because the federation is active.
CAUSE: You cannot destroy a dm_federation if the governing docbase is ACTIVE. You must deactivate the federation first.
ACTION: Deactivate the federation.
PARAMS:

ERROR: [DM_DCNFG_E_INVALID_MACP]

SEVERITY: ERROR
DESCRIPTION: S Invalid mac access protocol %s.
CAUSE: The user tried to specify an invalid mac access protocol.
ACTION: Specify a valid mac access protocol: none, ushare, double.
PARAMS:

ERROR: [DM_DCNFG_E_RIGHTS_NOT_EXIST]

SEVERITY: ERROR
DESCRIPTION: S Could not find entry for client %s in the rights database.
CAUSE: Could not find a dm_client_rights object for the specified client.
ACTION: Check if client application is listed in the docbase rights database.
PARAMS:

ERROR: [DM_DCNFG_E_CANT_CHANGE_NAME]

SEVERITY: ERROR
DESCRIPTION: S Cannot change %s name of docbase_config object
CAUSE: The name of docbase_config object must always be the same as the docbase name.
ACTION: None.
PARAMS:

ERROR: [DM_DCNFG_E_BAD_FEDERATION_MEMBER_ATTRC]

SEVERITY: ERROR
DESCRIPTION: SSII In dm_federation named %s, count of %s: %d does not match the count of r_member_docbases: %d.
CAUSE: Tried to save a dm_federation with invalid member attribute count.
ACTION: Most likely the user tried to manipulate a member attribute without updating information in the other member attributes.
PARAMS:

ERROR: [DM_DCNFG_E_NEED_PRIV_FOR_CHANGE]

SEVERITY: ERROR
DESCRIPTION: SS The current user (%s) needs to have superuser or sysadmin privilege to save or destroy %s docbase_config object.
CAUSE: Must have Superuser or SysAdmin privilege to save/destroy docbase_config objects.
ACTION: Consult your system administrator.
PARAMS:

ERROR: [DM_DCNFG_E_INVALID_DEFAULT_APP_PERMIT_VALUE]

SEVERITY: ERROR
DESCRIPTION: I The docbase_config object has an invalid default_app_permit value of %d. Valid values must be between 1 (NONE) and 7 (DELETE).
CAUSE: The docbase_config object has an unrecognized value for default_app_permit.
ACTION: Correct the value of the default_app_permit attribute. It must be between 1 (NONE) and 7 (DELETE)
PARAMS: The first parameter is the value that was supplied for default_app_permit

ERROR: [DM_DCNFG_E_CANT_CHANGE_ACL]

SEVERITY: ERROR
DESCRIPTION: S Can not change security mode from ACL to %s.
CAUSE: The user tried to change security mode from ACL mode to other mode.
ACTION: System only allows security mode to be changed from non-ACL to ACL mode, not the other way around. A docbase is in ACL mode only when the following two conditions are satisfied: (1) the security_mode of its docbase config object is acl, and (2) the i_stamp of the dmi_vstamp object is greater than 0. Once, the i_stamp value is set to be greater than 0, the security mode can only set to acl or none.
PARAMS:

ERROR: [DM_DCNFG_E_CANT_FIND]

SEVERITY: ERROR
DESCRIPTION: S Cannot find %s docbase_config.
CAUSE: Could not find the docbase object by name.
ACTION: This is probably caused by invalid name or user destroying the docbase object through SQL.
PARAMS:

ERROR: [DM_DCNFG_E_PKCERT_PUBLICKEY]

SEVERITY: ERROR
DESCRIPTION: I Error getting public key from certificate value. Error code: %d.
CAUSE: Certificate objects must have a valid certificate_value field.
ACTION: Create object with valid certificate_value.
PARAMS:

ERROR: [DM_DCNFG_E_CANT_CHANGE_CRYPTO_KEY]

SEVERITY: ERROR
DESCRIPTION: The i_crypto_key attribute cannot be changed/updated.
CAUSE: An attempt is being made to change the i_crypto_key attribute.
ACTION: Do not attempt to change the i_crypto_key attribute
PARAMS:

ERROR: [DM_DCNFG_E_CLIENTREG_ILLEGAL_VALUE]

SEVERITY: ERROR
DESCRIPTION: SS The value %s is not legal for field %s of dm_client_registration.
CAUSE: An attempt was made to create a dm_client_registration object with an illegal value for a required field.
ACTION: Correct the data value for the specified field.
PARAMS:

ERROR: [DM_DCNFG_E_UPDATE_MIN_OWNER_XPERMIT]

SEVERITY: ERROR
DESCRIPTION: S You have specified an invalid value (%s) for the minimum owner extended permit.
CAUSE: You tried to set the minimum_owner_xpermit field of dm_docbase_config to a value that is not allowed. PARAMETER: The minimum owner extended permit must either be empty or a comma-delimited list of valid extended permits. See the documentation for details.
ACTION: Use an allowed value and try again.
PARAMS:

ERROR: [DM_DCNFG_E_CANT_CHANGE_AUTH_PROTOCOL]

SEVERITY: ERROR
DESCRIPTION: S Can not change auth_protocol mode from domain_required to %s.
CAUSE: The user tried to change authentication mode from domain_required mode to other mode.
ACTION: System only allows authentication mode to be changed from non domain_required mode to domain_required mode, not the other way around. A docbase is in domain_required mode only when the following two conditions are satisfied: (1) the auth_protocol of its docbase config object is domain_required, and (2) the i_stamp of the dmi_vstamp object is greater than 0. Once, the i_stamp value is set to be greater than 0, the auth_protocol mode can only set to domain_required.
PARAMS:

ERROR: [DM_DCNFG_E_CANT_CHANGE_AUDIT_OLD_VALUES]

SEVERITY: ERROR
DESCRIPTION: Cannot change audit_old_values to T because auditing old values of audited properties is not enabled due to a database page size limitation.
CAUSE: Auditing old values of audited properties is not allowed due to the database page size limitation
ACTION: Use a tablespace page size of at least 8K for DB2, and set the database page size to at least 8K for Sybase.
PARAMS:

ERROR: [DM_DCNFG_E_CLIENTRIGHTS_NOT_UNIQUE]

SEVERITY: ERROR
DESCRIPTION: SS Object value (%s) not unique in field %s. Conflicts with existing object.
CAUSE: Client rights objects must be unique in certain fields and an attempt was made to create a non-unique value.
ACTION: Create object with unqiue identifiers.
PARAMS:

ERROR: [DM_DCNFG_E_INVALID_DD_LOCALE]

SEVERITY: ERROR
DESCRIPTION: S The docbase config object has an unrecognized dd_locales value %s.
CAUSE: The docbase_config object has an unrecognized value for the dd_locales attribute.
ACTION: Correct the value of the dd_locales attribute that is unrecognized.
PARAMS:

ERROR: [DM_DCNFG_E_DUPLICATE_DD_LOCALE]

SEVERITY: ERROR
DESCRIPTION: S The docbase config object has duplicate dd_locales value %s. dd_locales must be unique.
CAUSE: The docbase_config object cannot have duplicate values for dd_locales
ACTION: Make sure that there are no duplicate values for dd_locales.
PARAMS:

ERROR: [DM_DCNFG_E_CLIENTREG_NO_PRIV]

SEVERITY: ERROR
DESCRIPTION: S User %s does not have permission to create this dm_client_registration entry.
CAUSE: Registry entries may require privilege for creation. Creating objects that are marked as validated requires Sysadmin privilege.
ACTION: User with appropriate privilege must create the object.
PARAMS:

ERROR: [DM_DCNFG_W_INVALID_MIN_OWNER_XPERMIT]

SEVERITY: WARNING
DESCRIPTION: S An invalid value for minimum owner extended permit (%s) was found when loading the docbase config. The server default value was used instead.
CAUSE: An invalid value was found in the docbase config object.
ACTION: Set the attribute to a valid value and restart the server.
PARAMS:

ERROR: [DM_DCNFG_W_INVALID_MIN_OWNER_PERMIT]

SEVERITY: WARNING
DESCRIPTION: I An invalid value for minimum owner permit (%d) was found when loading the docbase config. The server default value was used instead.
CAUSE: An invalid value was found in the docbase config object.
ACTION: Set the attribute to a valid value and restart the server.
PARAMS:

nahoru

DM_DIRECTORY

ERROR: [DM_DIRECTORY_E_BROWSE_NO_DIRECTORY_SUPPLIED]

SEVERITY: ERROR
DESCRIPTION: Must provide a directory with argument DIRECTORY.
CAUSE: There was no DIRECTORY argument supplied to the method.
ACTION: Provide a directory. $Id: dmdoc.e,v 5.0 1998/01/10 02:07:35 sol_ora Exp $ DmDocument class errors
PARAMS:

ERROR: [DM_DIRECTORY_E_BROWSE_CANT_RETRIEVE_DIRECTORY]

SEVERITY: ERROR
DESCRIPTION: S Failed to retrieve directory listing %s
CAUSE: Failed to retrieve the directory requested. Possible cause is insufficient permissions on directory.
ACTION: Change permissions to allow directory listing.
PARAMS:

ERROR: [DM_DIRECTORY_E_BROWSE_INSUFF_PRIVS]

SEVERITY: ERROR
DESCRIPTION: Must be have Administrator privilege.
CAUSE: The caller must have Administrator privilege to perform this operation.
ACTION: Functionality is for use by a user of the Administration Tools.
PARAMS:

ERROR: [DM_DIRECTORY_E_MEMORY_EXHAUSTED]

SEVERITY: ERROR
DESCRIPTION: I Memory exhausted allocating %d bytes
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DIRECTORY_E_BROWSE_NOT_DIRECTORY]

SEVERITY: ERROR
DESCRIPTION: S The path provided (%s) is not a directory.
CAUSE: The directory path provided is not a directory.
ACTION: Provide a directory path.
PARAMS:

ERROR: [DM_DIRECTORY_E_BROWSE_INSUFF_FS_PRIVS]

SEVERITY: ERROR
DESCRIPTION: S The current user does not sufficient privilege to access this directory: (%si)
CAUSE: The operating system user does not have enough privilege to access the specified directory.
ACTION: Change the permissions on the current directory.
PARAMS:

Konec první části…

Michal Šika

One Response to Documentum 6.6 – chybové zprávy – část 1.

  1. Pingback: Documentum 6.6 – chybové zprávy – část 2. » IT notes © Michal Šika