This message is issued when an internal System/T routine
is passed invalid arguments.
Contact your TUXEDO System Technical Support.
An attempt was made to send a message to the
DBBL
and its whereabouts could not be ascertained either from the
BB
or from a
BRIDGE
process.
Check for a partitioned network, corrupted shared memory, or if all
administrative processes are running.
The system was attempting to decode message header information for
a reply, and the operation failed.
Examine the
userlog
for other messages about the error.
If necessary, contact the TUXEDO System Administrator
or your TUXEDO System Technical Support.
While processing a reply, the internal buffer type is unknown.
This refers to an internal system problem that could be caused,
for example, by corrupted shared memory.
Contact your TUXEDO System Technical Support.
The process received a message whose type and subtype
are not known. That is, the process' type switch was
not built to recognize the type and/or subtype of the
message received.
The process should be re-linked with the appropriate type
switch including the type and subtype that are printed
as part of this error message. Or, the process sending
the offending type/subtype should be altered to send a
buffer that the receiver understands.
tuxtypes(5), ubbconfig(5)
The process received a message whose type
is not known. That is, the process' type switch was
not built to recognize the type of the message received.
The process should be re-linked with the appropriate type
switch including the type that is printed
as part of this error message. Or, the process sending
the offending type should be altered to send a
buffer that the receiver understands.
tuxtypes(5), ubbconfig(5)
This message is issued when a process receives a typed buffer
that it fails to decode. The decode function called is part
of the buffer type switch.
Check the userlog for additional messages indicating why the
decoding failed.
If the buffer type or the encode/decode function is provided
by the application, contact your system administrator.
If this is one of the System/T provided
buffer types, contact your TUXEDO System Technical Support.
typesw(5)
Post-processing of the message received
by internal "post-receive" function for the buffer type failed.
Check the userlog for additional messages indicating why the
post-processing failed.
If the buffer type or the
postreceive
function is provided
by the application, contact your system administrator.
If this is one of the System/T provided
buffer types, contact your TUXEDO System Technical Support.
typesw(5)
While trying to retrieve the status field entry, the
tmid
passed in is invalid.
Contact your TUXEDO System Technical Support.
While trying to retrieve the status field entry, the
tmid
passed in is invalid.
Contact your TUXEDO System Technical Support.
While trying to retrieve the TMPROC information associated with the
tmid
specified, the entry is found to be invalid.
Contact your TUXEDO System Technical Support.
While trying to retrieve the TMPROC information associated with the
tmid
specified, the entry is found to be invalid.
Contact your TUXEDO System Technical Support.
While doing a warm start or load of the transaction log, an attempt
to add an entry to the transaction table was invalid.
Contact your TUXEDO System Technical Support.
While adding a transaction to the transaction table during warm start
or load of the transaction log of decided transactions,
the transaction table entry was found to have a group
whose state indicated that the transaction was either normally or
heuristically rolled back.
The state will be overwritten and no further notification will
be given as to the inconsistent state of the global transaction.
Since the transaction will most likely be driven through to
completion, the rollback status indicates that the operation
done by the rolled back transaction will be inconsistent.
For instance, this could indicate inconsistent data in a data base.
The action to reconcile this situation is application specific.
While warm starting the transaction log, an inconsistent entry
was found in the transaction table entry
Contact your TUXEDO System Technical Support.
This error occurs when the process is unable to detach from
shared memory or a failure is detected while trying to release
a request queue.
Contact your TUXEDO System Technical Support.
A memory allocation failure occurs while the system is mapping
the well known IPC key to an internal structure.
Remove processes that may be tying up physical memory, ensure
that the application ipc key is correct, or verify that the UNIX
sysgen
process sizing parameters are correct.
While attempting to shut down a server, the bulletin board entry for
the specified server cannot be found.
Try shutting the server down again. If this fails, you will
have to use the UNIX system
kill (1)
command to remove the process.
While trying to update the server table entry, the server's queue
entry cannot be accessed.
Contact your TUXEDO System Technical Support.
During shutdown of a MSSQ set server, the shutdown message needs to
be enqueued for each server instance. The message re-queuing has
failed.
Contact your TUXEDO System Technical Support.
The meta message header type was of an unknown type.
Contact your TUXEDO System Technical Support.
While advertising a new service, a reply is expected for the
meta-message but fails.
Contact your TUXEDO System Technical Support.
During the shutdown of a server the queue must be drained, and while
the queue is being checked the
getqcnt()
call fails. This error may occur if the Bulletin Board is not
locked or the queue information passed is in error.
Contact your TUXEDO System Technical Support.
While trying to shut down a server, the sentinel message could not
be queued.
Try to shut down the server again. If this fails, contact your TUXEDO System
Technical Support.
An attempt is made to shut down a group of TMS processes in an
invalid order. Specifying the TMS processes to be shut down by
group, lmid, or (S) will order the shutdown sequence properly.
The TMSs should not be shut down individually (using the -i option).
The -g -l -S flags should be used instead.
The application has denied a shutdown request.
This error can occur in a variety of different scenarios.
The system processes such as
(D)BBL ,
TMS ,
or
BRIDGE
may reach a condition in which they are unable to shut down.
For example, the
BBL
cannot process a shutdown request because a server fails
to disconnect.
Application servers may also reach this condition by returning a
"0" value in the default shutdown function,
_tmsvrstop ().
If this occurs, contact your TUXEDO System application administrator.
Check the
userlog
for other messages to determine the proper action to take.
In the above example of a system process (BBL) unable
to shut down, the force option (-w) may be used.
tmshutdown(1)
While attempting to reply to a shutdown request, the meta-message
send fails.
Contact your TUXEDO System Technical Support.
While trying to send a meta-message, the request cannot be sent.
Possible causes may be
a message type switch function failure,
an invalid message length,
or a low level message send failure.
Check for a partitioned network or corrupted shared memory.
Check that all administrative processes are running
and that the
sysgen
parms
(IPC parameters)
for messages are appropriate.
Also check the
userlog
for additional messages that may help to isolate the
problem.
Contact your TUXEDO System Technical Support.
While attempting to migrate servers to another machine, the system
is unable to process this request. All of the servers affected by
this request must be shut down.
Shut down the desired servers with the relocate (-R) option and reissue
the migrate request.
"TUXEDO Administrator's Guide" ,
tmadmin(1)
When attempting to migrate server(s) to another site, the system
is unable to complete the request because the alternate location
is not specified for an affected server group(s).
The LMID entry in the *GROUPS section for the affected server groups
must be updated. This may be achieved by using the
tmconfig()
command and updating the TA_LMID field of the affected server groups
to include the alternate location.
"TUXEDO Administrator's Guide" ,
tmadmin (1),
tmconfig (1)
When attempting to migrate server(s) to another site, the system
is unable to complete the request because the alternate locations
specified for the affected server group(s) are not the same.
The appropriate action for this request depends on if the alternate
locations are set properly or not. If the alternate locations of
server groups on an lmid are different, they may be migrated
independently by group. See the
tmadmin()
subcommand
migrategroup .
If the groups are to be moved to the same lmid,
the LMID entry in the *GROUPS section for the affected server groups
must be updated. This may be achieved by using the
tmconfig()
command and updating the TA_LMID field of the affected server groups
to specify the same alternate location. Then the request may be
resubmitted.
"TUXEDO Administrator's Guide" ,
tmadmin (1),
tmconfig (1)
During a migration request, this message is issued to point out that
the bulletin board for the alternate location
(lmid)
has been updated.
No action necessary.
During a migration request, this message is issued to point out that
the bulletin board for the alternate location
(lmid)
has been updated.
No action necessary.
While trying to get the status of a remote queue via
tmadmin ,
the message to the remote
BRIDGE
failed.
Check the userlog for earlier messages indicating the cause of the failure.
While trying to get the status of a remote queue via
tmadmin ,
the message to the remote
BRIDGE
failed.
Check the userlog for earlier messages indicating the cause of the failure.
An attempt dynamically to allocate memory from the operating system
using
malloc ()
failed while trying to suspend the
BRIDGE
during a partitioned shutdown.
Make sure 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.
While trying to suspend the
BRIDGE
during a partitioned shutdown,
the number of server entries retrieved is larger than the
number of entries allocated for retrieval.
This should not occur.
Re-run the
tmshutdown
command.
tmshutdown(1)
When opening a resource manager with
tpopen ,
the resource manager had the
TMUSEBRANCH
flag set from the XA Preliminary Specification.
This option is not supported.
Contact your resource manager vendor.
When opening a resource manager with
tpopen ,
the resource manager had the
TMUSEASYNC
flag set from the XA Preliminary Specification.
This option is not supported.
400 ERROR: Invalid arguments for getting acknowledgement
DESCRIPTION
ACTION
401 ERROR: Could not find DBBL
DESCRIPTION
ACTION
402 ERROR: Received message, decode of header failed
DESCRIPTION
ACTION
403 ERROR: Received message with an unknown internal type index val
DESCRIPTION
ACTION
404 ERROR: Received message of unknown type 'type' subtype 'subtype'
DESCRIPTION
ACTION
SEE ALSO
405 ERROR: Received message of unknown type 'type'
DESCRIPTION
ACTION
SEE ALSO
406 ERROR: Message decode failure
DESCRIPTION
ACTION
SEE ALSO
407 ERROR: Post receive operation on message failed
DESCRIPTION
ACTION
SEE ALSO
409 ERROR: Invalid table entry information given
DESCRIPTION
ACTION
410 ERROR: [Invalid table entry information given]
DESCRIPTION
ACTION
411 ERROR: [Invalid table information given]
DESCRIPTION
ACTION
412 ERROR: [Invalid table information given]
DESCRIPTION
ACTION
415 ERROR: Invalid transaction creation
DESCRIPTION
ACTION
416 WARN: Invalid state stateval for group groupname while adding transaction
DESCRIPTION
ACTION
417 ERROR: warmstart found bad log page entry
DESCRIPTION
ACTION
419 ERROR: Exit failure
DESCRIPTION
ACTION
421 ERROR: Memory allocation failure
DESCRIPTION
ACTION
422 ERROR: Cannot find own BB entry
DESCRIPTION
ACTION
423 ERROR: [Cannot update own queue]
DESCRIPTION
ACTION
424 ERROR: Cannot re-queue msg
DESCRIPTION
ACTION
425 ERROR: [Service receive: unknown meta-msg type: 0xmsg_type]
DESCRIPTION
ACTION
426 ERROR: [Service receive: cannot send meta-msg reply]
DESCRIPTION
ACTION
427 ERROR: [Cannot find own BB entry]
DESCRIPTION
ACTION
428 ERROR: Cannot re-queue msg
DESCRIPTION
ACTION
429 ERROR: Cannot perform shutdown at this time
DESCRIPTION
ACTION
430 ERROR: Application rejects shutdown request
DESCRIPTION
ACTION
SEE ALSO
431 ERROR: Service receive: cannot send meta-msg reply
DESCRIPTION
ACTION
433 ERROR: Send/receive error on remote procedure call
DESCRIPTION
ACTION
439 ERROR: Migration failed: Not all the servers are shutdown
DESCRIPTION
ACTION
SEE ALSO
441 ERROR: Migration failed: alternate location not specified
DESCRIPTION
ACTION
SEE ALSO
442 ERROR: Migration failed: alternate locations not the same
DESCRIPTION
ACTION
SEE ALSO
445 INFO: BB on machine lmid has been updated for migration of group group_name.
DESCRIPTION
ACTION
446 INFO: BB on machine lmid has been update for migration of groups from machine lmid.
DESCRIPTION
ACTION
459 ERROR: Send to BRIDGE failed
DESCRIPTION
ACTION
460 ERROR: Send to BRIDGE failed
DESCRIPTION
ACTION
461 ERROR: Memory allocation failure
DESCRIPTION
ACTION
462 ERROR: Retrieved too many entries in tmsuspend
DESCRIPTION
ACTION
SEE ALSO
463 ERROR: TMUSEBRANCH option not supported
DESCRIPTION
ACTION
465 ERROR: TMUSEASYNCH option not supported
DESCRIPTION