Download
Abstract
4.3.1-TMF-0025 is a interim fix for TMR servers, managed nodes, and gateways. No other interim fixes or fixpacks need to be installed prior to this interim fix.
Download Description
Please see the download package for the full Readme.
Interim Fixes superseded by this interim fix:
4.3.1-TMF-0001LA
4.3.1-TMF-0002LA
4.3.1-TMF-0003LA
4.3.1-TMF-0005
4.3.1-TMF-0007LA
4.3.1-TMF-0012
4.3.1-TMF-0013LA
4.3.1-TMF-0016LA
4.3.1-TMF-0017LA
4.3.1-TMF-0018LA
New fixes in 4.3.1-TMF-0025 (includes fix from 4.3.1-TMF-0013LA,
4.3.1-TMF-0016LA, 4.3.1-TMF-0017LA, and 4.3.1-TMF-0018LA):
Internal CMVC defect 252552
Symptoms: Installation on linux-ix86 managed nodes can fail at TMF
4.3.1 upgraded environment. The installation includes wclient, winstall,
wpatch, or Tivoli Desktop GUI operations related to those functions.
The linux-ix86 platform includes newly supported OS in TMF 4.3.1 like
RHEL 5 which has 'tail' command requiring notation like "tail -n +2"
instead of "tail +2".
Internal CMVC defect 257773, Enhancement request MR041410129
Symptoms: Provide support for Windows UAC (User Access Control) on
Windows Vista or later. For this feature, the oserv service needs to
run with SYSTEM account.
Internal CMVC defect 258342
Symptoms: oservlog will not be updated after reexec oserv.
Internal CMVC defect 260852
Symptoms: Endpoint installation fails on Windows domain controller
if the Tivoli_Admin_Privileges group or the tmersrvd account already
exists on the domain.
Internal CMVC defect 263118
Symptoms: The oserv crashes if the length of tivoli desktop login
password is longer than 64. This problem occurs only when TMR is
running on Solaris. The oservlog may contain an error message that
is similar to:
"!oserv went down on signal 6".
Internal CMVC defect 266366
Symptoms: A task execution dialog of Tivoli Desktop failes with
"Assertion !done() failed" message if a list entry is empty.
Internal CMVC defect 269524
Symptoms: wchknode can be aborted with the message like
"*** glibc detected *** wchknode: double free or corruption (!prev)".
APAR IV01169
Symptoms: The installation of the managed node failed while the TMR is
registering the installation information in the tivoli database. The error
like "FRWSL0006E A reference to an object is invalid. The object no longer
exists or is in a disconnected TMR." is input in the tivoli.cinstall log
file, and the output of the command "wlsinst -a" is like "FRWSL0009E The
incorrect type of data was passed from a client to an object: FRWSF0018E
ADR decode tag error".
APAR IZ83162
Symptoms: Attempting to enable multicast (after setting
endpoint_multicast=TRUE) on UNIX platforms except AIX, mcast still posts:
"Please run wmdist -s <HOSTNAME> [-C noprompt|nostart|nostop]
endpoint_multicast=TRUE in order to enable multicasting to endpoints."
mcast.log posts UnsatisfiedLinkError java exception caused by the load
error of libhdjni library:
Time: XX:XX:XX.XXX
Class: com.tivoli.framework.DepotServer_programs.DepotServer_impl
Method: startDepotServer
Thread Name: Thread-X
create advertThread
java.lang.UnsatisfiedLinkError: ...
APAR IZ90221
Symptoms: The rim_db_log is created under the directory of
the RIM_DB_LOG while the trace level is set to TRACE_OFF and
the SELECT_BIND variable has been enabled. And the rim_db_log
is filled with debug messages as below when a distribution is
deleted in database.
00021075 [Fri Nov 19 12:27:15 2010] Trace Message - Connection ID::
Call OBNDRV in val_execute_with_bind_delete. progv = 0, progvl=65
APAR IZ90485
Symptoms: On Windows, the oserv.exe can leak memory when a
new child process is created by the method call. This problem
only happens if the patch 4.3.1-TMF-0012 is installed.
APAR IZ94733
Symptoms: The BDT service (bdtsvc.exe) crashes on Windows Server 2008
R2 while installing a product or patch. The bdtlog may show an error
similar to:
"2010/12/23 17:27:22 -02: ^OpenEvent failed @ ../../../../../src/
substrate/oserv/lib/winsock_comm.c 1810 The system cannot find the
file specified."
APAR IZ95372
Symptoms: A task execution dialog of Tivoli Desktop failes to get list
entries of options and shows the message
"assertion `!done()' failed, line: 550, file: `../../../../src/
ui/gl/GLChoiceList.C'".
APAR IZ97225
Symptoms: Turning on User Account Control (UAC) setting will effect
Tivoli functioning well.
Installation Instructions
Applying this Interim Fix:
1) Extract the interim fix:
On a Unix system:
Extract the contents into a scratch directory. For the purpose
of this release note, assume that the symbol $PATCH points to
this directory.
# cd $PATCH
# tar xvf 4.3.1-TMF-0025.tar
On a Windows system:
Extract the contents into a scratch directory. For the purpose
of this release note, assume that the symbol %PATCH% points to
this directory.
> %SystemRoot%\system32\drivers\etc\Tivoli\setup_env
> X:
^-- 'X' is drive letter where %PATCH% is found
> cd %PATCH%
> tar xvf 4.3.1-TMF-0025.tar
NOTE: If you are extracting the tar image on a Windows
system, you will find an executable for tar in the TME
installation on Windows under bin/w32-ix86/tools/tar.exe.
2) If this interim fix is to be installed on a release level of
3.7.1 or greater, follow these instructions for using Software
Installation Service (SIS). If not, skip to step 3 below.
NOTE: SIS can install Tivoli products on any hardware
platform supported by Tivoli, but there are some
hardware platforms on which SIS cannot be run. Please
check your SIS User's Manual for the list of platforms
on which SIS can be run.
NOTE: You must have the install_product and super authorization
roles to successfully install this interim fix.
a) From the Tivoli Desktop, pull down
Desktop --> Install --> Software Installation Service.
b) SIS will initialize, and bring up the Get Installation
Password Dialog. Enter your Installation Password.
c) Click the Install Button on the dialog which contains
the Tivoli image.
d) Click the Select Product Button on the Install Spreadsheet
Dialog.
e) Click the Import Product Button on the Select Product
Dialog.
f) Locate the media to 4.3.1-TMF-0025 using the file browser,
and select the PATCHES.LST file by double-clicking it.
g) Select 4.3.1-TMF-0025 in the Import Product Dialog, and
click the Import Button.
h) When the import is complete, click the OK Button on the
Global Progress Dialog.
i) Select 4.3.1-TMF-0025 in the Select Product Dialog, if it
is not already selected, and click the OK Button.
j) Now click the Select Machine Button on the Install
Spreadsheet Dialog.
k) Select the machine(s) you would like to install
4.3.1-TMF-0025 on and click the OK Button.
l) Click the appropriate cell(s) in the Install Spreadsheet
Dialog. (NOTE: This should yield an "X" in the cell(s)
for the machines you want to install 4.3.1-TMF-0025 to).
m) Click the Install Button.
n) Select the install algorithm you want to use on the
Installation Algorithm Dialog, and click OK.
o) SIS will perform the installation(s) you designated
in the Install Spreadsheet Dialog.
p) Installation is complete. Check the Additional
Installation Instructions section below.
3) Use the following steps to install the interim fix using the
Tivoli GUI install mechanism.
NOTE: You must have the install_product and super authorization
roles to successfully install this interim fix.
a) Select the "Install -> Install Patch..." option from the
"Desktop" menu to display the "Install Patch" dialog.
b) Press the "Select Media..." button to display the "File
Browser" dialog.
c) Enter the path to the directory containing the interim fix,
$PATCH, in the "Path Name:" field.
d) Press the "Set Media & Close" button to return to the
"Install Patch" dialog.
e) The patch install list now contains the name of the interim
fix. Select the interim fix by clicking on it.
f) Select the clients to install this interim fix on. This
interim fix needs to be installed on the TME server and on
each managed node client.
g) Press the "Install" button to install the interim fix.
Additional Installation Instructions:
After applying this interim fix, perform the following numbered
steps to restart the oservs on the TMR server and managed nodes /
gateways.
1) From the TMR server, run the following command to shut down all
managed nodes / gateways:
odadmin shutdown clients
2) When the client oservs have all terminated, run the following
command to restart the TMR server:
odadmin reexec 1
3) Once the oserv on the TMR server has fully restarted, then run
the following command to restart the managed nodes / gateways:
odadmin start clients
Problems (APARS) fixed
Problems (APARS) fixed
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg24031274