IBM Support

IBM Smart Analytics System 7700 Fix Pack 2.1.2.0 readme document

Fix Readme


Abstract

Readme documentation for IBM Smart Analytics System 7700 Fix Pack 2.1.2.0 (also known as Fix Pack 6), including installation instructions, prerequisites, and a list of fixes.

Content

Readme document for: IBM® Smart Analytics System
Product/Component Release: 7700
Update Name: Fix Pack 2.1.2.0
Fix ID: 2.1.2.0-IM-ISAS7700
Publication date: 13 June 2013


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


Download location and fix pack contents

Download IBM Smart Analytics System 7700 Fix Pack 2.1.2.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 7700 can download Fix Pack 2.1.2.0 from Fix Central. For more information, refer to step one in the Troubleshooting section.

Fix Pack 2.1.2.0 contains the following updates:

Operating System stack:
  • IBM AIX 6.1 TL8 SP2 (6100-08-02-1316)
  • IBM General Parallel File System 3.5.0.7
  • IBM Reliable Scalable Cluster Technology (RSCT) 3.1.4.4
  • IBM Systems Director Platform Control for Power 3.0.2.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 Fix Pack 8 special build 30703
  • 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.4
  • IBM Smart Analytics System Control Console 2.1.2.0
  • IBM WebSphere® Application Server 7.0.0.27

Other software:
  • IBM DS Storage Manager 10.84

Firmware:
  • Power 740 firmware AL730_099
  • DS3500 storage controller firmware 7.84.46.00
  • IBM DS3K HDD firmware package 4.12
  • HMC firmware V7 R7.6.0 with SP2 (7.7.6.0.2) + fix MH01353
  • 10Gb Fibre Ethernet adapter (FC 5708) firmware 020111
  • Dual-port 8 Gb Fibre Channel PCIe adapter (FC 5735/5273) 202307
  • SSD RAID Card adapter (CCIN 57CD) firmware 422003a
  • SSD drive firmware 304E3646
  • SAN40-B switch firmware 7.0.2.a
  • Juniper switch firmware 12.3 R1.7

If you are installing the fix pack over a version earlier than 2.1.1.0, the Fix Pack 2.1.2.0 installation migrates existing data from DB2 Performance Expert to InfoSphere Optim Performance Manager Extended Edition for DB2, Linux, and Windows. After the migration process is completed, DB2 Performance Expert is removed from your system.

Back to top

Prerequisites and co-requisites

Before you start the fix pack installation, check the following information on your system:



1. Confirm that you have Fix Pack 2.0.0.100 or later installed.

See the Related Information section for a link to the Fix Pack 2.0.0.100 readme document.


2. 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 (all data, administration, and standby nodes)
  • /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

Warehouse applications module (all nodes)
  • /usr: 5 GB
  • /tmp: 5 GB
  • /var: 500 MB
  • /opt: 500 MB
  • /iswhome: 5 GB
  • /usr/IBM/dwe/appserver_001: 500 MB (warehouse applications node only)
  • /usr/IBM/dwe/appserver_002: 500 MB (warehouse OLAP node only)
a. 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.

b. 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.2.0 on your system using the IBM Smart Analytics System Control Console software. The fix pack is installed on the management node, the core warehouse nodes (all administration, data, and standby nodes), and the warehouse applications nodes.



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.

The software updates made to your system are not committed until the commit stage completes. As long as you have not started the commit stage, you can roll back the software updates made to your system using the procedure in the Uninstalling if necessary section. Firmware updates cannot be uninstalled.

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 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 and the rollback option, see the IBM Smart Analytics System 7700 User Guide.


Back to top

Prior to installing

Perform the following steps before you install Fix Pack 2.1.2.0.



1. Download Fix Pack 2.1.2.0 from Fix Central to the management node. The fix pack contains the 2.1.2.0-IM-ISAS7700.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 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 high availability (HA) is configured for the core warehouse, 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.

b. Log in to the warehouse applications node as the root user and issue the lssam command to verify that all Tivoli SA MP resources in the warehouse applications module are online on the appropriate node. All resources that contain db2_instancename or type1 in the name should be online on the warehouse applications node. If your system includes the warehouse OLAP node, all resources that contain type2 in the name should be online on the warehouse OLAP node.

c. Optional: 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.


4. If you have changed the passwords for the root user, HMCs, SAN switches, 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, SAN switch, Ethernet network switch, and DS3500 storage controller where the password was changed without using the control console, issue the following command as the root user 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 SAN switches: admin
  • User on all Ethernet network switches: admin
  • For the storage controllers, you do not need to specify the -u option.


