Message Reference > M Message Codes > MQ Messages
  

MQ Messages

MQ_29000 Cannot connect to queue manager <queue manager> reason <reason> <reason message>.

Explanation:
The queue manager name is inaccurate.
User Response:
Check the queue manager name.
Explanation:
You might not have proper permission to connect to the queue manager.
User Response:
Verify the privileges to connect to the queue manager.

MQ_29001 Cannot open queue <queue> reason <reason> <reason message>.

Explanation:
The queue name is inaccurate.
User Response:
Check the queue name.
Explanation:
You might not have proper permission to connect to the queue.
User Response:
Verify the privileges to connect to the queue.

MQ_29002 Error closing queue <queue> reason <reason> <reason message>.

Explanation:
The Integration Service could not close the message queue due to the reason code stated in the message.
User Response:
Look up the reason code in the WebSphere MQ documentation for instructions to correct the error.

MQ_29003 Error disconnecting from queue manager <queue manager> reason <reason> <reason message>.

Explanation:
The Integration Service could not disconnect from the queue manager due to the reason code stated in the message.
User Response:
Look up the reason code in the WebSphere MQ documentation for instructions to correct the error.

MQ_29004 Filter parse error: <parse error message>.

Explanation:
The filter condition in the MQ Source Qualifier is invalid.
User Response:
Correct the error stated in the parse error message.

MQ_29005 Error getting message from queue <queue>:<queue manager> reason <reason> <reason message>.

Explanation:
The Integration Service failed to get a message from the queue due to the reason code stated in the message.
User Response:
Look up the reason code in the WebSphere MQ documentation for instructions to correct the error.

MQ_29006 Message data truncated reading from queue <queue>:<queue manager> reason <reason> <reason message>.

Explanation:
The message size is too large for the Integration Service to read.
User Response:
Look up the reason code in the WebSphere MQ documentation for instructions to correct the error.

MQ_29007 No message under cursor while attempting to remove message from queue <queue>:<queue manager> reason <reason> <reason message>.

Explanation:
You might not have the permission to remove the message from the queue.
The message was removed by another process.
User Response:
Look up the reason code in the WebSphere MQ documentation for instructions to correct the error.

MQ_29008 Error putting message on queue <queue>:<queue manager> reason <reason> <reason message>.

Explanation:
The Integration Service could not put message on the queue due to reason code stated in message.
User Response:
Look up the reason code in the WebSphere MQ documentation for instructions to correct the error.

MQ_29009 Invalid RowsPerMesage value for queue <queue>:<queue manager> (<rows per message> > 0).

Explanation:
The Rows Per Message parameter in the session properties is incorrect.
User Response:
Specify a value greater than 0 for the Rows Per Message in the session properties.

MQ_29010 Error opening cache <cache file> for reading: <operating system error>.

Explanation:
You might not have permission to read from the cache file.
The $PMCacheDir variable is incorrect.
User Response:
Fix the operating system error stated in the message.

MQ_29011 Error opening cache <cache file> for writing: <operating system error>.

Explanation:
You might not have permission to write to the cache file.
The hard disk is full.
The $PMCacheDir variable is incorrect.
User Response:
Fix the operating system error stated in the message. Look in the directory $PMCacheDir.

MQ_29012 Error attempting to load MQ driver.

Explanation:
PowerCenter could not load the MQ driver shared library because the file does not exist.
User Response:
Verify the search path for the MQ driver shared library. Depending on the platform, look for the driver file in the appropriate location:
  • •Windows - pmmqdrvc.dll
  • •Solaris - libpmmqdrvc.so
  • •Linux - libpmmqdrvc.so
  • •AIX - libpmmqdrvc.a
  • •HP - libpmmqdrvc.sl
Explanation:
PowerCenter could not load the MQ driver shared library due to insufficient permissions.
User Response:
Make sure the permissions for the MQ driver file are correct.

MQ_29013 Delete operation for this target not enabled. Queue connection is <queue>:<queue manager>.

Explanation:
The WebSphere MQ target received a row with the delete flag set to TRUE. However, the Integration Service does not have delete permission for the queue.
User Response:
Enable delete permission for the Integration Service on the target queue.

MQ_29014 MsgId field has not been set. Queue connection is <queue>:<queue manager>.

Explanation:
There may be no port projected to the MsgId column in the dynamic WebSphere MQ target. The Integration Service cannot delete messages from the queue.
User Response:
Project a port to the MsgId column of the dynamic WebSphere MQ target.

