6.6-dm_composite

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: