DB2 V10 Migration Guidance

Getting to DB2 10 for z/OS

Migration Considerations

align

Craig S. Mullins
Mullins Consulting, Inc.
http://www.craigsmullins.com

© 201 1 M u llins C ons u lting, Inc.

Author

This presentation was prepared by:

Craig S. Mullins
President & Principal Consultant

15 Coventry Ct
Sugar Land, TX 77479
Tel: 281-494-6153
Fax: 281.491.0637
E-mail: craig@craigsmullins.com

This document is protected under the copyright laws of the United States and other countries as an unpublished work. Any use or
disclosure in whole or in part of this information without the express written permission of Mullins Consulting, Inc. is prohibited.
© 2011 Craig S. Mullins, Mullins Consulting, Inc. All rights reserved.

© 201 1 M u llins C ons u lting, Inc. 2

Abstract

The pressure is on for organizations to migrate from DB2 V8 or V9 to DB2 10.
A migration can be a traumatic thing… I’m sure many of us still remember
migration from V7 to V8. But it doesn’t have to be such a burden!

Getting to DB2 10 should be less problematic, but we must be sure to plan
appropriately, learn lessons from past migrations, and be prepared. This
session will offer guidance on migration issues and concerns and along the way
we will discuss topics such as:

•Skip Level Migration
•Deprecated Features
•Rebinding and Dealing with Access Path Changes

If your organization is considering moving to the next level of DB2 then this
presentation will provide an insight into making the job easier with a lot less
pain.


Agenda

• Overview
• Migration Issues and Concerns
• Skip Level Migration
• Deprecated Features
• Access Paths
• New Features
• Changed Access Paths
• Categorizing Changes


DB2 10 for z/OS

• DB2 10 for z/OS was released for GA on October 19, 2010.
• Highlights of the release include:
– Out-of-the-box reduction in CPU utilization and from 5 to 10 times more concurrent users on
a single DB2 subsystem (as compared to DB2 9; results based on early customers and internal IBM testing)
– Greater concurrency for data management, data definition, and data access, including
additional online changes for data definitions, utilities, and subsystems
– Improved security with better granularity for administrative privileges, data masking, and
audit capabilities
– Temporal or versioned data to understand system and business times at the database level
– Hashed indexes
– pureXML™ and SQL enhancements to simplify portability from other database solutions
– Productivity improved for database administrators, application programmers, and systems
administrators
– Many QMF improvements
• …and there are a lot of optimizer enhancements and performance
improvements that you won’t get without a REBIND.


Migration Issues

• In August 2010, IBM announced the end of service for DB2 for z/
OS Version 8
– In the announcement letter (910-169) IBM indicates that the date for EoS
will be April 30, 2012.
– This is less than a year and a half away.

DB2 Version GA Date EoM Date EoS Date

7 March 30, 2001 March 5, 2007 March 30, 2008

8 March 26, 2004 September 8, 2009 April 30, 2012

9 March 16, 2007

10 October 22, 2010

EoS: End of Service EoM: End of Marketing


Issues and Conclusion

• Many sites are still running DB2 Version 8
• IBM is offering skip level migration
– DB2 V8  DB2 9  DB2 10
• Of course, you can also migrate to 10 from 9
– DB2 9  DB2 10
• 2011 will be a year of many migrations
– DB2 V8 to DB2 9
– DB2 V8 to DB2 10
– DB2 9 to DB2 10

n d if y o u a r e s t il l o n V 7 o r e a r l ie r , y o u a r e W AY o v e r d u e t o u p d a t e !

Migration Concerns

• Issues with skipping a DB2 version
• Regular issues with any version migration
– System pre-requisites
• System software versions
(z/OS, IMS, CICS, programming languages, etc.)
• Fallback PTF
– Deprecated features?
– Defaults changed?
– Building a migration plan
• Vendor support?
• Test Implementation Plan
• Moving to Production
– Validation

– Access path changes?

Skipping DB2 9?

• Should you skip from V8 to 10?
– Gauge your organization’s “bleeding edge” tolerance
• DB2 10 is still very new; You are on an older version of DB2…
why?
• DB2 10 will have more defects at first, then fewer as the
software matures (and DB2 9 is mature, at this point)
– Are there features in DB2 10 that compel you to move
more quickly to it?
– A skip migration project requires a longer timeline, and
involves more risk
– Are there organizational hurdles?
• Training – for two versions, not just one!

• If you make an informed, educated decision,
migrating directly to DB2 10 from V8 can be a smart
move.

Check the Pre-requisites

