|
 |
| e-docs > Tuxedo > Messages > LIBTUX Catalog List > LIBTUX Messages 600-699 |
|
LIBTUX Messages 600-699
600
ERROR: [Invalid buffer type information type]
Description
The buffer type information provided in the configuration file was incorrect.
Action
Check the configuration file, verify that the buffer type provided is correct, and repeat the operation.
See Also
ubbconfig(5), tmloadcf(1)
601
ERROR: [Invalid buffer subtype information subtype_val]
Description
The buffer subtype information provided in the configuration file was incorrect.
Action
Check the configuration file, verify that the buffer type provided is correct, and repeat the operation.
See Also
ubbconfig(5), tmloadcf(1)
602
ERROR: TUXCONFIG environment variable not set
Description
The TUXCONFIG environment variable is not set.
Action
Set and export the TUXCONFIG environment variable, which should be the same as defined in the UBBCONFIG file.
See Also
ubbconfig(5)
603
ERROR: TUXCONFIG file filename does not exist
Description
The TUXCONFIG file, filename, does not exist.
Action
Check the TUXCONFIG environment variable to see if it matches with the definition of the TUXCONFIG in the UBBCONFIG file. Then, check to see if the TUXCONFIG file has been generated. If not, use tmloadcf(1) to create the TUXCONFIG file.
See Also
tmloadcf(1), ubbconfig(5)
604
ERROR: Cannot get file status on TUXCONFIG file filename, errno = errno_val
Description
Cannot get the file status on the TUXCONFIG file, filename.
Action
Check the UNIX errno for reasons and take appropriate actions accordingly.
See Also
stats(2) in UNIX system reference manuals
605
ERROR: TUXOFFSET environment variable must be >= 0
Description
The TUXOFFSET environment variable is less than 0.
Action
Specify a value for the TUXOFFSET environment variable that is greater than or equal to 0. This TUXOFFSET value must be the same as defined in the UBBCONFIG file.
See Also
ubbconfig(5)
607
ERROR: Cannot open section section_name of the TUXCONFIG: file
Description
The section_name of the TUXCONFIG file cannot be opened. The TUXCONFIG file might be corrupted.
Action
You can shut down the application and re-load the TUXCONFIG file using tmloadcf. If the error still occurs, contact your BEA TUXEDO system Technical Support.
See Also
tmloadcf(1)
608
ERROR: Memory allocation failure
Description
Memory allocation failed for adding new sections in the TUXCONFIG file.
Action
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.
610
ERROR: Cannot close the TUXCONFIG file
Description
The TUXCONFIG file in the VTOC table cannot be closed.
Action
Check the permission and the existence of the TUXCONFIG file, or contact your BEA TUXEDO system Technical Support.
612
ERROR: Read an entry from the VTOC table failed
Description
Reading an entry from the disk table failed. Possible causes:
read() to fail.
Action
Check your disk tables such as VTOC for possible corruptions and/or damages. If this error still occurs, contact your BEA TUXEDO system Technical Support.
See Also
read(2) in UNIX system reference manuals
614
ERROR: Cannot write to the section_name of the TUXCONFIG file which is not opened
Description
Cannot write to the section_name of the TUXCONFIG file which was never opened.
Action
Check your TUXCONFIG file, or contact your BEA TUXEDO system Technical Support.
See Also
tmunloadcf(1), write(2) in UNIX system reference manuals
615
ERROR: Write to the section_name of the TUXCONFIG file failed
Description
Write to the section_name of the TUXCONFIG file in VTOC table failed. Possible causes:
write() to fail.
Action
Check your disk tables such as VTOC for possible corruptions and/or damages. If this error still occurs, contact your BEA TUXEDO system Technical Support.
See Also
write(2) in UNIX system reference manuals
616
ERROR: The routing section of the TUXCONFIG file cannot be located
Description
The routing section of the TUXCONFIG file cannot be located. Possible causes:
Action
Contact your BEA TUXEDO system Technical Support. See Messages 602, 605, and 607 in this chapter for explanation.
624
ERROR: Data tables for routing section full
Description
Data routing tables in the Bulletin Board are full when parsing the routing range and creating the data routing entries.
Action
This is a system error, contact your BEA TUXEDO system Technical Support.
625
ERROR: More than one wild card in entry range
Description
More than one wild-card (*) range for the short routing data was specified in the data routing entry.
Action
Check your UBBCONFIG file for multiple definitions of wild-card ranges for the short routing data. Only one wild-card range is allowed per routing entry and it should be the last (ranges following it will be ignored).
See Also
ubbconfig(5)
626
ERROR: Range values out of order upper_range < lower_range
Description
The range values for the short routing data are out of order, that is, the upper range value is less than the lower range value.
Action
Check routing range values for the short routing data in your UBBCONFIG file. The lower range value must be less than or equal to the upper range value.
See Also
ubbconfig(5)
627
ERROR: More than one wild card in entry range
Description
More than one wild-card (*) range for the integer routing data was specified in the data routing entry.
Action
Check your UBBCONFIG file for multiple definitions of wild-card ranges for the integer routing data. Only one wild-card range is allowed per routing entry and it should be the last (ranges following it will be ignored).
See Also
ubbconfig(5)
628
ERROR: Range values out of order upper_range < lower_range
Description
The range values for the integer routing data are out of order, that is, the upper range value is less than the lower range value.
Action
Check routing range values for the integer routing data in your UBBCONFIG file. The lower range value must be less than or equal to the upper range value.
See Also
ubbconfig(5)
629
ERROR: More than one wild card in entry range
Description
More than one wild-card (*) range for the long routing data was specified in the data routing entry.
Action
Check your UBBCONFIG file for multiple definitions of wild-card ranges for the long routing data. Only one wild-card range is allowed per routing entry and it should be the last (ranges following it will be ignored).
See Also
ubbconfig(5)
630
ERROR: Range values out of order upper_range < lower_range
Description
The range values for the long routing data are out of order, that is, the upper range value is less than the lower range value.
Action
Check routing range values for the long routing data in your UBBCONFIG file. The lower range value must be less than or equal to the upper range value.
See Also
ubbconfig(5)
631
ERROR: More than one wild card in entry range
Description
More than one wild-card (*) range for the float routing data was specified in the data routing entry.
Action
Check your UBBCONFIG file for multiple definitions of wild-card ranges for the float routing data. Only one wild-card range is allowed per routing entry and it should be the last (ranges following it will be ignored).
See Also
ubbconfig(5)
632
ERROR: Range values out of order upper_range < lower_range
Description
The range values for the float routing data are out of order, that is, the upper range value is less than the lower range value.
Action
Check routing range values for the float routing data in your UBBCONFIG file. The lower range value must be less than or equal to the upper range value.
See Also
ubbconfig(5)
633
ERROR: More than one wild card in entry range
Description
More than one wild-card (*) range for the double routing data was specified in the data routing entry.
Action
Check your UBBCONFIG file for multiple definitions of wild-card ranges for the double routing data. Only one wild-card range is allowed per routing entry and it should be the last (ranges following it will be ignored).
See Also
ubbconfig(5)
634
ERROR: Range values out of order upper_range < lower_range
Description
The range values for the double routing data are out of order, that is, the upper range value is less than the lower range value.
Action
Check routing range values for the double routing data in your UBBCONFIG file. The lower range value must be less than or equal to the upper range value.
See Also
ubbconfig(5)
635
ERROR: More than one wild card in entry range
Description
More than one wild-card (*) range for the char routing data was specified in the data routing entry.
Action
Check your UBBCONFIG file for multiple definitions of wild-card ranges for the char routing data. Only one wild-card range is allowed per routing entry and it should be the last (ranges following it will be ignored).
See Also
ubbconfig(5)
636
ERROR: Range values out of order upper_range < lower_range
Description
The range values for the char routing data are out of order, that is, the upper range value is less than the lower range value.
Action
Check routing range values for the char routing data in your UBBCONFIG file. The lower range value must be less than or equal to the upper range value.
See Also
ubbconfig(5)
637
ERROR: More than one wild card in entry range
Description
More than one wild-card (*) range for the string routing data was specified in the data routing entry.
Action
Check your UBBCONFIG file for multiple definitions of wild-card ranges for the string routing data. Only one wild-card range is allowed per routing entry and it should be the last (ranges following it will be ignored).
See Also
ubbconfig(5)
638
ERROR: Range values out of order for the string routing data
Description
The range values for the string routing data are out of order, that is, the upper range value is less than the lower range value.
Action
Check routing range values for the string routing data in your UBBCONFIG file. The lower range value must be less than or equal to the upper range value.
See Also
ubbconfig(5)
639
ERROR: More than one wild card in entry range
Description
More than one wild-card (*) range for the carray routing data was specified in the data routing entry.
Action
Check your UBBCONFIG file for multiple definitions of wild-card ranges for the carray routing data. Only one wild-card range is allowed per routing entry and it should be the last (ranges following it will be ignored).
See Also
ubbconfig(5)
640
ERROR: Range values out of order for the carray routing data
Description
The range values for the carray routing data are out of order, that is, the upper range value is less than the lower range value.
Action
Check routing range values for the carray routing data in your UBBCONFIG file. The lower range value must be less than or equal to the upper range value.
See Also
ubbconfig(5)
641
ERROR: Unknown field type was specified for data routing entry
Description
An unknown field type was specified in the data routing entry.
Action
Check the field types specified in the ROUTING section of the UBBCONFIG file.
See Also
ubbconfig(5)
642
ERROR: Expected colon to separate server group range
Description
Within a range and a server group pair, the range is separated from the server group by a colon (:) in the ROUTING section of the UBBCONFIG file.
Action
Check the range and server group specified in the ROUTING section of the UBBCONFIG file. A colon (:) is expected to separate the range and the server group.
See Also
ubbconfig(5)
643
ERROR: Expected comma after group name grpname,string
Description
Within a range and a server group pair, a comma (,) is expected after server group name in the ROUTING section of the UBBCONFIG file.
Action
Check the range and the server group specified in the ROUTING section of the UBBCONFIG file. A comma (,) is expected after the server group name.
See Also
ubbconfig(5)
644
ERROR: Expecting keyword MAX
Description
The keyword MAX is expected to indicate the maximum value for the data type of the associated field in the ROUTING section of the UBBCONFIG file.
Action
Check the range and server group specified in the ROUTING section of the UBBCONFIG file. The keyword MAX should be specified to indicate the maximum value for the data type of the associated field.
See Also
ubbconfig(5)
645
ERROR: Expecting keyword MIN
Description
The keyword MIN is expected to indicate the minimum value for the data type of the associated field in the ROUTING section of the UBBCONFIG file.
Action
Check the range and the server group specified in the ROUTING section of the UBBCONFIG file. The keyword MIN should be specified to indicate the minimum value for the data type of the associated field.
See Also
ubbconfig(5)
646
ERROR: Expecting keyword MIN or MAX
Description
The keyword MAX or MIN is expected to indicate the maximum or minimum value for the data type of the associated field in the ROUTING section of the UBBCONFIG file.
Action
Check the range and server group specified in the ROUTING section of the UBBCONFIG file. The keyword MAX or MIN should be specified to indicate the maximum or the minimum value for the data type of the associated field.
See Also
ubbconfig(5)
647
ERROR: Value out of range for a short value
Description
The routing value for a short routing data is out of range.
Action
Check routing range values for the short routing data in the ROUTING section of the UBBCONFIG file.
See Also
ubbconfig(5)
648
ERROR: Value out of range for an int value
Description
The routing value for an integer routing data is out of range.
Action
Check routing range values for the integer routing data in the ROUTING section of the UBBCONFIG file.
See Also
ubbconfig(5)
649
ERROR: Value out of range for a long value
Description
The routing value for a long routing data is out of range.
Action
Check routing range values for the long routing data in the ROUTING section of the UBBCONFIG file.
See Also
ubbconfig(5)
650
ERROR: Expecting a ' ', '+', '-' or number after 'e/E' in float/double
Description
A ' ', '+', '-' or number after 'e' or 'E' is expected for float or double routing values.
Action
Check the routing range values of the float and double in the ROUTING section of the UBBCONFIG file.
See Also
ubbconfig(5)
651
ERROR: Value out of range for a float value
Description
The routing value for a float routing data is out of range.
Action
Check routing range values for the float routing data in the ROUTING section of the UBBCONFIG file.
See Also
ubbconfig(5)
652
ERROR: Value out of range for a double value
Description
The routing value for a double routing data is out of range.
Action
Check routing range values for the double routing data in the ROUTING section of the UBBCONFIG file.
See Also
ubbconfig(5)
653
ERROR: Expected single quote to begin char routing data value
Description
A single quote (') is expected at the beginning of char routing data.
Action
Check routing range values for the char routing data in the ROUTING section of the UBBCONFIG file. A char routing data must be begun with a single quote (').
See Also
ubbconfig(5)
654
ERROR: Expected single quote to end char routing data value
Description
A single quote (') is expected at the end of char routing data.
Action
Check routing range values for the char routing data in the ROUTING section of the UBBCONFIG file. A char routing data must be ended with a single quote (').
See Also
ubbconfig(5)
655
ERROR: No more string pool free space available for routing strings and carrays
Description
The routing string pool in the Bulletin Board is full when filling the data routing section with string and carray data.
Action
This is a system error, contact your BEA TUXEDO system Technical Support.
656
ERROR: Expected single quote for string/carray routing data value
Description
A single quote (') is expected for string and carray routing data.
Action
Check routing range values for string and carray routing data in the ROUTING section of the UBBCONFIG file. The string and carray routing data must be within single quotes (').
See Also
ubbconfig(5)
657
ERROR: No more string pool free space available for routing strings and carrays
Description
There is not enough routing free string pool space in the Bulletin Board when filling the data section with string and carray data.
Action
This is a system error, contact your BEA TUXEDO system Technical Support.
659
ERROR: Discovered a NULL character in string routing data value
Description
A NULL character is found in the string routing data.
Action
Check the string routing data for NULL characters in the ROUTING section of the UBBCONFIG file. A string value is terminated with a NULL character.
See Also
ubbconfig(5)
660
ERROR: [Unable to find server group section of TUXCONFIG file]
Description
A BEA TUXEDO system internal function was used to retrieve server group information from the TUXCONFIG file, but the function failed.
Action
Contact your BEA TUXEDO system Technical Support for assistance.
661
ERROR: Invalid logical machine name - lmid
Description
The logical machine name identifier provided is invalid. The most likely reason for that is a duplicate logical machine identifier.
Action
Check the configuration file and ensure that no duplicate logical machine names are being used. If so, correct the name and try the operation again.
See Also
ubbconfig(5), tmloadcf(1)
662
ERROR: Invalid logical machine name - lmid
Description
The logical machine name identifier provided is invalid. The most likely reason for that is a duplicate logical machine identifier.
Action
Check the configuration file and ensure that no duplicate logical machine names are being used. If duplicates are present, correct the name and try the operation again.
See Also
ubbconfig(5), tmloadcf(1)
663
ERROR: Invalid logical machine name for server group
Description
The logical machine name identifier provided for the server group is invalid.
Action
Check the configuration file and ensure that the LMID used for the server group is correct. Then try the operation again.
See Also
ubbconfig(5), tmloadcf(1)
664
ERROR: Duplicate server group entry
Description
A duplicate entry for server groups was defined.
Action
Check the configuration file and ensure that the server group names and IDs are unique. Then try the operation again.
See Also
ubbconfig(5), tmloadcf(1)
665
ERROR: Invalid server group name - svrgrp_name
Description
Cannot retrieve server group from the Bulletin Board because an invalid server group name was given.
Action
This is a system error, contact your BEA TUXEDO system Technical Support.
666
ERROR: Message operation failed because the queue was removed
Description
msgsnd to a queue failed because the queue was removed.
Action
Check the message queues, or contact your BEA TUXEDO system Technical Support.
See Also
intro(2), msgsnd(2), msgrcv(2), msgctl(2) in UNIX system reference manuals
667
ERROR: Message operation failed because of the bad message type
Description
msgsnd to a queue failed because of the bad message type.
Action
Check the message type in msgsnd(). The message is probably corrupted. Contact your BEA TUXEDO system Technical Support.
See Also
intro(2), msgsnd(2), msgrcv(2), msgctl(2) in UNIX system reference manuals
668
ERROR: Message operation failed because the message size < 0
Description
msgsnd to a queue failed because the message size is less than zero.
Action
Check the message size in msgsnd(). The message is probably corrupted. Contact your BEA TUXEDO system Technical Support.
See Also
intro(2), msgsnd(2), msgrcv(2), msgctl(2) in UNIX system reference manuals
669
ERROR: Message operation failed because of the invalid message queue identifier
Description
msgsnd to a queue failed because of invalid message queue identifier. This can also occur if a request is made by a client who exits before the request is satisfied. The cleanup after the client exits removes the message queue.
Action
Check the message queue identifier in msgsnd(). The message may be corrupted. Contact your BEA TUXEDO system Technical Support.
See Also
intro(2), msgsnd(2), msgrcv(2), msgctl(2) in UNIX system reference manuals
670
ERROR: Message operation failed because the message is too big
Description
msgsnd to a queue failed because the message is too big.
Action
Check the size of the message in msgsnd().
See Also
intro(2), msgsnd(2), msgrcv(2), msgctl(2) in UNIX system reference manuals
671
ERROR: Message operation failed because the message queue is empty
Description
msgsnd to a queue failed because the message queue is empty.
Action
Check the message queues.
See Also
intro(2), msgsnd(2), msgrcv(2), msgctl(2) in UNIX system reference manuals
672
ERROR: Message operation failed because the message queue or the system is full
Description
msgsnd to a queue failed because the message queue or the system is full.
Action
Check kernel parameters for message queues. Re-configure your system to meet your needs.
See Also
intro(2), msgsnd(2), msgrcv(2), msgctl(2) in UNIX system reference manuals
673
ERROR: Message operation failed because the access permissions were denied
Description
msgsnd to a queue failed because the message queue cannot be accessed.
Action
Check the message queue permissions.
See Also
intro(2), msgsnd(2), msgrcv(2), msgctl(2) in UNIX system reference manuals
674
ERROR: Message operation failed because of a bad address
Description
msgsnd to a queue failed because the message pointer is pointing to an illegal address.
Action
Check the address of the message queue pointer, or contact your BEA TUXEDO system Technical Support.
See Also
intro(2), msgsnd(2), msgrcv(2), msgctl(2) in UNIX system reference manuals
675
ERROR: Message operation failed due to unknown causes
Description
msgsnd to a queue failed due to unknown causes.
Action
Contact your BEA TUXEDO system Technical Support.
See Also
intro(2), msgsnd(2), msgrcv(2), msgctl(2) in UNIX system reference manuals
678
ERROR: Message send/receive failure for remote procedure call
Description
msgsnd/rcv failed for remote procedure call requests that are sent to the DBBL (or BBL in SHM mode). Possible causes:
Action
Check DBBL, servers, and message queues, or contact your BEA TUXEDO system Technical Support. See Messages 503, 505, and 506 in this chapter for explanation
See Also
intro(2), msgsnd(2), msgrcv(2), msgctl(2) in UNIX system reference manuals
679
ERROR: Memory allocation failure
Description
An attempt dynamically to allocate memory from the operating system using malloc() failed while making a private copy of the bulletin board.
Action
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.
680
ERROR: Effective UID or GID does not match bulletin board
Description
The calling process's effective user-id, UID, or group-id, GID, is incorrect. They should match the UID and GID specified in the RESOURCES or *MACHINES section of the configuration file.
Action
Run the process with the correct effective UID and GID.
681
ERROR: Failure to create message queue
Description
A UNIX system message queue could not be created during BEA TUXEDO system process initialization.
Action
Verify the UNIX's kernel parameters related to message queues, and increase if necessary. In particular, check MSGMNI. The BEA TUXEDO system's multi-server single queue, MSSQ, feature allows multiple servers to share the same queue, reducing the number required.
See Also
BEA TUXEDO Installation Guide
682
ERROR: Send/receive error for remote procedure call
Description
A message send failed. The message send failure may have resulted from a message type switch function failure, an invalid message length, or a low level message send failure.
Action
Check for a partitioned network, corrupted shared memory, all administrative processes are running, and sysgen parms for messages are appropriate.
683
ERROR: Memory allocation failure
Description
An attempt dynamically to allocate memory from the operating system using malloc() failed while creating a system message buffer.
Action
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.
684
ERROR: Memory allocation failure
Description
An attempt dynamically to allocate memory from the operating system using malloc() failed while a server process was trying to advertise its services.
Action
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.
687
ERROR: Received message with an unknown release number X
Description
A BEA TUXEDO system message was received with an unknown release number in its message header. Messages from both the current release and the previous release are understood. This does not include minor "point" maintenance releases. For example, a 4.2.1 BEA TUXEDO system process understands 4.2.1, 4.2, and 4.1 message formats. It does not understand a release 4.0 message, since that is two major releases old.
There is a different problem if the unknown release number is 0 or a very large number. It has been observed that if the underlying TCP/IP network is unreliable, and drops bytes from the middle of messages, this "unknown release number" error may occur frequently. It would typically be reported by the BRIDGE or WSH process. The problem is that the BEA TUXEDO system message header describes how many bytes follow the header. If some are lost by the network, all subsequent message headers will not be in the correct position in the data stream.
Action
Upgrade any machines in the network running an old release of the BEA TUXEDO system. Note that the MASTER and BACKUP must be upgraded first, so they are always running the most recent version. Investigate and resolve any networking problems. TCP/IP should guarantee reliable end-to-end transport of data.
689
ERROR: Received a message that is smaller than system minimum
Description
A BEA TUXEDO system message was received by the process, and is known to be invalid because it was too small.
Action
A likely cause is a compressed message being received by a process linked with release 4.2 or earlier BEA TUXEDO system libraries. The message compression feature was introduced in release 4.2.1, and should not be enabled until the entire application is running 4.2.1 or a later release. This includes application client and server processes, which need to be relinked.
695
ERROR: Unknown table type given
Description
An internal BEA TUXEDO system table was requested, and could not be read because its type is unknown.
Action
Contact your BEA TUXEDO system Technical Support.
696
ERROR: Missing search key
Description
An internal BEA TUXEDO system table was requested, and could not be read because a search key was not provided to the low-level access routine.
Action
Contact your BEA TUXEDO system Technical Support.
697
ERROR: Missing search key
Description
An internal BEA TUXEDO system table was requested, and could not be read because a search key was not provided to the low-level access routine.
Action
Contact your BEA TUXEDO system Technical Support.
698
ERROR: Invalid search key
Description
An internal BEA TUXEDO system table was requested, and could not be read because an invalid search key was passed to the low-level access routine.
Action
Contact your BEA TUXEDO system Technical Support.
699
ERROR: Missing search key
Description
An internal BEA TUXEDO system table was requested, and could not be read because a search key was not provided to the low-level access routine.
Action
Contact your BEA TUXEDO system Technical Support.
|
|
|
|
||
 |
|
|
 |
 |
 |
|
||