IBM Information Server

IBM Information Server Patch Installation Instructions

Instructions for installing patches for IBM® Information Server 8.0.1. Document updated June 8, 2009, version 5.

Important: Latest version of patch installation instructions

Always refer to the latest version of the patch installation instructions. The instructions are periodically updated and contain critical information to ensure successful installation of patches. Access the latest version of the instructions at http://www.ibm.com/support/docview.wss?uid=swg27011896.

Note: Before using this information and the product that it supports, be sure to read the general information under Notices and trademarks.

© Copyright International Business Machines Corporation 2008, 2009. All rights reserved. US Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Contents

This information is the most current about the product on the date of publication.

About patches and patch installation

Patches for IBM Information Server Version 8.0.1 are distributed separately from the Version 8.0.1 Update Installer components that are required to install the patches.

Patch components
The patch distribution consists of two files. The following table lists the patch component files:
Table 1. Patch component file names and descriptions
Patch component Description
README.txt Contains important information specific to the patch. Read the information in the README.txt file before you install a patch.
*.ispkg The contents of the patch package.
Update Installer components
To install a patch you use the operating system-specific launcher to start the installation and an associated .jar file that is compatible with all operating systems. The following table lists the Update Installer components.
Table 2. Update Installer component file names and descriptions
Update Installer component File name Description
Update Installer Launcher Updater.exe or Updater Operating system-specific launcher application for Linux®, UNIX®, or Microsoft® Windows®
Update Installer updater.jar .jar file for all operating systems

Instructions in this document use the default installation paths. Your path varies if you installed IBM Information Server in a different location.

Default installation paths
The following table lists the default IBM Information Server installation locations:
Table 3. Default installation locations
Operating system Directory
Windows C:\IBM\InformationServer
Linux, UNIX /opt/IBM/InformationServer
Patch installation instructions
Before you install a patch, see the README.txt file that is included with the patch for installation instructions that are specific to the patch.
Location of the vpd.script file
This document refers to the vpd.script file. The following table lists the vpd.script file directory by operating system.
Table 4. Directory of vpd.script file by operating system
Operating system Directory
Windows C:\Program Files\Common Files\InstallShield\Universal\IBM\InformationServer\Gen2\_vpddb
AIX® /usr/lib/objrepos/InstallShield/Universal/IBM/InformationServer/Gen2/_vpddb
Solaris /InstallShield/Universal/IBM/InformationServer/Gen2/_vpddb
Red Hat Linux and SUSE Linux /root/InstallShield/Universal/IBM/InformationServer/Gen2/_vpddb
Location of the Version.xml file
This document refers to the Version.xml file. The following table lists the Version.xml file directory by operating system.
Table 5. Directory of Version.xml file by operating system
Operating system Directory
Windows C:\IBM\InformationServer\Version.xml
Linux, UNIX /opt/IBM/InformationServer/Version.xml

Requirements

Ensure that the following requirements are met when installing patches.

Install the patch on all layers that the patch applies to: domain first, then server, and then client layer
Some patches apply to more than one layer. In distributed installations of IBM Information Server, you must install these patches on all computers that have layers installed that the patch applies to. When you install a patch on multiple computers, install the patch on the domain layer first, then on the server layer, and then on the client layer. See the README.txt file included with the patch to determine which layers 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 domain layers
The following requirements apply to patch installation on engine and domain layers 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 Information Server to ensure that you have the correct privileges.
Windows Vista administrator privileges
On Windows Vista, you must use a command window that has been elevated to have full administrative privileges to install a patch.
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.

Preparing your system for patch installation or uninstallation on domain and server layers

Shut down IBM Information Server
Shut down IBM Information Server, including IBM WebSphere® Application Server, before you perform a complete backup.
Back up content
Before you install a patch, create a complete backup of all IBM Information Server content, including the metadata repository database and Information Analyzer analysis database (if installed).
Start IBM Information Server
Start IBM Information Server after backing up the content.
Increase Inactive Session Timeout value for Global Session Properties
Increase the value of the Inactive Session Timeout field to 7200 seconds (120 minutes) to ensure a successful installation when you install patches on slower computers. Follow these steps to change the value of the timeout to avoid being disconnected automatically during patch installations:
  1. Log in to the IBM Information Server Web console.
  2. Click the Administration tab.
  3. In the Navigation pane, select Session Management > Active Sessions.
  4. In the Active Sessions pane, click Global Session Properties.
  5. Specify 7200 for the Inactive Session Timeout field.
  6. Click Save and Close.
Note: Reset the Inactive Session Timeout value to the original value after you install a patch.
Ensure that the server and domain are running
To ensure that the server and domain are running:
  1. In a browser window, enter http://host_server:9080 where host_server is the name or IP address of the domain server.
  2. Log in by using the IBM Information Server Administrator user name and password (this is not the WebSphere Application Server user name).
Ensure that the following products and services are running properly
The database for IBM Information Server and the following products and services must be running for the patch installation to succeed.
  • Metadata repository database and database server
  • WebSphere Information Analyzer database and database server (if installed)
  • WebSphere Application Server
  • Logging agent
  • Application Services Backbone (ASB) Agent
  • WebSphere DataStage® engine services (if installed)
Ensure that IBM Information Server 8.0.1 is not in use
Do not perform any actions on IBM Information Server components during the patch installation. The server and domain layers of IBM Information Server must be fully dedicated to the installation process. Do not run any other applications or attempt to access any IBM Information Server services during the installation.
Some patches require that the WebSphere Application Server and IBM Information Server be shut down and restarted one or more times. Do not interfere with the automatic shutting down and restarting of WebSphere Application Server and IBM Information Server.
Note: See the README.txt file that is included with the patch to determine if you must restart the computer after the patch is installed.
Set IDTHTOIN to 600 seconds when using IBM DB2® for IBM z/OS® for the metadata repository
The value of the currently active DB2 DSNZPARM parameter IDTHTOIN (in the DSN6FAC macro) must be set to 600 seconds during installation on the domain layer. After installation is complete, this parameter can be restored to its original value. This is a system-wide parameter and must be set by a database administrator.
Note: IBM WebSphere Information Services Director deployment requires that the IDTHTOIN parameter be set to a value longer than the time required to deploy an application. If you do not plan to have your database administrator change this value for each application deployment, you must leave the DSNZPARM parameter set to a value that allows application deployment to succeed.

Preparing your system for patch installation or uninstallation on the client layer

Shut down clients
Ensure that IBM Information Server 8.0.1 client applications are not running on the computer.

Installing a patch

The Update Installer Launcher (Updater.exe on Windows or Updater on Linux and UNIX) and the Update Installer (updater.jar) must be in the same directory when you install a patch.

The paths shown in the following commands assume that the product is installed in the default location. Your path will vary if you installed IBM Information Server in a different location.

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.

The user name and password shown in the following commands are examples. Use the same user name and password that you used to install IBM Information Server.

The Update Installer supports two installation modes on all operating systems: installation wizard mode and console mode. You can use command line parameters can be used in both installation modes.

Patch installation command line parameters

The following command line parameters are available for the patch installation. If you do not specify values for an optional parameter, the Update Installer prompts you to enter the values during the patch installation. You must always provide the –i parameter and value.

Table 6. Patch installation command line parameters
Parameter Description
-i IBM Information Server installation root directory.
-p Optional. The file name of the patch installation package.
-user Optional. IBM Information Server administrator user name.
-password IBM Information Server administrator password, required when the -user parameter is provided.
-wasadmin Optional. WebSphere Application Server administrator (server ID) user name. Applies only when installing a patch on computers with the domain layer installed.
-waspassword WebSphere Application Server administrator (server ID) password, required when the -wasadmin parameter is provided.
-console Optional. Install without opening the installation wizard.
-force Forces reinstallation of a patch. To ensure a consistent installation, reinstall all patches and fix packs that were initially installed after you originally installed this patch.
-verbose Optional. Include detailed information in the console output.
-version Display the version number of the Update Installer.
Note: The IBM Information Server administrator and WebSphere Application Server administrator user names and passwords are not required when you install the patch on computers where only the client layer is installed.

Using console mode installation on Linux and UNIX operating systems

Follow these steps to install a patch on Linux or UNIX operating systems:
  1. Log in as the root user.
  2. If your installation includes WebSphere DataStageWebSphere DataStage, source the dsenv file. In the command prompt window, type the following command:
    . /opt/IBM/InformationServer/Server/DSEngine/dsenv
  3. If you are installing a patch on HP-UX 11i v2 on Intel® Itanium® systems, run the following command:
    unset LD_PRELOAD
  4. If you are installing a patch on IBM AIX, unset LDR_CNTRL after sourcing dsenv to avoid adversely impacting the amount of available memory in WebSphere Application Server. Type the following command:
    unset LDR_CNTRL
  5. In the command prompt window, type the following command to install a patch:
    ./Updater -i /opt/IBM/InformationServer -console
    Alternatively, you can specify all of the command line parameters and values to avoid interactive installation prompts. Type the following command to install a patch:
    ./Updater -i /opt/IBM/InformationServer –p patch_JR000000_type_os.ispkg
    -user admin -password AdminPassword -wasadmin wasadmin
    -waspassword WebSpherePassword –console -verbose

Using the installation wizard on Linux and UNIX operating systems

If you use the wizard to install patches on Linux or UNIX operating systems, the X11 client must be running. The following instructions ensure that your DISPLAY variable is set properly, and verifies that the X Window System application is running by starting xterm, which uses X11. You can also verify that the X11 client is running by starting xclock, or another application that uses X11.
Note: The installation wizard prompts you to enter the required values before you install the patch.
  1. Log in as the root user.
  2. Set the DISPLAY environment variable. For example,
    export DISPLAY=myhost.mydomain.com:0.0
  3. Start the X11 client application to test the DISPLAY environment variable. In the command prompt window, type:
    xterm
    On Solaris operating systems, type:
    /usr/openwin/bin/xterm 
    A new X11 terminal window is displayed and confirms that the X11 DISPLAY environment variable is configured properly. You cannot use the wizard to install patches without the correct DISPLAY environment variable.
  4. If your installation includes WebSphere DataStage, source the dsenv file. In the command prompt window, type:
    . /opt/IBM/InformationServer/Server/DSEngine/dsenv
  5. If you are installing a patch on HP-UX 11i v2 on Intel Itanium systems, run the following command:
    unset LD_PRELOAD
  6. If you are installing a patch on IBM AIX, unset LDR_CNTRL after sourcing dsenv to avoid adversely impacting the amount of available memory in WebSphere Application Server. Type the following command:
    unset LDR_CNTRL
  7. Type the following command to start the installation:
    ./Updater -i /opt/IBM/InformationServer
  8. Follow the instructions in the installation wizard to install the patch.

Using console mode installation on Windows operating systems

Follow these steps to install a patch in console mode on Windows operating systems:

  1. Log in with administrator rights.
  2. In the command prompt window, type the following command to install a patch:
    Updater -i C:\IBM\InformationServer -console

    Alternatively, you can specify all of the command line parameters and values to avoid interactive installation prompts. Type the following command to install a patch:

    ./Updater -i /opt/IBM/InformationServer –p patch_JR000000_type_os.ispkg
    -user admin -password Admin_Password -wasadmin wasadmin
    -waspassword WebSphere_Password –console -verbose
    Note: The IBM Information Server administrator and WebSphere Application Server administrator user names and passwords are not required when you install the patch on computers where only the client layer is installed.

Using the installation wizard on Windows operating systems

Note: The installation wizard prompts you to enter the required values before you install the patch.
  1. Log in with administrator rights.
  2. In the command prompt window, type the installation command to start the installation:
    Updater -i C:\IBM\InformationServer
  3. Follow the instructions in the installation wizard to install the patch.

Verifying installation

After you install the patch, verify the installation. The paths shown in the following example assume that the product is installed in the default location. Your path will vary if you installed IBM Information Server in a different location.

  • Ensure that all IBM Information Server client applications start and run correctly.
  • Verify that the Version.xml file includes Status="Success". When the entry shows Status="PartialSuccess" or there is no entry for the patch that you installed, the patch installation did not succeed.
    In the Version.xml file, the status entry for the last patch installed will be at the end of the history section as shown in 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/patch_JR000000" 
    status="Success" version=""/>
    </History>
    ...
  • Review the ISinstalltimestamp.txt log file (where timestamp is the time stamp in YYYY.MM.dd.hh.mm.ss format) to ensure that FATAL and SEVERE errors are not present. Locate the ISinstalltimestamp.txt file:
    • Windows: C:\IBM\InformationServer\logs\ISinstalltimestamp.txt
    • Linux, UNIX: /opt/IBM/InformationServer/logs/ISinstalltimestamp.txt
    See IBM Information Server Version 8.0.1 known patch installation problems for information about errors that can be ignored. For all other errors, contact IBM customer support.

Post-installation backup

Perform a complete backup of the IBM Information Server installation. See "Back up content" in the Preparing your system for patch installation or uninstallation on domain and server layers section for details.

Uninstalling a patch

To uninstall a patch, the Update Installer Launcher (Updater.exe on Windows or Updater on Linux and UNIX) and the Update Installer (updater.jar) must be in the same directory.

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 latest 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, view 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/patch_JR000000" 
status="Success" version=""/>
</History>
...

The paths shown in the following commands assume that the product is installed in the default location. Your path will vary if you installed IBM Information Server in a different location.

You must use the Update Installer in console mode when you uninstall patches.

Patch uninstallation command line parameters
The following command line parameters are available for patch uninstallation:
Table 7. Patch uninstallation command line parameters
Parameter Description
-i IBM Information Server installation root directory.
-rollback Name of the latest installed patch.
-verbose Optional. Include detailed information in the console output.

Uninstalling on Linux and UNIX operating systems

Follow these steps to uninstall the latest patch installed on Linux or UNIX operating systems:
  1. Log in as the root user.
  2. If your installation includes WebSphere DataStage, source the dsenv file. In the command prompt window, type the following command:
    . /opt/IBM/InformationServer/Server/DSEngine/dsenv
  3. If you are uninstalling a patch on HP-UX 11i v2 on Intel Itanium systems, run the following command:
    unset LD_PRELOAD
  4. If you are uninstalling a patch on IBM AIX, unset LDR_CNTRL after sourcing dsenv to avoid adversely impacting the amount of available memory in WebSphere Application Server. Type the following command:
    unset LDR_CNTRL
  5. In the command prompt window, type the following command to uninstall the latest installed patch:
    ./Updater -i /opt/IBM/InformationServer -rollback patch_JR000000

Uninstalling on Windows operating systems

Follow these steps to uninstall the latest patch installed on a Windows operating system:
  1. Log in with administrator rights.
  2. In the command prompt window, type the following command to uninstall the latest installed patch:
    Updater -i C:\IBM\InformationServer -rollback patch_JR000000

IBM Information Server Version 8.0.1 known patch installation problems

At the time of publication, the following problems are known for patch installations.

WebSphere Information Analyzer services are not deployed during installation
Operating system: All

Installation appears to be successful, but WebSphere Information Analyzer services are not deployed during installation.

Workaround

Verify if you have the problem and then resolve the problem.

To verify that WebSphere Information Analyzer services are deployed:
  1. In a command window, type the following commands:
    • Windows:
      cd C:\IBM\InformationServer\ASBServer\bin 
      ServiceAdmin.bat -user InformationServer_Username -password InformationServer_Password -la
    • Linux, UNIX:
      cd /opt/IBM/InformationServer/ASBServer/bin
      ./ServiceAdmin.sh -user InformationServer_Username -password InformationServer_Password -la 
  2. Run the following command:
    Serviceadmin -user InformationServer_Username -password InformationServer_Password -la
  3. Verify that the WebSphere Information Analyzer services are listed with this entry:
    Info IAServicesApp

The WebSphere Information Analyzer services are successfully deployed when the WebSphere Information Analyzer services entry is listed.

The WebSphere Information Analyzer services are not deployed when the WebSphere Information Analyzer services entry is not listed. The UNIX temporary directory is typically \tmp or \var\tmp.

