System Messages: TMQ Catalog 2200-2299
|
2202 |
ERROR: Invalid message type from BBL | |
|
Description |
An invalid message was sent from the BBL process. |
Action |
Contact Oracle Customer Support. | |
2203 |
ERROR: Process pid terminated abnormally | |
|
Description |
A process within the queuing server group terminated abnormally. |
Action |
Shut down all processes connected to the queue space, including tmqadmin. Restarting an administrative process that connects to the queue space will rebuild the queue space. | |
See Also |
| |
2204 |
WARN: Error queue val is a temporary queue | |
|
Description |
When creating a queue that is specified as the error queue for the queue space, it was created as a temporary queue. That means that if the machine goes down or the IPC resources for the queue space are removed, any messages on the error queue will be lost. |
Action |
No action required. | |
See Also |
| |
2205 |
ERROR: xa_open() - no more message entries (max = max_entries) | |
|
Description |
While opening the queue space for the first time after the machine has been booted or after the IPC resources have been removed, the queue space is warm started. During warm start, there were not enough message table entries. |
Action |
This could occur if the queue space message table size was changed to be smaller than the number of persistent messages in the queue space. Use the qspacechange command to increase the size of the message table. | |
See Also |
| |
2210 |
ERROR: tpalloc() failed - server exiting | |
|
Description |
An attempt to allocate a buffer in the |
Action |
Check that your system has enough physical or virtual memory to complete the operation. If you believe your system has enough memory for the operation and that the malloc arena has not been corrupted by user code, contact Oracle Customer Support. | |
See Also |
| |
2211 |
ERROR: tpreturn could not send reply (val) | |
|
Description |
TuxMsgQ server failed to send reply for a request. This failure could occur if the ipc queue of the recipient is invalid. The recipient ipc queue can become invalid because the recipient has exited, or because the TuxMsgQ is out of pending reply space or inter-process communication (IPC) resources. |
Action |
If the recipient has not exited check that your system has enough inter-process communication (IPC) resources configured to complete the operation. Otherwise contact Oracle Customer Support. | |
2212 |
ERROR: tpreturn could not send reply (No Pending List Space) | |
|
Description |
TuxMsgQ server failed to send reply for a request. The TuxMsgQ process failed to allocate memory to store the pending replies. |
Action |
Check that your system has enough physical or virtual memory to complete the operation. If you believe your system has enough memory for the operation, contact Oracle Customer Support. | |
2213 |
ERROR: tpreturn could not send reply (val) | |
|
Description |
TuxMsgQ server failed to send reply for a request. An internal function call returned a failure. |
Action |
This is an internal error with no associated user action. If the error persists, contact Oracle Customer Support. | |
2217 |
ERROR: The queue space is deadlocked, report code val,val | |
|
Description |
Despite the locks being acquired in hierarchical order, two Queue servers have each other's locks. This should be impossible. |
Action |
Contact Oracle Customer Support and report code val,val. Shut down *all* processes connected to the queue space, including tmqadmin. The next time an administrative process connects to the queue space, the queue space will be rebuilt. | |
2218 |
ERROR: memory allocation failure | |
|
Description |
An attempt to dynamically allocate memory from the operating system using malloc () failed in a queuing services operation. |
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. | |
2219 |
ERROR: memory allocation failure | |
|
Description |
An attempt to dynamically allocate memory from the operating system using malloc () failed in a queuing services operation. |
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. | |
2220 |
ERROR: memory allocation failure | |
|
Description |
An attempt to dynamically allocate memory from the operating system using malloc () failed in a queuing services operation. |
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. | |
2221 |
ERROR: memory allocation failure | |
|
Description |
An attempt to dynamically allocate memory from the operating system using malloc () failed in a queuing services operation. |
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. | |
2222 |
ERROR: memory allocation failure | |
|
Description |
An attempt to dynamically allocate memory from the operating system using malloc () failed in a queuing services operation. |
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. | |
2223 |
ERROR: failed to realize JMS filter plugin, interface 'val', implementation 'val', error code val | |
|
Description |
The registry was unable to properly realize an implementation for the JMS filter plug-in. |
Action |
Ensure the registry is in a valid state. If the registry is valid and the implementation appears to be known to the system, contact Oracle Customer Support. | |
2224 |
ERROR: memory allocation failure | |
|
Description |
An attempt to dynamically allocate memory from the operating system using malloc() failed while trying to use a dequeue filter. The dequeue operation will fail. |
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. | |
2225 |
ERROR: Invalid message properties | |
|
Description |
A message has invalid properties. This message will be ignored by dequeue filters that reference message properties. |
Action |
Contact Oracle Customer Support. | |
2227 |
WARN: Unable to invoke audit postop | |
|
Description |
A call to the |
Action |
Check the registration of the auditing plugin. If the plugin used is the default supplied plugin, check the userlog file and filesystem space. If the plugin used is not the default supplied plugin, contact the supplier of the plugin code. | |
See Also |
| |
2229 |
WARN: Unable to invoke audit postop | |
|
Description |
A call to the |
Action |
Check the registration of the auditing plugin. If the plugin used is the default supplied plugin, check the userlog file and filesystem space. If the plugin used is not the default supplied plugin, contact the supplier of the plugin code. | |
See Also |
| |
2230 |
WARN: Unable to invoke audit preop on service invocation | |
|
Description |
A call to the |
Action |
Check the registration of the auditing plugin. If the plugin used is the default supplied plugin, check the userlog file and filesystem space. If the plugin used is not the default supplied plugin, contact the supplier of the plugin code. | |
See Also |
| |
2231 |
WARN: Unable to invoke audit preop on service invocation | |
|
Description |
A call to the |
Action |
Check the registration of the auditing plugin. If the plugin used is the default supplied plugin, check the userlog file and filesystem space. If the plugin used is not the default supplied plugin, contact the supplier of the plugin code. | |
See Also |
| |
2234 |
ERROR: Double panic, scheduler can no longer NAK | |
|
Description |
This should never happen. After detecting a problem in the queue space, the scheduler began filling in the failure return codes of outstanding requests, and then began to send out replies. Unfortunately, there was yet another failure in the course of the recovery action. |
Action |
There may be illegal references in the queue space. Shut down *all* processes connected to the queue space, including tmqadmin. Then the next time an administrative process connects to the queue space, the queue space will be rebuilt. | |
2235 |
ERROR: Double panic, scheduler did not complete NAK | |
|
Description |
This should never happen. After detecting a problem in the queue space, the scheduler began filling in the failure return codes of outstanding requests, and then began to send out replies. Unfortunately, there was yet another failure in the course of the recovery action. |
Action |
There may be illegal references in the queue space. Shut down *all* processes connected to the queue space, including tmqadmin. Then the next time an administrative process connects to the queue space, the queue space will be rebuilt. | |
2236 |
ERROR: Scheduler insane, shutting down | |
|
Description |
This should never happen. The scheduler has encountered an impossible condition and is terminating. |
Action |
There may be illegal references in the queue space. Shut down *all* processes connected to the queue space, including tmqadmin. Then the next time an administrative process connects to the queue space, the queue space will be rebuilt. | |
2238 |
ERROR: xa_open() - the system time is val seconds older than the queue space time | |
|
Description |
When opening (warm starting) a queue space, the current system time was found to be older than the queue space. |
Action |
Reset the system time val seconds forward. | |
2239 |
ERROR: val must be a non-negative number and less than or equal to val | |
|
Description |
The value specified for val is not a valid numeric value or is too large. |
Action |
Change the value to be in the specified numeric range and re-run the operation. | |
2242 |
ERROR: unexpected transaction state, shutting down, values val, val | |
|
Description |
The process encountered an unexpected return value. |
Action |
Contact Oracle Customer Support. | |
2243 |
ERROR: unexpected transaction state, shutting down, values val, val | |
|
Description |
The process encounted an unexpected return value. |
Action |
Contact Oracle Customer Support. | |
2244 |
ERROR: The queue space hierarchy was matched, report code val,val | |
|
Description |
This diagnostic message is for early debug prototypes and can not occur in production. The locks were acquired in an illegal order. |
Action |
Contact Oracle Customer Support with the values. | |
2245 |
ERROR: The queue space hierarchy was violated, report code val,val | |
|
Description |
This diagnostic message is for early debug prototypes and can not occur in production. The locks were acquired in an illegal order. |
Action |
Contact Oracle Customer Support with the values. | |
2246 |
ERROR: discarding unreadable message | |
|
Description |
The message was not produced by the system libraries, it is incorrectly formatted. |
Action |
Insure all programs are using supported APIs and have no stray values. Contact Oracle Customer Support. | |
2248 |
WARN: -b option ignored. Argument is too large | |
|
Description |
The argument for the -b option on the command line for TMQFORWARDPLUS is too large and is ignored. |
Action |
Change the server command line options, CLOPT, for the TMQFORWARDPLUS server such that the argument for the -b option is an allowed numeric value >0 and < 32768. | |
See Also |
| |
2249 |
WARN: -b option ignored as argument must be numeric | |
|
Description |
The argument for the -b option on the command line for TMQFORWARDPLUS is non-numeric and is ignored. |
Action |
Change the server command line options, CLOPT, for the TMQFORWARDPLUS server such that the argument for the -b option is a numeric value indicating the number of seconds that the server will timeout in forward mode. | |
See Also |
| |
2250 |
WARN: tpsblktime failed - error message | |
|
Description |
tpsblktime() functions failed. |
Action |
Contact your Oracle TUXEDO System Technical Support. | |
2251 |
WARN: -b option ignored. Not in forwarded mode | |
|
Description |
The argument for the -b option on the command line for TMQFORWARDPLUS can only be used with -f option. |
Action |
Change the server command line options, CLOPT, for the TMQFORWARDPLUS server so that the -b option is used only when the -f option specified. | |
See Also |
|