IBM Support

IBM Smart Analytics System 7710 Fix Pack 2.1.3.0 readme document

Fix Readme


Abstract

Readme documentation for IBM Smart Analytics System 7710 Fix Pack 2.1.3.0 (also known as Fix Pack 3), including installation instructions and prerequisites.

Content

Readme file for: IBM® Smart Analytics System
Product/Component Release: 7710
Update Name: Fix Pack 2.1.3.0
Fix ID: 2.1.3.0-IM-ISAS7710
Publication date: 17 June 2014



IMPORTANT: If your IBM Smart Analytics System is configured with Lightweight Directory Access Protocol (LDAP), use the instructions in Installing IBM Smart Analytics System 7710 Fix Pack 2.1.3.0 on a system configured with LDAP to install Fix Pack 2.1.3.0 on your system.

Download location and fix pack contents

Download IBM Smart Analytics System 7710 Fix Pack 2.1.3.0 from Fix Central: http://www.ibm.com/support/fixcentral



To find IBM Smart Analytics System fix packs, select the Information Management product group and the IBM Smart Analytics System product.

Note: Only entitled customers for IBM Smart Analytics System 7710 can download Fix Pack 2.1.3.0 from Fix Central. For more information, refer to step one in the Troubleshooting section.

Fix Pack 2.1.3.0 contains the following updates:

Operating System stack:
  • IBM AIX 6.1 TL8 SP2 (6100-08-02-1316) + APAR IV46910
  • IBM General Parallel File System 3.5.0.7
  • IBM Reliable Scalable Cluster Technology (RSCT) 3.1.5.2
  • IBM Systems Director Platform Control for Power 3.0.3.0
  • IBM Systems Director 6.3.2.1
  • OpenSSH 6.0.0.6101
  • OpenSSL 0.9.8.2500

Enterprise Software stack:
  • IBM DB2® Enterprise Server Edition (ESE) for Linux, UNIX, and Windows 9.7 FP9a
  • IBM InfoSphere Optim Performance Manager Extended Edition for Linux, UNIX and Windows Version 5.2 interim fix 6242
  • IBM InfoSphere Warehouse 9.7.7
  • IBM Tivoli® Systems Automation for Multiplatforms (Tivoli SA MP) 3.2.2.7
  • IBM Smart Analytics System Control Console 2.1.3.0

Other software:
  • IBM DS Storage Manager 10.84

Firmware:
  • Power 740 firmware AL740_100
  • DS3500 storage controller firmware 7.84.46.00
  • IBM DS3K HDD firmware package 4.12
  • HMC firmware V7 R7.7.0 with SP2 (7.7.7.0.2) + fix MH01425
  • Dual-port 8 Gb Fibre Channel PCIe adapter (FC 5735/5273) 202307
  • Juniper switch firmware 12.3 R3.4



Back to top

Prerequisites and co-requisites


Before you install Fix Pack 2.1.3.0, verify that each of the file systems has a sufficient amount of free space to install the fix pack. The following information describes the required amount of free space needed for each file system:

Core warehouse nodes (data, administration, and optional standby node)
  • /usr: 5 GB
  • /tmp: 5 GB
  • /var: 5 GB
  • /opt: 500 MB
  • /db2home: 5 GB (administration node only)

Management node
  • /usr: 10 GB
  • /tmp: 5 GB
  • /var: 5 GB
  • /opt: 15 GB
  • /BCU_share: 60 GB
Check the amount of free space in a file system by issuing the following command:
df -g <filesystem>

where <filesystem> is the path of the file system you are checking.

Use the chfs -a command to increase the size of a file system. The following command is an example, which allocates an additional 2 GB of space to the /BCU_share directory:
chfs -a size=+2G /BCU_share



Back to top

Installation overview

Install Fix Pack 2.1.3.0 on your system using the IBM Smart Analytics System Control Console software. The fix pack is installed on the management node and the core warehouse nodes (administration, data, and optional standby node).



To install the fix pack on the system, issue the miupdate command with the -u option to run the update process as an interactive session. The fix pack is installed on your system in the following stages: preview, management, prepare, apply, and commit. After each stage completes successfully, you are prompted to continue to the next stage.

All of the stages in the fix pack installation can be performed while the system is online, except for the apply stage. To reduce the amount of time your system is offline, run the preview, management, and prepare stages before all before your scheduled outage window.

Some of the fix pack installation stages can take a long time. To view additional details while the miupdate command is running, see the log file /var/aixappl/pflayer/log/platform_layer.log.

For more information about the fix pack installation process, see the IBM Smart Analytics System 7710 User Guide.


Back to top

Prior to installing

Perform the following steps before you install Fix Pack 2.1.3.0.



1. Download Fix Pack 2.1.3.0 from Fix Central to the management node. The fix pack contains the 2.1.3.0-IM-ISAS7710.tar file. The fix pack file can be placed in any directory that has sufficient space but it is recommended that you place it in the /backups directory on the management node. This can help reduce the the time needed to run the prepare stage of the installation. The directory where you add the fix pack can be located on either the internal storage on the management node or external storage that is visible to the management node.


2. Verify that all hardware devices are online and running correctly. You must check all servers for active hardware events and resolve all reported hardware issues before you install the fix pack. You can also use the ping command to check for connectivity between all IP addresses.


3. Verify that all Tivoli SA MP resources are online and that resource groups function correctly.

a. If you have high availability (HA) configured, log in to the management node as the root user and issue the hals command to verify that all Tivoli SA MP resources in the core warehouse are online on the appropriate node. All resources should be online on the primary node.

Optionally, you can verify that the Tivoli SA MP resource groups function correctly by stopping and starting the resource groups. This step requires an outage of the system. See Chapter 5, Startup and shutdown procedures in the IBM Smart Analytics System 7700 User Guide for the appropriate commands.

b. After you have verified that Tivoli SA MP resources in the core warehouse nodes, the warehouse applications nodes, and the warehouse OLAP nodes are online, issue the following command to backup the domain configurations:

dsh -n $BCUALL "/usr/sbin/rsct/bin/ctbackup " > dsh_ct_backup_$(date +%s)


4. If you have changed the passwords for the root user, HMCs, Ethernet network switches, or DS3500 storage controllers without using IBM Smart Analytics System Control Console, you must change these passwords before you update your system. To change the password using these steps, you are prompted to enter the current password for each server and hardware device in the system. If you do not know the current password, contact IBM Support. The new passwords you provide should comply with your corporate security policies.

For each server, HMC, Ethernet network switch, and DS3500 storage controller where the password was changed without using the control console, issue the following command as root on the management node to change the password:
miauth -pw -h <hostname> -u <username>

where <hostname> represents the server host name or the device name and <username> represents the name of the administrative user. You can use the miinfo -d command to list all of the server and device host names in your system.

The administrative user names are as follows:
  • User on all servers: root
  • User on all HMCs: hscroot
  • User on all Ethernet network switches: admin
  • For the storage controllers, you do not need to specify the -u option.


5. Verify that the locale is set to US English during the fix pack update. On each node, log in as root and perform the following steps.

a. Issue the following command to determine if the LANG environment variable is set to en_US:
echo $LANG

If the command returns the value en_US, the environment variable is set correctly and you can skip step 5b.

b. If the LANG environment variable is not set to the en_US value, add the following line to the /.profile file:
export LANG=en_US

Save your changes and issue the export LANG=en_US command to set the value.


6. Create a file to store the root user password for each of the Juniper switches in your system.

a. Log in to the management node as the root user and create a file called isas_passwd in the /tmp directory.

b. For the Juniper passwords, add the following information:
juniper.<IP>=<password>

where <IP> is the IP address of a Juniper switch and <password> is the root user password for a Juniper switch. You must add an entry for each of the Juniper switches in your system.

c. Set the permission level on the password file by issuing the following command:
chmod go= /tmp/isas_passwd


7. The password for the ftp user on the management node cannot contain the @ character. Use the following steps if you need to change the password.

a. Issue the following command as the root user on the management node:
passwd ftp

b. After you change the password for the ftp user, log in to the management node as the ftp user to verify that the password change was successful.

c. Update the password for the ftp user in Systems Director.

i. Log in to the Systems Director console as the root user:
https://<management_node>:8422/ibm/console/logon.jsp

where <management_node> represents the host name of the management node.

If a certificate error is displayed in the browser, you can safely ignore the warning and continue.

