7.0-dm_mq

DM_MQ


ERROR: [DM_MQ_E_CREATE_DAEMON_CONTEXT]

SEVERITY: ERROR
DESCRIPTION: Creating execution context for message queue daemon failed.
CAUSE: This may happen only after running out memory.
ACTION: Restart server. Report the error message to Documentum Engineering.
PARAMS: None

ERROR: [DM_MQ_E_MESSAGE_SAVE]

SEVERITY: ERROR
DESCRIPTION: SS Save message object (%s) failed in function (%s).
CAUSE: Maybe due to database deadlock.
ACTION: Retry the failed operation. PARAMETER: Message object id
PARAMS:

ERROR: [DM_MQ_E_MESSAGE_NOT_ACQUIRED]

SEVERITY: ERROR
DESCRIPTION: S Attempt to acknowledge message object (%s) that is not not in acquired state.
CAUSE: You attempt to acknowledge a message without first acquirint it.
ACTION: TRy to acquire the message first, process the mesage, and then acknowledge it. PARAMETER: Message object id
PARAMS:

ERROR: [DM_MQ_E_CANNOT_PURGE]

SEVERITY: ERROR
DESCRIPTION: SS User (%s) has no permission to purge messages from queue (%s). Only the queue owner, sysadmin, or superuser can purge messages from the queue.
CAUSE: The specified user is not the queue owner, sysadmin, nor superuser.
ACTION: Connect as the queue owner, sysadmon, or superuser to retry.
PARAMS: The first parameter is the user name who attempts to purge messages from the queue. The second one is the queue name

ERROR: [DM_MQ_E_SQL_EXEC]

SEVERITY: ERROR
DESCRIPTION: SSS Execution of SQL statement(%s) in function %s failed with error: %s.
CAUSE: Database error
ACTION: Check database error PARAMETER: The first paramter is the SQL statement. The second one is the calling function name. The third one is the database error message.
PARAMS:

ERROR: [DM_MQ_E_CANNOT_CONSUME]

SEVERITY: ERROR
DESCRIPTION: SS User (%s) has no permission to consume messages from queue (%s).
CAUSE: The specified user has not been granted permission to receive the messages from this queue.
ACTION: Grant receive permission to the user using either DQL or DFC APIs.
PARAMS: The first parameter is the user name who attempts to acquire messages from the queue. The second one is the queue name

ERROR: [DM_MQ_E_MESSAGE_ACK_USER]

SEVERITY: ERROR
DESCRIPTION: SSS User (%s) attempt to acknowledge message object (%s) that was acquied by user (%s).
CAUSE: A user attempts to acknowledge a message that was acquired by a different user.
ACTION: A message can be acquired and acknowledged by the same user only. PARAMETER: The first paramter is the name of the user who attempts to acknowledge the message. The second one is the message object id. The third one is the name of the user whow has acquired the message.
PARAMS:

ERROR: [DM_MQ_E_SQL_FETCH]

SEVERITY: ERROR
DESCRIPTION: SSS Fetch failed during executing SQL statement(%s) in function %s with error: %s.
CAUSE: Database error
ACTION: Check database error PARAMETER: The first paramter is the SQL statement. The second one is the calling function name. The third one is the database error message.
PARAMS:

ERROR: [DM_MQ_E_MAKE_TYPE]

SEVERITY: ERROR
DESCRIPTION: SS Creating type in function (%s) failed with error: %s.
CAUSE: Server memory corruption
ACTION: Reboot the server and retry the operation. PARAMETER: The first paramter the calling function name. The second one is the database error message.
PARAMS:

ERROR: [DM_MQ_E_MESSAGE_NOT_EXIST]

SEVERITY: ERROR
DESCRIPTION: S Message object (%s) does not exist.
CAUSE: The message has been purged by some other session.
ACTION: It is upto to application program on what action to take. Maybe simply ignore the error. PARAMETER: Message object id
PARAMS:

ERROR: [DM_MQ_E_MESSAGE_NOT_VALID]

SEVERITY: ERROR
DESCRIPTION: S Message object (%s) is invalid.
CAUSE: Server memory corruption
ACTION: Reboot the server and retry the operation. PARAMETER: Message object id
PARAMS:

ERROR: [DM_MQ_E_CANNOT_BROWSE]

SEVERITY: ERROR
DESCRIPTION: SS User (%s) has no permission to browse messages in queue (%s).
CAUSE: The specified user has not been granted permission to browse messages in this queue.
ACTION: Grant browse permission to the user using either DQL or DFC APIs.
PARAMS: The first parameter is the user name who attempts to browse the queue. The second one is the queue name

ERROR: [DM_MQ_E_CONFIG_NOT_EXIST]

SEVERITY: ERROR
DESCRIPTION: S Message queue configuration object (%s) does not exist.
CAUSE: Server memory corruption
ACTION: Reboot the server and retry the operation. PARAMETER: Message queue configuration object id.
PARAMS:

ERROR: [DM_MQ_E_CONFIG_NOT_VALID]

SEVERITY: ERROR
DESCRIPTION: S Message config object (%s) is invalid.
CAUSE: Server memory corruption
ACTION: Reboot the server and retry the operation. PARAMETER: Message queue configuration object id.
PARAMS:

ERROR: [DM_MQ_E_MESSAGE_DELETE]

SEVERITY: ERROR
DESCRIPTION: SS Delete message object (%s) failed in function (%s).
CAUSE: Maybe due to database deadlock.
ACTION: Retry the failed operation. PARAMETER: The first paramter is the message object id. The second one is the function where the message is expunged.
PARAMS:

ERROR: [DM_MQ_E_DAEMON_LAUNCH]

SEVERITY: ERROR
DESCRIPTION: SS Failed to launch %s due to operating system error: %s.
CAUSE: Launch failure was caused by an operation system error.
ACTION: Verify the operating system has enough resources.
PARAMS: S – The name of message queue daemon S – error message from operation system

ERROR: [DM_MQ_W_EXEC_POOL_FULL]

SEVERITY: WARNING
DESCRIPTION: S Failed to launch %s because the execution context pool is full.
CAUSE: The number of sessions has exceeded the supported limit.
ACTION: No actions are necessary. The server will re-launch such agent upon availability of the execution context pool.
PARAMS: S – name of message queue daemon

ERROR: [DM_MQ_I_DAEMON_START]

SEVERITY: INFORMATION
DESCRIPTION: SIS Message queue daemon (%s : %d, session %s) is started sucessfully.
CAUSE: This is an informational message generated at session startup.
ACTION: None. Informational message only.
PARAMS: The first parameter is pid or tid The second parameter is the process/thread id The third parameter is session id.

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: