Corporate Info  |  News  |  Solutions  |  Products  |  Partners  |  Services  |  Events  |  Download  |  How To Buy
	http://www.oracle.com/technology/documentation/index.html   |   Site Map   |   Search   |   PDF Files   |   Contact   |   Glossary
Tuxedo Doc Home   |   Messages   |   Catalog List   |   Previous   |   Next

Q Messages 1400-1499

1400	ERROR: Queue scan - realloc() failed
	Description	An attempt to dynamically re-allocate memory from the operating system using realloc() failed while scanning the queue. The associated operation (qlist, qchangetime, qchangeprio, qchangequeue, or qdeletemsg) 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.
	See Also	qmadmin(1)
1401	INFO: Queue list - no messages matched on queue name
	Description	While executing the qlist command, no messages were found on the queue name that was set with qset and the selection criteria set with qscan.
	Action	Try specifying a different queue name or different scan criteria using qset or qscan. No action required.
	See Also	qmadmin(1)
1407	INFO: operation - no messages matched on queue name
	Description	While executing the qchangetime or qchangeprio command, no messages were found on the queue name that was set with qset and the selection criteria set with qscan.
	See Also	qmadmin(1)
	1409	WARN: Queue change - new queue name newqueue matches old queue name
	Description	While changing the queue on which messages are queued, the new queue name matched the original queue name so no change occurred.
	Action	No action required.
	See Also	qmadmin(1)
1410	INFO: operation - no messages matched on queue name
	Description	While executing the qchangequeue or qdeletemsg command, no messages were found on the queue name that was set with qset and the selection criteria set with qscan.
	Action	No action required
	See Also	qmadmin(1)
1422	ERROR: ipcrm - processes attached to queue space qspace
	Description	While executing the ipcrm command without the -f option or while executing the qaddext or qspacedestroy command, the IPC resources could not be removed because other processes were attached to the queue space.
	Action	Stop all processes attached to the queue space and re-execute the command. In rare situations where it doesn't matter if processes are attached to the queue space, the -f option of ipcrm can be used to force removal of the IPC resources, even if processes are attached to the queue space.
	See Also	qmadmin(1)
1423	WARN: ipcrm - failed to remove semid ident for queue space qspace
	Description	While executing the ipcrm, qaddext, or qspacedestroy command, one of the semaphores with semaphore identifier ident was not removed.
	Action	Normally this should not occur since the administrator is running qmadmin and is also the owner of the IPC resources. It is possible that the semaphore was removed directly using the operating system ipcrm(1) command. The operating system command (outside of qmadmin) "ipcs -s" will list currently existing semaphores and the semaphore can be removed directly by executing "ipcrm -s" ident.
	See Also	qmadmin(1)
1424	WARN: ipcrm - failed to delete shared memory id ident for queue space qspace
	Description	While executing the ipcrm, qaddext, or qspacedestroy command, one of the shared memory segments with identifier ident was not removed.
	Action	Normally this should not occur since the administrator is running qmadmin and is also the owner of the IPC resources. It is possible that the shared memory segment was removed directly using the operating system ipcrm(1) command. The operating system command (outside of qmadmin) "ipcs -m" will list currently existing shared memory segments and the segment can be removed directly by executing "ipcrm -m" ident.
	See Also	qmadmin(1)
1425	ERROR: Queue space creation - invalid parameter
	Description	While executing the qspacecreate command, an invalid parameter was specified. The following are invalid: the IPC key is less than or equal to 0; the number of queues, transactions, processes, or messages is less than or equal to 0; the configuration device is not specified; the queue space name is not specified or is greater than 15 characters in length; or the extent size is less than or equal to 0.
	Action	Re-enter the command with the correct parameters.
	See Also	qmadmin(1)
1427	ERROR: Queue space creation - extent size too small
	Description	While executing the qspacecreate command, the size of the extent that was specified was too small.
	Action	Re-enter the qspacecreate command with an extent size that is at least (Q +2) where Q is the number of queues specified.
	See Also	qmadmin(1)
1428	ERROR: Queue space creation - failed to create table name, size size on config config
	Description	While executing the qspacecreate command, qmadmin was unable to create a table, name, of size, size, on the configuration file, config. Most likely, there was not enough space available in the universal device list (or the UDL was not correctly initialized).
	Action	Use the lidl command to ensure that the universal device list is properly initialized and has enough space (use the crdl command to initialize it and create an extent that can be used to allocate space for the queue space). Also check the userlog for messages regarding locking the configuration or other configuration errors.
	See Also	qmadmin(1)
1429	ERROR: Add extent - invalid parameter
	Description	While executing the qaddextent command, an invalid parameter was specified. The following are invalid: the device is not specified; the queue space name is not specified or is greater than 15 characters in length; or the extent size is less than or equal to 0.
	Action	Re-enter the command with the correct parameters.
	See Also	qmadmin(1)
1430	ERROR: Add extent - cannot lock queue space name
	Description	While executing the qaddext command, qmadmin failed to lock the QMCONFIG device for exclusive update.
	Action	Check the userlog for further information about the process that has the configuration locked. Re-enter the command after the configuration has been unlocked.
	See Also	qmadmin(1)
1431	ERROR: Add extent - failed to create table name, size size for new extent on config config
	Description	While executing the qaddext command, qmadmin was unable to create a table, name, of size, size, on the configuration file, config. Most likely, there was not enough space available in the universal device list (or the UDL was not correctly initialized).
	Action	Use the lidl command to ensure that the universal device list is properly initialized and has enough space (use the crdl command to initialize it and create an extent that can be used to allocate the extent for the queue space). Also check the userlog for messages regarding locking the configuration or other configuration errors.
	See Also	qmadmin(1)
1432	ERROR: Destroy queue space - invalid parameter
	Description	While executing the qspacedestroy command, an invalid parameter was specified. The following are invalid: the device is not specified; or the queue space name is not specified or is greater than 15 characters in length.
	Action	Re-enter the command with the correct parameters.
	See Also	qmadmin(1)
1433	ERROR: Destroy queue space - cannot lock queue space name
	Description	While executing the qdestroyspace command, qmadmin failed to lock the QMCONFIG device for exclusive update.
	Action	Check the userlog for further information about the process that has the configuration locked. Re-enter the command after the configuration has been unlocked.
	See Also	qmadmin(1)
1434	ERROR: Destroy queue space - queue exists and force flag not specified
	Description	The qspacedestroy command without the -f option but one or more queues exist in the queue space.
	Action	Execute the qinfo command to see what queues exist in the queue space and how many messages are on the queues. To destroy the queue space, even if queues exist and processes may be attached, execute the qspacedestroy command with the -f option.
	See Also	qmadmin(1)
1435	WARN: Destroy queue space - failed to destroy table name on config config
	Description	While executing the qspacedestroy command, qmadmin was unable to destroy a configuration table, name, associated with queue space extent.
	Action	Check the userlog to see if further information failure has been printed there. Contact your BEA TUXEDO system Technical Support.
	See Also	qmadmin(1)
1436	ERROR: Create queue - invalid parameter
	Description	While executing the qcreate command, an invalid parameter was specified. The following are invalid: invalid ordering parameters such as the same sort value specified more than once or 'lifo'/'fifo' not specified as the least significant sort value; an invalid out-of-order value; retries or delay time less than 0; the queue space name is not specified or greater than 15 characters in length; the upper threshold less than or equal to 0 or less than the lower threshold value; or an invalid threshold type or a threshold type of '%' with a upper threshold value greater than 100.
	Action	Re-enter the command with the correct parameters.
	See Also	qmadmin(1)
1437	ERROR: Create queue - duplicate queue name 'queue_name'
	Description	While executing the qcreate command, a queue name, queue_name, was specified that already exists in the queue space.
	Action	Use the qinfo command to list the queues that currently exist in the queue space and choose a different queue name.
	See Also	qmadmin(1)
