© 2013 IBM Corporation
1
pureScale + HADR for Always Available
Transactions in DB2 10.5
June 20, 2013
Presented by:
Aamer ...
© 2013 IBM Corporation
2 Need webcast troubleshooting help? Click attachments
Rick Swagerman, Host
Language Architect, DB2...
© 2013 IBM Corporation
3 Need webcast troubleshooting help? Click attachments
Disclaimer
The information contained in this...
© 2013 IBM Corporation
Agenda
 DB2 pureScale technology overview
 DB2 10.5 marquee pureScale enhancements
– Availability...
© 2013 IBM Corporation
© 2013 IBM CorporationJune 19, 2013
DB2 pureScale Technology Overview
© 2013 IBM Corporation
Cluster Interconnect
Technology Overview
Single Database View
Clients
Database
Log Log Log Log
Shar...
© 2013 IBM Corporation
Online Recovery
Log LogLogLog
DB2 DB2 DB2 DB2
 A key DB2 pureScale design
point is to maximize ava...
© 2013 IBM Corporation
Recap of Key Design Points
 Deep RDMA exploitation over low
latency fabric
– Enables round-trip re...
© 2013 IBM Corporation
Recap of Key Design Points
 Deep RDMA exploitation over low
latency fabric
– Enables round-trip re...
© 2013 IBM Corporation
Rough Latency Comparison
App
Memory
Receiver
spins
looking
for msg
RDMA
NIC
DMAs
directly
into app
...
© 2013 IBM Corporation
© 2013 IBM CorporationJune 19, 2013
DB2 10.5 Marquee pureScale Enhancements
10.5
© 2013 IBM Corporation
HADR in DB2 pureScale
 Integrated disaster recovery solution
– Simple to setup, configure, and man...
© 2013 IBM Corporation
10.5
© 2013 IBM Corporation
HADR in DB2 pureScale: Example
Member
Member
Member
CF
CF
Primary site
Member
Member
Member
CF
CF
S...
© 2013 IBM Corporation
HADR in DB2 pureScale: Example
Member
Member
Member
CF
CF
Primary site
Member
Member
Member
CF
CF
S...
© 2013 IBM Corporation
© 2013 IBM Corporation16
Monitoring multiple log streams
select LOG_STREAM_ID, PRIMARY_MEMBER, STAN...
© 2013 IBM Corporation
© 2013 IBM Corporation17
HADR: Interesting tid-bits
 Members on primary must be = standby OR a sub...
© 2013 IBM Corporation
© 2013 IBM Corporation18
HADR: Replay is highly available
 Failure of replay member will automatic...
© 2013 IBM Corporation
© 2013 IBM Corporation19
HADR: Replay is highly available
 Failure of replay member will automatic...
© 2013 IBM Corporation
© 2013 IBM Corporation20
HADR: Replay is highly available
 No automatic fail-back to old replay me...
© 2013 IBM Corporation
© 2013 IBM Corporation21
Rolling Fix Pack Updates
 DB2 pureScale fix packs can be applied in an on...
© 2013 IBM Corporation
© 2013 IBM Corporation22
Member 1 Member 2
Code level: GA Code level: GA
1. db2stop member1
quiesce...
© 2013 IBM Corporation
© 2013 IBM Corporation23
Member 1 Member 2
Code level: GA Code level: GA
1. db2stop member1
quiesce...
© 2013 IBM Corporation
© 2013 IBM Corporation24
Member 1 Member 2
Code level: GA Code level: GA
1. db2stop member1
quiesce...
© 2013 IBM Corporation
© 2013 IBM Corporation25
Member 1 Member 2
Code level: GA
1. db2stop member1
quiesce
3. db2start me...
© 2013 IBM Corporation
© 2013 IBM Corporation26
Member 1 Member 2
Code level: GA
1. db2stop member1
quiesce
3. db2start me...
© 2013 IBM Corporation
© 2013 IBM Corporation27
Member 1 Member 2
Code level: GA
1. db2stop member1
quiesce
3. db2start me...
© 2013 IBM Corporation
© 2013 IBM Corporation28
Member 1 Member 2
1. db2stop member1
quiesce
3. db2start member1
2. instal...
© 2013 IBM Corporation
© 2013 IBM Corporation29
Member 1 Member 2
1. db2stop member1
quiesce
3. db2start member1
2. instal...
© 2013 IBM Corporation
© 2013 IBM Corporation30
Member 1 Member 2
1. db2stop member1
quiesce
3. db2start member1
2. instal...
© 2013 IBM Corporation
© 2013 IBM Corporation31
Member 1 Member 2
1. db2stop member1
quiesce
3. db2start member1
2. instal...
© 2013 IBM Corporation
© 2013 IBM Corporation32
Member 1 Member 2
1. db2stop member1
quiesce
3. db2start member1
2. instal...
© 2013 IBM Corporation
Eliminating complexity: Installing fixpacks prior to 10.5
 Manual lookup of TSA / GPFS levels (db2...
© 2013 IBM Corporation
Eliminating complexity: Installing fixpacks in 10.5
 ONE command
installFixPack
 Now accepts <ins...
© 2013 IBM Corporation
© 2013 IBM Corporation35
Rolling Fix Pack Updates: Best Practices
 One host at a time
 Do member’...
© 2013 IBM Corporation
Miscellaneous install improvements
Passwordless root ssh access is now optional
–Install requires ...
© 2013 IBM Corporation
 New members can be added to an instance while it is online
– No impact to workloads running on ex...
© 2013 IBM Corporation
 New members can be added to an instance while it is online
– No impact to workloads running on ex...
© 2013 IBM Corporation
39
Workload Consolidation: Member Subsets
 Previously, an application/tenant could only be configu...
© 2013 IBM Corporation
40
Workload Consolidation: Member Subsets
 Previously, an application/tenant could only be configu...
© 2013 IBM Corporation
41
Workload Consolidation: Member Subsets
Assume I have a database called MYDB and I want all OLTP ...
© 2013 IBM Corporation
42
Workload Consolidation: Member Subsets
Say I want to add another member to my OLTP subset since ...
© 2013 IBM Corporation
© 2013 IBM Corporation43
Workload Consolidation: Self-Tuning Memory Management (STMM)
 Prior DB2 p...
© 2013 IBM Corporation
© 2013 IBM Corporation44
ESE to/from pureScale Backup and Restore
Data
Log
Member 2
ESE
• OFFLINE b...
© 2013 IBM Corporation
© 2013 IBM Corporation45
pureScale Topology Changing Backup and Restore
 BACKUP from instance whic...
© 2013 IBM Corporation
© 2013 IBM Corporation46
pureScale Topology Changing Backup and Restore
 BACKUP from instance whic...
© 2013 IBM Corporation
June 19, 2013
DB2 10.5 Near-Term Futures
Peek
© 2013 IBM Corporation
© 2013 IBM Corporation48
Performance: Explicit Hierarchical Locking (EHL)
 Designed to remove data...
© 2013 IBM Corporation
Misc
 Online (inplace) table reorg Peek
© 2013 IBM Corporation
DB2 10.5 with BLU Acceleration now electronically available!
50 Need webcast troubleshooting help? ...
© 2013 IBM Corporation
51
DB2 Tech Talk: Technical Tour of DB2 10.5 with BLU Acceleration
Next Steps Roadmap
Reference
Cal...
© 2013 IBM Corporation
52
Upcoming Tech Talks
Don’t miss these in-depth DB2 10.1 feature talks!
Dates and topics subject t...
© 2013 IBM Corporation
DB2 Tech Talk
53 Need webcast troubleshooting help? Click attachments
© 2013 IBM Corporation
54 Need webcast troubleshooting help? Click attachments
Questions
Listening in replay?
Questions: w...
© 2013 IBM Corporation
55 Need webcast troubleshooting help? Click attachments
Thanks for attending!
Please rate the sessi...
Upcoming SlideShare
Loading in …5
×

Pure scale enhancements in db2 105 aamer sachedina_final

5,242 views

Published on

IBM DB2 Pure Scale

Published in: Technology
1 Comment
4 Likes
Statistics
Notes
No Downloads
Views
Total views
5,242
On SlideShare
0
From Embeds
0
Number of Embeds
554
Actions
Shares
0
Downloads
0
Comments
1
Likes
4
Embeds 0
No embeds

No notes for slide

Pure scale enhancements in db2 105 aamer sachedina_final

  1. 1. © 2013 IBM Corporation 1 pureScale + HADR for Always Available Transactions in DB2 10.5 June 20, 2013 Presented by: Aamer Sachedina, IBM Distinguished Engineer DB2 Chief Kernel and pureScale Architect
  2. 2. © 2013 IBM Corporation 2 Need webcast troubleshooting help? Click attachments Rick Swagerman, Host Language Architect, DB2 for Linux, UNIX, and Windows at IBM www.sqltips4db2.com 1. The presentation for this Tech Talk: bit.ly/ttfilejun20 2. Next steps and troubleshooting guide: click “Attachments“ in this webcast window A few details …. Aamer Sachedina Distinguished Engineer DB2 Chief Kernel and pureScale Architect Today’s technical presenters . . . DB2 Tech Talk series host and today’s presenter: DB2 10.5 with BLU Acceleration now electronically available! Download free trial: ibm.co/db2download
  3. 3. © 2013 IBM Corporation 3 Need webcast troubleshooting help? Click attachments Disclaimer The information contained in this presentation is provided for informational purposes only. While efforts were made to verify the completeness and accuracy of the information contained in this presentation, it is provided “as is”, without warranty of any kind, express or implied. In addition, this information is based on IBM’s current product plans and strategy, which are subject to change by IBM without notice. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, this presentation or any other documentation. Nothing contained in this presentation is intended to, or shall have the effect of: • Creating any warranty or representation from IBM (or its affiliates or its or their suppliers and/or licensors); or • Altering the terms and conditions of the applicable license agreement governing the use of IBM software. Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput or performance that any user will experience will vary depending upon many factors, including considerations such as the amount of multiprogramming in the user's job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve results similar to those stated here.
  4. 4. © 2013 IBM Corporation Agenda  DB2 pureScale technology overview  DB2 10.5 marquee pureScale enhancements – Availability: • HADR • Rolling fixpack upgrades • Online add member – Workload consolidation: • Member subsets • Per member Self Tuning Memory Management – ESE to/from pureScale backup and restore – pureScale topology changing backup and restore  DB210.5 near term pureScale futures – Performance: Explicit Hierarchical Locking (EHL) – Online (inplace) table reorg 10.5 Peek
  5. 5. © 2013 IBM Corporation © 2013 IBM CorporationJune 19, 2013 DB2 pureScale Technology Overview
  6. 6. © 2013 IBM Corporation Cluster Interconnect Technology Overview Single Database View Clients Database Log Log Log Log Shared Storage Access CS CS CSCS CS CS CS Member Member Member Member Primary2nd-ary DB2 engine runs on several host computers – Co-operate with each other to provide coherent access to the database from any member Data sharing architecture – Shared access to database – Members write to their own logs – Logs accessible from another host (used during recovery) Cluster caching facility (CF) from STG – Efficient global locking and buffer management – Synchronous duplexing to secondary ensures availability Low latency, high speed interconnect – Special optimizations provide significant advantages on RDMA- capable interconnects (eg. Infiniband) Clients connect anywhere,… … see single database – Clients connect into any member – Automatic load balancing and client reroute may change underlying physical member to which client is connected Integrated cluster services – Failure detection, recovery automation, cluster file system – In partnership with STG (GPFS,RSCT) and Tivoli (SA MP) Leverages IBM’s System z Sysplex Experience and Know-How
  7. 7. © 2013 IBM Corporation Online Recovery Log LogLogLog DB2 DB2 DB2 DB2  A key DB2 pureScale design point is to maximize availability during failure recovery processing  When a database member fails, only data in-flight on the failed member remains locked during the automated recovery – In-flight = data being updated on the member at the time it failed %ofDataAvailable Time (~seconds) Only data in-flight updates locked during recovery Database member failure 100 50
  8. 8. © 2013 IBM Corporation Recap of Key Design Points  Deep RDMA exploitation over low latency fabric – Enables round-trip response time ~10-15 microseconds  Silent Invalidation – Informs members of page updates requires no CPU cycles on those members – No interrupt or other message processing required – Increasingly important as cluster grows  Hot pages available without disk I/O from GBP memory – RDMA and dedicated threads enable read page operations in ~10s of microseconds GBP GLM SCA Buffer Mgr Lock Mgr Lock Mgr Lock Mgr Lock Mgr
  9. 9. © 2013 IBM Corporation Recap of Key Design Points  Deep RDMA exploitation over low latency fabric – Enables round-trip response time ~10-15 microseconds  Silent Invalidation – Informs members of page updates requires no CPU cycles on those members – No interrupt or other message processing required – Increasingly important as cluster grows  Hot pages available without disk I/O from GBP memory – RDMA and dedicated threads enable read page operations in ~10s of microseconds GBP GLM SCA Buffer Mgr Lock Mgr Lock Mgr Lock Mgr Lock Mgr
  10. 10. © 2013 IBM Corporation Rough Latency Comparison App Memory Receiver spins looking for msg RDMA NIC DMAs directly into app memory Sending process or thread Receiving process or thread RDMA write recvmsg NIC DMAs Into kernel buffer & raises interrupt Receiving process or thread pureScale RDMA Other DB Vendor TCPIP Send/Recv App Memory Sending process or thread App Mem sendmsg RDMA NIC DMAs directly from app memory NIC DMAs from kernel buffer Krnl Mem Krnl Mem App Mem Kernel int handler schedules receiving proc/thread recvmsg Receiving process or thread Sending process or thread App Mem sendmsg NIC DMAs from kernel buffer App Mem Kernel int handler schedules receiving proc/thread “Give me page X” round trip Observed min: ~30 usec “Give me page X” round trip Documented min: ~300 usec “Give me page X” round trip Documented min: ~130 usec NIC DMAs app buffer & raises interrupt Other DB Vendor RDS Send/Recv pureScale data from Galaxy 2 IB HCA measuremnts Other data was gathered from public sources. Should not be quoted.
  11. 11. © 2013 IBM Corporation © 2013 IBM CorporationJune 19, 2013 DB2 10.5 Marquee pureScale Enhancements 10.5
  12. 12. © 2013 IBM Corporation HADR in DB2 pureScale  Integrated disaster recovery solution – Simple to setup, configure, and manage  Support includes – DB2 10.5 GA ASYNC and SUPERASYNC modes • SYNC/NEARSYNC - future • Multiple standby - future – Time delayed apply – Log spooling – Both non-forced (role switch) and forced (failover) takeovers CFCF CFCF Primary Cluster Standby DR Cluster 10.5
  13. 13. © 2013 IBM Corporation 10.5
  14. 14. © 2013 IBM Corporation HADR in DB2 pureScale: Example Member Member Member CF CF Primary site Member Member Member CF CF Standby site Logs 1 Logs 2 Logs 3 TCP/IP Replay member Transactions 10.5
  15. 15. © 2013 IBM Corporation HADR in DB2 pureScale: Example Member Member Member CF CF Primary site Member Member Member CF CF Standby site Logs 1 Logs 2 Logs 3 Failed member's logs TCP/IP Replay member Transactions 10.5
  16. 16. © 2013 IBM Corporation © 2013 IBM Corporation16 Monitoring multiple log streams select LOG_STREAM_ID, PRIMARY_MEMBER, STANDBY_MEMBER, HADR_STATE from table (mon_get_hadr(-2)) LOG_STREAM_ID PRIMARY_MEMBER STANDBY_MEMBER HADR_STATE ------------- -------------- -------------- ---------- 0 0 0 PEER 1 1 0 PEER 2 2 0 PEER STANDBY_MEMBER is 0 as this is is the member where replay is occurring 10.5
  17. 17. © 2013 IBM Corporation © 2013 IBM Corporation17 HADR: Interesting tid-bits  Members on primary must be = standby OR a subset – New members must be added to the standby before they are added to the primary  However, asymmetrically sized members can be supported Member Member Member Primary Standby cMember m logs Preferred replay member • A member can be designated as the ‘preferred replay member’ on each site 10.5
  18. 18. © 2013 IBM Corporation © 2013 IBM Corporation18 HADR: Replay is highly available  Failure of replay member will automatically cause one of the other members to take over Member Member Member Primary logs Member Member Standby Member Preferred replay member 10.5
  19. 19. © 2013 IBM Corporation © 2013 IBM Corporation19 HADR: Replay is highly available  Failure of replay member will automatically cause one of the other members to take over Member Member Member Primary logs Member Member Standby Member Member New replay member selected on failure of preferred replay member 10.5
  20. 20. © 2013 IBM Corporation © 2013 IBM Corporation20 HADR: Replay is highly available  No automatic fail-back to old replay member once it comes back Member Member Member Primary logs Member Standby Member Member Replay continues here Member Preferred replay member User can cause fail-back by issuing on the standby: $> DB2 DEACTIVATE DATABASE MYDB $> DB2 ACTIVATE DATABASE MYDB 10.5
  21. 21. © 2013 IBM Corporation © 2013 IBM Corporation21 Rolling Fix Pack Updates  DB2 pureScale fix packs can be applied in an online rolling fashion – Transparently install DB2 pureScale fix packs with no outage  New options for installFixPack to do to online update, do a pre-commit check, and to subsequently commit the changes  Includes updates of CFs and members 10.5
  22. 22. © 2013 IBM Corporation © 2013 IBM Corporation22 Member 1 Member 2 Code level: GA Code level: GA 1. db2stop member1 quiesce 3. db2start member1 2. installFixPack –online_update member1 inst1 4. db2stop member2 quiesce 5. installFixPack –online_update member2 inst1 6. db2start member2 C C Rolling Fix Pack Updates – Example 10.5
  23. 23. © 2013 IBM Corporation © 2013 IBM Corporation23 Member 1 Member 2 Code level: GA Code level: GA 1. db2stop member1 quiesce 3. db2start member1 2. installFixPack –online_update member1 inst1 4. db2stop member2 quiesce 5. installFixPack –online_update member2 inst1 6. db2start member2 C C Rolling Fix Pack Updates – Example Two member cluster (each at GA level) with clients (C) connecting into each member 1. Member 1 is quiesced – clients all move to Member 2 2. DB2 binaries updated on Member 1 3. Member 1 started again and a portion of the clients get rerouted to Member 1 to balance the workload 4. Member 2 is quiesced – clients all move to Member 1 5. DB2 binaries updated on Member 2 6. Member 2 started again and a portion of the clients get rerouted to member 2 to balance the workload At this point, code is at FP1 level, but can't use any new FP1 features; can test stability and roll down to GA level if necessary 7. Updates are committed The instance is now completely running at FP1 and new features can be used; cannot roll down to GA any longer. 10.5
  24. 24. © 2013 IBM Corporation © 2013 IBM Corporation24 Member 1 Member 2 Code level: GA Code level: GA 1. db2stop member1 quiesce 3. db2start member1 2. installFixPack –online_update member1 inst1 4. db2stop member2 quiesce 5. installFixPack –online_update member2 inst1 6. db2start member2 C C Rolling Fix Pack Updates – Example Two member cluster (each at GA level) with clients (C) connecting into each member 1. Member 1 is quiesced – clients all move to Member 2 2. DB2 binaries updated on Member 1 3. Member 1 started again and a portion of the clients get rerouted to Member 1 to balance the workload 4. Member 2 is quiesced – clients all move to Member 1 5. DB2 binaries updated on Member 2 6. Member 2 started again and a portion of the clients get rerouted to member 2 to balance the workload At this point, code is at FP1 level, but can't use any new FP1 features; can test stability and roll down to GA level if necessary 7. Updates are committed The instance is now completely running at FP1 and new features can be used; cannot roll down to GA any longer. 10.5
  25. 25. © 2013 IBM Corporation © 2013 IBM Corporation25 Member 1 Member 2 Code level: GA 1. db2stop member1 quiesce 3. db2start member1 2. installFixPack –online_update member1 inst1 4. db2stop member2 quiesce 5. installFixPack –online_update member2 inst1 6. db2start member2 C C Rolling Fix Pack Updates – Example Two member cluster (each at GA level) with clients (C) connecting into each member 1. Member 1 is quiesced – clients all move to Member 2 2. DB2 binaries updated on Member 1 3. Member 1 started again and a portion of the clients get rerouted to Member 1 to balance the workload 4. Member 2 is quiesced – clients all move to Member 1 5. DB2 binaries updated on Member 2 6. Member 2 started again and a portion of the clients get rerouted to member 2 to balance the workload At this point, code is at FP1 level, but can't use any new FP1 features; can test stability and roll down to GA level if necessary 7. Updates are committed The instance is now completely running at FP1 and new features can be used; cannot roll down to GA any longer. 10.5 Code level: FP1
  26. 26. © 2013 IBM Corporation © 2013 IBM Corporation26 Member 1 Member 2 Code level: GA 1. db2stop member1 quiesce 3. db2start member1 2. installFixPack –online_update member1 inst1 4. db2stop member2 quiesce 5. installFixPack –online_update member2 inst1 6. db2start member2 C C Rolling Fix Pack Updates – Example Two member cluster (each at GA level) with clients (C) connecting into each member 1. Member 1 is quiesced – clients all move to Member 2 2. DB2 binaries updated on Member 1 3. Member 1 started again and a portion of the clients get rerouted to Member 1 to balance the workload 4. Member 2 is quiesced – clients all move to Member 1 5. DB2 binaries updated on Member 2 6. Member 2 started again and a portion of the clients get rerouted to member 2 to balance the workload At this point, code is at FP1 level, but can't use any new FP1 features; can test stability and roll down to GA level if necessary 7. Updates are committed The instance is now completely running at FP1 and new features can be used; cannot roll down to GA any longer. 10.5 Code level: FP1
  27. 27. © 2013 IBM Corporation © 2013 IBM Corporation27 Member 1 Member 2 Code level: GA 1. db2stop member1 quiesce 3. db2start member1 2. installFixPack –online_update member1 inst1 4. db2stop member2 quiesce 5. installFixPack –online_update member2 inst1 6. db2start member2 C C Rolling Fix Pack Updates – Example Two member cluster (each at GA level) with clients (C) connecting into each member 1. Member 1 is quiesced – clients all move to Member 2 2. DB2 binaries updated on Member 1 3. Member 1 started again and a portion of the clients get rerouted to Member 1 to balance the workload 4. Member 2 is quiesced – clients all move to Member 1 5. DB2 binaries updated on Member 2 6. Member 2 started again and a portion of the clients get rerouted to member 2 to balance the workload At this point, code is at FP1 level, but can't use any new FP1 features; can test stability and roll down to GA level if necessary 7. Updates are committed The instance is now completely running at FP1 and new features can be used; cannot roll down to GA any longer. 10.5 Code level: FP1
  28. 28. © 2013 IBM Corporation © 2013 IBM Corporation28 Member 1 Member 2 1. db2stop member1 quiesce 3. db2start member1 2. installFixPack –online_update member1 inst1 4. db2stop member2 quiesce 5. installFixPack –online_update member2 inst1 6. db2start member2 C C Rolling Fix Pack Updates – Example Two member cluster (each at GA level) with clients (C) connecting into each member 1. Member 1 is quiesced – clients all move to Member 2 2. DB2 binaries updated on Member 1 3. Member 1 started again and a portion of the clients get rerouted to Member 1 to balance the workload 4. Member 2 is quiesced – clients all move to Member 1 5. DB2 binaries updated on Member 2 6. Member 2 started again and a portion of the clients get rerouted to member 2 to balance the workload At this point, code is at FP1 level, but can't use any new FP1 features; can test stability and roll down to GA level if necessary 7. Updates are committed The instance is now completely running at FP1 and new features can be used; cannot roll down to GA any longer. 10.5 Code level: FP1 Code level: FP1
  29. 29. © 2013 IBM Corporation © 2013 IBM Corporation29 Member 1 Member 2 1. db2stop member1 quiesce 3. db2start member1 2. installFixPack –online_update member1 inst1 4. db2stop member2 quiesce 5. installFixPack –online_update member2 inst1 6. db2start member2 C C Rolling Fix Pack Updates – Example Two member cluster (each at GA level) with clients (C) connecting into each member 1. Member 1 is quiesced – clients all move to Member 2 2. DB2 binaries updated on Member 1 3. Member 1 started again and a portion of the clients get rerouted to Member 1 to balance the workload 4. Member 2 is quiesced – clients all move to Member 1 5. DB2 binaries updated on Member 2 6. Member 2 started again and a portion of the clients get rerouted to member 2 to balance the workload At this point, code is at FP1 level, but can't use any new FP1 features; can test stability and roll down to GA level if necessary 7. Updates are committed The instance is now completely running at FP1 and new features can be used; cannot roll down to GA any longer. 10.5 Code level: FP1 Code level: FP1
  30. 30. © 2013 IBM Corporation © 2013 IBM Corporation30 Member 1 Member 2 1. db2stop member1 quiesce 3. db2start member1 2. installFixPack –online_update member1 inst1 4. db2stop member2 quiesce 5. installFixPack –online_update member2 inst1 6. db2start member2 C C Rolling Fix Pack Updates – Example Two member cluster (each at GA level) with clients (C) connecting into each member 1. Member 1 is quiesced – clients all move to Member 2 2. DB2 binaries updated on Member 1 3. Member 1 started again and a portion of the clients get rerouted to Member 1 to balance the workload 4. Member 2 is quiesced – clients all move to Member 1 5. DB2 binaries updated on Member 2 6. Member 2 started again and a portion of the clients get rerouted to member 2 to balance the workload At this point, code is at FP1 level, but can't use any new FP1 features; can test stability and roll down to GA level if necessary 7. Updates are committed The instance is now completely running at FP1 and new features can be used; cannot roll down to GA any longer. 10.5 Code level: FP1 Code level: GA
  31. 31. © 2013 IBM Corporation © 2013 IBM Corporation31 Member 1 Member 2 1. db2stop member1 quiesce 3. db2start member1 2. installFixPack –online_update member1 inst1 4. db2stop member2 quiesce 5. installFixPack –online_update member2 inst1 6. db2start member2 C C Rolling Fix Pack Updates – Example Two member cluster (each at GA level) with clients (C) connecting into each member 1. Member 1 is quiesced – clients all move to Member 2 2. DB2 binaries updated on Member 1 3. Member 1 started again and a portion of the clients get rerouted to Member 1 to balance the workload 4. Member 2 is quiesced – clients all move to Member 1 5. DB2 binaries updated on Member 2 6. Member 2 started again and a portion of the clients get rerouted to member 2 to balance the workload At this point, code is at FP1 level, but can't use any new FP1 features; can test stability and roll down to GA level if necessary 7. Updates are committed The instance is now completely running at FP1 and new features can be used; cannot roll down to GA any longer. 10.5 Code level: FP1 Code level: FP1
  32. 32. © 2013 IBM Corporation © 2013 IBM Corporation32 Member 1 Member 2 1. db2stop member1 quiesce 3. db2start member1 2. installFixPack –online_update member1 inst1 4. db2stop member2 quiesce 5. installFixPack –online_update member2 inst1 6. db2start member2 C C Rolling Fix Pack Updates – Example Two member cluster (each at GA level) with clients (C) connecting into each member 1. Member 1 is quiesced – clients all move to Member 2 2. DB2 binaries updated on Member 1 3. Member 1 started again and a portion of the clients get rerouted to Member 1 to balance the workload 4. Member 2 is quiesced – clients all move to Member 1 5. DB2 binaries updated on Member 2 6. Member 2 started again and a portion of the clients get rerouted to member 2 to balance the workload At this point, code is at FP1 level, but can't use any new FP1 features; can test stability and roll down to GA level if necessary 7. Updates are committed The instance is now completely running at FP1 and new features can be used; cannot roll down to GA any longer. 10.5 Code level: FP1 Code level: FP1 7. installFixPack –commit_level inst1
  33. 33. © 2013 IBM Corporation Eliminating complexity: Installing fixpacks prior to 10.5  Manual lookup of TSA / GPFS levels (db2cktsa / db2ckgpfs)  Global “db2stop”  If applicable, enter maintenance mode (for cfs and cm)  installFixPack –b <base_install_path> -p <target_install_path>  If applicable, exit maintenance mode (for cfs and cm)  db2iupdt <instanceName>  db2cluster –cfs/cm –commit  Global “db2start”
  34. 34. © 2013 IBM Corporation Eliminating complexity: Installing fixpacks in 10.5  ONE command installFixPack  Now accepts <instanceName> as a parameter: installFixPack -p <targetfp_installation_path> -l <install-log-path> –I <InstName> – When –I <instanceName> is provided (pureScale), manual steps (pre 10.5) are automatically invoked on the host/machine e.g.: • GPFS/TSA/RSCT stopped / put into maintenance mode as necessary • New binaries (DB2 and cluster services) deployed • Member is started – No need to even do db2iupdt  When all hosts have been processed as described above, the new fixpack level can be committed using the “commit_level” switch of installFixPack – Performs “commit” of DB2 and cluster services code (GPFS/TSA/RSCT) 10.5
  35. 35. © 2013 IBM Corporation © 2013 IBM Corporation35 Rolling Fix Pack Updates: Best Practices  One host at a time  Do member’s first  Secondary CF before primary CF so you only have one failover  Then primary CF* * Suggestion: Do primary CF during a time of lower activity 10.5
  36. 36. © 2013 IBM Corporation Miscellaneous install improvements Passwordless root ssh access is now optional –Install requires you to do a host by host install instead of initiating it at a single host and having it deploy it for you
  37. 37. © 2013 IBM Corporation  New members can be added to an instance while it is online – No impact to workloads running on existing members – Previously, required an outage of the entire instance to add a new member  No change in add member command  Offline backup no longer needed after adding new members 37 Online Add Member Log LogLogLog MemberMemberMemberMember CF CF 10.5
  38. 38. © 2013 IBM Corporation  New members can be added to an instance while it is online – No impact to workloads running on existing members – Previously, required an outage of the entire instance to add a new member  No change in add member command  Offline backup no longer needed after adding new members 38 Online Add Member Log LogLogLog Member added online db2iupdt –add –m <newHost> -mnet <networkName> <instance> Log MemberMemberMemberMemberMember CF CF 10.5
  39. 39. © 2013 IBM Corporation 39 Workload Consolidation: Member Subsets  Previously, an application/tenant could only be configured to run 1. On one member (client affinity) or 2. Across all members in cluster (workload balancing)  Can now point applications to subsets of members which enables – Isolation of batch from transactional workloads – Multiple databases in a single instance can be isolated from each other Log LogLogLog Member Log Member Member Member Member CFCF Batch OLTPBatch OLTP 10.5
  40. 40. © 2013 IBM Corporation 40 Workload Consolidation: Member Subsets  Previously, an application/tenant could only be configured to run 1. On one member (client affinity) or 2. Across all members in cluster (workload balancing)  Can now point applications to subsets of members which enables – Isolation of batch from transactional workloads – Multiple databases in a single instance can be isolated from each other Log LogLogLog Member Log Member Member Member Member CFCF Batch OLTPBatch OLTP 10.5
  41. 41. © 2013 IBM Corporation 41 Workload Consolidation: Member Subsets Assume I have a database called MYDB and I want all OLTP apps connecting to it to go to members 0, 1, 2 only CALL SYSPROC.WLM_CREATE_MEMBER_SUBSET( ‘OLTP_DB’,’<databaseAlias>MYOLTP</databaseAlias>’,’(0,1,2)’) Will create a local alias called MYOLTP which OLTP applications can connect to M0 M1 M2 M3 M4 OLTPAPP CONNECT TO MYOLTP MYOLTP 10.5
  42. 42. © 2013 IBM Corporation 42 Workload Consolidation: Member Subsets Say I want to add another member to my OLTP subset since the OLTP workload is heavier than I expected CALL SYSPROC.WLM_ALTER_MEMBER_SUBSET( ‘OLTP_APP’, NULL, ‘( ADD 3 )’ ) M0 M1 M2 M3 M4 OLTPAPP MYOLTP 10.5
  43. 43. © 2013 IBM Corporation © 2013 IBM Corporation43 Workload Consolidation: Self-Tuning Memory Management (STMM)  Prior DB2 pureScale STMM design – Single tuning member makes local tuning decisions based on workload running on that member • Other member becomes tuning member in case of member failure – Broadcasts tuning decisions to other members – Works well in single homogeneous workload scenarios  DB2 pureScale now allows per-member STMM tuning – Workload consolidation – Multi-tenancy – Batch workloads – Affinitized workloads Member STMM Daemon Member STMM Daemon Member STMM Daemon Member STMM Daemon Workload 1 Workload 2 Workload 3 Workload 4 10.5
  44. 44. © 2013 IBM Corporation © 2013 IBM Corporation44 ESE to/from pureScale Backup and Restore Data Log Member 2 ESE • OFFLINE backup required Log Data LogLogLog Member 0 Log Member 1 Member 2 Member 3 Member 4 CFCF OFFLINE Backup Restore 10.5
  45. 45. © 2013 IBM Corporation © 2013 IBM Corporation45 pureScale Topology Changing Backup and Restore  BACKUP from instance which has a subset of members to instance with super set – OFFLINE BACKUP _NOT_ required Log Data LogLogLog Member 0 Log Member 1 Member 2 Member 3 Member 4 CFCF Log Data LogLog Member 0 Member 1 Member 2 CFCF ONLINE Backup Restore Clients 10.5
  46. 46. © 2013 IBM Corporation © 2013 IBM Corporation46 pureScale Topology Changing Backup and Restore  BACKUP from instance which has a superset of members to instance subset of members – OFFLINE BACKUP required Log Data LogLogLog Member 0 Log Member 1 Member 2 Member 3 Member 4 CFCF Log Data LogLog Member 0 Member 1 Member 2 CFCF OFFLINE Backup Restore 10.5
  47. 47. © 2013 IBM Corporation June 19, 2013 DB2 10.5 Near-Term Futures Peek
  48. 48. © 2013 IBM Corporation © 2013 IBM Corporation48 Performance: Explicit Hierarchical Locking (EHL)  Designed to remove data sharing costs for tables/partitions that are only accessed by a single member – Avoids CF communication if object sharing not occurring  Target scenarios – Workload affinitization – Workload consolidation and application affinitization  Enabled via new OPT_DIRECT_WRKLD database configuration parameter – Detection of data access patterns happens automatically and EHL will kick in when data is not being shared after configuration parameter set Member Member Member Member Table or Partition A Table or Partition B Table or Partition C Table or Partition D CF CF No member/CF communication necessary Peek
  49. 49. © 2013 IBM Corporation Misc  Online (inplace) table reorg Peek
  50. 50. © 2013 IBM Corporation DB2 10.5 with BLU Acceleration now electronically available! 50 Need webcast troubleshooting help? Click attachments http://ibm.co/db2download Download the free 90-day trial! • Test drive BLU Acceleration, as discussed in other Tech Talks • Try the new pureScale enhancements as discussed here • pureScale works on AIX and Linux 64 bit only • Supported RDMA network adapter required • Refer to the DB2 Info Center for pureScale requirements: http://bit.ly/DB2105Infocenter
  51. 51. © 2013 IBM Corporation 51 DB2 Tech Talk: Technical Tour of DB2 10.5 with BLU Acceleration Next Steps Roadmap Reference Call IBM to schedule a demo or learn more • 1 800 966-9875 (U.S) • 1-888-746-7426 (Canada) • 1800-425-3333 (India) • Or visit http://www.ibm.com/planetwide/ for contact information worldwide IBM DB2 10.5 product page Ibm.com/db2 IBM DB2 10.5 Product features ibm.co/12c1PJz Tech forum on developerWorks bit.ly/db2forumluw Rick Swagerman SQL Tips Blog: www.sqltips4db2.com Listen to the DB2 Technical Tour and Introduction to DB2 10.5 • bit.ly/tt2013may8 Read the technical information • developerWorks What’s new in DB2 10.5: ibm.co/16cxr7l o ibm.co/16cxr7l • DB2 pureScale Features ‒ bit.ly/dW_purescale_article • DB2 Info Center Information, search on pureScale ‒ http://bit.ly/DB2105Infocenter Download the DB2 Trial Software  Software download: ibm.co/db2download Connect with your Peers and IBM experts DB2 for Linux UNIX and Windows forum: bit.ly/db2forumluw Step Three Step Two Step One Step Four Need webcast troubleshooting help? Click attachments
  52. 52. © 2013 IBM Corporation 52 Upcoming Tech Talks Don’t miss these in-depth DB2 10.1 feature talks! Dates and topics subject to change and modification. How to register : DB2 Tech Talks web site Next DB2 Tech Talk: Adopt BLU Acceleration the Faster Easier Way • July 25, 2013 at 12:30 PM • Daniel Zilio and Marcia Miskimen, IBM Labs • Registration: bit.ly/tt2013jul Next IDUG DB2 Tech Conference Australia • In-person conference sponsored by IDUG • Melbourne, Australia • September • Agenda and registration: www.idug.org, select events Information on Demand Conference • November 3 – 7, 2013 • Las Vegas, Nevada • Information: bit.ly/iod2013 Need webcast troubleshooting help? Click attachments
  53. 53. © 2013 IBM Corporation DB2 Tech Talk 53 Need webcast troubleshooting help? Click attachments
  54. 54. © 2013 IBM Corporation 54 Need webcast troubleshooting help? Click attachments Questions Listening in replay? Questions: www.sqltips4db2.com Click submit a question.
  55. 55. © 2013 IBM Corporation 55 Need webcast troubleshooting help? Click attachments Thanks for attending! Please rate the session Presentation download: bit.ly/ttfilejun20 click Attachments in this webcast environment

×