ii. In the left navigation, click Release Management > Updates

iii. In the Updates tab, click Settings.

iv. Click the BladeCenter tab. In the FTP server credentials area, enter the password from step 7b in the password field.


8. Update the RSM for Storage software to version 2.8.4. You must install the software manually. For more information about this update, see the RSM for Storage page in Fix Central.

Note: The RSM for Storage update is required for compatibility with the DS3500 controller firmware update installed in the fix pack.


9. Before you install the fix pack, run the preview stage to identify and resolve issues that can prevent a successful fix pack installation. You can run the preview stage multiple times to verify that issues in the system are resolved.

a. Issue the following command to enable FTP on the management node:
startsrc -t ftp

b. Run the preview stage command:
miupdate -u preview -s <update_directory>/2.1.3.0-IM-ISAS7710.tar

where <update_directory> represents the directory that contains the fix pack file.

Restriction: After you issue the miupdate command, do not change any passwords on the system until the commit stage of the fix pack installation is complete. If you need to change a password during a fix pack installation, use the miauth command and ensure that the current stage of the fix pack installation is stopped or completed.



Back to top


Installing


IMPORTANT: If your IBM Smart Analytics System is configured with LDAP, use the instructions in Installing IBM Smart Analytics System 7710 Fix Pack 2.1.3.0 on a system configured with LDAP to install Fix Pack 2.1.3.0 on your system. Do not use the instructions in this section of the document to install the fix pack.

The fix pack contains fixes that are installed on all of the nodes. When the fix pack is installed using the miupdate command, the process requires an outage of the system.

Perform the following steps as the root user.

1. Enable FTP on the management node. Issue the following command on the management node:
startsrc -t ftp


2. Log in to the management node and issue the following command to run the update process as an interactive session:
miupdate -u preview -s <update_directory>/2.1.3.0-IM-ISAS7710.tar

where <update_directory> represents the directory that contains the fix pack file.

The miupdate command runs as an interactive session, and you are prompted to continue after each stage of the fix pack installation is completed.


3. During the management stage, the management node is rebooted and the installation is paused. To resume the fix pack installation, issue the following command after the management node reboots:
miupdate -resume


4. Optional: After the apply stage, stop the interactive session if it is still running and test the functioning of your system.


5. Continue with the interactive session to the commit stage to commit the updates. If you stopped the interactive session, issue the miupdate -u command again to continue to the commit stage.

If you encounter an error during the fix pack installation, do not continue to the next stage when prompted. Contact IBM Support to troubleshoot the fix pack installation on your system.


Back to top

Performing the necessary tasks after installing

1. Verify that the fix pack updates have been installed on your system using the miinfo -d -c command.




2. Log in to the management node as the root user and verify the passwordless SSH connectivity to each HMC in the system.

a. Issue the following command to view the host name for each switch in the system:
cat /etc/hosts | grep hmc

The following sample output is displayed:
172.n.n.n   hmc_hostname

where hmc_hostname is the host name of the HMC.

b. Using a host name listed in the output, issue the following command to log in to a switch using passwordless SSH:
ssh hscroot@<hmc_hostname>

where <hmc_hostname> is the host name of the HMC. If the following message is displayed, enter yes to proceed:
The authenticity of host 'hmc_hostname (172.n.n.n)' can't be established.
RSA key fingerprint is nn.nn.nn.nn.nn.nn.nn.nn.nn.nn.nn.nn.nn.nn.nn.nn
Are you sure you want to continue connecting (yes/no)?

c. Repeat step 2b for each HMC in the system.


3. If you have high HA configured for your system, verify that all Tivoli SA MP resources are online and that resource groups function correctly. Log in to the administration node as the root user and issue the hals command to verify that all Tivoli SA MP resources in the core warehouse are online on the appropriate node. All resources should be online on the primary node.


4. Update the HA configuration for the core warehouse.

a. Log in to the management node as root user.

b. Issue the following command to back up the current HA configuration:
hareset -backup

c. Issue the following command to update the HA configuration:
hachkconfig -repair


5. This step must be run on the administration node as the core warehouse instance owner (bcuaix) or another database user that has rebind privileges on the database. Manually rebind all of the DB2 packages on the core warehouse database. After you install a fix pack, some packages are marked as invalid. Packages marked as invalid are implicitly rebound the first time an application uses them. To eliminate this overhead and to ensure that the rebind is successful, manually rebind all of the packages by running the following command:

db2rbind dbname -l logfile_name all

where dbname represents the name of the core warehouse database, and where logfile_namerepresents the log file to be used for recording any errors during the package revalidation procedure. An example of a time stamped log file name that you can specify is db2rbind_$(date +%s).log.


6. Verify that your applications run correctly on the system after the fix pack installation is complete.


7. Delete the isas_passwd file in the /tmp directory on the management node that contains the Juniper switch root user passwords.


8. Disable FTP on the management node by issuing the following command as root on the management node:
stopsrc -t ftp


9. If the US English locale setting is not appropriate for your environment, log in to each node as the root user and comment out the export LANG=en_US line in the /.profile file. You can set the LANG environment variable to a value that is appropriate for your system.

10. Review Known issues for the IBM Smart Analytics System 7710 for additional issues.

Back to top

Troubleshooting

1. If you get an an authorization error when you attempt to download the fix pack, ask your Passport Advantage site technical contact to add the appropriate entitlement to your account. For additional help, contact your Accelerated Value Program representative or IBM Support.




2. After the SSH keys are updated, if you see a warning message that the remote host identification has changed when you log in to a node through the corporate network, update the known_hosts file on the node. Issue the following command as the root on the node, where <IP_address> represents the corporate IP address of the node:
ssh-keygen -R <IP_address>

The known_hosts file contains information about each host, including the host name, IP address, and alias over each of the network interfaces. Use the following command to compare each entry in the file with the valid public host key that is retrieved from a host:
ssh-keygen -F <IP_address>
ssh-keyscan <IP_address>

If the host key does not match the entry in known_hosts, then remove it. After you remove the entry, you can use the following command to add a valid entry:
ssh-keyscan <IP_address> >> ~/.ssh/known_hosts

The ssh-keyscan command can be used with a list of hosts.

By default, SSH is configured to use RSA keys.


3. After you update the known_hosts file using the ssh-keygen command, verify that you can access the node using the ssh command. If you see the following prompt, enter yes to accept the new key:
The authenticity of host 'hostname (172.n.n.n)' can't be established.
RSA key fingerprint is nn.nn.nn.nn.nn.nn.nn.nn.nn.nn.nn.nn.nn.nn.nn.nn
Are you sure you want to continue connecting (yes/no)?

If there are a large numbers of hosts, you can use the ssh-keyscan command with the list of hosts.


4. If you encounter an error during the fix pack installation, do not continue to the next stage when prompted. Contact IBM Support to troubleshoot the fix pack installation on your IBM Smart Analytics System.

Back to top

Command output: miupdate


Preview stage output:



========================
Previewing fixpack:
========================

========================
Summary of Updates:
========================
IBM Smart Analytics System Solution Update

Existing Version: 2.1.0.0
Update Version: 2.1.3.0

[Management]
Management IBM Smart Analytics System: 2.1.0.0->2.1.3.0
Management Optim Performance Manager: 5.1.0.0.3624->5.2.0.0.6242
Management DB2 Enterprise Server Edition: 9.7.0.4..1->9.7.0.8..0
Management Storage Manager: 10.77.6514.0->10.84.6530.0
Management IBM AIX: 6100-06-04-1112->6100-08-02-1316
Management HA_DB2: Not Available->1.0.0.2
Management IBM Systems Director Server: 6.2.1.2->6.3.2.1
Management IBM Smart Analytics System Control Console: 2.1.0.0->2.1.3.0
Management IBM Systems Director Platform Control: 3.0.0.0->3.0.3.0
Management Platform Management: 3.0.2.0->3.0.3.0
Management Power 740 firmware: AL740_043->AL740_100
Management Hardware Management Console firmware: 7.7.4.0.0->7.7.6.0.2

