System Messages: LIBTUX Catalog 6800-6899
|
![]() |
![]() |
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 Oracle 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 Oracle 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 Oracle 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 Oracle 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 Oracle 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 Oracle 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 Oracle 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 Oracle 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 Oracle 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 Oracle 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 Oracle support to get a TSAM license. | |
6825 |
ERROR: TSAM license has expired | |
|
Description |
TSAM license date has expired. |
Action |
Contact your Oracle 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. | |
6835 |
ERROR: Service servicename in BEGIN session role is forwarding request | |
|
Description |
Service in BEGIN session role is forwarding a request |
Action |
Do not use tpforward in services where SESSIOROLE is set to BEGIN | |
6836 |
ERROR: Service servicename in END session role is forwarding request | |
|
Description |
Service in END session role is forwarding a request |
Action |
Do not use tpforward in services where SESSIOROLE is set to END | |
6837 |
ERROR: Service servicename in BEGIN session role cannot be invoked with TPNOREPLY flag | |
|
Description |
Service in BEGIN session role cannot be invoked with TPNOREPLY flag |
Action |
Do not call services where SESSIONROLE is set to BEGIN with TPNOREPLY flag if you want to use Client/Server affinity feature correctly. | |
6838 |
ERROR: Service servicename in END session role cannot be invoked with TPNOREPLY flag | |
|
Description |
Service in END session role cannot be invoked with TPNOREPLY flag |
Action |
Do not call services where SESSIONROLE is set to END with TPNOREPLY flag if you want to use Client/Server affinity feature correctly. | |
6839 |
ERROR: Service servicename in BEGIN session role in conversation server | |
|
Description |
Service in BEGIN session role is advertised by conversation server |
Action |
Do not allow services on the conversation server to be set with BEGIN session role. | |
6840 |
ERROR: Service servicename in END session role in conversation server | |
|
Description |
Service in END session role is advertised by conversation server |
Action |
Do not allow services on the conversation server to be set with END session role. | |
6841 |
ERROR: Install Oracle TSAM before enabling TM_RQSTLIVETIME. | |
|
Description |
To enable the Clean Stale Request feature, Oracle TSAM must be installed first |
Action |
Purchase Oracle TSAM and install. | |
6842 |
INFO: Message request dropped. In queue longer than times* SCANUNIT, as specified by TM_RQSTLIVETIME. | |
|
Description |
A stale message request is dropped. |
Action |
None. | |
6843 |
ERROR: File filename specified in TM_RQSTLIVETIME cannot be opened. | |
|
Description |
File specified in TM_RQSTLIVETIME cannot be found or is unreadable. |
Action |
Specify a valid file (under $APPDIR) in TM_RQSTLIVETIME.
Lines in this file must use the format: | |
6844 |
ERROR: [Unable to find | |
|
Description |
|
Action |
Verify that the environment variable | |
See Also |
| |
6845 |
ERROR: Unable to read the | |
|
Description |
|
Action |
Verify that the environment variable | |
See Also |
| |
6846 |
ERROR: Resource manager identifier rmid of group groupname error. | |
|
Description |
The |
Action |
Make sure the | |
See Also |
| |
6847 |
ERROR: Resource manager identifier rmid xa switch is not set. | |
|
Description |
The required xa switch symbol specified by rmid in the |
Action |
Make sure the resource manager name is correct and consistent with the name in the | |
See Also |
| |
6848 |
ERROR: Resource manager identifier rmid xa switch is not supported. | |
|
Description |
It is not allowed to configure an old preliminary version of XA resource manager in |
Action |
Delete the item which specifies an old preliminary version of XA resource manager. | |
See Also |
| |
6850 |
ERROR: tprmopen TPERMERR xa_open for resource manager rmid returned errstring | |
|
Description |
The call to |
Action |
Look for | |
See Also |
| |
6851 |
ERROR: Unable to read the *RMS section of the TUXCONFIG file. | |
|
Description |
The |
Action |
Verify that the TUXCONFIG file or Tuxedo shared memory was not accidentally removed while Tuxedo was running. If this error occurs consistently, contact Oracle support. | |
See Also |
| |
6852 |
ERROR: tprmclose resource manager rmid TPERMERR xa_close returned errstring. | |
|
Description |
The call to |
Action |
Look for | |
See Also |
| |
6853 |
ERROR: tprmstart resource manager rmid xa_start returned errstring | |
|
Description |
The call to |
Action |
Look for | |
See Also |
| |
6854 |
ERROR: tprmclose called with ongoing transaction | |
|
Description |
|
Action |
The transaction must be completed via | |
See Also |
| |
6856 |
ERROR: Cannot find xa switch symbol with specific resource manager name in OPENINFO string. | |
|
Description |
The resource names specified in |
Action |
Make sure all the required resource manager symbols are imported while executing | |
See Also |
| |
6857 |
ERROR: FML32 field name fieldname specified for routing criteria routingname has field type typenum which exceeds the allowed maximum of maxtypenum | |
|
Description |
FML32 field fieldname was specified for routing entry routingname, but this field has type typenum which is greater than the maximum allowable type number maxtypenum, which is currently equal to 7. |
Action |
Specify a routing field with a valid type. The only FML32 types currently allowed for routing are short (0), long (1), char (2), float (3), double (4), string (5), and carray (6). | |
See Also |
| |
6858 |
ERROR: FML32 field name fieldname specified for routing criteria routingname has field number fldnum which exceeds the allowed maximum of maxroutefldnum | |
|
Description |
FML32 field fieldname was specified for routing entry routingname, but this field has number fldnum which is greater than the maximum allowable routing field number maxroutefldnum, which is currently equal to 8191. |
Action |
Specify a routing field with a field number less than or equal to 8191. | |
See Also |
| |
6867 |
ERROR: TLOGNAME must be specified when TLOG is stored in database | |
|
Description |
When you want write tlog into database, |
Action |
Set | |
See Also |
| |
6868 |
ERROR: action met a database error:errmsg | |
|
Description |
You met a database error :errmsg when tuxedo write/read tlog infomation from database. |
Action |
Contact your DBA according to the error message. | |
6869 |
WARN: TM_ENVFILE_BEFOREBOOT doesn't taken effect for servername. | |
|
Description |
Environment variable "TM_ENVFILE_BEFOREBOOT" doesn't taken effect for this server. |
Action |
None. | |
6870 |
WARNING: Could not load OCI library. Library name is longer than the allowed length. | |
|
Description |
Failed to load OCI library dynamically. |
Action |
Check the user OCI library name specified by the user. Make sure the lenth of OCI library name is no longer than 255. | |
6871 |
WARNING: Could not load OCI library. oci_generic_init failed. | |
|
Description |
Failed to load OCI library dynamically. |
Action |
Check the user OCI library name specified by the user. Make sure that the OCI library can be accessed successfully. | |
6872 |
WARNING: Could not create OCI environment. _OCIEnvCreate failed with errcode = %d. | |
|
Description |
Failed to setup the OCI environment for ECID propagation from Oracle Tuxedo to Oracle DB. |
Action |
Make sure that the environment variables for OCI have been set correctly. If the problem persists, contact Oracle Customer Support. | |
6873 |
WARNING: Could not register OCI roundtrip callback. Status = %d. | |
|
Description |
Failed to setup the OCI environment for ECID propagation from Oracle Tuxedo to Oracle DB. |
Action |
Check the version of OCI library. Make sure that the OCI library supports the OCI roundtrip callback feature. | |
6874 |
WARNING: Could not register OCI roundtrip callback context. Status = %d. | |
|
Description |
Failed to setup the OCI environment for ECID propagation from Oracle Tuxedo to Oracle DB. |
Action |
Check the version of OCI library. Make sure that the OCI library supports the OCI roundtrip callback feature. | |
6875 |
ERROR: Could not load DMS library libname, err = code. | |
|
Description |
Failed to load DMS library libname dynamically, receive error 'code'. |
Action |
Check the Oracle Tuxedo installation. If the installation is fine but problem persists, contact Oracle Customer Support. | |
6876 |
ERROR: Could not get DMS library function funname, err = code. | |
|
Description |
The process received the error 'code' while trying to read the DMS function funname from the DMS library. |
Action |
Check the Oracle Tuxedo installation. If the installation is fine but problem persists, contact Oracle Customer Support. | |
6877 |
ERROR: nzos_SetThrUse returned error error_number [error_string] | |
|
Description |
An error occurred while setting up the Oracle NZ security layer to operate in multithreaded mode. The error returned by the Oracle NZ security layer was error_number and a text description of that error is error_string. |
Action |
Verify that the application is not linked with a different version of the Oracle security layers than the version provided with Tuxedo. If the problem persists, contact Oracle customer support. | |
6878 |
ERROR: nzos_SetSqlnetFunc returned error error_number [error_string] | |
|
Description |
An error occurred while setting up callback functions for the Oracle NZ security layer. The error returned by the Oracle NZ security layer was error_number and a text description of that error is error_string. |
Action |
Verify that the application is not linked with a different version of the Oracle security layers than the version provided with Tuxedo. If the problem persists, contact Oracle customer support. | |
6879 |
ERROR: NZ Toolkit initialization returned error error_number [error_string] | |
|
Description |
An error occurred while initializing the Oracle NZ security layer. The error returned by the Oracle NZ security layer was error_number and a text description of that error is error_string. |
Action |
Verify that the application is not linked with a different version of the Oracle security layers than the version provided with Tuxedo. If the problem persists, contact Oracle customer support. | |
6880 |
ERROR: SEC_PRINCIPAL_LOCATION is not set | |
|
Description |
Processes that are on the server side of an SSL connection or that are on the client side of an SSL connection using mutual authentication must provide security credentials, which will be verified by the other side of the SSL connection. If an Oracle Wallet is being used for security credentials then SEC_PRINCIPAL_LOCATION is used to specify the location of the wallet. If legacy security credentials are being used, then SEC_PRINCIPAL_LOCATION specifies the location of the private key file. The SEC_PRINCIPAL_PASSVAR parameter specifies the name of an an environment variable that contains the password needed to open SEC_PRINCIPAL_LOCATION. (In processes not attached to the Bulletin Board, the equivalent environment variable is SEC_PRINCIPAL_PASSWORD, which contains the password.) |
Action |
Set the SEC_PRINCIPAL_LOCATION and SEC_PRINCIPA_PASSVAR parameters in the TUXCONFIG file to appropriate values. | |
6881 |
ERROR: Cannot stat Oracle Wallet \"wallet_loc\" | |
|
Description |
The |
Action |
Ensure that permissions allow searching all directories above wallet_loc and taht there is not a looping symbolic link in the wallet_loc path. | |
6882 |
ERROR: Cannot open Oracle Wallet \"wallet_loc\", error error_number [error_string] | |
|
Description |
Tuxedo was unable to open the Oracle Wallet located in directory wallet_loc. The error returned by the Oracle NZ security library was error_number and a text description of that error is error_string. |
Action |
Ensure that the wallet_loc directory exists, that it contains an | |
6883 |
ERROR: nzosSetCredential returned error error_number [error_string] | |
|
Description |
The function used to set SSL security credentials in the Oracle NZ security layer failed. The error returned by the Oracle NZ security layer was error_number and a text description of that error is error_string. |
Action |
Examine the error returned by the Oracle NZ security layer for information about the cause of the error. Ensure that the Oracle Wallet contains all credentials needed by the application. For example, if the process is on the server side of the SSL connection, ensure that the Oracle Wallet contains a private key and a certificate. | |
6884 |
ERROR: No supported cipher suites found. Please check the configured minimum bits = minbits and maximum bits = maxbits | |
|
Description |
No supported SSL cipher suites with a strengh of between minbits and maxbits were found. |
Action |
Change the values of minbits and maxbits. Remember that 0 bit SSL cipher suites (which do not actually use any encryption) are not allowed in Tuxedo 12c and above. | |
6885 |
"ERROR: SSL Handshake failed with error error_number [error_string] | |
|
Description |
An error occurred during the SSL handshake process and this process was unable to establish an SSL connection. The error returned by the Oracle NZ security layer was error_number and a text description of that error is error_string. |
Action |
If the problem occurs repeatedly, setting the environment variable |
![]() |
![]() |
![]() |