DB2 V11 Migration Experience. Steven Goedertier

Transcription

1 DB2 V11 Migration Experience Steven Goedertier

2 Agenda Environment Migration plan Issues Results New features

3 1 Environment

4 Environment Galileï (zec12-705) 5 CPU & 2 ziip 6628 MIPS Newton (zec12-705) 5 CPU & 2 ziip 6628 MIPS XPC01 DBP1 DB2P DBP2 DBS2 DB2S DBS1 DBE1 DB2E XOC01 DBT2 DB2T DBT1 Legend: Production Development Test XAC01 DBA1 DB2A DBA2 Training Sandbox (DBA)

5 2 Migration plan

6 Migration plan

7 Migration plan Pre-migration steps BIF_COMPATIBILITY DSNTIJPB: No special actions V11 early code Activated during IPL beforehand

8 Migration plan Extra maintenances Rebind strategy Extended LRSN During migration NFM: 1. Convert BSDS 2. DB2 catalog and directory User tablespaces Was planned for weekly maintenance cycles

9 Migration plan Extended LRSN RED Alerts 29/10/2015 DB2 V11 converting partitioned table spaces from basic format to extended format FIXED in PI47967, PI50913 and PI /11/2015 An incorrect data-sharing join timestamp stored in the BSDS may prevent log reads of a peer member from returning any log records. This could cause data replication issues, recovery issues, or even potential data loss. FIXED in PI51674

10 3 Issues

11 Issues DB2 Query Monitor Error message: CQM2002E MONITORING AGENT INSTALLATION FAILED Parameter file had parameter PARALLEL(N) In V11 the value N is no longer supported FIXED in APAR PI37726

12 Issues DB2 Log Analysis Tool Continuous file reports fails with SQLCODE -302 SQLCODE = -302, ERROR: THE VALUE OF INPUT VARIABLE OR PARAMETER NUMBER 3 IS INVALID OR TOO LARGE FOR THE TARGET COLUMN OR THE TARGET VALUE The MODEFILE was not converted properly Fixed in APAR PI41594

13 Issues DB2 Administration Tool Generated DDL for VIEWs generate a random schema in the CREATE script FIX in APAR PI40665

14 Issues DB2 LIMITKEY is stored differently in SYSTABLEPART When performing rotate partition, we calculate the new limit based on column LIMITKEY in SYSIBM.SYSTABLEPART. After converting to CM, the newly created values for this column are wrapped with a single quote ( ). Answer IBM: The LIMITKEY column is marked Internal Use Only, which gives us carte blanche to change it as we see fit, but a lot of customers and vendors also use this field Workarround: SELECT STRIP(LIMITKEY,B,X'27') FROM SYSIBM.SYSTABLEPART

15 Issues DB2 Problem with DSNMQHLP MQSEND SQLCODE = -805, ERROR: DBRM OR PACKAGE NAME DB2T.DSNMQUDF.DSNMQHLP.0E4C9F2F02F5F3F0 NOT FOUND IN PLAN DARSARTI. REASON 02 The root cause of this problem is that 'the DBRM and the load modules are not in synch'. Fixed in APAR PI43041

16 4 Results

17 5/01/ /01/ /01/ /01/ /01/ /01/2015 4/02/2015 9/02/ /02/ /02/ /02/2015 1/03/2015 6/03/ /03/ /03/ /03/ /03/ /03/2015 5/04/ /04/ /04/ /04/ /04/ /04/2015 5/05/ /05/ /05/ /05/ /05/ /05/2015 4/06/2015 9/06/ /06/ /06/ /06/ /06/2015 4/07/2015 9/07/ /07/ /07/ /07/ /07/2015 3/08/2015 8/08/ /08/ /08/ /08/ /08/2015 2/09/2015 7/09/ /09/ /09/ /09/ /09/2015 2/10/2015 7/10/ /10/ /10/ /10/ /10/2015 1/11/2015 6/11/ /11/ /11/ /11/ /11/2015 1/12/2015 Results MSTR Sum of PRE_CP_SRB Sum of TCB_TIME Sum of SRB_TIME Sum of PRE_IIP_SRB 900 MSTR Address Space DATE Values Sum of PRE_CP_SRB Sum of TCB_TIME Sum of SRB_TIME Sum of PRE_IIP_SRB

18 Results - Utilities

19 Results - Utilities

20 Results Overall CPU , , , , ,00 13/01/ /01/ /01/ /01/2015 2/02/2015 7/02/ /02/ /02/ /02/ /02/2015 4/03/2015 9/03/ /03/ /03/ /03/ /03/2015 3/04/2015 8/04/ /04/ /04/ /04/ /04/2015 3/05/2015 8/05/ /05/ /05/ /05/ /05/2015 2/06/2015 7/06/ /06/ /06/ /06/ /06/2015 2/07/2015 7/07/ /07/ /07/ /07/ /07/2015 1/08/2015 6/08/ /08/ /08/ /08/ /08/ /08/2015 5/09/ /09/ /09/ /09/ /09/ /09/2015 5/10/ /10/ /10/ /10/ /10/ /10/2015 4/11/2015 9/11/ /11/ /11/ /11/ /11/2015 Overall CPU Trend CLASS2_CPU CLASS2_IIP

21 Results Overall CPU AVERAGES PER STAGE Migration Stages CLASS2_CPU CLASS2_IIP DB NFM , ,95 DB CM , ,95 DB NFM , ,49 PERCENTAGES BETWEEN STAGES Migration Stages CLASS2_CPU CLASS2_IIP V10NFM vs V11CM -19,37% 1,72% V11CM vs V11NFM 34,30% 2,78% V10NFM vs V11NFM 8,29% 4,55% We can see a significant drop in CPU after CM, but these savings are lost after migrating to NFM.

22 Results Overall CPU CPU AMOUNT 0% 2% 9% 22% CICS DB2CALL DRDA QUERY UTILITY 67%

23 2/01/2015 9/01/ /01/ /01/ /01/2015 6/02/ /02/ /02/2015 2/03/2015 9/03/ /03/ /03/ /03/2015 7/04/ /04/ /04/ /04/2015 6/05/ /05/ /05/ /05/2015 5/06/ /06/ /06/ /06/2015 3/07/ /07/ /07/ /07/2015 3/08/ /08/ /08/ /08/ /08/2015 7/09/ /09/ /09/ /09/2015 5/10/ /10/ /10/ /10/2015 2/11/2015 9/11/ /11/ /11/2015 1/12/2015 Results Overall CPU Sum of CLASS2_CPU ,00 CPU Usage / Transaction Type , , , , , ,00 0,00 DATE CONNECT_TYPE CICS DB2CALL DRDA QUERY UTILITY

24 Results Overall CPU OVERALL CPU USAGE - AVERAGES PER STAGE Migration Stages DB2CALL DRDA CICS DB NFM 7.566, , ,90 DB CM 5.657, , ,30 DB NFM 8.135, , ,83 PERCENTAGES BETWEEN STAGES Migration Stages DB2CALL DRDA CICS V10NFM vs V11CM -25,23% -19,28% -0,99% V11CM vs V11NFM 43,79% 35,86% 14,11% V10NFM vs V11NFM 7,51% 9,66% 12,97% After migrating to CM, we can see a drop in CPU consumption for all connection types, to rise again after NFM migration.

25 Results Overall Transactions /01/2015 9/01/ /01/ /01/ /01/2015 6/02/ /02/ /02/ /02/2015 6/03/ /03/ /03/ /03/2015 3/04/ /04/ /04/ /04/2015 1/05/2015 8/05/ /05/ /05/ /05/2015 5/06/ /06/ /06/ /06/2015 3/07/ /07/ /07/ /07/ /07/2015 7/08/ /08/ /08/ /08/2015 4/09/ /09/ /09/ /09/2015 2/10/2015 9/10/ /10/ /10/ /10/2015 6/11/ /11/ /11/ /11/2015 TRANSACTIONS/DAY TRANSACTIONS Poly. (TRANSACTIONS)

