System Messages: TMQ Catalog 2100-2199
|
![]() |
![]() |
2166 |
ERROR: Memory allocation failure | |
|
Description |
An attempt to dynamically allocate memory from the operating system using malloc() failed in TuxMsgQ while trying to create a cursor. The 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. | |
2167 |
ERROR: Memory allocation failure | |
|
Description |
An attempt to dynamically allocate memory from the operating system using malloc() failed in TuxMsgQ while trying to destroy a cursor. The 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. | |
2168 |
ERROR: Memory allocation failure | |
|
Description |
An attempt to dynamically allocate memory from the operating system using malloc() failed in TuxMsgQ while trying to enqueue a message. The 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. | |
2169 |
ERROR: Memory allocation failure | |
|
Description |
An attempt to dynamically allocate memory from the operating system using malloc() failed in TuxMsgQ while trying to enqueue a message. The 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. | |
2170 |
ERROR: timer_action() - Invalid timer type | |
|
Description |
The TuxMsgQ server detected an invalid timer type when processing timers. |
Action |
Contact Oracle Customer Support. | |
2172 |
ERROR: 'expiration' specified multiple times | |
|
Description |
While executing the qcreate command, the 'expiration' option was specified multiple times for the queue ordering value. The values 'fifo', 'lifo', 'priority', 'expiration' and 'time' may be entered once; 'fifo' and 'lifo' may not both be specified and must be specified as the last (least significant) option. Multiple values must be specified separated by commas. |
Action |
Re-enter the qcreate command specifying a valid value for the queue ordering argument. | |
See Also |
| |
2173 |
ERROR: Threshold command length must be less than val characters | |
|
Description |
While executing the qcreate or qchange command, the threshold command for nonpersistent messages was too long (that is, len characters or more). |
Action |
Re-enter the command with a threshold command that is 128 characters or less in length. | |
See Also |
| |
2175 |
WARN: Expiration time not changed | |
|
Description |
While changing message expiration time with the qchangetime command, the user did not respond with Y or y to the prompt for confirmation and the operation was not done. |
Action |
No action required. | |
2176 |
ERROR: Dead process val connected to queue space, Queue space is insane | |
|
Description |
A process exited or was killed before cleanly disconnecting from the queue space. There may be illegal references in the queue space. |
Action |
Shutdown *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. | |
2177 |
ERROR: Process val died while holding lock | |
|
Description |
A process exited or was killed before cleanly disconnecting from the queue space. There may be illegal references in the queue space. |
Action |
Shutdown *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. | |
2178 |
ERROR: Process val died while holding lock | |
|
Description |
A process exited or was killed before cleanly disconnecting from the queue space. There may be illegal references in the queue space. |
Action |
Shutdown *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. | |
2179 |
ERROR: Process val has exited, qspace is invalid | |
|
Description |
A process exited or was killed before cleanly disconnecting from the queue space. There may be illegal references in the queue space. |
Action |
Shutdown *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. | |
2180 |
ERROR: Process val has exited, qspace is invalid | |
|
Description |
A process exited or was killed before cleanly disconnecting from the queue space. There may be illegal references in the queue space. |
Action |
Shutdown *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. | |
2181 |
ERROR: Queue space is insane, must NAK and exit | |
|
Description |
The queue space has been marked invalid, so the server must reply to all clients and exit. |
Action |
Shutdown *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. | |
2182 |
WARN: dequeue can not block, out of action entries | |
|
Description |
The action table for blocking dequeue requests was full, so this dequeue returned without blocking. |
Action |
Re-create the queue space with more action table entries and/or more shared memory heap space. | |
See Also |
tmqadmin(1) | |
2183 |
INFO: Rebuilding queue space that was marked insane | |
|
Description |
The queue space was marked insane. After all processes disconnected, an administrative process has rebuilt the queue space. |
Action |
No action required. | |
2184 |
ERROR: Shared memory heap could not be created | |
|
Description |
The shared memory section of the queue space used as a heap could not be initialized. This should not occur. |
Action |
Call Oracle Customer Support. | |
2185 |
ERROR: xa_open() - out of Action entries | |
|
Description |
The action table for blocking dequeue requests was full, so this dequeue returned without blocking. |
Action |
Re-create the queue space with more action table entries and/or more shared memory heap space. | |
See Also |
tmqadmin(1) | |
2186 |
ERROR: Queue qspace has policy SIGNATURE_REQUIRED=signature-policy and ENCRYPTION_REQUIRED=encryption-policy but the input buffer was neither signed nor sealed | |
|
Description |
A message arrived at queue space qspace that violated the policy constraints of the application. The queue space qspace has a signature policy of signature-policy and an encryption policy of encryption-policy. |
Action |
Determine why a message arrived for qspace that violates the policy, or change the policy. Policy determination starts at the *SERVICE level, goes to the *GROUP level, then goes to the *MACHINE level, and finally to the *RESOURCE level. If any of those policies is Y, then the policy for qspace is Y. | |
See Also |
| |
2187 |
ERROR: Queue qspace requires encryption but the input buffer is not encrypted | |
|
Description |
A message arrived for the queue space qspace that violated the policy constraints of the application. The queue space qspace has an encryption policy of Y. |
Action |
Determine why a message arrived for qspace that violates the policy, or change the policy. Policy determination starts at the *SERVICE level, goes to the *GROUP level, then goes to the *MACHINE level, and finally to the *RESOURCE level. If any of those policies is Y, then the policy for qspace is Y. | |
2188 |
ERROR: Unable to decrypt message in order to determine signature status | |
|
Description |
A message arrived at a queue space. The queue space has a signature policy of Y. However, the message was encrypted, and the queue server does not have a valid decryption key. Therefore, the presence of digital signatures could not be verified. |
Action |
Using the public key plugin method, open a valid decryption key for the user event broker. Otherwise, ensure that messages sent to the queue server requiring digital signatures are not encrypted. | |
See Also |
| |
2189 |
ERROR: Invalid public key context | |
|
Description |
The user event broker detected an invalid buffer while attempting to process a posted message. The user event broker has an encryption or signature policy of Y. |
Action |
Contact Oracle Customer Support. | |
See Also |
| |
2190 |
ERROR: Queue qspace requires encryption but the input buffer is not encrypted | |
|
Description |
A posted message arrived for queue space qspace that violated the policy constraints of the application. The user event broker has an encryption policy of Y. |
Action |
Determine why a message arrived for qspace that violates the policy, or change the policy. Remember that policy determination starts at the *SERVICE level, goes to the *GROUP level, then goes to the *MACHINE level, and finally to the *RESOURCE level. If any of those policies is Y, then the policy for qspace is Y. | |
See Also |
| |
2191 |
ERROR: Queue qspace requires a signature but the input buffer is not signed | |
|
Description |
A posted message arrived for queue space qspace that violated the policy constraints of the application. The user event broker has a signature policy of Y. |
Action |
Determine why a message arrived for qspace that violates the policy, or change the policy. Remember that policy determination starts at the *SERVICE level, goes to the *GROUP level, then goes to the *MACHINE level, and finally to the *RESOURCE level. If any of those policies is Y, then the policy for qspace is Y. | |
See Also |
| |
2192 |
WARN: Unable to audit policy enforcement event | |
|
Description |
The queue server was unable to audit a security failure. |
Action |
Ensure that the auditing plugin is properly registered in the registry. Ensure
that the registry is in a consistent state with the | |
See Also |
| |
2193 |
ERROR: xa_open() - shared memory required for the queue space is too big, key = val | |
|
Description |
TuxMsgQ server failed to open the queue space. As configured, the shared memory required for the queue space was too big for the system to handle. |
Action |
Reduce queue space configuration sizes so that the total shared memory required is less than 2147483648 bytes and re-try the operation. Contact Oracle Customer Support, if the problem persists. | |
2194 |
ERROR: shared memory required for the queue space is too big | |
|
Description |
As configured in the |
Action |
Reduce queue space configuration sizes so that the total shared memory required is less than 2147483648 bytes and re-try the operation. Contact Oracle Customer Support, if the problem persists. | |
See Also |
|
![]() |
![]() |
![]() |