7.0-dm_reltype

DM_RELTYPE


ERROR: [DM_RELTYPE_F_INIT3]

SEVERITY: FATAL
DESCRIPTION: The type manager returned an error storing the dmRelation_Type 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_RELTYPE_F_INIT1]

SEVERITY: FATAL
DESCRIPTION: The dmRelation_Type 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_RELTYPE_F_INIT2]

SEVERITY: FATAL
DESCRIPTION: II Version stamp %d was expected to be %d.
CAUSE: The version stamp that the dmRelation_Type 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_RELTYPE_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 $Id: dmrouter.e,v 5.0 1998/01/10 02:08:11 sol_ora Exp $ dmRouter class errors
PARAMS:

ERROR: [DM_RELTYPE_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_RELTYPE_E_CANT_VALIDATE_SYSTEM]

SEVERITY: ERROR
DESCRIPTION: Server could not create server defined relation types.
CAUSE: Server was not successful in creating the system defined relation types.
ACTION: Most likely database error.
PARAMS:

ERROR: [DM_RELTYPE_E_NEED_PRIVS]

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

ERROR: [DM_RELTYPE_E_NOT_EMPTY]

SEVERITY: ERROR
DESCRIPTION: S There are dm_relation object using %s relation_type object.
CAUSE: User tried to destroy a dm_relation_type object that still has dm_relation object using it.
ACTION: Either drop all dm_relation of this type before tring this operation.
PARAMS:

ERROR: [DM_RELTYPE_E_INVALID_SECURITY]

SEVERITY: ERROR
DESCRIPTION: S Invalid security %s for relation.
CAUSE: A user has defined an invalid relation_type security.
ACTION: Change to a valid relation_type security.
PARAMS:

ERROR: [DM_RELTYPE_E_CANT_CREATE_SYSTEM]

SEVERITY: ERROR
DESCRIPTION: S Can not system defined create relation type %s
CAUSE: Can not create relation type that start with DM_ prefix. Reservered for server use.
ACTION: Try another name.
PARAMS:

ERROR: [DM_RELTYPE_E_ALREADY_EXISTS]

SEVERITY: ERROR
DESCRIPTION: S Relation_Type with %s name already exists.
CAUSE: A user tried to define a relation_type that already exists. All relation_type names must be unique.
ACTION: Try another unique name.
PARAMS:

ERROR: [DM_RELTYPE_E_MUST_HAVE_NAME]

SEVERITY: ERROR
DESCRIPTION: A new relation_type must have a name.
CAUSE: All relation_types must have a name during creation.
ACTION: Set the name and try to save again.
PARAMS:

Advertisements

Leave a Reply

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

WordPress.com Logo

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

Twitter picture

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

Facebook photo

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

Google+ photo

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

Connecting to %s

%d bloggers like this: