Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Always refer to the latest version of the patch installation instructions. The instructions are periodically updated
and contain critical information to ensure the successful installation of patches. Access the latest version of the
instructions at http://www.ibm.com/support/docview.wss?uid=swg27012519.
Note: Before using this information and the product that it supports, read the general information under Notices
and trademarks.
Copyright International Business Machines Corporation 2008. All rights reserved. US Government Users
Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
Contents
About this document
Patch installation log files
About patches
Use the latest version of the Update Installer
Requirements
Preparing your system for patch installation or uninstallation on services and engine tiers
Preparing your system for patch installation or uninstallation on the client tier
Installing a patch
o Command line parameters
o Using console mode installation on Linux and UNIX operating systems
o Using the installation wizard on Linux and UNIX operating systems
o Using console mode installation on Windows operating systems
o Using the installation wizard on Windows operating systems
o Verifying installation
o Post-installation backup
Uninstalling a patch
o Uninstalling on Linux and UNIX operating systems
o Uninstalling on Windows operating systems
IBM InfoSphere Information Server Version 8.1 known patch installation problems
Accessing information about IBM
Notices and trademarks
This information is the most current about the product on the date of publication.
Windows C:\IBM\InformationServer
Microsoft Windows:
C:\IBM\InformationServer\logs
C:\IBM\InformationServer\Updates\PatchName
Linux, UNIX:
/opt/IBM/InformationServer/logs
/opt/IBM/InformationServer/Updates/PatchName
About patches
Patches for IBM InfoSphere Information Server Version 8.1 consist of two files.
On IBM AIX, Microsoft Windows, and Red Hat Linux, the script might not exist. If the script does not
exist, you do not have the latest version of the Update Installer. When you install a patch with Update
Installer Version 8.1.0.160 or later, the script is created automatically for future use.
After you download the latest version of the Update Installer, install it by replacing the updater.jar file in
the following directory:
Windows: C:\IBM\InformationServer\Updates\bin
Linux, UNIX: /opt/IBM/InformationServer/Updates/bin
Patches are installed with the Update Installer that is part of the IBM InfoSphere Information
Server installation. Updated versions of the Update Installer are located
at http://www.ibm.com/support/docview.wss?uid=swg27012519.
Requirements
Ensure that the following requirements are met before you install patches.
Install the patch on all tiers that the patch applies to: services first, then engine, and then client
tier
Some patches apply to more than one tier. In distributed installations of IBM InfoSphere Information
Server, you must install these patches on all computers that have tiers installed that the patch applies
to. When you install a patch on multiple computers, install the patch on the services tier first, then on
the engine tier, and then on the client tier. See the README.txt file included with the patch to
determine which tiers the patch applies to.
UNIX systems umask setting
On UNIX systems, set the umask value to 022.
UNIX root user
On UNIX operating systems, you must log in as the root user to install a patch.
Windows administrator privileges on engine and services tiers
For engine and services tiers on Windows operating systems:
Patches must be installed by a user with administrator privileges.
Use the same user name that you used to install IBM InfoSphere Information Server to ensure
that you have the correct privileges.
Windows Vista administrator privileges on the client tier
To install IBM Information Server patches, you must use a command window that has been elevated to
have full administrative privileges. Follow these steps to open an elevated command window:
1. Click the Start menu.
2. Type cmd in the Start Search box.
3. Press Ctrl+Shift+Enter.
4. Click Continue to accept the prompt asking for your permission to continue.
Patch-specific installation instructions
Before you install a patch, see the README.txt file that is included with the patch for any installation
instructions that are specific to the patch.
Installing a patch
The patch name patch_JR000000_type_os.ispkg in the
following commands is an example. Use the correct name
of the patch that you are installing.
Parameter Description
Parameter Description
Verifying installation
Post-installation backup
Uninstalling a patch
Not all patches can be uninstalled. The README.txt file
included with each patch indicates whether the patch can
be uninstalled. Only the last patch installed can be
uninstalled. To uninstall a patch that is not the last installed
patch, you must first uninstall the latest installed patch and
then uninstall all later patches. Installing a patch that cannot
be uninstalled prevents all previously installed patches from
being uninstalled because patches must be uninstalled in
reverse order of their installation. To determine which
patches have been installed, locate the Version.xml file:
Windows: C:\IBM\InformationServer\Version.xml
Linux,
UNIX: /opt/IBM/InformationServer/Version.xml
In the Version.xml file, the entry for the last patch installed
is at the end of the history section and is similar to the
following example:
...
<History>
...
<Sequence description="Description of the
patch" id="1" installLocation=""
lastUpdateDate="Thu Feb 14 13:13:52 EST 2008"
patch="patch_JR000000"
rollback="/opt/IBM/InformationServer/Updates/p
atch_JR000000"
status="Success" version=""/>
</History>
...
Parameter Description
If IBM InfoSphere Information Server Pack for SAP BW or the IBM InfoSphere Information Server Pack
for SAP R/3 is installed on your computer, before installing a patch, shut down SAP and BW listeners
to avoid a possible installation failure.
Workaround
1. Before running the Update Installer, shut down the SAP and BW listeners.
2. Install the patch.
3. Restart the listeners.
Command line options for the Update Installer are
ignored
Operating systems: IBM AIX, Linux, Windows
Command line options that are passed to the Update Installer are ignored when you use
the InstallUpdate.sh or InstallUpdate.bat script. This issue exists only on some installations.
Workaround
Modify the InstallUpdate script to pass through command line options to the Update Installer.
If the port for the InfoSphere Information Server services was modified in IBM WebSphere Application
Server after the original installation, the patch installation fails with an authentication error. The
following error message appears in the log file:
SEVERE:
com.ibm.is.install.update.installer.ConsoleUpdateDriver Failed to
authenticate username/password, please ensure your application server
is running, and ensure you have entered valid Information server
administrator user name/password. Return message is: null
Workaround
Before installing the patch, confirm that the ASBPort value in the Version.xml file matches the actual
port used for InfoSphere Information Server.
1. Confirm the port number by using a Web browser to access the InfoSphere Information
Server Web console. For example, the InfoSphere Information Server port number in the
following URL is 9080:
http://hostname:9080/index.jsp
2. Verify that the Version.xml file also has the
correct LPV_ASB_HOST and LPV_ASB_PORT values.
3. Locate the following variables in the <Properties> section:
4. <Property name="AsbHostName" value=localhost.localdomain/>
<Property name="AsbPortNumber" value=9080/>
localhost.localdomain is your system hostname. In the AsbPortNumber value, enter the
application server port number that you use to connect to the InfoSphere Information
Server Web console.
Patch installation fails when the installation
is unable to stop the ASBAgent service
Operating system: Windows
During patch installation, the IBM WebSphere Application Server and the IBM InfoSphere Information
Server are automatically shut down and restarted. The patch installation fails when the ASBAgent
service fails to stop the ASBAgent process after a shutdown request times out. When this occurs, the
following entry is found in the installation log file:
Workaround
Restart your computer, and then restart the patch installation. If the issue is not resolved, contact IBM
customer support. To resolve issues with the taskkill.exe process, contact Microsoft Corporation.
Patch installation might fail if the maximum heap size is not sufficient for that system, resulting in an
OutOfMemory exception in IBM WebSphere Application Server. Some systems runningIBM
WebSphere Application Server might require increasing the heap size to successfully install a patch.
The default maximum heap size allocation of IBM WebSphere Application Server process is
automatically set to 768 MB during IBM InfoSphere Information Server installation.
Workaround
Set the maximum heap size property to 1280 MB before installing the patch.
To change the maximum heap size allocated to the application server process:
1. Log in to the WebSphere administrative console as the WebSphere administrator.
2. In the topology tree, expand Servers and click Application Servers.
3. Click the server1 link (where server1 is the name of the application server that you want to
configure).
4. Under Server Infrastructure, expand Java and Process Management.
5. Click Process Definition.
6. Under the Additional Properties section, click Java Virtual Machine.
7. In the Maximum Heap Size field, type 1280.
8. Click Apply or OK.
9. Install the patch.
10. Reset the value of Maximum Heap Size to the original value after you install the patch.
Invalid Version.xml file causes the
patch installation to fail
Operating system: All
If the Version.xml file is edited manually, the patch installation might fail.
Workaround
If the Version.xml file is edited or becomes corrupt, rename this file and extract the original version
from the most recent ISdump-os-timestamp.zip file. Retain the renamed version of the
original Version.xmlfile as a record of what patches were previously installed before you recovered it.
Patch installation might fail if
you do not have all default
local administrator
privileges
Operating system: Windows
The installation might fail because of authentication and other errors if you are a member of the
domain administrators group, but you are not a member of the local administrators group, or if the
account used does not have all default local administrator privileges.
Workaround
Ensure that the account that is used has all default local administrator privileges and reinstall the
patch.
Successful patch
installation has a
SEVERE error in
the installation log
Operating system: All
IBM InfoSphere Information Server installations that include might generate a SEVERE error message
in the installation log file.
SEVERE: Exit Code: 0, Info: Stopping JobMonApp JobMonApp has been shut down.
DataStage Engine 8.0.1.0 instance "801" has been brought down., Error: DeadLock
Daemon shutdown
Workaround
The patch installed successfully. Ignore the error message.
Kindly follow below instruction for installing Patches/Updates on datastage client machine.
Copy the installation files from IBM sites. and keep those files into updates folder and follow
below steps to complete the instalation.
Console mode:
installUpdates.exe -console
Enter the required values as you are prompted during the installation.
d. Alternatively, you can provide all of the parameters and values and enter the
following command to install an update package as shown in the following example:
e. installUpdates.exe -installLocation C:\IBM\InformationServer
f. -patchPackage C:\IBM\InformationServer\Updates\Downloads\UpdatePackageName
g. -user isadmin -password isadminpassword -wasadmin WebSphereUsername
h. -waspassword WebSpherePassword -console -verbose
i. where:
UpdatePackageName = the update package that you want to install
isadmin = InfoSphere Information Server administrator user
isadminpassword = InfoSphere Information Server administrator
password
WebSphereUsername = WebSphere Application Server user name
WebSpherePassword = WebSphere Application Server password