Embed Size (px)
Citation preview
1
GSE DB2 Working Group meeting 10 December 2015
11 OMG! Migrating to DB2 11
Euroclear experience migrating to DB2 11
About Euroclear
• Active in the financial transaction processing, Euroclear is the world’s largest provider of domestic and cross-border settlement & related services for bonds, equity and funds.
• Our clients are banks and financial institutions, brokers, dealers from over 80 countries.
2
Euroclear facts & figures
3
• Number of employees: 3600 worldwide► 2,500 in Belgium, and approximately 900 in IT
• Nationalities: >80
• Average age: 37
• Number of offices worldwide: 12
• Countries in which we have clients: 80
• Headquarters: Belgium► Main office in Brussels, a 2nd office in Braine L’Alleud
Our offices and hubs worldwide
4
Acknowledgement and Disclaimers
5
The information contained in this presentation has not been submitted to any formal Euroclear or other review and is distributed on an ‘as is basis’ without any warranty either express or implied. The use of this information is a user responsibility.
Reference to third party software is not for advertisement. The issues explained in the following slides are explained at best of current knowledge. Different installation sites may or may not experience the issue hereafter presented.
The comments in this presentation may or may not represent the Euroclear opinions concerning the topics hereafter discussed.
Users attempting to adapt procedures and data to their own environments do so at their own risk. All procedures presented have been designed for educational purposes only.
6
We don’t talk about PROBLEMS
but SOLUTIONS!
Matching columns Join
7
• SQL with join between► Char(5) and Char(7)
• In DB2 10 this was not an issue► Index to support the Join► Index with matching columns 2
• In DB2 11 some performance degradation► Index to support the Join► Not matching index scan
–Increase in the getpages of the index–X5 increase of CPU
• Discussion ongoing
Missing XML_RESTRICT_EMPTY_TAG
8
• Zparm influencing the serialization of XML Documents► DB2 10 (UK97183)
–Introduced with RSU1312► DB2 11 (UI26407)
–Forward fixed with PUT1504 + RSU1509–Available in DB2 11 CM
IBM Customization Tool
9
• Used by ► IBM Admin Tool► IBM Query Monitor
• Issue with the Discovery and the fulfillment of values from previous installation► Issue in ISPF Tables created► In the JCL created for dataset qualification
–May be specific to Euroclear setup to deploy software • Noticeable improvements comparing to previous version …
• Youtube is your friend!
Euroclear Planning
10
• Migration to DB2 11 CM with RSU1503• Migration to DB2 11 NFM with RSU1509• In between RSU1506
• HOLDDATA in RSU1509 flagging a lot of PTFs in errors• 79 PTFs to exclude in the APPLY …
• End of October lots of changes in HOLDDATA for the RSU1506-RSU1509
• All the software displaying bufferpools allocation managed to display wrong/missing information
• IBM Admin tool 11.1► VPSIZEMIN and VPSIZEMAX to * instead of 0
–Corrected with RSU1509► SPSIZE and SPSEQT missing (PMR open)► Use "Browse” command to display the correct size of the bufferpool
• CA Sysview 18► Display of the allocation in panel R/BUFLISTS not matching► PTF RO77823
Wrong definition of bufferpools
11
Enter in AdminTool to the Z->BA , exit and « ops, I did it again »
IBM0451S ONCODE=451 The STORAGE condition was raised. From entry point PROCESS_DB2CMD at statement 8110 at compile unit offset +00000CE2 at entry offset +00000CE2 at address 1CFAEC2A. User abend 4,038 dec occurred processing command 'DSN '.
VARCHAR9/CHAR9 too late in NFM
12
• As off CM, you can start to use IFCID 366 and 376 to identify SQL incompatibilities
• VAR/CHAR9 Functions are supported SQL functions to mimic the format of decimal in DB2 V9 ( BIF_COMPATIBILITY )
• Issue► Between CM and NFM it takes about 6 months► Average life of a DB2 version is 3 years► We can identify but not correct the incompatible SQL
• Why not anticipate the availability of VAR/CHAR9 to CM ?
• 7 out of 8 SQL incompatibilities can be solved with CHAR9
More Real Storage for small LPARS
13
• During Migration most of the STCs are down and the environment is not stressed
► But:–After an IPL all the STC are starting more or less together–In small LPARS (2G real storage)–DB2 unable to allocate enough storage to start–IRA* messages, just a little bit after DB2 startup –All the pages were currently in use
► Such behavior was not occurring with DB2 10
• Best solution: increase the Real Storage for all the LPARS from 2G to 3G• Decreasing the OUTBUFF can help
IRA405I 03, 81% OF THE REAL STORAGE FRAMES ARE FIXED D ASM OPS1000I Suppressed Alert:ALERTAPP 2 MIS D FROM:*MASTER* MSG: IRA400E 03,PAGEABLE STORAGE SHORTAGE IRA400E 03,PAGEABLE STORAGE SHORTAGE
Reason 03: means below the 16 MB line
DB2 performance Business Temporal Table
14
• Drastic performance decrease in DB2 11 CM with high CPU increase when query Business Temporal Tables
• How did we identified the issue?► Longer time to replicate data coming from Temporal tables
• Root cause► DB2 matching criteria when using temporal constructs not reusing the SQL
statement already prepared in the Dynamic Statement Cache► Full prepare of the SQL instead of the DSC hit
• APAR Open and PTF expected by the 15th of December • Workaround: In NFM REBIND the package with ARCHIVESENSITIVE(YES),
BUSTIMESENSITIVE(YES) and SYSTIMESENSITIVE(YES)
• Not forecasted reasons why DSNTIJEN (Enabling new features job ) is failing• How did we identify the issue?
► Simple, we crashed the job several times• Root causes:
► In case of replication some Catalog tables are Data Capture change (SYSTABLES)
► MQT defined on some of the Catalog tables► Missing Mapping DB
• Solution: The JCL is well written, you can restart it easily from the beginning► Set RESTRICT_ALT_COL_FOR_DCC=NO► DROP all the MQT defined on the Catalog► Create the Mapping DB as defined in the REORG_MAPPING_DATABASE
DB2U 332 13:40:30.63 DSNUEXDL - ERROR PROCESSING SQL STATEMENT - SQL CODE IS: -20180 SQLERRP: DSNXIATB SQLERRD: 00000032 00000000 00000000 FFFFFFFF 00000000 00000000 SQL MESSAGE TEXT: COLUMN RBA1 IN TABLE SYSIBM.SYSTABLES CAN NOT BE ALTERED A SQL STATEMENT: E SYSIBM.SYSTABLES ALTER COLUMN "RBA1" SET DATA TYPE CHAR(10) MN "RBA2" SET DATA TYPE CHAR(10) 332 13:40:30.64 DSNUGBAC - UTILITY DATA BASE SERVICES MEMORY EXECUTION ABENDED
DSNTIJEN Failing
15
Issue with DSN1COPY,PARM CHECK for SYSHIST
16
• DSN1COPY CHECK fails on A00x where x>1 datasets of SYSHIST if PAGESIZE(8K) is not defined
• How did we identify the issue?► DSN1COPY Check failing on DSNDBC.DSNDB06.SYSHIST.I0001.A00x but not
on DSNDBC.DSNDB06.SYSHIST.I0001.A001► Gets error DSN1990I (broken page)► Behavior in DB2 10 different from DB2 11
• Root cause► Despite for the A001 DSN1COPY is able to derive the PAGESIZE, for A00x is
not able• Solution:
► Change the JCL to add the PAGESIZE for those additional VSAM
DSN1998I INPUT DSNAME = DBWC.DSNDBC.DSNDB06.SYSHIST.I0001.A002 , VSAM DSN1997I OUTPUT DSNAME = NULLFILE , SEQ DSN1990I DSN1CPGD BROKEN PAGE. PAGE NUMBER = 00040000. REASON: RECORDS AND HOLE SERVICE INFO: CODE= 'C2C'X XFREEP='00025EFE'X XFRSTMAP='00024F7C'X 0000 002C83D1 2C4CF800 04000000 007E1EFE 00004104 01007A02 71020010 5844495F 0020 52444E5F 5041525F 42414C30 00085044 42324920 2020000E 44495F52 444E5F50 0040 41525F42 414C0008 50444232 49202020 59800003 16800320 11012119 32590461 0060 78C2C400 00000000 00C528DC 70000000 00C0F83A D23D61BA 9EC432A0 00000000 0080 004E8000 000CC468 C2000000 00000100 7A027102 00105844 495F5244 4E5F5041 00A0 525F4241 4C300008 50444232 49202020 000E4449 5F52444E 5F504152 5F42414CEtc…
Data Broken Page
17
• Map ID table pointing to a HOLE but the ROW is not flagged as a HOLE• Reason: While the system was waiting for writing a trace table, an error
occurred. The trace table could not be written.• APAR PI41127
► DSNISMRT 0C17 ABEND WAS ISSUED AFTER LOCK ESCALATION OF RLL TABLESPACE IN V11
► Similar, but wrong module► Page compaction is triggered by update ( DSNIREPR ) instead of insert (DSNISMRT )► Confirmed by IBM that the issue was linked► PTF UI29844 (PUT1508,RSU1509,HYPER) 17/08/2015
• Impossible to reproduce the issue• Two weeks before the migration of production
Check Often
18
• Upgrade DB2B10, Subset HDBBB10/1501• http://
www-01.ibm.com/support/docview.wss?uid=isg1_DB2B10_HDBBB10-1501
Good Practices
19
• In order to reduce the time to perform the migration► Enlarge of Catalog and Directory’s Bufferpool to provide additional real
storage• Check the Upgrade DB2B10, Subset HDBBB10/1501 webpage often• REBIND to reactivate the sPROCs after migration
► A03 - Conquer Your Fears. Episode 1 - Fear of REBIND - Bart Steegmans• Cleaning of Catalog
► Modify Statistics to clean up► Free of unused packages► REORG of Catalog before migrating to CM
and…
21
