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.
6700 |
WARN: Peer validation failed on server at val | |
|
Description |
The common name OID contained in the server peer certificate did not match the hostname in the object reference. The hostname in the object reference has the value 'code'. |
Action |
None. If you wish to eliminate the warning, modify the server peer certificate to contain the correct hostname in the common name OID. | |
6701 |
ERROR: SSL certificate chain could not be validated, err = val | |
|
Description |
The process received the error 'val' while attempting to validate the certificate chain. |
Action |
Check your ULOG for message indicating the nature of the failure. | |
6702 |
INFO: SSL function completed successfully | |
|
Description |
The SSL function was successful. |
Action |
None. | |
6703 |
ERROR: SSL memory allocation function failure | |
|
Description |
An attempt to allocate memory dynamically from the operating system using |
Action |
Make sure the operation 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. Either reduce the memory usage on the machine or increase the amount of physical memory on the machine. Also increate the space on the swap device. | |
See Also |
See the For UNIX system, see the For Microsoft Windows systems, see the Microsoft Visuall C++ online help. | |
6704 |
ERROR: SSL feature or value not supported | |
|
Description |
An SSL feature or value that is not supported has been specified. |
Action |
Contact BEA Customer Support. | |
6705 |
ERROR: SSL index out of range | |
|
Description |
An internal error has occurred. |
Action |
Contact BEA Customer Support. | |
6706 |
ERROR: Unknown SSL error | |
|
Description |
An unknown SSL error has occurred. |
Action |
Contact BEA Customer Support. | |
6707 |
ERROR: SSL protocol violation occurred | |
|
Description |
There was a violation of the SSL protocol. |
Action |
Contact BEA Customer Support. | |
6708 |
ERROR: SSL secure connection could not be negotiated | |
|
Description |
A secure connection could not be negotiated. This may occur due to encryption strength differences, certificate validation errors, or initialization failure. |
Action |
The ULOG may give more information about the error. Verify that the encryption strength is within the range supported by TUXEDO. | |
6709 |
ERROR: SSL fatal alert was received | |
|
Description |
The process encountered a fatal SSL error. |
Action |
Contact BEA Customer Support. | |
6710 |
INFO: SSL connection would block | |
|
Description |
The process has encountered a situation where it would block if it attempts to read the SSL connection. |
Action |
Contact BEA Customer Support. | |
6711 |
ERROR: SSL connection fatal I/O error | |
|
Description |
An SSL feature or value that is not supported has been specified. |
Action |
Contact BEA Customer Support. | |
6712 |
ERROR: SSL session record could not be located | |
|
Description |
The process could not locate the SSL session record. |
Action |
this indicates an internal error. Contact BEA Customer Support. | |
6713 |
INFO: SSL connection has been closed | |
|
Description |
The process' SSL connection is closed. |
Action |
None. | |
6714 |
ERROR: Call failed because the SSL Connection has already been closed due to an error | |
|
Description |
The process encountered an internal error. |
Action |
Contact BEA Customer Support. | |
6715 |
ERROR: Invalid ASN encoding | |
|
Description |
An internal error occurred while processing an ASN encoded object. |
Action |
The ULOG may give more information about the nature of the error. Contact BEA Customer Support. | |
6716 |
ERROR: ASN integer too big | |
|
Description |
A data field of the ASN encoded object contains an integer too big for the platform. |
Action |
Contact BEA Customer Support. | |
6717 |
ERROR: X.509 certificate chain is invalid | |
|
Description |
The process encountered an invalid X.509 certificate chain. |
Action |
Verify the certificate chain and contact your Certificate Authority. | |
6718 |
ERROR: One of the X.509 certificates in the chain has expired or is not yet valid | |
|
Description |
The process encountered a X.509 certificate that has expired or is yet valid. |
Action |
Verify the certificate chain and contact your Certificate Authority. | |
6719 |
ERROR: X.509 names are not equal | |
|
Description |
The X.509 names contained within two SSL certificates are not equal. |
Action |
Verify the certificates. Contact BEA Customer Support. | |
6720 |
ERROR: X.509 certificate chain could not be completed with a self-signed root certificate | |
|
Description |
The process was unable to verify the SSL certificate chain without a self-signed root certificate. |
Action |
Verify that the certificate chain contains a self-signed root certificate. | |
6721 |
ERROR: X.509 certificate data extraction function failed to find the requested data | |
|
Description |
The process was unable to find the requested data in the certificate. |
Action |
Verify the certificate. Contact BEA Customer Support. | |
6722 |
ERROR: SSL function called with an invalid parameter | |
|
Description |
The process encountered an internal error when passing a parameter. |
Action |
Contact BEA Customer Support. | |
6723 |
ERROR: SSL connection closed without check for graceful close message | |
|
Description |
The process' SSL connection closed without verification. |
Action |
None. | |
6724 |
ERROR: SSL file was not found | |
|
Description |
An SSL file was not found. |
Action |
Contact BEA Customer Support. | |
6725 |
ERROR: SSL data was not found | |
|
Description |
An SSL data was not found. |
Action |
Verify the filename and directory of the private keys, the public keys, the certification rules files, and the LDAP files. | |
6726 |
ERROR: SSL decryption failed | |
|
Description |
The process could not decrypt an SSL message. |
Action |
Contact BEA Customer Support. | |
6727 |
ERROR: x.509 certificate is issued by an unauthorized certificate authority | |
|
Description |
The process received a certificate that was signed by an unauthorized certificate authority. |
Action |
Contact your Certificate Authority or BEA Customer Support. | |
6728 |
ERROR: x.509 certificate contains an unknown critical extension | |
|
Description |
The process received a certificate that contains an extension unknown to the TUXEDO SSL subsystem. |
Action |
Contact your Certificate Authority or BEA Customer Support. | |
6729 |
ERROR: x.509 certificate is unauthorized | |
|
Description |
The process received a certificate that is not authorized. |
Action |
Verify the certificate. Contact your Certificate Authority or BEA Customer Support. | |
6730 |
ERROR: ASN error val | |
|
Description |
The process received the error 'val' while processing a SSL key or certificate. |
Action |
Contact your BEA Customer Support. | |
6731 |
ERROR: ASN OID not found | |
|
Description |
SSL did not find an exptected OID in a certificate or key. |
Action |
Contact your Certificate Authority or BEA Customer Support. | |
6732 |
ERROR: ASN certificate dates invalid | |
|
Description |
The ASN dates pf a SSL certificate are invalid. |
Action |
Contact your Certificate Authority or BEA Customer Support. | |
6733 |
ERROR: ASN certificate name excluded | |
|
Description |
The name of the SSL ASN certificate is missing. |
Action |
Contact your Certificate Authority or BEA Customer Support. | |
6734 |
ERROR: ASN certificate name constrained | |
|
Description |
The name of the SSL ASN certificate is restricted. |
Action |
Contact your Certificate Authority or BEA Customer Support. | |
6735 |
ERROR: ASN certificate policy identifier required | |
|
Description |
The process encountered an ASN SSL certificate that did not identify the certificate. |
Action |
Contact your Certificate Authority or BEA Customer Support. | |
6736 |
ERROR: ASN certificate policy mapping inhibited | |
|
Description |
The process encountered an ASN SSL certificate in which the certificate policy could not be mapped from the ASN format. |
Action |
Contact your Certificate Authority or BEA Customer Support. | |
6737 |
ERROR: ASN certificate constraints exceeded | |
|
Description |
The process encountered an ASN SSL certificate in which the certificate constraints were exceeded. |
Action |
Contact your Certificate Authority or BEA Customer Support. | |
6738 |
ERROR: ASN certificate key usage violation | |
|
Description |
The process encountered an ASN SSL certificate in which the SSL certificate violated the ASN usage limits. |
Action |
Contact your Certificate Authority or BEA Customer Support. | |
6739 |
ERROR: ASN certificate unrecognized critical extension | |
|
Description |
The process encountered an ASN SSL certificate in which the SSL certificate has an unrecognized critical extension. |
Action |
Contact your Certificate Authority or BEA Customer Support. | |
6740 |
ERROR: ASN certificate basic constraints missing | |
|
Description |
The process encountered an ASN SSL certificate in which the SSL certificate was missing basic constraint. |
Action |
Contact your Certificate Authority or BEA Customer Support. | |
6741 |
ERROR: SSL error code | |
|
Description |
The process encountered an ASN SSL certificate for which SSL reports the error 'code'. |
Action |
Contact your Certificate Authority or BEA Customer Support. | |
6742 |
ERROR: SSL bad key type | |
|
Description |
The process encountered a bad SSL key type. |
Action |
Contact your Certificate Authority or BEA Customer Support. | |
6743 |
ERROR: SSL bad key agreement algorithm | |
|
Description |
The process encountered an internal error processing SSL keys. |
Action |
Contact your Certificate Authority or BEA Customer Support. | |
6744 |
ERROR: SSL bad public key type | |
|
Description |
The process encountered a public SSL key that is of the incorrect type. |
Action |
Contact your Certificate Authority or BEA Customer Support. | |
6745 |
ERROR: Unknown SSL error code | |
|
Description |
The process received an SSL error 'code' that is unknown. |
Action |
Contact BEA Customer Support. | |
6746 |
ERROR: Memory allocation failure | |
|
Description |
An attempt to allocate memory dynamically from the operating system using |
Action |
Make sure the operation 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. Either reduce the memory usage on the machine or increase the amount of physical memory on the machine. Also increate the space on the swap device. | |
See Also |
See the For UNIX system, see the For Microsoft Windows systems, see the Microsoft Visuall C++ online help. | |
6747 |
ERROR: Could not create random object, err = val | |
|
Description |
The process received the error 'val' while initializing SSL random objects. |
Action |
Contact BEA Customer Support. | |
6748 |
ERROR: Could not seed random object, err = val | |
|
Description |
The process received the error 'val' while initializeing the SSL random object. |
Action |
Contact BEA Customer Support. | |
6749 |
ERROR: Could not set SSL callback info, err = code | |
|
Description |
The process received the error 'code' while initializing SSL. SSL reported this error while trying to set the random data ojbect callback information. |
Action |
Contact BEA Customer Support. | |
6750 |
ERROR: Could not set SSL callback, err = val | |
|
Description |
The process received the error 'val' while initializing SSL. SSL reported this error while trying to set the random object callback function. |
Action |
Contact BEA Customer Support. | |
6751 |
ERROR: Could not generate random bytes, err = val | |
|
Description |
The process received the error 'val' while attempting to get random data from the SSL random data object. |
Action |
Contact BEA Customer Support. | |
6752 |
ERROR: Could not generate random bytes, err = val | |
|
Description |
The process received the error 'val' while attempting to get random data from the SSL random data object. |
Action |
Contact BEA Customer Support. | |
6753 |
ERROR: Could not seek random pool file, err = val | |
|
Description |
The process received the error 'val' while attempting to update the random pool file with new seed data. |
Action |
Verify that the disk has space, and that you have permission to write in the APPDIR directory. | |
6754 |
ERROR: SSL encryption parameter negotiation error | |
|
Description |
The process failed the encryption negotiation. There was no suitable encryption algorithm can be agree upon. |
Action |
Check your configuration and TUXEDO installation make sure it is correct. | |
6756 |
ERROR: SSL encryption parameter negotiation error | |
|
Description |
The process failed the encryption negotiation. There was no suitable encryption algorithm can be agree upon. |
Action |
Check your configuration and TUXEDO installation make sure it is correct. | |
6757 |
ERROR: SSL encryption parameter negotiation error | |
|
Description |
The process failed the encryption negotiation. There was no suitable encryption algorithm can be agree upon. |
Action |
Check your configuration and TUXEDO installation make sure it is correct. | |
6758 |
ERROR: SSL error code | |
|
Description |
The process encountered an SSL error with error code |
Action |
Check your ULOG for more specific error information. | |
6759 |
ERROR: SSL encryption parameter negotiation error | |
|
Description |
The process failed the encryption negotiation. There was no suitable encryption algorithm can be agree upon. |
Action |
Check your configuration and TUXEDO installation make sure it is correct. | |
6760 |
ERROR: SSL error code | |
|
Description |
The process encountered an SSL error with error code |
Action |
Check your ULOG for more specific error information. | |
6761 |
ERROR: SSL encryption parameter negotiation error | |
|
Description |
The process failed the encryption negotiation. There was no suitable encryption algorithm can be agree upon. |
Action |
Check your configuration and TUXEDO installation make sure it is correct. | |
6762 |
ERROR: SSL error code | |
|
Description |
The process encountered an SSL error with error code |
Action |
Check your ULOG for more specific error information. | |
6764 |
INFO: SSL connection negotiated cipher cipher_name | |
|
Description |
Informational message telling which cryptographical cipher suite the SSL connection will be using. |
Action |
None. | |
6765 |
INFO: SSL renegotiation in progress | |
|
Description |
Informational message, indicating SSL cipher suite renegotiation is in progress. |
Action |
None. | |
6766 |
ERROR: SSL renegotiation failed with error code | |
|
Description |
The renegotiation of new cipher suite of an existing SSL connection failed with error 'code'. |
Action |
Contact your BEA Customer Support. | |
6767 |
ERROR: The TMMONITOR policy val must be used together with its monitoring category | |
|
Description |
TSAM Agent failed to parse TMMONITOR due to the monitoring policy is not consistent with the related monitoring category. |
Action |
Specify the monitoring category also in TMMONITOR specification if some policy is used. | |
6768 |
ERROR: The TMMONITOR required fields val must be used together with its monitoring category | |
|
Description |
TSAM Agent failed to parse TMMONITOR due to the required fields are not consistent with the related monitoring category. |
Action |
Specify the monitoring category also in TMMONITOR specification if appfields or svcfields is used. | |
6769 |
ERROR: Invalid password in TUXCONFIG file | |
|
Description |
The password stored in TUXEDO TUXCONFIG file is invalid. This occurred while trying to get TPADM key. |
Action |
Contact BEA Customer Support. | |
6770 |
ERROR: Memory allocation failure | |
|
Description |
An attempt to allocate memory dynamically from the operating system using |
Action |
Make sure the operation 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. Either reduce the memory usage on the machine or increase the amount of physical memory on the machine. Also increate the space on the swap device. | |
See Also |
See the For UNIX system, see the For Microsoft Windows systems, see the Microsoft Visuall C++ online help. | |
6771 |
ERROR: Memory allocation failure | |
|
Description |
An attempt to allocate memory dynamically from the operating system using |
Action |
Make sure the operation 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. Either reduce the memory usage on the machine or increase the amount of physical memory on the machine. Also increate the space on the swap device. | |
See Also |
See the For UNIX system, see the For Microsoft Windows systems, see the Microsoft Visuall C++ online help. | |
6772 |
ERROR: Memory allocation failure | |
|
Description |
An attempt to allocate memory dynamically failed either because internal structure error or the operating system returned failure for |
Action |
Make sure the operation 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. Either reduce the memory usage on the machine or increase the amount of physical memory on the machine. Also increate the space on the swap device. | |
See Also |
See the For UNIX system, see the For Microsoft Windows systems, see the Microsoft Visuall C++ online help. If problem persist contact your BEA Customer Support. | |
6773 |
ERROR: Memory allocation failure | |
|
Description |
An attempt to allocate memory dynamically from the operating system using |
Action |
Make sure the operation 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. Either reduce the memory usage on the machine or increase the amount of physical memory on the machine. Also increate the space on the swap device. | |
See Also |
See the For UNIX system, see the For Microsoft Windows systems, see the Microsoft Visuall C++ online help. | |
6774 |
WARN: LMS server is currently unavailable. | |
|
Description |
In case plugin fails to send monitor data to LMS due to LMS is not booted up or LMS is too busy to process the monitor data. |
Action |
None | |
6775 |
"ERROR: Failed to load TSAM Event Trigger rules from file | |
|
Description |
This error occurs when the BBL/DBBL fails to load the file_name rule file. The rule file can be specified by using either the TSAMPLUGINRULES environment variable or the tmadmin "configtsam load" command. The estimated error reason is error_reason. See the ULOG for more detailed information. |
Action |
It depends on what the error reason is. For example, if the error reason illustrates that the format is invalid, then the rule file should be corrected; if the error reason is space limit, then either MAXSPDATA in UBBCONFIG or TSAMPLUGINRULES environment variable should be modified, etc. | |
6776 |
"INFO: Load TSAM Event Trigger rules from file | |
|
Description |
This message is printed when a TSAM Event Trigger rule file is loaded successfully. |
Action |
No action required. | |
6777 |
"ERROR: Cannot load TSAM Event Trigger rule. Reason: | |
|
Description |
This error occurs when a BBL in an MP system fails to load the rule sent from the DBBL. The estimated error reason is error_reason. See the ULOG for more detailed information |
Action |
Upgrade the Tuxedo software on the machine where this error occurs to the same release and Rolling Patch as the master machine. If it is already upgraded, please contact BEA customer support. | |
6778 |
"ERROR: Cannot enable/disable when TSAM Event Trigger is not loaded." | |
|
Description |
When a user tries to enable/disable the TSAM Event Trigger before the TSAM Event Trigger is successfully loaded, this error occurs. |
Action |
Load the rule file first, by using either the TSAMPLUGINRULES environment variable or the tmadmin "configtsam load" command when booting. | |
6780 |
ERROR: Cannot open parameter file | |
|
Description |
The TSAM rule file can not be open. |
Action |
Please check if the directory and filename is correct and you have rights to access it. | |
6781 |
ERROR: Line lineno, bad file format | |
|
Description |
The TSAM rule format is incorrect. |
Action |
Please check if the rule has '=' after the key. And ':' is a separator of the rule section, please do not use ':' as value in the rule. | |
See Also |
See TSAM Plug-in Event User Guide | |
6782 |
ERROR: Line lineno, bad keyword | |
|
Description |
The keyword in the line is not supported. |
Action |
Please check if the keyword in the rule is valid for TSAM. | |
See Also |
See TSAM Plug-in Event User Guide | |
6783 |
ERROR: Line lineno, key too long | |
|
Description |
The length of the keyword in the line can not longer than 256. |
Action |
Please make sure if the keyword in the line is valid. | |
See Also |
See TSAM Plug-in Event User Guide | |
6784 |
ERROR: Line lineno, the keyword can not be in this section | |
|
Description |
The keyword in the line can not exist in this rule type section. |
Action |
Please check if the keyword is in a suitable file section. We support different keywords for different rule type. Please reference TSAM Plug-in Event User Guide for detail. | |
See Also |
See TSAM Plug-in Event User Guide | |
6785 |
ERROR: Line lineno, key has no value | |
|
Description |
The keyword in the line has no value after '='. |
Action |
Please add value for the keyword, the rule format is 'keyword=value'. | |
See Also |
See TSAM Plug-in Event User Guide | |
6786 |
ERROR: Line lineno, invalid value | |
|
Description |
The keyword in the line has invalid value. |
Action |
Please check if there is non-printable character in the line. For general or report policy rule, please check if the value is Y|N. | |
See Also |
See TSAM Plug-in Event User Guide | |
6787 |
ERROR: Line lineno, field_name invalid field name | |
|
Description |
The field is not a valid FML32 field. |
Action |
Please check if environment variable FLDTBLDIR32 and FIELDTBLS32 is set correctly and the field is a valid FML32 field. | |
6788 |
ERROR: Memory allocation error | |
|
Description |
An attempt to allocate memory dynamically from the operating system using |
Action |
Make sure the operation 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. Or increase the amount of physical memory on the machine. Also increase the space on the swap device. | |
See Also |
See the For UNIX system, see the For Microsoft Windows systems see the Microsoft Visual C++ online help. | |
6789 |
ERROR: Line lineno, duplicate section | |
|
Description |
Section name duplicated. |
Action |
Please delete the duplicated section name. | |
See Also |
See TSAM Plug-in Event User Guide | |
6790 |
ERROR: Line lineno, bad action format | |
|
Description |
The action format in the line is incorrect. |
Action |
Please correct the action format according to e-doc. TSAM only support event action. The event action should be quoted by '()', and the first character after '(' should not be ','. | |
See Also |
See TSAM Plug-in Event User Guide | |
6791 |
ERROR: Line lineno, duplicate action field | |
|
Description |
The action field is duplicated. |
Action |
Delete the duplicated action field. | |
See Also |
See TSAM Plug-in Event User Guide | |
6792 |
ERROR: Line lineno, not supported action type | |
|
Description |
The action type is not supported. |
Action |
So far only support event action. | |
See Also |
See TSAM Plug-in Event User Guide | |
6793 |
ERROR: Line lineno, bad event name | |
|
Description |
The event name in the action is invalid. |
Action |
Event name is a string of at most 31 characters. Valid characters are '0'..'9', 'a'..'z', 'A'..'Z' and '_'. The event name can not begin with '.'. | |
6794 |
ERROR: Line lineno, bad expression | |
|
Description |
The expression in the line is invalid. |
Action |
Please check if the expression in component and metric filter is a valid regular or logical expression. | |
6795 |
ERROR: Cannot write parameter file | |
|
Description |
The rule can not be unloaded to the file. |
Action |
Please check if there is enough disk space. | |
6796 |
ERROR: Line lineno, bad section name | |
|
Description |
The section name is incorrect. |
Action |
Please check the section name in the rule file. The section name supported are: *GENERAL_RULES, *SVC_TRIGGER, *CALL_TRIGGER, *BBL_TRIGGER and *REPORT_POLICY. | |
See Also |
See TSAM Plug-in Event User Guide | |
6797 |
ERROR: Line lineno, bad metric filter | |
|
Description |
The metric filter in the line is invalid. |
Action |
The metric filter can not be NULL in a rule. | |
6798 |
ERROR: Line lineno, bad rule type | |
|
Description |
The rule type in Tuxedo bulletin board is invalid. |
Action |
Contact BEA Customer Support. | |
6799 |
ERROR: Too many rules | |
|
Description |
There are too many rules in the rule file. |
Action |
The maximum number of rules in the rule file is 2048. Please simplify the rule files. |