26 Results Overall Transactions TRANSACTION Types 0%0% 11% 1% CICS DB2CALL DRDA QUERY UTILITY 88%

27 2/01/2015 9/01/ /01/ /01/ /01/2015 6/02/ /02/ /02/2015 2/03/2015 9/03/ /03/ /03/ /03/2015 7/04/ /04/ /04/ /04/2015 6/05/ /05/ /05/ /05/2015 5/06/ /06/ /06/ /06/2015 3/07/ /07/ /07/ /07/2015 3/08/ /08/ /08/ /08/ /08/2015 7/09/ /09/ /09/ /09/2015 5/10/ /10/ /10/ /10/2015 2/11/2015 9/11/ /11/ /11/2015 1/12/2015 Results Sum of COUNT Amount of transactions / Connection Types CONNECT_TYPE CICS DB2CALL QUERY UTILITY DRDA DATE

28 Results Overall Transactions TRANCATIONS COUNT - AVERAGES PER STAGE Migration Stages DB2CALL DRDA CICS DB NFM , , ,02 DB CM , , ,04 DB NFM , , ,11 PERCENTAGES BETWEEN STAGES Migration Stages DB2CALL DRDA CICS V10NFM vs V11CM 17,34% 5,08% 6,80% V11CM vs V11NFM 10,77% 15,14% 13,47% V10NFM vs V11NFM 29,97% 20,99% 21,19% For all connection types, we can see an increase in amount of transactions when going to CM, and further increasing in NFM

29 Results CICS

30 Results CICS

31 Results CICS CICS - AVG CPU/OCC - AVERAGES PER STAGE Migration Stages CLASS2_CPU CLASS2_IIP DB NFM 0, , DB CM 0, , DB NFM 0, , PERCENTAGES BETWEEN STAGES Migration Stages CLASS2_CPU CLASS2_IIP V10NFM vs V11CM -1,61% 87,63% V11CM vs V11NFM 0,60% 13,97% V10NFM vs V11NFM -1,02% 113,84% When looking at average CPU consumption, we see that we re using less CPU. ziip usages does double, so are we actually using less?

32 Results Online

33 Results Online

34 Results Online AVG CPU/OCC - AVERAGES PER STAGE Migration Stages CLASS2_CPU CLASS2_IIP DB NFM 0, , DB CM 0, , DB NFM 0, , PERCENTAGES BETWEEN STAGES Migration Stages CLASS2_CPU CLASS2_IIP V10NFM vs V11CM -19,96% -19,03% V11CM vs V11NFM 15,02% 15,37% V10NFM vs V11NFM -7,93% -6,59% When looking at average CPU consumption, we see that we re using less CPU after migrating to CM. In NFM however we re losing part of this.

35 Results Batch

36 Results Batch

37 Results Batch AVG CPU/OCC - AVERAGES PER STAGE Migration Stages CLASS2_CPU CLASS2_IIP DB NFM 0, , DB CM 0, , DB NFM 0, , PERCENTAGES BETWEEN STAGES Migration Stages CLASS2_CPU CLASS2_IIP V10NFM vs V11CM -33,63% 183,36% V11CM vs V11NFM 25,67% -80,94% V10NFM vs V11NFM -16,59% -46,00% When looking at average CPU consumption, we see that we re using less CPU after migrating to CM. In NFM however we re losing part of this.

38 Results Batch A few packages

39 Results Batch DEGREE=ANY

40 Results Batch

41 Results Overall averages OVERALL AVG CPU/OCC - AVERAGES PER STAGE Migration Stages CLASS2_CPU CLASS2_IIP DB NFM 0, , DB CM 0, , DB NFM 0, , PERCENTAGES BETWEEN STAGES Migration Stages CLASS2_CPU CLASS2_IIP V10NFM vs V11CM -23,30% -3,25% V11CM vs V11NFM 19,97% -8,16% V10NFM vs V11NFM -7,99% -11,14% Overall the average CPU is still lower then in V10, but V11CM was more promising

42 5 New features

43 New features No concrete projects yet Possible candidates are: Extra options for temporal tables Audit & Logging tables Global variables

44 6 Questions?