Messages
Oracle Tuxedo System Messages provide the following information:
Description: The meaning and context of the message.
Action: What steps you can take to correct any problems identified.
See Also: A pointer to related information (not specified for all messages).
The Oracle Tuxedo System Messages are numbered and organized in catalogs, based on parts of the Oracle Tuxedo 10g Release 3 (10.3) system from which they are generated. For information about a specific message, click on the name of the appropriate catalog.
Note: Some messages for deprecated features may still display. Be aware that deprecated features are not supported.
6800 |
WARN: rule not supported rule | |
|
Description |
The rule is not supported by this machine. |
Action |
Please upgrade this Tuxedo version or install the new rolling patch. | |
6801 |
ERROR: Line lineno, bad section type | |
|
Description |
The section type is invalid. |
Action |
Contact BEA Customer Support. | |
6802 |
ERROR: Line lineno, bad message severity | |
|
Description |
The event action message severity is invalid. |
Action |
Please check the line event message severity, the valid values are: Information, Warn, Critical and Fatal. | |
See Also |
See TSAM Plug-in Event User Guide | |
6803 |
ERROR: The parameter file exists | |
|
Description |
The rule file exists. |
Action |
Remove the file or rename it. | |
6804 |
ERROR: Cannot open for write | |
|
Description |
The rule file can not be opened for write. |
Action |
Please check if the directory or filename is correct and you have rights to write it. | |
6805 |
ERROR: Cannot stat the parameter file | |
|
Description |
Can not get information from the parameter file. |
Action |
Please check if the directory or filename is correct and you have rights to access it. | |
6806 |
ERROR: The buffer size too small | |
|
Description |
There is no enough space in bulletin board to hold the rules. |
Action |
Please increase MAXSPDATA in UBBCONFIG according to your configuration. | |
See Also |
See TSAM Plug-in Event User Guide | |
6807 |
WARN: Line lineno, duplicated rule rule, use new one | |
|
Description |
The global or report policy is repetitious. |
Action |
Delete the repetitious rule. | |
6808 |
WARN: Line lineno, duplicated rule, ignore it | |
|
Description |
The service,call path or BBL rule is repetitious. |
Action |
Delete the repetitious rule. | |
6809 |
ERROR: The buffer size is too small, the required size is bufsize | |
|
Description |
There is no enough space in bulletin board to hold the rules. |
Action |
Please increase MAXSPDATA in UBBCONFIG according to your configuration. | |
See Also |
See TSAM Plug-in Event User Guide | |
6810 |
ERROR: Memory allocation error | |
|
Description |
An attempt to dynamically allocate memory from the operating system failed. |
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. | |
6811 |
ERROR: Failed to lock mutex for trigger rules | |
|
Description |
An internal error occurs for a mutex lock in TSAM plug-in event trigger process. |
Action |
Contact BEA Customer Support. | |
6812 |
ERROR: Failed to allocate FML32 buffer failed in event action handling | |
|
Description |
An attemp to allocate a Tuxedo FML32 typed buffer failed in TSAM Plug-in event trigger process. |
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. If this problem persists, please contact BEA Customer Support. | |
6813 |
ERROR: Failed to re-allocate FML32 buffer failed in event action handling | |
|
Description |
An attemp to re-allocate a Tuxedo FML32 typed buffer failed in TSAM Plug-in event trigger process. |
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. If this problem persists, ple ase contact BEA Customer Support. | |
6814 |
ERROR: Fcpy32 returns error(number) in event action handling | |
|
Description |
TSMA PLug-in event trigger process failed to invoke Fcpy32 routine. |
Action |
Contact BEA Customer Support. | |
6815 |
ERROR: Fchg32 returns error(number) in event action handling | |
|
Description |
TSMA PLug-in event trigger process failed to invoke Fchg32 routine. |
Action |
Contact BEA Customer Support. | |
6816 |
ERROR: tppost returns error(number) in event action handling | |
|
Description |
TSMA PLug-in event trigger process failed to invoke tppost routine when post an event to Tuxedo Event Broker. |
Action |
The most likely reason is Tuxedo Event Broker is not configured in your Tuxedo domain but the destination of the event is specified to "eventbroker" in the trigger rules file. Setup TMUSREVT server in UBBCONFIG. | |
See Also |
See Manual of TMUSREVT(5). | |
6817 |
ERROR: Line lineno, bad destination | |
|
Description |
The action destination is invalid. |
Action |
Please check the event action destination. The valid values are: 'eventbroker' or 'tsammanager'. | |
See Also |
See TSAM Plug-in Event User Guide | |
6818 |
ERROR: Line lineno, event name is too long | |
|
Description |
The event name is too long. |
Action |
The maximum length of event name is 31. | |
6819 |
ERROR: Line lineno, field_name cannot exist in the rule rule_section section | |
|
Description |
The field can not be configured in the rule section. |
Action |
Please check if the keyword is in a suitable rule section. We support different keywords for different rule section. Please reference TSAM Plug-in Event User Guide for detail. | |
See Also |
See TSAM Plug-in Event User Guide | |
6820 |
ERROR: A workstation client(ip address address) does not have a proper application password | |
|
Description |
The application password authentication was failed for a workstation client. |
Action |
Check ULOG and find the ip address. Then make sure the client on this address has a correct application password if the security level is APP_PW or above. | |
6821 |
ERROR: xa_rollback returned error for group groupname | |
|
Description |
This message is issued when BEA TUXEDO tries unsuccessfully to rollback a transaction via xa_rollback() after receiving a reply. The message prints the error code that the function returned. |
Action |
Contact your BEA TUXEDO system Technical Support or your database system vendor. See the userlog for more information on the outcome of the transaction. Also, use tmadmin's printtrans command to find out more information about the transaction. | |
6822 |
ERROR: xa_rollback returned errcode for group groupname | |
|
Description |
This message is issued if a process attempting to commit a transaction could not unlock the bulletin board. It then attempted to roll back the transaction, and encountered an error when calling the database resource manager's |
Action |
Contact your BEA TUXEDO system Technical Support or your database system vendor. The database system documentation or error logs may contain more information about why | |
6823 |
ERROR: TSAM SDK License requires Tuxedo SDK license | |
|
Description |
TSAM license check failed due to TSAM SDK license used by no Tuxedo SDK license. |
Action |
TSAM SDK license requires a valid Tuxedo SDK license. Contact your BEA support to get a Tuxedo SDK license. | |
6824 |
ERROR: TSAM is unlicensed | |
|
Description |
TSAM is unlicensed but TSAM functionality is used. |
Action |
TSAM is a product requiring seperate license. Contact your BEA support to get a TSAM license. | |
6825 |
ERROR: TSAM license has expired | |
|
Description |
TSAM license date has expired. |
Action |
Contact your BEA support to renew the TSAM license. | |
6826 |
INFO: TSAM License Serial #: serial, Expiration date | |
|
Description |
TSAM License information. |
Action |
None. | |
6827 |
INFO: TSAM Licensed to : owner | |
|
Description |
TSAM License owner information. |
Action |
None. | |
6828 |
ERROR: Field name not found for id fieldid | |
|
Description |
While doing service contract discovery, discovery process parses the FML buffer to get buffer field contract detail information when buffer type is FML or FML32. The operation tries to get FML/FML32 field name using the buffer field identifier. Upon the operation failure, this message is displayed. |
Action |
Make sure FML/FML32 required environment variables are set correctly for the server that enabled service contract discovery. | |
6829 |
ERROR: Call .SCD failed with error val | |
|
Description |
Service contract discovery module failure. Cannot send contract information to TMMETADATA server. |
Action |
Make sure TMMETADATA server is configured correclty in UBBCONFIG. If TMMETADATA is in "readonly" mode, "-o" must be specified for the output text file. | |
See Also |
| |
6830 |
WARN: Error encountered while creating SCA administrative thread, initiate without SCA administrative thread. | |
|
Description |
An error occurred while trying to create a mutex or condition variable for use by the SCA administrative thread that is normally used to process scaadmin statistics requests in an SCA server. As a result, the processing of scaadmin statistics requests will be delayed if there are other operations currently being performed in the server. |
Action |
Try rebooting the server to see if the problem still occurs. If the problem is persistent, contact Oracle support. | |
6831 |
WARN: Failure to create SCA administrative thread, initiate without SCA administrative thread. | |
|
Description |
An thread cration error occurred while creating the SCA administrative thread that is normally used to process scaadmin statistics requests in an SCA server. As a result, the processing of scaadmin statistics requests will be delayed if there are other operations currently being performed in the server. |
Action |
Try rebooting the server to see if the problem still occurs. Check the operating system to see if sufficient thread resources exist in the system. If the problem is persistent, contact Oracle support. | |
6832 |
WARN: SCA Server running on non-threaded platform! | |
|
Description |
This hardware platform does not support multithreading, so this SCA server could not create the administrative thread that is normally used to process scaadmin statistics requests. As a result, the processing of scaadmin statistics requests will be delayed if there are other operations currently being performed in the server. |
Action |
No action required. | |
6833 |
ERROR: Workstation client(ip address address) does not have proper application password | |
|
Description |
Workstation client is using wrong application password. |
Action |
Use correct application password in workstation client. | |
6834 |
ERROR: Workstation client(ip address address) authentication failure | |
|
Description |
Workstation client authentication failure. |
Action |
Check the tuxedo application security setting and ensure workstation client is compliant. |