[Core Warehouse]
Data Tivoli SAMP: 3.2.1.3->3.2.2.7
Data DB2 Enterprise Server Edition: 9.7.0.4..1->9.7.0.8..0
Data IBM AIX: 6100-06-04-1112->6100-08-02-1316
Data SMI-S Eagle Provider: 10.10.55.0->10.27.5.0
Data HA_DB2: Not Available->1.0.0.2
Data InfoSphere Warehouse: 9.7.2.20110507_9.7.0.4..1->9.7.7.20121015
Data IBM Systems Director Common Agent: 6.2.1.1->6.3.0.0
Data GPFS: 3.4.0.6->3.5.0.7
Data Power 740 firmware: AL740_043->AL740_100
Data Fibre Channel Adapter (FC5735/5273) firmware: 111304->202307

[Infrastructure]
Infrastructure DS3500 firmware: 07.77.20.00->07.84.46.00
Infrastructure Juniper Switch firmware: 11.1S1.0->12.3R3.4 

========================
Verifying update requirements
========================

[Management]
Management IBM Smart Analytics System: Validated Successfully
Management IBM Systems Director Platform Control: Validated Successfully
Management Platform Management: Validated Successfully
Management IBM Systems Director Server: Validated Successfully
Management Hardware Management Console firmware: Validated Successfully
Management Power 740 firmware: Validated Successfully
Management IBM AIX: Validated Successfully
Management Storage Manager: Validated Successfully
Management DB2 Enterprise Server Edition: Validated Successfully
Management OPM: Validated Successfully
Management IBM Smart Analytics System Control Console: Validated Successfully

[Core Warehouse]
Data IBM AIX: Validated Successfully
Data SMI-S Eagle Provider: Validated Successfully
Data GPFS: Validated Successfully
Data Tivoli SAMP: Validated Successfully
Data DB2 Enterprise Server Edition: Validated Successfully
Data InfoSphere Warehouse: Validated Successfully

[Infrastructure]
Infrastructure Juniper Switch firmware: Validated Successfully
Infrastructure DS3500 firmware: Validated Successfully

========================
The preview operation has completed successfully.
========================

Management stage output:



You must update the Management Service before updating the rest of the system. During this period the Management Services will not be available. The Core Warehouse or other services will not be affected by this operation.

During this update the Management Server will reboot.  Once the system has rebooted you need to issue "miupdate -resume" to complete the update process.

Do you want to proceed to update the management services? (Yes/No)?
Yes

Log file: /var/aixappl/pflayer/log/platform_layer.log
Preparing management system:
    Preparing DB2 Enterprise Server Edition update : 0 of 4 task completed
    Preparing DB2 Enterprise Server Edition update : 0 of 4 task completed
    ... <omitted lines> ...
Preparing DB2 Enterprise Server Edition update : 4 of 4 task completed

Log file: /var/aixappl/pflayer/log/platform_layer.log
Applying non-impact updates to management services:

Log file: /var/aixappl/pflayer/log/platform_layer.log
Applying disruptive updates to management services:
    Applying IBM AIX update : 0 of 2 task completed
    Applying DB2 Enterprise Server Edition update : 0 of 4 task completed
    Applying IBM AIX update : 0 of 2 task completed
    Applying DB2 Enterprise Server Edition update : 0 of 4 task completed

The system is now rebooting. Issue miupdate -resume to continue the operation after the reboot completes.

miupdate -resume
Are you sure you want to perform the "resume" operation? (Yes/No)?
Yes

Resuming updates:
Applying disruptive updates to management services:
Log file: /var/aixappl/pflayer/log/platform_layer.log
Applying disruptive updates to management services:
    Applying IBM AIX update : 1 of 2 task completed
    Applying IBM Systems Director Server update : 5 of 5 task completed
    Applying Hardware Management Console firmware update : 1 of 1 task completed
    ...  <omitted lines> ...
Applying OPM update : 5 of 5 task completed

========================
The Management node update operation has completed successfully.
========================

Prepare stage output:



During the Prepare stage, the system is prepared for an update and system services are available. Optionally, you can apply non-disruptive updates to the system in this stage.

Do you want to prepare the system for an update? (Yes/No)?
Yes

Log file: /var/aixappl/pflayer/log/platform_layer.log
Preparing system:

    Log file:
    Core Warehouse Data DB2 Enterprise Server Edition: DB2 prepare started 0 of 4 task completed

    Log file:
    Core Warehouse Data DB2 Enterprise Server Edition: DB2 prepare started 1 of 4 task completed