5. If you have changed the passwords for the InfoSphere Warehouse administrative user (called dweadmin by default) or the WebSphere administrative user (called wasadmin by default) without using the procedure described in the IBM Smart Analytics System 7700 User Guide, you must change the passwords using the documented procedures. If you do not do so, the updates to the warehouse applications module will fail. First change the password for the WebSphere administrative user using the procedure described in Changing the WebSphere administrative user's password, and then change the password for the InfoSphere Warehouse administrative user using the procedure described in Changing the InfoSphere Warehouse metadata instance owner and database administrator user's password.


6. Verify that the passwords for the InfoSphere Warehouse administrative user (dweadmin) and the WebSphere administrative user (wasadmin) are not expired. Log in to the management node as a non-root user, and then log in as the InfoSphere Warehouse administrative user or the WebSphere administrative user using the su - <username> command, where <username> represents the InfoSphere Warehouse administrative user or the WebSphere administrative user. The output of the command indicates if the password is expired.


7. Verify that the locale is set to US English during the fix pack update. On each node, log in as the root user 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 7b.

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.


8. Create a file to store the root user password for each of the Juniper switches in your system. If you are installing Fix Pack 2.1.2.0 from a version earlier than 2.1.1.0, you also must use this file to store the password for the DB2 Performance Expert user. The sample name for the DB2 Performance Expert user is bcupe.

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. Add the following entry to the file, only if you are installing from a version earlier than 2.1.1.0:
mgmt.pe_instance=<password>