1438	INFO: Create queue - error queue name created
	Description	The queue that was just created with the qcreate command is the error queue that was defined for the queue space (using the qspacecreate command). When the queue space is first created and opened, the error queue does not exist and a warning is printed in the userlog. This message indicates that the error queue is now available.
	Action	No action required.
	See Also	qmadmin(1)
1439	ERROR: Destroy queue - invalid queue name parameter
	Description	While executing the qdestroy command, the queue name was not specified.
	Action	Re-execute the command with a valid queue name.
	See Also	qmadmin(1)
1440	ERROR: Destroy queue failed - processes attached
	Description	While executing the qdestroy command without the -f option, the operation failed because processes were attached to the queue space.
	Action	Stop the processes that are attached to the queue space and re-execute the command. In situations where it doesn't matter if processes are attached to the queue space, the -f option of qdestroy can be used to force removal of the queue, even if processes are attached to the queue space.
	See Also	qmadmin(1)
1441	ERROR: Destroy queue failed - shmctl returned -1, errno = errno
	Description	While executing the qdestroy command without the -f option, the operation failed because qmadmin was unable to get the status of the queue space shared memory. The errno, errno, is printed as part of the message.
	Action	Using the errno, determine why the status (shmctl) failed and re-execute the command. If necessary, stop all processes attached to the queue space and remove the IPC resources using the qmadmin ipcrm command.
	See Also	qmadmin(1)
1442	ERROR: Semaphore initialization - Memory allocation failure
	Description	An attempt to dynamically allocate memory from the operating system using malloc() failed while initializing the system semaphores.
	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.
1443	ERROR: Destroy queue failed - messages on queue and force or purge not specified
	Description	While executing the qdestroy command without the -f or -p options, messages were found on the queue.
	Action	If the queue is to be destroyed, purging the messages from the queue, then re-execute the qdestroy command with the -p option.
	See Also	qmadmin(1)
1444	WARN: Destroy queue - error queue queue_name destroyed
	Description	While executing the qdestroy command, the error queue for the queue space was destroyed. This means that when messages have reached their retry count limit, they will be deleted instead of being moved to the error queue.
	Action	No action required.
	See Also	qmadmin(1)
1445	ERROR: operation - invalid queuespace qspace on config config
	Description	While executing the specified operation, operation, for the queue space, qspace, on the specified configuration, config, the operation failed because the queue space was not valid. In particular, the first block of the first extent did not contain a valid queue space block (superblock). The operation may be one of ipcs, ipcrm, "Add extent", "Destroy queue space", or xa_open.
	Action	Check to make sure that the correct queue space name and device were specified. Contact your BEA TUXEDO system Technical Support.
	See Also	qmadmin(1)
1446	ERROR: semop() lock failure, id = ident, errno = errno
	Description	While trying to lock a portion of the queue space (using a system semaphore with the specified identifier, ident), an error was returned from the semop() system call (the error number was errno). This usually indicates that the semaphore was removed using ipcrm and can be verified by using the ipcs(1) command.
	Action	Stop all processes attached to the queue space. Remove all IPC resources using the ipcrm command within qmadmin, and re-start the processes.
	See Also	qmadmin(1)
1447	WARN: [Semaphore appears stuck - currently held by pid]
	Description	While trying to lock a portion of the queue space (using a user-level semaphore), the process is unable to get the lock for a long period.
	Action	This WARNING message is from _qm_lock() function, which locks any semaphore used by the queue space. The process identifier printer in this WARNING message should give you some indication of which process is trying to lock the semaphore. If the process is hung it must be stopped and the IPC resources must be removed using qmadmin ipcrm command
	See Also	qmadmin(1)
1448	ERROR: semop() unlock failure, id = ident, errno = errno
	Description	While trying to unlock a portion of the queue space (using a system semaphore with the specified identifier, ident), an error was returned from the semop() system call (the error number was errno). This usually indicates that the semaphore was removed using ipcrm and can be verified by using the ipcs(1) command.
	Action	Contact your BEA TUXEDO system Technical Support.
	See Also	qmadmin(1)
1449	ERROR: Create queue - no more queue entries (max = entries)
	Description	While executing the qcreate command, no more queue entries were available. The number of queues is specified when the queue space is created.
	Action	Use the qinfo command to see what queues are available in the queue space and determine if they are all being used. Re-use an existing queue or delete an existing queue using the qdelete command.
	See Also	qmadmin(1)
1450	ERROR: semctl() SETALL failure, key = key, errno = errno
	Description	While first opening the queue space and initializing the IPC resources, semctl failed to initialize a newly created semaphore set. The key for the semaphore set, key, and the error number, errno, are printed in the message.
	Action	Determine why the error occurred by looking at the errno value and also checking if the semaphore set exists using the ipcs(1) command. Remove any IPC resources created for the queue space using the ipcrm command in qmadmin and try again.
	See Also	qmadmin(1)
1451	ERROR: semget() failure, key = key, errno = errno
	Description	While first opening the queue space and initializing the IPC resources, semget failed to get a semaphore set. The key for the semaphore set, key, and the error number, errno, are printed in the message.
	Action	Determine why the error occurred by looking at the errno value and also checking if the semaphore set exists using the ipcs(1) command.
	See Also	qmadmin(1)
1452	ERROR: semop() lock failure, id = ident, errno = errno
	Description	While trying to lock the queue space (using a system semaphore with the specified identifier, ident), an error was returned from the semop() system call (the error number was errno). This usually indicates that the semaphore was removed using ipcrm and can be verified by using the ipcs(1) command.
	Action	Stop all processes attached to the queue space. Remove all IPC resources using the ipcrm command within qmadmin, and re-start the processes.
	See Also	qmadmin(1)
1456	ERROR: Enqueue - Memory allocation failure
	Description	An attempt to dynamically allocate memory from the operating system using malloc() failed while enqueuing a message.
	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	qmadmin(1)
1458	ERROR: Enqueue - out of message entries
	Description	While trying to enqueue a message, the maximum number of messages that can be stored in the queue space was reached so the message could not be enqueued. A diagnostic "(QMESYSTEM)" is returned to the process trying to enqueue the message.
	Action	Remove some messages from the queue space either by processing them or by deleting some via the qdeletemsg command of qmadmin. The qinfo command of qmadmin can be used to determine on what queues the messages reside.
	See Also	qmadmin(1), tpenqueue(3c)
1459	ERROR: Enqueue - out of queue space
	Description	While trying to enqueue a message, no room was found to store the message in the queue space so the message could not be enqueued. A diagnostic "(QMESYSTEM)" is returned to the process trying to enqueue the message.
	Action	Remove some messages from the queue space either by processing them or by deleting some via the qdeletemsg command of qmadmin. The qinfo command of qmadmin can be used to determine on what queues the messages reside. The qaddext command can be used to add another extent to the queue space to provide more room for storing messages.
	See Also	qmadmin(1)
1460	ERROR: Dequeue - Memory allocation failure
	Description	An attempt to dynamically allocate memory from the operating system using malloc() failed while dequeuing a message.
	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	tpdequeue(3c)
1464	ERROR: xa_open() - OPENINFO string is null
	Description	xa_open was called with a NULL OPENINFO string. The NULL value is only supposed to be passed to the "NULL XA" interface. This usually indicates that the application was configured as the "NULL XA" interface but the server provided was that for the Queue Manager.
	Action	Change the configuration to indicate the correct resource manager.
	See Also	ubbconfig(5)
1465	ERROR: xa_open() - OPENINFO string length must be less than len characters
	Description	xa_open was called with an OPENINFO string that was too long (that is, len characters or more).
	Action	Change the application configuration to ensure that the OPENINFO string, composed of the name of configuration device or file and the queue space name, separated by a colon, is 256 characters or less in length.
	See Also	ubbconfig(5)
1467	ERROR: xa_open() - invalid OPENINFO string
	Description	xa_open was called with an invalid OPENINFO string; it did not contain a colon separating the configuration name from the queue space name.
	Action	Change the application configuration to ensure that the OPENINFO string is composed of the name of configuration device or file and the queue space name, separated by a colon.
	See Also	ubbconfig(5)
1469	ERROR: [xa_close() - thread must dissociate before calling xa_close]
	Description	xa_close was called while still associated with a transaction.
	Action	Contact your BEA TUXEDO system Technical Support.
1471	ERROR: operation - effective user id, userid, must match the owner of config, config_userid
	Description	The process was run by a user whose effective user identifier, userid, is not the same as the owner of the configuration device, config, which has a user identifier config_userid.
	Action	Change the ownership of the configuration device or file, or run the program as the corresponding user.
	See Also	qmadmin(1)
1472	ERROR: xa_start() - no more tran table entries (max = entries)
	Description	xa_start was called to start a new transaction but no transaction entries are free in the queue space.
	Action	Execute the qprinttrans command to see what transactions are currently outstanding. Use qcommittrans or qaborttrans to complete transactions that are in READY state but not completed.
	See Also	qmadmin(1)
1473	ERROR: Queue space creation - ipckey is already used -- choose another one or check existing semaphores
	Description	While executing the qspacecreate command, an IPC key was specified for which a semaphore already exists. This probably means that another application is using the IPC key.
	Action	Choose another IPC key and re-execute the command.
	See Also	qmadmin(1)
1474	ERROR: [xa_start() - TMRESUME specified for unassociated thread]
	Description	xa_start was called with the TMRESUME flag in a process that is not associated with the transaction.
	Action	Contact your BEA TUXEDO system Technical Support.
1475	ERROR: [xa_start() - cannot associate with prepared transaction]
	Description	xa_start was called for a transaction that is prepared for commit. xa_start will fail.
	Action	Contact your BEA TUXEDO system Technical Support.
1476	ERROR: [xa_start() - called with TMJOIN when TMRESUME expected]
	Description	xa_start() was called with the TMJOIN flag for a transaction in which the process is currently suspended.
	Action	Contact your BEA TUXEDO system Technical Support.
1477	ERROR: [xa_start() - called twice with no intervening xa_end]
	Description	xa_start() was called for a transaction with which the process is already associated.
	Action	Contact your BEA TUXEDO system Technical Support.
1478	ERROR: [xa_end() - TMMIGRATE not supported]
	Description	xa_end() was called with the TMMIGRATE flag, even though the resource manager indicated that it does not support migration.
	Action	Contact your BEA TUXEDO system Technical Support.
1479	ERROR: [xa_end() - xid differs from xa_start xid]
	Description	xa_end was called with a transaction identifier that is different from the one with which the process is currently associated.
	Action	Contact your BEA TUXEDO system Technical Support.
1480	ERROR: [xa_end() - called from unassociated thread]
	Description	xa_end was called in a process that is not associated with a transaction.
	Action	Contact your BEA TUXEDO system Technical Support.
1481	ERROR: [xa_end() - xid differs from xa_start xid]
	Description	xa_end was called with a transaction identifier that does not match the transaction identifier specified in the prior xa_start.
	Action	Contact your BEA TUXEDO system Technical Support.
1482	ERROR: [xa_end() - transaction status not valid (trx = index, status = status)]
	Description	xa_end() was called but the transaction status is not valid.
	Action	Contact your BEA TUXEDO system Technical Support.
1483	ERROR: [xa_prepare() - transaction already in ready state]
	Description	xa_prepare was called but the transaction is already in READY state.
	Action	Contact your BEA TUXEDO system Technical Support.
1484	ERROR: [xa_prepare() - threads still active]
	Description	xa_prepare() was called while one or more processes were still associated with the transaction.
	Action	Contact your BEA TUXEDO system Technical Support.
1485	ERROR: [xa_prepare() - transaction not in proper state for prepare (status = 0xstatus)]
	Description	xa_prepare() was called but the transaction is not in a valid state.
	Action	Contact your BEA TUXEDO system Technical Support.
