System Messages: TMQ Catalog 1600-1699
|
1600 |
ERROR: Memory allocation failure | |
|
Description |
An attempt to dynamically allocate memory from the operating system using malloc() failed in TMQFORWARDPLUS while parsing and storing the command line queue names. The server will not boot. |
Action |
Ensure that the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine. | |
See Also |
| |
1601 |
ERROR: realloc() failed | |
|
Description |
An attempt to dynamically re-allocate memory from the operating system using realloc() failed in TMQFORWARDPLUS while parsing and storing the command line queue names. The server will not boot. |
Action |
Ensure that the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine. | |
See Also |
| |
1602 |
WARN: -t option ignored as argument must be numeric | |
|
Description |
The argument for the -t option on the command line for TMQFORWARDPLUS is non-numeric and is ignored. The default transaction time value will be used. |
Action |
Change the server command line options, CLOPT, for the TMQFORWARDPLUS server such that the argument for the -t option is a numeric value indicating the number of seconds before transaction timeout occurs. | |
See Also |
| |
1603 |
WARN: -t option ignored as argument is too large | |
|
Description |
The numeric argument for the -t option on the command line for TMQFORWARDPLUS is too large and is ignored. The default transaction time value will be used. |
Action |
Change the server command line options, CLOPT, for the TMQFORWARDPLUS server such that the argument for the -t option is a numeric value less than 2147483648 indicating the number of seconds before transaction timeout occurs. | |
See Also |
| |
1604 |
WARN: -i option ignored as argument must be numeric | |
|
Description |
The argument for the -i option on the command line for TMQFORWARDPLUS is non-numeric and is ignored. The default idle time value, 30 seconds, will be used. |
Action |
Change the server command line options, CLOPT, for the TMQFORWARDPLUS server such that the argument for the -i option is a numeric value indicating the number of seconds that the server is idle after finding no messages on the queues before it reads the queues again. | |
See Also |
| |
1605 |
WARN: -i option ignored as argument is too large | |
|
Description |
The numeric argument for the -i option on the command line for TMQFORWARDPLUS is too large and is ignored. The default idle time value, 30 seconds, will be used. |
Action |
Change the server command line options, CLOPT, for the TMQFORWARDPLUS server such that the argument for the -i option is a numeric value less than 2147483648 indicating the number of seconds that the server is idle after finding no messages on the queues before it reads the queues again. | |
See Also |
| |
1606 |
WARN: Invalid command line argument 'opt' ignored | |
|
Description |
An invalid option, opt, was specified on the command line for TMQFORWARDPLUS. |
Action |
Change the server command line options, CLOPT, for the TMQFORWARDPLUS server to remove the invalid command line option. Check the manual page for valid options. | |
See Also |
| |
1607 |
ERROR: -q option not specified | |
|
Description |
The -q option is a required option for the TMQFORWARDPLUS and was not specified in the command line options. The server will not boot. |
Action |
Change the server command line options, CLOPT, for the TMQFORWARDPLUS server to include the -q option with a list of one or more queues for which the server will forward queued messages. | |
See Also |
| |
1608 |
ERROR: TMSNAME must begin with TMS_TMQM | |
|
Description |
The application is configured such that the TMQFORWARDPLUS server is in a group in the GROUPS section that does not have the TMSNAME set to TMS_TMQM. The server will not boot. |
Action |
Change the TUXCONFIG file to have the TMSNAME set to TMS_TMQM and reboot the TMQFORWARDPLUS server. | |
See Also |
| |
1609 |
WARN: [Unable to verify that TMSNAME begins with TMS_TMQM] | |
|
Description |
The TMQFORWARDPLUS server was unable to verify that the TMSNAME for the group in the GROUPS section associated with TMQFORWARDPLUS is set to TMS_TMQM (that is, it was unable to find the corresponding GROUPS entry). |
Action |
Contact Oracle Customer Support. | |
See Also |
| |
1610 |
ERROR: Must not have a reply queue configured | |
|
Description |
The application is configured such that the TMQFORWARDPLUS server has a reply queue. The server will not boot. |
Action |
Change the TUXCONFIG file such that the TMQFORWARDPLUS server does not have a reply queue (that is, REPLYQ=N). | |
See Also |
| |
1611 |
ERROR: Must not be configured as part of an MSSQ | |
|
Description |
The application is configured such that the TMQFORWARDPLUS server is part of an multiple-server-single-queue, MSSQ, set. The server will not boot. |
Action |
Change the TUXCONFIG file such that the TMQFORWARDPLUS server is not part of an MSSQ set (that is, don't specify a RQADDR). | |
See Also |
| |
1612 |
ERROR: Must not advertise services | |
|
Description |
The application is configured such that the TMQFORWARDPLUS server advertised services as part of booting. The server will not boot. |
Action |
Change the TUXCONFIG file such that the CLOPT for the TMQFORWARDPLUS server does not include the -s option. If a custom version of TMQFORWARDPLUS is built using buildserver, don't specify the -s option. | |
See Also |
| |
1613 |
ERROR: tpopen() failed, tperrno = tperrno | |
|
Description |
While initializing the TMQFORWARDPLUS server, tpopen() returned an error. The server will not boot. |
Action |
Use the returned tperrno and check the userlog to determine what the error was. Resolve the problem and re-boot the server. | |
See Also |
| |
1614 |
ERROR: Queue name not found | |
|
Description |
One of the queue names, name, specified as an argument to the -q option of the TMQFORWARDPLUS server is not valid for the associated queue space. The server will not boot. |
Action |
Use the qinfo command of tmqadmin to get a list of valid queues for the queue space. Change the TUXCONFIG file such that the CLOPT for the TMQFORWARDPLUS server has a valid list of queue names for the -q option and re-boot the server. | |
See Also |
| |
1615 |
WARN: Dropping message received | |
|
Description |
An application message was received by the TMQFORWARDPLUS server. Since the TMQFORWARDPLUS server is not set up to handle application messages directly, the message was dropped. (The TMQFORWARDPLUS server cannot be booted if it advertises services but there is no mechanism to keep an administrator from dynamically advertising services for the server from tmadmin ). |
Action |
Unadvertise any services that were accidentally advertised for the TMQFORWARDPLUS server. | |
See Also |
| |
1616 |
ERROR: Failed to start a transaction count times; exiting | |
|
Description |
The TMQFORWARDPLUS server has failed to start a transaction via tpbegin count times. The server will exit (assuming that there something is wrong). |
Action |
If the TMQFORWARDPLUS server is set to restart, then the server will be restarted automatically. Check for other userlog messages that may indicate the problem. | |
See Also |
| |
1617 |
INFO: no messages on queues - shutting down | |
|
Description |
The TMQFORWARDPLUS server tried to dequeue a message from each of the queues named in the -q command line option and found no messages on any queue. The -e command line option was specified and the server is shutting down gracefully. |
Action |
No action required. | |
See Also |
| |
1618 |
ERROR: tpalloc() failed - server exiting | |
|
Description |
An attempt to dynamically allocate a typed buffer using tpalloc() failed in TMQFORWARDPLUS. The failure will cause the server to exit. |
Action |
Ensure that the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine. The server will restart automatically if it is configured as restartable. | |
See Also |
| |
1621 |
WARN: Unable to dequeue message for deleting, diagnostic diagnostic | |
|
Description |
A message was dequeued and forwarded to the associated service. The server returned failure and an application message. The -d option was specified on the TMQFORWARDPLUS server command line but TMQFORWARDPLUS was unable to delete the queued message from the queue. The associated diagnostic, diagnostic, is printed as part of the message. |
Action |
Determine what caused the dequeuing to fail. Most likely, the message reached the retry limit and was moved to the error queue; in this case, the diagnostic would be QMENOMSG . In the worst case, the message will not be deleted from the queue and will be executed again. | |
See Also |
| |
1622 |
WARN: Unable to enqueue failure message, diagnostic diagnostic | |
|
Description |
A message was dequeued and forwarded to the associated service. The server returned failure and an application message. The -d option was specified on the TMQFORWARDPLUS server command line but TMQFORWARDPLUS was unable to enqueue the reply message on the failure queue. The associated diagnostic, diagnostic, is printed as part of the message. |
Action |
Determine what caused the enqueuing to fail based on the diagnostic and by looking for other messages in the userlog and take actions (based on the associated system message manual for the printed messages) to ensure that it doesn't happen again. In this case, the reply message is lost. | |
See Also |
| |
1623 |
WARN: Failed to dequeue message and queue failure message, tperrno = tperrno | |
|
Description |
A message was dequeued and forwarded to the associated service. The server returned failure and an application message. The -d option was specified on the TMQFORWARDPLUS server command line but TMQFORWARDPLUS was unable to commit the transaction in which the original message was dequeued and the reply message was enqueued on the failure queue. |
Action |
Determine what caused the transaction to fail by looking for other messages in the userlog and take actions (based on the associated system message manual for the printed messages) to ensure that it doesn't happen again. In this case, the reply message is lost. | |
See Also |
| |
1624 |
WARN: Failed to start transaction to handle service failure, tperrno = tperrno | |
|
Description |
A message was dequeued and forwarded to the associated service. The server returned failure and an application message. The -d option was specified on the TMQFORWARDPLUS server command line but TMQFORWARDPLUS was unable to start a transaction in which the original message is dequeued and the reply message is enqueued on the failure queue. |
Action |
Determine what caused the transaction start, tpbegin , to fail by looking for other messages in the userlog and take actions (based on the associated system message manual for the printed messages) to ensure that it doesn't happen again. In this case, the reply message is lost. | |
See Also |
| |
1625 |
WARN: -t option ignored as argument must be numeric | |
|
Description |
The argument for the -t option on the command line for TuxMsgQ is non-numeric and is ignored. The default transaction time value will be used. |
Action |
Change the server command line options, CLOPT , for the TuxMsgQ server such that the argument for the -t option is a numeric value indicating the number of seconds before transaction timeout occurs. | |
See Also |
| |
1626 |
WARN: -t option ignored as argument is too large | |
|
Description |
The numeric argument for the -t option on the command line for TuxMsgQ is too large and is ignored. The default transaction time value will be used. |
Action |
Change the server command line options, CLOPT , for the TuxMsgQ server such that the argument for the -t option is a numeric value less than 2147483648 indicating the number of seconds before transaction timeout occurs. | |
See Also |
| |
1627 |
WARN: Invalid command line option 'opt' ignored | |
|
Description |
An invalid option, opt, was specified on the command line for TMQFORWARDPLUS and ignored. |
Action |
Change the server command line options, CLOPT , for the TMQFORWARDPLUS server to remove the invalid command line option. Check the manual page for valid options. | |
See Also |
| |
1628 |
ERROR: TMSNAME must begin with TMS_TMQM | |
|
Description |
The application is configured such that the TuxMsgQ server is in a group in the GROUPS section that does not have the TMSNAME set to TMS_TMQM. |
Action |
Change the TUXCONFIG file to have the TMSNAME set to and reboot the TuxMsgQ server. | |
See Also |
| |
1629 |
WARN: [Unable to verify that TMSNAME begins with TMS_TMQM] | |
|
Description |
The TuxMsgQ server was unable to verify that the TMSNAME for the group in the GROUPS section associated with TuxMsgQ is set to TMS_TMQM (that is, it was unable to find the corresponding GROUPS entry). |
Action |
Contact Oracle Customer Support. | |
See Also |
| |
1630 |
ERROR: tpopen() failed, tperrno = tperrno | |
|
Description |
While initializing the TuxMsgQ server, tpopen() returned an error. |
Action |
Use the returned tperrno and check the userlog to determine what the error was. When the problem has been resolved, re-boot the server. | |
See Also |
| |
1631 |
WARN: TuxMsgQ received the wrong buffer type - type | |
|
Description |
The TuxMsgQ server received a message from an application program that was sent via tpcall or tpconnect instead of tpenqueue or tpdequeue. A failure message is returned to the originator. |
Action |
Re-write the application software or re-configuration the TUXCONFIG file so that messages are sent to the correct services using the correct primitives. | |
See Also |
| |
1633 |
ERROR: [Failed to get field fieldname from operation message] | |
|
Description |
The TuxMsgQ server could not get the specified field, fieldname, while performing the operation. The operation can be "tpenqueue" or "tpdequeue", and the fieldname can be "FLAGS", "QNAME", "CORRID", "FAILUREQ", "MSGID", "PRIORITY", "REPLYQ", or "TIME". |
Action |
The operation will fail. Contact Oracle Customer Support. | |
See Also |
| |
1634 |
WARN: [Failed to set field fieldname in operation message] | |
|
Description |
The TuxMsgQ server could not set the specified field, fieldname, in the reply message while performing the operation. The operation can be "tpenqueue" or "tpdequeue", and the fieldname can be "DIAGNOSTIC", "FLAGS", "CORRID", "FAILUREQ", "MSGID", "PRIORITY", or "REPLYQ". |
Action |
The operation will succeed but the associated information will not be passed back to the application from the tpenqueue or tpdequeue call. Contact Oracle Customer Support. | |
See Also |
| |
1637 |
ERROR: TuxMsgQ cannot be a conversational server | |
|
Description |
The application is configured such that the TuxMsgQ server is a conversational server (that is, its entry in the configuration has "CONV=Y"). |
Action |
Change the TUXCONFIG file to configure TuxMsgQ as a request/response server (without CONV=Y) and reboot the TuxMsgQ server. | |
See Also |
| |
1638 |
ERROR: Unable to re-enqueue message | |
|
Description |
The TMQFORWARDPLUS server was run with the -n option which indicates that the forwarding is not being run within a transaction. In this case, the message was deleted from the queue, the associated service was called, the call failed, and the message cannot be put back on the queue. |
Action |
If the application cannot afford to lose messages, don't use the -n option on TMQFORWARDPLUS (atomicity can only be guaranteed within transactions). | |
See Also |
| |
1639 |
ERROR: TA_MAXPAGES can only be increased | |
|
Description |
An /Admin API request attempted to change the number of pages allocated to a queue space by specifying that the number be decreased or remain the same. This is an invalid request; the number of pages can only be increased. |
Action |
To decrease the number of pages allocated to a queue space, the queue space must be deleted and then recreated with the desired number of pages. These operations will also delete all messages in the queue space unless the messages are first dequeued and then enqueued to another queue space. | |
See Also |
| |
1640 |
ERROR: Cannot update TA_MAXQUEUES after queue space is created | |
|
Description |
An /Admin API request specified a change to the maximum number of queues in a queue space. This is an invalid request; the maximum number of queues cannot be changed after the queue space is created. |
Action |
To change the maximum number of queues in a queue space, the queue space must first be deleted and then recreated with the desired maximum number of queues. These operations will also delete all messages in the queue space unless the messages are dequeued and then enqueued to another queue space. | |
See Also |
| |
1642 |
ERROR: /Q error processing /Admin service request | |
|
Description |
An error occurred during the processing of an /Admin API request. The cause of the error is recorded in the userlog on the machine where the queue space is located. |
Action |
Examine the userlog for more information. | |
See Also |
| |
1643 |
ERROR: Invalid attribute value on SET request | |
|
Description |
The value specified on a SET request for the attribute indicated by the TA_BADFLD attribute in the reply buffer is invalid. Valid values for writable attributes are specified on the |
Action |
Correct the attribute value in question to a valid value. | |
See Also |
| |
1644 |
ERROR: Device specified in TA_QMCONFIG does not exist | |
|
Description |
The /Admin API request to create a new queue space failed because the device where the queue space is to be located does not exist. |
Action |
Create the device, then resubmit the request to create the queue space. The device can be created via the /Admin API (using SET NEW to create an object of the T_DEVICE class), or via the crdl command of tmqadmin or tmadmin. | |
See Also |
| |
1645 |
ERROR: Cannot update TA_APPQORDER after queue is created | |
|
Description |
An /Admonish request attempted to change the order in which messages in the queue are to be processed. This is an invalid request; the order cannot be changed after the queue is created. |
Action |
To change the message processing order of a queue, the queue must be deleted and then recreated with the desired order. These operations will also delete all messages in the queue unless the messages are first moved to another queue. | |
See Also |
| |
1646 |
ERROR: Unable to determine license level | |
|
Description |
An error occurred while retrieving the current license attributes. |
Action |
Contact Oracle Customer Support. | |
1647 |
ERROR: No license for /Q | |
|
Description |
You do not have a license to use /Q. |
Action |
Purchase a license for /Q. If you believe that you own and have installed the license for /Q, contact Oracle Customer Support. | |
1648 |
ERROR: Unable to determine license level | |
|
Description |
An error occurred while retrieving the current license attributes. |
Action |
Contact Oracle Customer Support. | |
1649 |
ERROR: No license for /Q | |
|
Description |
You do not have a license to use /Q. |
Action |
Purchase a license for /Q. If you believe that you own and have installed the license for /Q, contact Oracle Customer Support. | |
1650 |
ERROR: Unable to determine license level | |
|
Description |
An error occurred while retrieving the current license attributes. |
Action |
Contact Oracle Customer Support. | |
1651 |
ERROR: No license for /Q | |
|
Description |
You do not have a license to use /Q. |
Action |
Purchase a license for /Q. If you believe that you own and have installed the license for /Q, contact Oracle Customer Support. | |
1654 |
WARN: -i option defaulted to 1 second | |
|
Description |
A value of |
Action |
No action required. To eliminate the warning message, change
the argument to the | |
See Also |
| |
1655 |
ERROR: Unable to open file filename | |
|
Description |
The |
Action |
Check that filename is a valid file name and is readable by the Tuxedo administrator. | |
See Also |
| |
1656 |
ERROR: Memory allocation failure | |
|
Description |
An attempt to dynamically allocate memory from the operating system using malloc() failed in TMQFORWARDPLUS while parsing and storing the command line queue names. The server will not boot. |
Action |
Ensure that the operating system parameters are set correctly for the amount of memory on the machine and for the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine. | |
1657 |
ERROR: realloc() failed | |
|
Description |
An attempt to dynamically re-allocate memory from the operating system using realloc() failed in TMQFORWARDPLUS while parsing and storing the command line queue names. The server will not boot. |
Action |
Ensure that the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine. | |
1658 |
WARN: File recursion not supported (val) | |
|
Description |
While parsing a file with a list of queues, specified using the -q@ option
on the command line of |
Action |
Edit the queue file list and correct the queue name. | |
See Also |
| |
1660 |
ERROR: Can not malloc space | |
|
Description |
An attempt to dynamically allocate memory from the operating system using malloc() failed in TMQFORWARDPLUS trying to enqueue the reply. The current transaction is rolled back and the server will exit. |
Action |
Ensure that the operating system parameters are set correctly for the amount of memory on the machine and for the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine. | |
1661 |
ERROR: Can not malloc space | |
|
Description |
An attempt to dynamically allocate memory from the operating system using malloc() failed while dequeuing an application message. |
Action |
Ensure that the operating system parameters are set correctly for the amount of memory on the machine and for the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine. | |
1662 |
ERROR: Can not process the typed buffer | |
|
Description |
The TMQFORWARDPLUS server failed to decode a message regarding the user data. |
Action |
Examine the | |
1672 |
ERROR: Invalid time format | |
|
Description |
While executing the qscan command, an invalid date and time value was specified. |
Action |
Re-enter the qscan command using a valid date/time value. The value must be of the form YY[MM[DD[HH[MM[SS]]]]] (that is, 2 digits for year, and optionally 2 digits each for the month, day, hour, minute, and second). | |
See Also |
| |
1673 |
ERROR: Invalid time format | |
|
Description |
While executing the qscan command with a range of date/time values, an invalid date and time value was specified for the second value. |
Action |
Re-enter the qscan command using a valid date/time value. The value must be of the form YY[MM[DD[HH[MM[SS]]]]] (that is, 2 digits for year, and optionally 2 digits each for the month, date, hour, minute, and second). A range of date/time values is two date/time values separated by a hyphen. | |
See Also |
| |
1674 |
ERROR: Invalid delivery mode | |
|
Description |
While executing the qscan command, an invalid delivery mode was specified. |
Action |
Re-enter the qscan command using a valid delivery mode. The value must be either "persist" or "nonpersist". | |
See Also |
| |
1679 |
ERROR: Invalid high threshold type | |
|
Description |
While executing the qcreate or qchange command, an invalid upper threshold value was specified for nonpersistent messages (the suffix was not valid). The threshold value must be a number suffixed with |
Action |
Re-enter the qcreate or qchange command using an appropriate threshold value. | |
See Also |
| |
1681 |
ERROR: Invalid high threshold number | |
|
Description |
While executing the qcreate or qchange command, an upper threshold value of 0 was specified, or a percentage greater than 100 was given, for nonpersistent messages. |
Action |
Re-enter the qcreate or qchange command using an appropriate threshold value. | |
See Also |
| |
1683 |
ERROR: High and low threshold types do not match | |
|
Description |
While executing the qcreate or qchange command, the suffix on the upper threshold value doesn't match the suffix on the lower threshold value for nonpersistent messages. |
Action |
Re-enter the qcreate or qchange command using appropriate threshold values. | |
See Also |
| |
1685 |
ERROR: Low threshold must be less than high threshold | |
|
Description |
While executing the qcreate or qchange command, the lower threshold value is larger than the upper threshold value for nonpersistent messages. |
Action |
Re-enter the qcreate or qchange command using appropriate threshold values such that the lower value is less than the upper threshold value. | |
See Also |
|