where <password> is the password for the DB2 Performance Expert user. The passwords should not start or end with white space. Blank lines and lines starting with the hash character (#) are also ignored.

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


9. 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, and enter the password from step 9b in the password field.


10. 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.


11. 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.2.0-IM-ISAS7700.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 7700 Fix Pack 2.1.2.0 on a system configured with LDAP to install Fix Pack 2.1.2.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 install the fix pack in an interactive session:
miupdate -u preview -s <update_directory>/2.1.2.0-IM-ISAS7700.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 will reboot twice. To resume the fix pack update after each reboot, you must first check that Systems Director is running and then resume the update. Note that Systems Director takes approximately 20 minutes to restart.

a. After the management node reboots for the first time, complete the following steps:

i. Check that Systems Director is running by issuing the following command on the management node:
smstatus

To proceed to the next step, the output of the smstatus command must display Active.

ii. If the output displays Inactive, manually start Systems Director by issuing the following command:
smstart

iii. Once you have verified that Systems Director is running, resume the fix pack installation by issuing the following command:
miupdate -resume

b. After the second management node reboot, complete the following steps:

i. Check that Systems Director is running by issuing the following command on the management node:
smstatus

To proceed to the next step, the output of the smstatus command must display Active.

ii. If the output displays Inactive, manually start Systems Director by issuing the following command:
smstart

iii. Once you have verified that Systems Director is running, resume the fix pack installation by issuing the following command:
miupdate -resume


4. IMPORTANT: If you are installing Fix Pack 2.1.2.0 (Fix Pack 6) without first installing Fix Pack 2.1.1.0 (Fix Pack 5), stop the interactive session after the apply stage and install the Tivoli SA MP 3.2 license manually. Use the instructions in the following document: IBM Smart Analytics System 7700 Fix pack 2.1.2.0 (Fix Pack 6) does not apply the license for IBM Tivoli SA MP 3.2.


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


6. 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 do not want to commit the updates, follow the instructions in the Uninstalling if necessary section to roll back the software updates on your system.


7. Immediately after the commit stage completes, use the following steps to commit the Tivoli SA MP update.

a. Log in to the administration node as the root user and issue the following command:
lssrc -ls IBM.RecoveryRM

Verify that the Our AVN field displays version 3.2.2.4.

b. If the version displayed is 3.2.2.4, no further action is required. If the version displayed is not 3.2.2.4, use the following steps to commit the Tivoli SA MP update.

i. Issue the following command:
samctrl -m

ii. When the following message is displayed, enter Y to accept:
Ready to Migrate! Are you Sure? [Y|N]:

iii. Issue the lssamctrl command again to verify that the Our AVN field displays version 3.2.2.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 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 SAN switch and network switch in the system.

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

The following sample output is displayed:
172.n.n.n   san_switch1
172.n.n.n   san_switch2
172.n.n.n   mgt_switch1
172.n.n.n   fcm_switch1
172.n.n.n   fcm_switch2

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

where <switch_hostname> is the host name of a switch. If the following message is displayed, enter yes to proceed:
The authenticity of host 'san_switch1 (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 SAN switch and network switch in the system.


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

a. If HA is configured for the core warehouse, 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.

b. Log in to the warehouse applications node as the root user and issue the lssam command to verify that all Tivoli SA MP resources in the warehouse applications module are online on the appropriate node. All resources that contain db2_instancename% or type1 in the name should be online on the warehouse applications node. If your system includes the warehouse OLAP node, all resources that contain type2 in the name should be online on the warehouse OLAP node.


4. Update the HA configuration for the core warehouse. IMPORTANT: If you installed Fix Pack 2.1.2.0 without first installing Fix Pack 2.1.1.0, verify that you applied the Tivoli SA MP 3.2 license in step 4 in the Installing section before you run the following HA commands.

a. Log in to the management node as the 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 file isas_passwd in the /tmp directory on the management node that contains the Juniper switch root user passwords. If you are installing Fix Pack 2.1.2.0 from a version earlier than 2.1.1.0, this step also removes the password for the DB2 Performance Expert user.


8. Disable FTP on the management node by issuing the following command as the root user 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 7700 for additional issues.

Back to top

Troubleshooting

1. If you get 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 user on the node, where <IP_address> represents the corporate IP address of the node:
ssh-keygen -R <IP_address>


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 'myhost (1.2.3.4)' can't be established.
RSA key fingerprint is xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx.
Are you sure you want to continue connecting (yes/no)?


4. During the fix pack update, an error might appear that indicates that the firmware update on a storage device failed, and might cause the fix pack installation to pause. If this issue occurs, the output will display as follows:

The operation has failed during apply. Storage Firmware update failed on 172.x.x.x-172.x.x.x. Refer to the platform layer log file for details.

To resolve the issue, complete the following steps:

a. Issue the following command on the management node to determine which storage devices are problematic:
SMcli -d -v -i

The output will display all of the storage devices in the system.

DS3500_1  172.x.x.x    Needs Attention
DS3500_2  172.x.x.x    Optimal
DS3500_3  172.x.x.x    Optimal
DS3500_4  172.x.x.x    Optimal
DS3500_5  172.x.x.x    Optimal

SMcli completed successfully.

b. If a storage device output displays a status of Needs Attention instead of Optimal, you must determine the nature of the issue.

i. Issue the following command:
SMcli <IP_address>  -c "show storageSubsystem healthStatus;"

where <IP_address> is the IP address for the storage device that did not display in an Optimal state. The following sample output is displayed:

Performing syntax check...
Syntax check complete.
Executing script...

The controller clocks in the storage subsystem are out of synchronization with the storage management station.

Controller in Slot A: Thu Jun 13 06:25:14 EDT 2013
Controller in Slot B: Thu Jun 13 06:25:14 EDT 2013
Storage Management Station: Thu Jun 13 07:04:20 EDT 2013

The following failures have been found:
Logical Drive Not On Preferred Path
Storage Subsystem: BWDS3500-4
Preferred owner: Controller in slot B
Current owner: Controller in slot A
Affected array: ARRAY2
  Logical Drive: LUN3_2428_ADM_STAGE, LUN4_300_ADM_DB2HOME, LUN5_10_ADM_HOME

Script execution complete.
SMcli completed successfully.

ii. Check the output of the script for the following information:
Logical Drive Not On Preferred Path

iii. If you do not see this output appear, you must log in to DS Storage Manager to resolve the issue. If the above output does appear, proceed with the following steps.

iv. Issue the following command:
SMcli <IP_address> -c "reset storageSubsystem logicalDriveDistribution;" -p '<storage_password>'

where <IP_address> is the IP address for the storage device you want to fix and <storage_password> is the password for the same storage device. The following output will be displayed:

Syntax check complete.
Executing script...
Script execution complete.
SMcli completed successfully.

c. After the issue is resolved, issue the SMcli -d -v -i command to verify that all of the storage devices display as "Optimal".

d. Resume the fix pack update by issuing the following command:
miupdate -resume


5. 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

Uninstalling if necessary

As long as the update process has not started the commit stage, you can roll back the software updates made to your system using the miupdate --rollback command. When a fix pack contains firmware updates, the firmware updates cannot be reverted. See the IBM Smart Analytics System 7700 User Guide for additional details.




Back to top

Command output: miupdate


Preview stage output:



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

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

Existing Version: 2.0.0.100
Update Version: 2.1.2.0

[Management]
Management IBM Smart Analytics System: 2.0.0.100->2.1.2.0
Management IBM AIX: 6100-06-01-1043->6100-08-02-1316
Management Hardware Management Console firmware: 7.7.2.0.2->7.7.6.0.2
Management Power 740 firmware: AL720_090->AL730_99
Management WebSphere Application Server: 7.0.0.15->0.0.0.0
Management Optim Performance Manager: Not Available->5.2.0.0.6242
Management IBM Smart Analytics System Control Console: 2.1.0.0->2.1.2.0
Management HA_DB2: Not Available->1.0.0.1
Management IBM Systems Director Platform Control: 2.0.1.0->3.0.2.0
Management 10Gb Fibre Ethernet Adapter (FC5708) firmware: 010522->020111
Management IBM Systems Director Server: 6.2.0.1->6.3.2.1
Management Platform Management: 2.0.1.0->3.0.2.0
Management DB2 Enterprise Server Edition: 9.7.0.2..0->9.7.0.8..1
Management Storage Manager: 10.70.6508.0->10.84.6530.0
Management Fibre Channel Adapter (FC5735/5273) firmware: 010522->202307

[Core Warehouse]
Data IBM AIX: 6100-06-01-1043->6100-08-02-1316
Data Power 740 firmware: AL720_090->AL730_99
Data InfoSphere Warehouse: 9.7.2.20100807_9.7.0.2..0->9.7.7.20121015
Data HA_DB2: Not Available->1.0.0.1
Data GPFS: 3.3.0.7->3.5.0.7
Data IBM Systems Director Common Agent: 6.2.0->6.3.0.0
Data 10Gb Fibre Ethernet Adapter (FC5708) firmware: 010522->020111
Data SSD Drive firmware: 30453633->304E3646
Data Tivoli SAMP: 3.1.0.7->3.2.2.4
Data SSD RAID Card Adapter (CCIN 57CD) firmware: 04220029->0422003a
Data DB2 Enterprise Server Edition: 9.7.0.2..0->9.7.0.8..1
Data SMI-S Eagle Provider: 10.10.15.0->10.27.5.0
Data Fibre Channel Adapter (FC5735/5273) firmware: 111304->202307

[Other Service]
Warehouse Applications IBM AIX: 6100-06-01-1043->6100-08-02-1316
Warehouse Applications Power 740 firmware: AL720_090->AL730_99
Warehouse Applications GPFS: 3.3.0.7->3.5.0.7
Warehouse Applications WebSphere Application Server: 7.0.0.3->0.0.0.0
Warehouse Applications IBM Systems Director Common Agent: 6.2.0->6.3.0.0
Warehouse Applications 10Gb Fibre Ethernet Adapter (FC5708) firmware: 010522->020111
Warehouse Applications Tivoli SAMP: 3.1.0.7->3.2.2.4
Warehouse Applications DB2 Enterprise Server Edition: 9.7.0.2..0->9.7.0.8..1
Warehouse Applications SMI-S Eagle Provider: 10.10.15.0->10.27.5.0
Warehouse Applications Fibre Channel Adapter (FC5735/5273) firmware: 111304->202307

[Infrastructure]
Infrastructure Juniper Switch firmware: 10.2R1.8.0->12.3R1.7
Infrastructure SAN40B-4 Switch firmware: v6.3.1b->v7.0.2a
Infrastructure DS3500 firmware: 07.70.16.01->07.84.46.00

========================
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 10Gb Fibre Ethernet Adapter (FC5708) firmware: Validated Successfully
Management Storage Manager: Validated Successfully
Management DB2 Enterprise Server Edition: Validated Successfully
Management WebSphere Application Server: Validated Successfully
Management DB2 Performance Expert: Validated Successfully
Management Optim Performance Manager: Validated Successfully
Management IBM Smart Analytics System Control Console: Validated Successfully

[Core Warehouse]
Data Power 740 firmware: Validated Successfully
Data IBM AIX: Validated Successfully
Data SSD RAID Card Adapter (CCIN 57CD) firmware: Validated Successfully
Data SSD Drive firmware: Validated Successfully
Data 10Gb Fibre Ethernet Adapter (FC5708) firmware: 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

[Other Service]
Warehouse Applications Power 740 firmware: Validated Successfully
Warehouse Applications IBM AIX: Validated Successfully
Warehouse Applications 10Gb Fibre Ethernet Adapter (FC5708) firmware: Validated Successfully
Warehouse Applications SMI-S Eagle Provider: Validated Successfully
Warehouse Applications Tivoli SAMP: Validated Successfully
Warehouse Applications DB2 Enterprise Server Edition: Validated Successfully
Warehouse Applications WebSphere Application Server: Validated Successfully

[Infrastructure]
Infrastructure SAN40B-4 Switch firmware: Validated Successfully
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 IBM Systems Director Server update : 0 of 3 task completed
Preparing DB2 Enterprise Server Edition update : 0 of 4 task completed  
Preparing Optim Performance Manager update :  
...  <omitted lines> ...
Preparing IBM Systems Director Server update : 3 of 3 task completed
Preparing DB2 Enterprise Server Edition update : 4 of 4 task completed
Preparing Optim Performance Manager update : 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 IBM Systems Director Server update : 0 of 5 task completed
...  <omitted lines> ...    
Applying IBM AIX update : 1 of 2 task completed
Applying IBM Systems Director Server update : 0 of 5 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

Log file: /var/aixappl/pflayer/log/platform_layer.log
Resuming updates:
Applying disruptive updates to management services:
Log file: /var/aixappl/pflayer/log/platform_layer.log
...  <omitted lines> ...
Applying DB2 Enterprise Server Edition update : 0 of 4 task completed
Applying HA_DB2 update : 0 of 6 task completed
Applying WebSphere Application Server update : 0 of 1 task completed
Applying Optim Performance Manager update : 0 of 5 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
 
Log file: /var/aixappl/pflayer/log/platform_layer.log
Resuming updates:
Applying disruptive updates to management services:
Log file: /var/aixappl/pflayer/log/platform_layer.log
...  <omitted lines> ...
Applying DB2 Enterprise Server Edition update : 4 of 4 task completed
Applying HA_DB2 update : 6 of 6 task completed
Applying WebSphere Application Server update : 1 of 1 task completed
Applying Optim Performance Manager update : 5 of 5 task completed


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

Prepare stage output:



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

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 Tivoli SAMP: TSA prepare started task completed

Log file:
Core Warehouse Data Tivoli SAMP: TSA prepare started task completed

Log file:
Other Service Warehouse Applications Tivoli SAMP: TSA prepare started task completed

 ...  <omitted lines> ...

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

    Log file:
    Other Service Warehouse Applications DB2 Enterprise Server Edition: DB2 prepare started task completed

    Log file:
    Core Warehouse Data InfoSphere Warehouse: ISW prepare started 2 of 2 task completed


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 step 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 step if they were not applied in the Prepare step. After this step completes, system services run on the new software and firmware levels without internal disk mirroring enabled. The updates can be reverted by performing a system rollback using the -rollback option.

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

Log file: /var/aixappl/pflayer/log/platform_layer.log
Applying updates to system:

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

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

Log file:
    Other Service Warehouse Applications IBM AIX: AIX apply started 3 of 3 task completed

    Log file:
    Core Warehouse Data SMI-S Eagle Provider: EagleProvider apply started task completed

...  <omitted lines> ...

Log file:
    Infrastructure Infrastructure SAN40B-4 Switch firmware: SANFW apply started 1 of 1 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: /var/aixappl/pflayer/log/platform_layer.log
Committing updates:

    Log file:
    Core Warehouse Data Tivoli SAMP: TSA commit started task completed

    Log file:
    Core Warehouse Data Tivoli SAMP: TSA commit started 0 of 1 task completed

    Log file:
    Core Warehouse Data Tivoli SAMP: TSA commit started 0 of 2 task completed

...  <omitted lines> ...

 Log file:
    Other Service Warehouse Applications DB2 Enterprise Server Edition: DB2 commit started 1 of 1 task completed

Log file:
    Core Warehouse Data InfoSphere Warehouse: ISW commit started 1 of 1 task completed
 
Log file:
    Management Management Optim Performance Manager: Optim Performance Manager commit started 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

11 November 2013:

  • Added instructions to rebind DB2 packages as step 5 in the "Performing the necessary tasks after installing" section.
  • Moved miupdate command output to a new "Command output" section.

04 November 2013:
  • Removed step 5 in "Performing the necessary tasks after installing" to install the Tivoli SA MP 3.2 license manually. Added as step 4 in the "Installing" section.

21 October 2013:
  • Added step 5 in "Performing the necessary tasks after installing" to install the Tivoli SA MP 3.2 license manually.

10 September 2013:
09 August 2013:
  • Updated step 11 in the "Prior to installing" section with a statement restricting password changes during a fix pack installation.

13 June 2013:
  • Original version published.


Back to top

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

Document Information

Modified date:
16 June 2018

UID

swg21625042

Page Feedback