To resolve this problem:
  1. Ensure that the IAServices.ear file exists in the temporary directory:
    • Windows: %TEMP%
    • Linux, UNIX: /tmp
  2. In a command window, run the following command to deploy the WebSphere Information Analyzer services:
    • Windows:
      cd C:\IBM\InformationServer\ASBServer\bin
      ServiceAdmin.bat -verbose -upgrade -deploy "%TEMP%\IAServices.ear" -user InformationServer_Username -password InformationServer_Password  
    • Linux, UNIX:
      cd /opt/IBM/InformationServer/ASBServer/bin
      ./ServiceAdmin.sh -verbose -upgrade -deploy "/tmp/IAServices.ear" -user InformationServer_Username -password InformationServer_Password 
  3. If an OutOfMemory error message is displayed, or if you see a Java™ exception similar to:
    java.rmi.RemoteException: CORBA NO_MEMORY
    run the ServerAdmin command again, then increase your WebSphere Application Server heap size, and redeploy the WebSphere Information Analyzer services.
Note: For instructions on changing the heap size, see Patch installation fails on OutOfMemory exception in this document.
Follow these steps to verify that the WebSphere Information Analyzer services deployment is successful:
  1. Run the ServiceAdmin command again to verify that WebSphere Information Analyzer services are deployed.
  2. Start the IBM Information Server console and open Home > Configuration > Analysis Setting.
  3. Validate both the analysis database and the analysis engine settings.
Patch installation fails with "InstallShield VPD database may be corrupted" error message
Operating system: All

If the vpd.script file was manually edited, it might be corrupted. It is also possible that the vpd.script file was not saved correctly if the IBM Information Server installation was terminated before it was completed.

Workaround

Contact IBM customer support.

Patch installation fails if the port for the IBM Information Server domain has been changed in WebSphere Application Server
Operating system: All
Patch installation fails when the port for the IBM Information Server domain computer was modified in WebSphere Application Server after the original installation or if a response file was used with earlier versions of the IBM Information Server suite installer and values were not correctly recorded in the vpd.script file. Incorrect values in the vpd.script file cause the patch installation to fail. 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

Confirm that the value are in the vpd.script file matches the port that is used for IBM Information Server before installing the patch. To verify the values:
  1. Confirm the port number by using a Web browser to access the IBM Information Server Web console. For example, the port number in the following URL is 9080: http://domain:9080/index.jsp.
  2. In the vpd.script file, locate the following entry in the InstallShield Registry file where '/opt/IBM/InformationServer' is the installation location of the IBM Information Server version you are attempting to patch. The first numeric value after the opening parenthesis is the instance ID.
    INSERT INTO LOCAL_PERSISTED_VARIABLES_TABLE VALUES
    (211,'LPV_ROOT_INSTALL_DIR','/opt/IBM/InformationServer',NULL,'false')
  3. Search the vpd.script file for the LPV_ASB_HOST port configuration entry that is similar to the following example with a matching instance ID:
  4. INSERT INTO LOCAL_PERSISTED_VARIABLES_TABLE VALUES
    (211,'LPV_ASB_PORT','9080',NULL,'false')
  5. If the port is incorrect, change the value to the port that is used.
  6. Save the vpd.script file.
  7. Restart the installation.
Patch installation fails with "Port number: is not properly formatted" error message
Operating system: All

When a response file was used with earlier versions of the IBM Information Server Suite Installer, several values were not correctly recorded in the vpd.script file. Incorrect values in the vpd.script file cause the patch installation to fail.

Workaround

Ensure that the required values are in the vpd.script file before installing the patch. To verify the values:
  1. In the vpd.script file, locate the following entry in the InstallShield Registry file where '/opt/IBM/InformationServer' is the installation location of the IBM Information Server version you are attempting to patch. The first numeric value after the opening parenthesis is the instance ID.
    INSERT INTO LOCAL_PERSISTED_VARIABLES_TABLE VALUES
    (99,'LPV_ROOT_INSTALL_DIR','/opt/IBM/InformationServer',NULL,'false')
  2. Edit the vpd.script file and search for the LPV_ASB_HOST and LPV_ASB_PORT values that have matching instance IDs.
  3. Verify that the values are correct. Add the following two entries to the end of the file if they do not exist:
    INSERT INTO LOCAL_PERSISTED_VARIABLES_TABLE VALUES
    (99,'LPV_ASB_HOST','hostname.domain.com',NULL,'false')
    INSERT INTO LOCAL_PERSISTED_VARIABLES_TABLE VALUES
    (99,'LPV_ASB_PORT','9080',NULL,'false')
  4. Change 99 to the instance ID that was determined in Step 1.
  5. Change 9080 to the correct port for the installation.
  6. Save the vpd.script file.
  7. Restart the installation.