• Read the information APAR
• Read the What’s New manual
– GC19-2985-01
• Read the Technical Overview redbook
– SG24-7892
• System pre-requisites
– System software versions
(z/OS, IMS, CICS, programming languages, etc.)
– Fallback PTF
• New Reserved Words
• PERIOD
• ORGANIZATION
• ZONE

Deprecated Features (9 – 10)

• Private Protocol Distribution
– No surprise since IBM has been indicating this was on its way out for a number of
releases now. Not too difficult to convert to DRDA (some help w/DSNTP2DP).
• ACQUIRE(ALLOCATE) is no longer supported for BIND | REBIND PLAN
– Rebind with ACQUIRE(USE)
• REBIND plans & packages that haven’t been rebound since V5 or before.
• EXPLAIN tables prior to V8 format are no longer supported
(UNICODE)
– Information APAR PK85068.
• DB2 MQ XML functions and the DB2 XML Extender no longer supported
– Use pureXML.
• DB2 Management Clients no longer supported
(DB2 Administration Server, Control Center, and Development Center)

– Data Studio is IBM’s new management client
• BookManager no longer supported
– Instead use the PDF versions and/or the Info Center online.

No Longer Suppored: Plans w/DBRMs

• As of DB2 10, plans containing DBRMs are no
longer supported
– MEMBER parameter is no longer supported for BIND | REBIND PLAN
– You will have to convert the DBRMs to packages.

• REBIND PLAN(X) COLLID(*)
– "*" is the default value
• It creates DSN_DEFAULT_COLLID_X (where X is the plan name)
– This enables customer to convert plans with DBRMs bound directly
into them into packages under a collection ID
(DSN_DEFAULT_COLLID_X) automatically.


Deprecated Features (V8 – 9)

• Don’t forget that if you are skipping from V8 to 10 then you
need to consider the features deprecated for DB2 9, too!
– AIV Extender, Text Extender, and Net Search Extender are removed.
– Net.Data, stabilized at V7, is removed.
• WebSphere is IBM’s strategic solution for getting DB2 data to Web applications.

– DB2 Estimator is not provided for DB2 9.
– DB2-managed stored procedure support is removed.
– Simple table space creation support is removed.
– JDBC/SQLJ Driver for OS/390 and z/OS support is removed.


The DB2 Catalog

• The Catalog is SMS-managed as of DB2 10.
• Links are removed from the DB2 Catalog and Directory.
• More usage of LOBs.
– SYSVIEWS.TEXT, SYSTRIGGERS.TEXT,
SYSROUTINES_SRC.CREATEMST, and SYSPACKSTMT.TEXT
• Many more table spaces.
– Table ← 1 to 1 → Table Space
• Each table is in its own partition-by-growth
table space in new-function mode
• Each table space uses row-level locking,
and all tables are in reordered-row format.
• And for skip-level migration:
– Don’t forget the V8 to DB2 9
changes to the DB2 Catalog!

DSNZPARMs

• Be sure to include a review of your DSNZPARM
settings in your migration plan.
– New DSNZPARMs
• e.g.) CATDDACL, CATDMGCL, CATDSTCL
– Deprecated DSNZPARMs
• e.g.) STATCLUS, SEQCACH, etc.
– Removed DSNZPARMs
• e.g.) PARTKEYU, TABLES_JOINED_THRESHOLD, etc.
– DSNZPARMs with new default values
• e.g.) CHKFREQ
– Old default: 500,000 records
– New default: 5 minutes

• Any/all of these can impact
your DB2 subsystem
Willie Favero’s blog at http://it.toolbox.com/blogs/db2zos/ has several great articles on this topic.

DB2 10:
BIND & Access Path Stuff

• Ability to EXPLAIN existing packages
– Command: BIND PACKAGE…EXPLAIN (ONLY)
• Works for all packages.
– SQL: EXPLAIN PACKAGE
• The package being explained must have been created in DB2 9 or above.
– Older packages cannot be explained like this!

• CURRENT EXPLAIN MODE special register
– Controls how EXPLAIN behaves for eligible dynamic SQL (SELECT,
INSERT, and the searched form of UPDATE and DELETE).
• NO - turns off capture of EXPLAIN information. (default)
• YES - turns on capture of EXPLAIN information; plan tables will be updated.
• EXPLAIN - this option is the same of YES. However, the dynamic SQL
statements are not executed.
• New authority that can be granted: EXPLAIN

DB2 10:
BIND & Access Path Stuff