MQ_29100 Line <line>, column <column>: Unknown character '<character>' in filter.

Explanation:
A filter condition has a general parsing error.
User Response:
Check the syntax of the expression.

MQ_29101 Line <line>, column <column>: Invalid operator.

Explanation:
A filter condition has a general parsing error.
User Response:
Check the syntax of the expression.

MQ_29102 Line <line>, column <column>: Unknown identifier <identifier>.

Explanation:
A filter condition has a general parsing error.
User Response:
Check the syntax of the expression.

MQ_29103 Line <line>, column <column>: String literal not terminated properly.

Explanation:
A filter condition has a general parsing error.
User Response:
Check the syntax of the expression.

MQ_29104 Line <line>, column <column>: Syntax Error.

Explanation:
A filter condition has a general parsing error.
User Response:
Check the syntax of the expression.

MQ_29105 Filter Expression does not have a boolean return type.

Explanation:
The filter condition does not return a boolean TRUE/FALSE value.
User Response:
Edit the filter condition to return a boolean TRUE/FALSE value.

MQ_29106 Line <line>, column <column>: Left operand must be boolean.

Explanation:
The filter condition does not contain a boolean operand.
User Response:
Check the left-hand side of the logical operator in the filter condition.

MQ_29107 Line <line>, column <column>: Right operand must be boolean.

Explanation:
The filter condition does not contain a boolean operand.
User Response:
Check the right-hand side of the logical operator in the filter condition.

MQ_29108 Line <line>, column <column>: Incompatible types for relational operator.

Explanation:
The logical operators [=, <>, >=, <=, >, <] in the left-hand and right-hand sub-expression have incompatible datatypes.
User Response:
Edit the filter condition with compatible datatypes for relational operators in the left-hand and right-hand sub-expression.

MQ_29109 Line <line>, column <column>: Not enough arguments. <function name> () should have argument(s).

Explanation:
The function in the filter condition does not enough arguments.
User Response:
Apply arguments to the function in the filter condition.

MQ_29110 Line <line>, column <column>: Too many arguments. <function name> () should have argument(s).

Explanation:
There are too many arguments in a function.
User Response:
Use fewer arguments in a function.

MQ_29111 Line <line>, column <column>: Wrong type in <function name> (). Argument should be CHAR/BYTE.

Explanation:
The function expects an argument in MQCHAR or MQBYTE type.
User Response:
Make sure argument is of MQCHAR or MQBYTE type in the filter expression.

MQ_29112 Line <line>, column <column>: Wrong type in <function name> (). Argument should be BOOLEAN.

Explanation:
The function expects an argument in boolean type.
User Response:
Make sure argument is of boolean type in the filter condition.

MQ_29113 Line <line>, column <column>: Wrong type in <function name> (). Argument should be LONG.

Explanation:
The function expects an argument in MQLONG type.
User Response:
Make sure argument is of MQLONG type in the filter condition.

MQ_29114 Line <line>, column <column>: String literal not terminated properly.

Explanation:
The string literals must be in double quotes.
User Response:
Use double quotes to enclose string literals in the filter condition.

MQ_29115 Line <line>, column <column>: Bad date format in <function name> (), Argument <argument number> should be <correct date format>.

Explanation:
The argument in the function does not contain the correct date format.
User Response:
Use the <correct date format> for the argument in the filter condition.

MQ_29200 Projected column metadata fetch failed.

Explanation:
Internal error.
User Response:
Contact Informatica Global Customer Support.

MQ_29201 Cannot retrieve source filter.

Explanation:
Internal error.
User Response:
Contact Informatica Global Customer Support.

MQ_29202 Unable to retrieve cache file name.

Explanation:
Internal error.
User Response:
Contact Informatica Global Customer Support.

MQ_29203 Error opening queue <queue>:<queue manager> because <error message>.

Explanation:
The Integration Service could not open the queue due to the reason code stated in message. You may have selected to install the WebSphere MQ server driver during installation. However, the WebSphere MQ server is not installed on the machine hosting the Integration Service.
User Response:
Reinstall the WebSphere MQ server driver. Make sure to select the WebSphere MQ client driver during installation.
Look up the reason code in the WebSphere MQ documentation for instructions to correct the error.

MQ_29204 Error fetching message from queue <queue>:<queue manager> because <error message>.

