Table of Contents Previous Next PDF


Known and Resolved Issues

Known and Resolved Issues
The following sections describe known issues with the Oracle Tuxedo software and include recommended workarounds. The problems are listed by the Change Request (CR) number. The CR number is provided to facilitate the tracking of these problems.
Contact your Oracle Customer Support Center for assistance in the tracking of any unresolved problems. When contacting the Oracle Customer Support Center, please refer to the CR number.
Known Limitations
Table 1 describes the known limitations for Oracle Tuxedo and provides recommended workarounds.
 
1.
Using Tuxedo 11gR1 as master in MP mode, if you installed a previous Tuxedo version and did not change tlisten password after installation, you will receive a security negotiation error message (CMDTUX_CAT:4291).
 
Product Constraints
Table 2 describes product constraints for Oracle Tuxedo and provides recommended workarounds.
 
1.
3.
Resolved Issues
Table 3 lists the software and documentation problems that have been fixed in Release 11g Release 1 (11.1.1.0). Problems are listed by CR (Change Request) number.
Any software or documentation fixes that are made to Tuxedo 11g Release 1 (11.1.1.0) are reported in updates to this section.
 
Table 3 Problems Fixed in Oracle Tuxedo 11g Release 1 (11.1.1.0)
Process cleanupsrv kill live server
TUX9.1: tmshutdown does not work when killed process id is recycled
TUX10.0: build command still links /usr/lib/libcrypt.a on 64bit Linux
10.
11.
TUX 10.0: dmadmin crashes on exit
12.
TUX 10.0: unadv subcommand of dmadmin does not work
13.
14.
TM_MQI Feedback not set correctly on TPFAIL when TPESVCFAILDATA=Y
15.
Fix SSL linking error when WSC calls tpchkauth() before tpinit()
16.
17.
18.
libcobatmis.dll should be provided for Windows platform
19.
ud/ud32 can not be the initiator if -C tpsysadm is not specified
20.
Inconsistent <LOCATION> information for TSAM events generated by BBL
21.
22.
dmunloadcf does not work well on AIX
23.
24.
25.
26.
WSH did not check if the TMALARM message is stale
27.
28.
CORBA: m3ifrclient case failed because missing the data
29.
30.

Copyright © 1994, 2017, Oracle and/or its affiliates. All rights reserved.