• New DB2 10 feature: Safe Query Optimization
• The DB2 Optimizer now considers the uncertainty of
predicate filtering when selecting an index.
– Previously, overestimating the filtering of a predicate was
possible when the value of a host variable was not known
(i.e. no literal).
– As of DB2 10, when indexes have a close cost estimate, the
DB2 Optimizer factors in the uncertainty of matching and
screening predicates.


Access Path Changes

• Access Paths
– This is perhaps the most time-consuming and worrisome aspects of
DB2 version migration.
– A new version typically means Optimizer enhancements.
– And that means changes to access paths!
– Changes that occur are not always predictable
• There may be trends that you can anticipate, though

– Other migration issues can cause
access path changes, too
• Statistics changes
• Environment changes


Additional DB2 10
REBIND Issues

• Incremental Rebinds
• DB2 incrementally rebinds static SQL statements that use
parallelism after migration to Version 10.
― Incremental rebinds can cause performance degradation, so you
should manually rebind those statements.
• A query in DSNTIJPM is provided that you can run to determine
which statements can use parallelism.
• Thread Constraint Relief
• DB2 10 improves the number of concurrent threads that can be
running. To get this relief, though, you must REBIND.
― After you REBIND, the work areas are moved above the bar.


Remembering V7  V8 ?

• DB2 Version 8 had many typical access path changes that
could be anticipated based on trends
• Most organization had the same type of changes
• For example:
 Matching Index Scan  TS Scan (for small tables)
 Non-matching Index Scan  TS Scan (for large indexes)

• So special rules could be applied
based on the trends


DB2 9 and 10 are different

• It is true that a migration to DB2 9 typically causes
access path changes, but…
– Different types of changes in every installation
– A general set of special rules is not really applicable

• DB2 10 exhibits similar behavior


2
1

Categorize Access Path Changes

• Why?
− Reduction of manual effort
− Typically, in a migration scenario,
between 10% to 35 % of all
SQL statements experience
changed access paths
− The good news…
• Many changes can be ignored


2
2

Access Paths Rely on Statistics

• Always remember that access paths rely on statistics
• The better the statistics, the better the DB2 Optimizer can
be at determining the appropriate access paths
• If you are going from V8 to 10: keep in mind
– Between DB2 V8 and DB2 9
• The algorithm used for RUNSTATS changed.
• Different “opinion” as to what is clustered.
• When will you update RUNSTATS?

• Always a good idea, though:
– Save performance and access path information
– To be able to compare before and after


Let’s Talk (briefly) About
Rebinding and Access Paths


When Are Access
Paths Changed?

Application
Development
Program changes:
BIND is required
Maintenance

Statistics change:
REBIND after RS

Optimizer changes:
REBIND
New DB2 Release
Version or PTF


2
5

Migration Scenario

New DB2
Release or PTF

No Program changes
No Statistic changes *

Optimizer changes
(* depending on your strategy)


Version Migration Concerns

Typically, it is not a hard & fast requirement to REBIND all
of your packages and plans when you move to a new
version of DB2.
› However, it is a really good idea to REBIND the most critical.

There are a lot of optimizer enhancements and performance
improvements that you won’t get without a REBIND.
And there are some REBINDs you cannot avoid.
› For DB2 9, plans and packages from DB2 V4 or earlier will be automatically
rebound when accessed by DB2 9.
› For DB2 10:
 Plans and packages from DB2 V5 or earlier will be automatically rebound when
accessed by DB2 10.
 Plans bound with DBRMs are automatically rebound to convert it to a PKLIST and the
DBRMs are bound into packages.


Additional Information

• IBM DB2 main web page:
http://www.ibm.com/software/data/db2/zos/
• DB2 10 web page:
http://www.ibm.com/software/data/db2/zos/db2-10/
• DB2 Information Center: http://www.ibm.com/support/docview.wss?
uid=swg27019288
• DB2 for z/OS IBM Redbooks:
http://www.redbooks.ibm.com/cgi-bin/searchsite.cgi?
query=DB2+AND+z/OS&SearchOrder=4&SearchFuzzy=


Summary

Learn the changes

Understand the impact

Plan ahead

REBIND for
performance

Do one thing at a time and;

You can migrate to DB2 10!


Contact Information

http://www.craigsmullins.com/dba_book.htm Craig S. Mullins
15 Coventry Court
Sugar Land, TX 77479

http://www.craigsmullins.com

craig@craigsmullins.com

Phone: (281) 494-6153

http://www.craigsmullins.com/cm-book.htm

DB2 V10 Migration Guidance

More Related Content

What's hot (20)

Similar to DB2 V10 Migration Guidance (20)

More from Craig Mullins (8)

Recently uploaded (20)

DB2 V10 Migration Guidance

Editor's Notes