Guest post from Al de Moya, Consulting Brand Manager
Have you moved to DB2 10 yet? If not, put these steps into your migration plan.
Benchmark the performance from your current version of DB2.
One of your primary reasons for moving to DB2 10 may be to obtain CPU savings. Be sure to capture current DB2 CPU resource consumption to prove to management that the investment of time, machine resources, and costs justifies the migration.
Plan for a multi-step migration.
When you migrate to DB2 10, you will move first to conversion mode, then to enable new function mode, and finally to new function mode. IBM has enabled a migration from DB2 V8 directly to DB2 10. If you are still using DB2 8, consider moving directly to DB2 10 because eliminate the migration from DB2 9 to DB2 10, and you will benefit from the CPU savings in DB2 10. But don’t wait too long to start your migration; IBM drops support for DB2 V8 support on April 30, 2012.
Beware of access path changes that can hurt performance.
If you have migrated to a new version of DB2 before, you may have seen performance degradation as a result of access path changes. For DB2 10, IBM documentation states that you can get significantly better performance by rebinding your plans.
To adequately test the impact of DB2 10 on existing plans, you need to explain the SQL statements on a DB2 10 subsystem with object statistics that match your production environment.
Create a baseline from your current DB2 version by EXPLAINing both static and dynamic SQL statements from your production workload, and then compare the access paths with those from the EXPLAINs run on DB2 10. Tools can help with this exercise.
Coordinate your DB2 management product migration with your DB2 system migration.
Check with your vendors to determine what version of their management products support DB2 10. You may find that one version of the products supports both your current DB2 version and DB2 10. You may need to migrate to the latest version of your management tools before migrating to DB2 10, but the payback would be a dramatic reduction in the time and effort to migrate to DB2 v10.
The postings in this blog are my own and don't necessarily represent BMC's opinion or position.