1486	ERROR: [xa_commit() - threads still active]
	Description	xa_commit() was called but one or more processes are still associated with the transaction.
	Action	Contact your BEA TUXEDO system Technical Support.
1487	ERROR: [xa_commit() - tried to one-phase commit and TMONEPHASE not set]
	Description	xa_commit() was called without first calling xa_prepare() but the TMONEPHASE flag was not set.
	Action	Contact your BEA TUXEDO system Technical Support.
1488	ERROR: [xa_commit() - transaction not in proper state for commit (status = 0xstatus)]
	Description	xa_commit() was called but the transaction is not in a valid state.
	Action	Contact your BEA TUXEDO system Technical Support.
1489	ERROR: [xa_rollback() - transaction not in proper state for roll back (status=0xstatus)]
	Description	xa_rollback() was called but the transaction is not in a valid state.
	Action	Contact your BEA TUXEDO system Technical Support.
1490	ERROR: [xa_recover() - xid pointer is NULL, count is not 0]
	Description	xa_recover() was called with a NULL pointer for the transaction array but the count of entries in the array is not 0.
	Action	Contact your BEA TUXEDO system Technical Support.
1491	ERROR: [xa_recover() - count cannot be negative]
	Description	xa_recover() was called with a negative count for the number of entries in the transaction array.
	Action	Contact your BEA TUXEDO system Technical Support.
1492	ERROR: [xa_recover() - called without TMSTARTRSCAN and scan not in progress]
	Description	xa_recover() was called without the TMSTARTRSCAN flag and it was not previously called with the TMSTARTRSCAN to start a scan.
	Action	Contact your BEA TUXEDO system Technical Support.
1493	ERROR: [xa_forget() - transaction has not been heuristically completed]
	Description	xa_forget() was called for a transaction that has not been heuristically committed or rolled back.
	Action	Contact your BEA TUXEDO system Technical Support.
1494	ERROR: xa_open() - failed to get shared memory, key = key, errno = errno
	Description	While opening the queue space, xa_open() was unable to get the necessary shared memory. The error number, errno, is printed in the message.
	Action	This failure can be caused by a number of reasons but the most likely is that either the amount of shared memory requested would cause an operating system tunable to be exceeded (shared memory for the system or shared memory identifiers), or another application is using the same key. Determine and correct the problem.
1495	ERROR: xa_open() - failed to attach to shared memory, key = key, errno = errno
	Description	While opening the queue space, xa_open() was unable to attach to the queue space shared memory. The error number, errno, is printed in the message.
	Action	This failure can be caused by a number of reasons but the most likely is that the amount of shared memory requested would cause an operating system tunable to be exceeded (shared memory for the system, process size or shared memory segments attached to a process). Determine and correct the problem.
1496	WARN: xa_open() - error queue name not created
	Description	While opening the queue space, the error queue, name, does not exist.
	Action	No action is required but any messages that reach the retry count limit for their queue will be deleted instead of being moved to the queue space error queue. It is recommended that the error queue be creating using the qcreate command of qmadmin.
	See Also	qmadmin(1)
1497	ERROR: xa_open() - no more process table slots
	Description	While opening the queue space, no more entries were found in the process table. The size of this table is specified when the queue space is created.
	Action	Stop any processes that are attached to the queue space that are not needed.
	See Also	qmadmin(1)
1498	WARN: xa_open() - message with no matching queue 'name'
	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 warmo start, a message was found that did not have a corresponding queue. This can occur when a queue with messages on it is deleted but the operation does not complete.
	Action	If the queue named in the message was not deleted, contact your BEA TUXEDO system Technical Support.
	See Also	qmadmin(1)
1499	ERROR: xa_open() - no more tran table entries (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, all transaction table entries were used.
	Action	This could occur if the queue space transaction table size was changed with outstanding transactions on the queue space. Use the qspacechange command to increase the size of the transaction table.