Update Installer Launcher cannot find Java in the IBM Information Server installation directory
Operating system: All
On machines where only the domain layer is installed, the Update Installer Launcher might not be able to locate a Java JRE and fails with the following message:
  • Windows:
    Could not find a valid IBM Java virtual machine in any of
    the following places:
    c:\IBM\InformationServer\ASBNode\apps\jre\bin\java.exe
    c:\IBM\InformationServer\_jvm\jre\bin\java.exe
  • Linux, UNIX:
    Could not find a valid IBM Java virtual machine in any of
    the following places:
    /opt/IBM/InformationServer/ASBNode/apps/jre/bin/java.exe
    /opt/IBM/InformationServer/_jvm/jre/bin/java.exe
This error occurs when the original IBM Information Server installation of IBM Information Server detected and used a version of Java on the system. The Update Installer requires a version of Java from the IBM Information Server installation directory.

Workaround

Copy the Java JRE used by the WebSphere Application Server to the root directory of the IBM Information Server installation. The paths shown in the following commands assume that the product is installed in the default location. Your path varies if you installed IBM Information Server or WebSphere Application Server in a different location.
  • Windows:
    • Copy the contents of C:\IBM\WebSphere\AppServer\_jvm to C:\IBM\InformationServer\_jvm
  • Linux, UNIX:
    • Run the following command:
      cp -rf /opt/IBM/WebSphere/AppServer/java/jre /opt/IBM/InformationServer/_jvm
Patch installation fails when the installation is unable to stop the ASBAgent service
Operating system: Windows
During patch installation, the WebSphere Application Server and the IBM Information Server are automatically shut down and restarted. The patch installation fails when the ASBAgent service is not stopped in one of the following scenarios:
  • The installer fails to stop the ASBAgent service by using a net stop command. The following entry is found in the installation log file:
    WARNING: java.lang.Exception: Information Server cannot be shut down
    in a timely manner, please reboot windows and complete the rest
    of the installation.
  • The installer fails to stop the ASBAgent service after a shutdown request times out. The following entry is found in the installation log file:
    taskkill.exe -Unable to Locate Component Window appears with the message.
    This application failed to start because framedyn.dll was not found.
    Re-installing the application may fix the problem.
ISinstalltimestamp.txt log file locations:
  • Windows: C:\IBM\InformationServer\logs\ISinstalltimestamp.txt
  • Linux, UNIX: /opt/IBM/InformationServer/logs/ISinstalltimestamp.txt

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 fails on OutOfMemory exception in WebSphere Application Server
Operating system: All

Patch installation might fail if the maximum heap size is not sufficient for that system, resulting in an OutOfMemory exception in WebSphere Application Server. Some systems running WebSphere Application Server might require increasing the heap size in order to successfully install a patch. The default maximum heap size allocation of WebSphere Application Server process is automatically set to 768 MB during IBM Information Server installation.

Workaround