Explanation:
The Integration Service could not fetch message from the queue due to the error.
User Response:
Correct the error indicated in the error message.

MQ_29207 Error closing queue <queue>:<queue manager>: <error message>.

Explanation:
The Integration Service could not close the queue due to the error stated in the message.
User Response:
Correct the error indicated in the error message.

MQ_29208 Error putting message on queue <queue>:<queue manager>: <error message>.

Explanation:
The Integration Service could not put the message on the queue due to the error stated in the message.
User Response:
Correct the error indicated in the error message.

MQ_29210 Error attempting to get MQ connection information.

Explanation:
Internal error.
User Response:
Contact Informatica Global Customer Support.

MQ_29211 Warning: Some message data was truncated reading from queue <queue>:<queue manager>.

Explanation:
This is only a warning. The MQ reader truncated one or more MESSAGE_DATA columns because the size of the message exceeded the maximum size for the MESSAGE_DATA port in the MQ Source Qualifier.
User Response:
However, you can increase the size of the MESSAGE_DATA column in the MQ Source Qualifier.

MQ_29212 Warning: Message with a total length of <length> was truncated to <length>.

Explanation:
This is only a warning. This is a more detailed warning that appears when Tracing is set to “VERBOSE RUN.” The message number is given as MSGNO.
User Response:
However, you can increase the size of the MESSAGE_DATA column in the MQ Source Qualifier.

MQ_29213 No filter is specified for queue <queue>:<queue manager>.

Explanation:
This is an informational message. It indicates that there is no filter set for reading messages from the queue.
User Response:
None. You can enter a filter condition in the MQ Source Qualifier or in the session properties.

MQ_29214 MQ Driver initialization failure <error message>.

Explanation:
An error occurred during the initialization of the MQ driver.
User Response:
Check the additional error message for more information.

MQ_29218 Filter Condition for MQSeries: StartTime should be prior to EndTime.

Explanation:
This is an informational message. The value for StartTime in the filter condition is equal to or greater than the value entered for EndTime.
User Response:
Make sure the StartTime value is less than the EndTime value.

MQ_29221 Partial message written into queue <queue>:<queue manager> due to commit.

Explanation:
This is an informational message. The Integration Service did not commit all rows in a message to the target. This might occur when the Integration Service reaches the end of a commit interval or a short FlushLatency interval. It commits the remaining rows at the next commit interval.
User Response:
None.

MQ_29222 Error committing from queue manager <queue manager>: reason <reason> <reason message>.

Explanation:
The Integration Service could not commit messages to the target. The WebSphere MQ system may not contain enough log space.
User Response:
Verify that the WebSphere MQ system contains enough log space.
Check the additional error message for more information.

MQ_29223 Error backing out from queue manager <queue manager>: reason <reason> <reason message>.

Explanation:
The Integration Service could not roll back messages from the target.
User Response:
Check the additional error message for more information.

MQ_29224 Device failed to commit: <error message>.

Explanation:
The Integration Service could not commit messages to the target.
User Response:
Check the additional error message for more information.

MQ_29225 Device failed to back out: <error message>.

Explanation:
The Integration Service could not roll back messages from the target.
User Response:
Check the additional error message for more information.

MQ_29226 Device failed to connect to queue manager: <error message>.

Explanation:
The Integration Service could not connect to the queue manager. The session failed to initialize.
User Response:
Check the additional error message for more information.

MQ_29231 Transactional MQ targets with the same queue manager name cannot be in different TCUs.

Explanation:
The WebSphere MQ targets have the same queue connection but belong to different transaction control units. As a result, the session failed.
User Response:
Make sure that all WebSphere MQ targets with the same queue connection belong to the same transaction control unit.

MQ_29234 Write to recovery cached failed.

Explanation:
Recovery cache folder is not available.
User Response:
Check that the recovery cache folder exists and has write permission.
Explanation:
The target may have insufficient disk space.
User Response:
Verify that enough disk space is available in the target.

MQ_29237 Failure occurred while reading messages from the queue in destructive mode.

Explanation:
The WebSphere MQ installation may not allow deleting messages from the queue.
User Response:
Look up the reason code in the WebSphere MQ documentation for instructions to correct the error.

MQ_29238 Invalid recovery cache folder specified.

Explanation:
The recovery cache folder is invalid.
User Response:
From the properties settings on the Mapping tab (Sources node) in the session properties, specify a valid recovery cache folder.

