Maintaining DB2 Analytics Accelerator in a DB2 for z/OS data sharing environment

When sharing a single accelerator

The IBM® DB2® Analytics Accelerator (IDAA) is a workload optimized appliance that uses both System z® and Netezza® technologies. In this article, learn how to maintain IDAA in configurations other than the standard configuration of connecting a single IDAA to a single DB2 subsystem or to a single member of a DB2 data sharing group.

Ed Lynch (edlynch@us.ibm.com), Executive Client Technical Professional, IBM

Ed Lynch is an executive client technical professional in the North America IOT — Data Warehousing and Business Analytics on System z.



29 November 2012

Introduction

The IBM DB2 Analytics Accelerator for z/OS Installation Guide defines the processes that are used to service the components involved in a DB2 Analytics Accelerator environment. These components include the DB2 for z/OS software, the DB2 Analytics Accelerator software on the appliance, the Netezza host software, and the Data Studio interface. This documentation provides clear information for connecting a single IDAA to a single DB2 subsystem or to a single member of a DB2 data sharing group. However, you may need clarification to address other environments, for example:

  • Connecting multiple standalone DB2 subsystems to a single DB2 Analytics Accelerator
  • Connecting multiple members of a single DB2 Data Sharing Group to a single DB2 Analytics Accelerator
  • Connecting multiple members of multiple DB2 Data Sharing Groups to a single DB2 Analytics Accelerator

Note that service practices could potentially be changed or enhanced in future releases and versions. The objective of this article is not to rewrite the provided documentation, but rather to complement it and provide clarity to the steps required for providing updates in these additional environments.

DB2 Analytics Accelerator environment

An IBM DB2 Analytics Accelerator installation consists of several components:

  1. The DB2 for z/OS software, in particular the DB2 optimizer, DB2 catalog, and the DDF address spaces that provide key support
  2. The IBM DB2 Analytics Accelerator for z/OS software, including the software for DB2 for z/OS stored procedures, which provide key administration and operations functionality
  3. The IBM DB2 Analytics Accelerator software that executes on the Netezza appliance and enables it to function only as an accelerator for DB2
  4. The Netezza appliance hardware and software
  5. The IBM DB2 Analytics Accelerator Data Studio graphical user interface

Figure 1 illustrates how these components are related.

Figure 1. DB2 Analytics Accelerator components
Client connects to DB2 with its various components, which is connected to Netezza, where the Analytics Accelerator resides

General guidelines for maintenance procedures

Maintenance needs to be applied to a DB2 Analytics Accelerator environment as follows:

  • Maintenance tasks that apply code changes to DB2 for z/OS or to the DB2 stored procedures that support IBM DB2 Analytics Accelerator (item numbers one and two in the list above) need to be performed on each member of each DB2 data sharing group, unless SCOPE(GLOBAL) is used. If SCOPE(GLOBAL) is used then the tasks can be performed from one member of each DB2 data sharing group.
  • Maintenance tasks that need to be performed on the Netezza system (item numbers three and four in the list above) only need to be done once. They can be performed from any member of any DB2 data sharing group or any DB2 subsystem.
  • Maintenance that needs to be performed to the Data Studio graphical user interface software needs to be performed once for each system containing this software.

Maintenance to any one component may have prerequisite or co-requisite maintenance from one of the other components. When applying maintenance to multiple components, be sure to determine the proper order that should be followed for each particular set of fixes.

The update sequence of the components is important. The general recommended order is as follows:

  1. IBM DB2 Analytics Accelerator Data Studio Graphical User Interface (component #5)
  2. The Netezza appliance hardware and software (component #4)
  3. DB2 for z/OS (component #1)
  4. Accelerator software that runs on the appliance (component #3)
  5. The IBM DB2 Analytics Accelerator for z/OS software, in particular the binding of the stored procedures (component #2)

Sample scenarios

Consider the following environment:

Note that the DB2 commands –START ACCEL and –STOP ACCEL have a SCOPE(GROUP) option that starts/stops acceleration for all members of the data sharing group against which the command is executed. The Data Studio interface operates against a single member and the start/stop request would need to be performed for each member.

  • DB2 Data Sharing Group A DSGA with 2 members DSGA1 on LPAR A1 and DSGA2 on LPAR A2
  • DB2 Data Sharing Group B DSGB with 2 members DSGB1 on LPAR B1 and DSGB2 on LPAR B2
  • DSGA and DSGB share a single IDAA

Here are two example scenarios that illustrate how you could apply maintenance in this environment.

Scenario 1: Netezza

In this scenario, you are applying maintenance to Netezza base microcode software. Here are the steps:

  1. Download the Netezza code to a System z USS file onto LPAR A1.
  2. Transfer the file to the Accelerator using an ssh interface into LPAR A1.
  3. Using the Data Studio interface or using the DB2 command –STOP ACCEL, stop the accelerator for all members: DSGA1, DSGA2, DSGB1, and DSGB2.
  4. With IBM support, follow directions for installing the code. Refer to Chapter 7 of the Installation Guide.
  5. Using the Data Studio interface or using the DB2 command –START ACCEL, start the accelerator for all members: DSGA1, DSGA2, DSGB1, and DSGB2.

Scenario 2: DB2 Analytics Accelerator and Data Studio

In this scenario, you are applying maintenance to the IBM DB2 Analytics Accelerator software that includes the supporting DB2 for z/OS stored procedures, to the Accelerator software that executes on the Netezza system's host node, and to the Data Studio interface. Follow these steps:

  1. Identify prerequisite and co-requisite software fixes for DB2 for z/OS.
  2. Update the software for the IBM DB2 Analytics Accelerator Data Studio graphical user interface.
  3. Using the Data Studio interface or using the DB2 command –STOP ACCEL, stop the accelerator for all members: DSGA1, DSGA2, DSGB1, and DSGB2.
  4. Download and SMP/E receive the DB2 for z/OS co-requisite / pre-requisite software.
  5. Download and SMP/E receive the PTF/APAR software fix for IBM DB2 Analytics Accelerator for System z using SCOPE(GLOBAL) against one member of DSGA and using one member of DSGB (for example, DSGA1 and DSGB1). If SCOPE(GLOBAL) is not used then perform against each member of each data sharing group (DSGA1, DSGA2, DSGB1, and DSGB2).
  6. SMP/E apply the DB2 for z/OS PTFs.
  7. Using the Data Studio interface, transfer the accelerator software updates to the appliance. This only needs to be done once from one member of one data sharing group, for example from DSGA1 only. The software will automatically install on the accelerator but will not be activated.
  8. Apply the fixes for the stored procedures by REBINDing the IBM DB2 Analytics Accelerator stored procedures to each data sharing group from one member of each data sharing group, (for example, from member DSGA1 and DSGB1). Reference job AQTTUSP)
  9. Using the Data Studio interface, activate the new software level for the accelerator. This is done once from one member of one data sharing group, for example from DSGA1 only.
  10. Using the Data Studio interface or using the DB2 command –START ACCEL, start the accelerator for each member of each data sharing group, for example DSGA1, DSGA2, DSGB1, and DSGB2.

Conclusion

This article has provided information about the basic components of a DB2 Analytics Accelerator environments, and given guidelines on how to maintain more complex Analytics Accelerator environments.

Resources

Comments

developerWorks: Sign in

Required fields are indicated with an asterisk (*).


Need an IBM ID?
Forgot your IBM ID?


Forgot your password?
Change your password

By clicking Submit, you agree to the developerWorks terms of use.

 


The first time you sign into developerWorks, a profile is created for you. Information in your profile (your name, country/region, and company name) is displayed to the public and will accompany any content you post, unless you opt to hide your company name. You may update your IBM account at any time.

All information submitted is secure.

Choose your display name



The first time you sign in to developerWorks, a profile is created for you, so you need to choose a display name. Your display name accompanies the content you post on developerWorks.

Please choose a display name between 3-31 characters. Your display name must be unique in the developerWorks community and should not be your email address for privacy reasons.

Required fields are indicated with an asterisk (*).

(Must be between 3 – 31 characters.)

By clicking Submit, you agree to the developerWorks terms of use.

 


All information submitted is secure.

Dig deeper into Information management on developerWorks


static.content.url=http://www.ibm.com/developerworks/js/artrating/
SITE_ID=1
Zone=Information Management
ArticleID=847637
ArticleTitle=Maintaining DB2 Analytics Accelerator in a DB2 for z/OS data sharing environment
publish-date=11292012