Set the maximum heap size property to 1280 MB before installing the patch.
Follow these steps 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 your 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 before you install the patch. Retain the renamed Version.xml file as a record of what patches were previously installed.
Patch installation might fail if you do not have 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.
Workaround
Log in as a user that is a member of the local administrators group and reinstall the patch.
Patch installation fails when NLS is enabled and locale is Spanish
Operating system: Solaris
Patches cannot be installed on Solaris systems when NLS is enabled and the locale is es_ES (or any other Spanish locales designated with es_). Installation fails with the error message:
A license file was not created.
Workaround
Install the patch after changing the system to use an English language locale, such as en_GB or en_US.
Successful patch installation has a SEVERE error in the installation log
Operating system: All
IBM Information Server installations that include WebSphere DataStage 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. You can ignore the error message.
Successful patch installation has a warning message in the log
Operating system: SUSE Linux Enterprise Server 10 on Intel x86
Successful patch installations might include the following warning message in the patch installation log file:
Error: cat: /scratch/Ascential/DataStage/DSEngine/.asbnode: No such file
or directory
This warning message is displayed in the following scenario:
  • DataStage engine with NLS disabled is upgraded from WebSphere DataStage 7.5.3 to WebSphere DataStage 8.0.1
  • Configuration includes a remote DB2 repository
  • ITAG with NLS enabled is installed on SUSE Linux Enterprise Server 10 on Intel x86 with the following DataStage Server values:
    • ITAG value not equal to the default ADE
    • Port number not equal to the default 31538
  • The selected product components to install are:
    • DataStage and QualityStage™
    • Information Analyzer
    • Business Glossary
Workaround
The patch installed successfully. You can ignore the error message.

IBM Information Server Version 8.0.1 known problems and workarounds

For information about the known problems and workarounds for the operation of IBM Information Server, go to http://publib.boulder.ibm.com/infocenter/iisinfsv/v8r0/topic/com.ibm.swg.im.iis.productization.iisinfsv.rnotes.kpw.doc/topics/knownprob.html.

Accessing information about IBM

IBM has several methods for you to learn about products and services.

You can find the latest information about IBM Information Server on the Web at http://www.ibm.com/software/data/integration/info_server/. To find your local IBM representative, go to the IBM Directory of Worldwide Contacts at http://www.ibm.com/planetwide.

Contacting IBM

You can contact IBM by telephone for customer support, software services, and general information.

Customer support

To contact IBM customer service for IBM Information Server in the United States or Canada, call 1-866-INFO-NOW (1-866-463-6669).

To find worldwide support contact information for IBM Information Server, see the eService Support Center Directory at https://www.ibm.com/software/data/support/iis/eservice/.

Software services

To learn about available service options, call one of the following numbers:
  • In the United States: 1-888-426-4343
  • In Canada: 1-800-465-9600

General information

To find general information in the United States, call 1-800-IBM-CALL (1-800-426-2255).

Go to http://www.ibm.com for a list of numbers outside of the United States.

Providing comments on the documentation

Please send any comments that you have about this information or other documentation.

Your feedback helps IBM to provide quality information. You can use any of the following methods to provide comments:
  • Send your comments using the online readers' comment form at http://www.ibm.com/software/data/rcf/.
  • Send your comments by e-mail to comments@us.ibm.com. Include the name of the product, the version number of the product, and the name and part number of the information (if applicable). If you are commenting on specific text, please include the location of the text (for example, a title, a table number, or a page number).

Notices and trademarks

Notices

IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to:

IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785 U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:

IBM World Trade Asia Corporation
Licensing 2-31 Roppongi 3-chome, Minato-ku
Tokyo 106-0032, Japan

The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:

IBM Corporation
J46A/G4
555 Bailey Avenue
San Jose, CA 95141-1003 U.S.A.

Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.

The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us.

Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only.

This information is for planning purposes only. The information herein is subject to change before the products described become available.

This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs.

Each copy or any portion of these sample programs or any derivative work, must include a copyright notice as follows:

© (your company name) (year). Portions of this code are derived from IBM Corp. Sample Programs. © Copyright IBM Corp. _enter the year or years_. All rights reserved.

If you are viewing this information softcopy, the photographs and color illustrations may not appear.

Trademarks

IBM, the IBM logo, and ibm.com® are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. These and other IBM trademarked terms are marked on their first occurrence in this information with the appropriate symbol (® or ™), indicating US registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be registered or common law trademarks in other countries. A complete and current list of IBM trademarks is available on the Web at www.ibm.com/legal/copytrade.shtml.

The following terms are trademarks or registered trademarks of other companies:

Intel is a registered trademark of Intel Corporation or its subsidiaries in the United States and other countries.

Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.

Microsoft, Windows, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Other company, product or service names may be trademarks or service marks of others.