MQ_29239 Reader partition <partition name> failed to close checkpoint at real-time flush: <additional error message>.

Explanation:
There may be insufficient disk space when the Integration Service commits messages to the target after the Real-time Flush Latency period expires.
User Response:
Verify that enough disk space is available in the target.

MQ_29240 Cache folder specified for reader partition <partition name> is invalid.

Explanation:
The operating system cannot find the recovery cache folder.
User Response:
Verify the recovery cache folder specified in the session properties exists.

MQ_29241 Reader partition <partition name> failed to register recovery.

Explanation:
The operating system may be low on memory.
User Response:
Verify the system has sufficient memory.

MQ_29242 Consumer handle failed to initialize.

Explanation:
The name of the recovery cache folder may be incorrect.
User Response:
Verify the recovery cache folder name specified in the session properties.
Contact the system administrator.

MQ_29243 Reader partition failed to read cached message.

Explanation:
The recovery cache file may be deleted.
User Response:
Verify that the cache file and directory exist. Specify the correct path to the cache file directory in the properties settings on the Mapping tab (Sources node) in the session properties.

MQ_29244 Reader partition <partition name> failed doing GMD flush: <additional error message>.

Explanation:
The recovery cache folder may have insufficient memory.
User Response:
Verify the recovery cache folder has sufficient memory for large files.
Explanation:
The recovery cache folder may not have write permission.
User Response:
Verify the recovery cache folder has write permission.

MQ_29245 You cannot specify both Destructive Read and RemoveMsg(TRUE).

Explanation:
You selected the Destructive Read option and specified the RemoveMsg(TRUE) function as a filter condition.
User Response:
You must set the RemoveMsg(TRUE) function to RemoveMsg(FALSE) in the filter condition or remove the function from the filter condition.

MQ_29246 The mapping contains an associated source qualifer.

Explanation:
You specify the Destructive Read option in a mapping with an associated source qualifier.
User Response:
The Integration Service ignores the Destructive Read option if the mapping contains an associated source qualifier. To remove messages from the source queue for mappings that contain an associated source qualifier, use the RemoveMsg(TRUE) function.

MQ_29248 MQ queue manager <queue manager> encountered a transient connection failure.

Explanation:
The Integration Service could not connect to the MQ queue manager. The network or the MQ server may be down. The Integration Service will attempt to connect to the MQ queue during the retry connection period. If it does not connect to the MQ queue during the retry connection period the session fails.
User Response:
Verify the MQ queue manager is running. Or, verify that the network is active.

MQ_29250 Connection retry period expired. The Integration Service could not connect to MQ queue manager <queue manager>.

Explanation:
The Integration Service could not connect to the MQ queue manager during the retry connection period. The network or the MQ server may be down. As a result, the session failed.
User Response:
Verify the MQ queue manager is running. Or, verify that the network is active. Restart the session.

MQ_29251 Resilience is disabled, because Destructive Read and recovery are not configured.

Explanation:
The Integration Service could not make multiple connection attempts to the MQ queue manager, because Destructive Read and recovery are not configured for the session.
User Response:
In the session properties, configure Destructive Read and recovery.

MQ_29255 The Integration Service truncated message data while reading from queue <queue>:<queue manager> in destructive read mode.

Explanation:
The Integration Service read a WebSphere MQ message that exceeded the precision of the MESSAGE_DATA column in the MQSeries source definition. As a result, the Integration Service truncated the data. Because the session is running in destructive read mode, the session failed and the Integration Service did not delete the message from the source queue.
User Response:
Increase the precision of the MESSAGE_DATA column in the MQSeries source definition.

MQ_29265 The repository data for source <source name> is corrupt.

Explanation:
The connection object for the specified source instance contains inconsistencies.
User Response:
Delete the connection object for the source instance. Create a connection object and assign it to the source instance.

MQ_29270 The Integration Service could not create a locale for code page ID: <code page>.

Explanation:
The Integration Service failed to create an I18N converter object.
User Response:
Contact Informatica Global Customer Support.

MQ_29280 The Integration Service fails a WebSphere MQ real-time session that is enabled for recovery and contains multiple partitions.

Explanation:
A WebSphere MQ real-time session that contains multiple partitions cannot be enabled for recovery.
User Response:
Delete the partitions or do not enable the session for recovery.