Skip navigation.

LIBTUX Messages 6800-6899

  Previous

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 xa_rollback() routine. The message prints the error code that xa_rollback() returned.

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 xa_rollback() failed.

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

TMMETADATA(5)

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: =. For example: TOUPPER=2 IDL:beasys.com/Simple:1.0=3 default=2

6844

ERROR: [Unable to find TUXCONFIG file *RMS section]

Description

tmboot cannot find the RMS section of the Tuxedo configuration file.

Action

Verify that the environment variable TUXCONFIG is set correctly and exported, TUXCONFIG is not corrupted, and TUXCONFIG was propagated to all machines in MP mode.

See Also

UBBCONFIG(5), tmboot(1)

6845

ERROR: Unable to read the RMS section of the TUXCONFIG file

Description

tmboot cannot read the RMS section of the Tuxedo configuration file.

Action

Verify that the environment variable TUXCONFIG is set correctly and exported, TUXCONFIG is not corrupted, and TUXCONFIG was propagated to all machines in MP mode.

See Also

UBBCONFIG(5), tmboot(1)

6846

ERROR: Resource manager identifier rmid of group groupname error.

Description

The RMID attribute of a resource manager specified in RMS section must be between 1 and 31, inclusive.

Action

Make sure the RMID configured in RMS is a valid value.

See Also

UBBCONFIG(5)

6847

ERROR: Resource manager identifier rmid xa switch is not set.

Description

The required xa switch symbol specified by rmid in the RMS section cannot be found in the internal xa switch symbol table which was created when building this server. A Tuxedo serverwhich supports MRM initializes its xa switch table in booting stage by matching the resource manager name specified in OPENINFO string and the name specified by buildserver with -r option. If a matched resource manager is found, this server sets the xa switch table with the rmid otherwise this message is logged.

Action

Make sure the resource manager name is correct and consistent with the name in the RM file.

See Also

UBBCONFIG(5), buildserver(1)

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 RMS section.

Action

Delete the item which specifies an old preliminary version of XA resource manager.

See Also

UBBCONFIG(5), buildserver(1)

6850

ERROR: tprmopen TPERMERR xa_open for resource manager rmid returned errstring

Description

The call to xa_open() from within tprmopen returned the XA error value string. As a result, resource manager rmid could not be opened.

Action

Look for RMID=rmid in the TUXCONFIG file to determine which resource manager rmid is associated with. Verify that the OPENINFO string for this resource manager matches the proper syntax and configuration values for that resource manager. Check the error reporting mechanism for the recource manager to determine if there is any further information about the cause of the problem. Contact the resource manager vendor technical support organization if needed.

See Also

tprmopen(3), Distributed Transaction Processing: The XA Specfication, X/Open Company Limited, 1991.

6851

ERROR: Unable to read the *RMS section of the TUXCONFIG file.

Description

The tprmclose() function was not able to read the TUXCONFIG file in order to obtain information about configured resource managers. As a result, tprmclose() was unable to close the requested resource manager.

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

tprmclose(3).

6852

ERROR: tprmclose resource manager rmid TPERMERR xa_close returned errstring.

Description

The call to xa_close() from within tprmclose returned the XA error value string. As a result, resource manager rmid could not be closed.

Action

Look for RMID=rmid in the TUXCONFIG file to determine which resource manager rmid is associated with. Check the error reporting mechanism for that recource manager to determine the cause of the problem. Contact the resource manager vendor technical support organization or Oracle support as appropriate.

See Also

tprmclose(3), Distributed Transaction Processing: The XA Specfication, X/Open Company Limited, 1991.

6853

ERROR: tprmstart resource manager rmid xa_start returned errstring

Description

The call to xa_start() from within tprmstart returned the XA error value string. As a result, resource manager rmid could not be associated with the transaction.

Action

Look for RMID=rmid in the TUXCONFIG file to determine which resource manager rmid is associated with. Check the error reporting mechanism for that recource manager to determine the cause of the problem. Contact the resource manager vendor technical support organization or Oracle support as appropriate.

See Also

tprmstart(3), Distributed Transaction Processing: The XA Specfication, X/Open Company Limited, 1991.

6854

ERROR: tprmclose called with ongoing transaction

Description

tprmclose() was called while within a global transaction (that is, tpbegin() or txbegin() was called).

Action

The transaction must be completed via tpcommit() or tpabort() before calling tprmclose().

See Also

tpabort(3c), tpbegin(3c), tpclose(3c), tpcommit(3c), tprmopen

6856

ERROR: Cannot find xa switch symbol with specific resource manager name in OPENINFO string.

Description

The resource names specified in buildserver are not consistent with the resource names specified in the OPENINFO string in the RMS sections.

Action

Make sure all the required resource manager symbols are imported while executing buildserver with -r option, and the resource manager name is consistent with the name configured in OPENINFO string in RMS section.

See Also

buildserver(1), UBBCONFIG(5)

 

Skip footer navigation  Back to Top Previous