...  <omitted lines> ...

When non-disruptive updates are applied to the system, some software and firmware levels are updated but system services are not disrupted.

Log file: /var/aixappl/pflayer/log/platform_layer.log
Applying non-disruptive updates to system:
    apply non-disruptive update step completed

========================
The prepare operation has completed successfully.
========================

Apply stage output:



The Apply stage applies disruptive updates to the system. All system nodes and system services (except the management node and Management services) are taken offline.  Non-disruptive updates are also applied to the system in this stage if they were not applied in the Prepare stage. After this stage completes, system services run on the new software and firmware levels without internal disk mirroring enabled.

Do you want to stop all services and apply updates to the system? (Yes/No)?
Yes

Log file:
    Core Warehouse Data IBM AIX: AIX apply started 0 of 3 task completed

    Log file:
    Core Warehouse Data IBM AIX: AIX apply started 0 of 3 task completed

    ...  <omitted lines> ...

Log file:
    Core Warehouse Data DB2 Enterprise Server Edition: DB2 apply started 4 of 4 task completed

Log file:
    Infrastructure Infrastructure Juniper Switch firmware: NetFW apply started 1 of 1 task completed

    Log file:
    Infrastructure Infrastructure DS3500 firmware: StorageFW apply started 1 of 1 task completed

========================
The apply operation has completed successfully.
========================

Commit stage output:



To stop the interactive session to test the functioning of your system, enter "No" when you are prompted to commit the updates. After you have finished your testing, use the miupdate -u command to resume the interactive session.

The Commit stage commits the current update and enables internal disk mirroring. After the current update is committed, the system cannot be rolled back to the previous state.

Do you want to commit the current update? (Yes/No)?
Yes

Log file:
    Management Management DB2 Enterprise Server Edition: DB2 commit started 0 of 1 task completed

    Log file:
    Management Management DB2 Enterprise Server Edition: DB2 commit started 1 of 1 task completed

    Log file:
    Core Warehouse Data DB2 Enterprise Server Edition: DB2 commit started 0 of 1 task completed

...  <omitted lines> ...

 Log file:
    Management Management DB2 Enterprise Server Edition: DB2 commit started 1 of 1 task completed

    Log file:
    Core Warehouse Data DB2 Enterprise Server Edition: DB2 commit started 1 of 1 task completed

========================
The commit operation has completed successfully.
========================
Internal disk mirroring is enabled and the system cannot be rolled back to a previous state.

Back to top

Copyright and trademark information



Notices
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 jurisdictions 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.

Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.
Microsoft, Windows, Windows NT, 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.

Third-party license terms and conditions, notices and information
The license agreement for this product refers you to this file for details concerning terms and conditions applicable to third party software code included in this product, and for certain notices and other information IBM must provide to you under its license to certain software code. The relevant terms and conditions, notices and other information are provided or referenced below. Please note that any non-English version of the licenses below is unofficial and is provided to you for your convenience only. The English version of the licenses below, provided as part of the English version of this file, is the official version.

Notwithstanding the terms and conditions of any other agreement you may have with IBM or any of its related or affiliated entities (collectively "IBM"), the third party software code identified below are "Excluded Components" and are subject to the following terms and conditions:
  • the Excluded Components are provided on an "AS IS" basis
  • IBM DISCLAIMS ANY AND ALL EXPRESS AND IMPLIED WARRANTIES AND CONDITIONS WITH RESPECT TO THE EXCLUDED COMPONENTS, INCLUDING, BUT NOT LIMITED TO, THE WARRANTY OF NON-INFRINGEMENT OR INTERFERENCE AND THE IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
  • IBM will not be liable to you or indemnify you for any claims related to the Excluded Components
  • IBM will not be liable for any direct, indirect, incidental, special, exemplary, punitive or consequential damages with respect to the Excluded Components.


Back to top

Document change history

[{"Product":{"code":"SSKT3D","label":"IBM Smart Analytics System"},"Business Unit":{"code":"BU050","label":"BU NOT IDENTIFIED"},"Component":"IBM Smart Analytics System 7710","Platform":[{"code":"PF002","label":"AIX"}],"Version":"9.7","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
16 June 2018

UID

swg21654973

Page Feedback