DB2 10 for z/OS includes major enhancements to memory management that allow most DB2 storage objects to reside above the 2GB bar, providing up to a 10x increase in threads per subsystem. This reduces a key scalability limitation. To take advantage of these virtual storage improvements, additional real memory is required, typically a 10-30% increase over DB2 9 requirements. Customers should also monitor and manage real storage usage with new DB2 10 functions to avoid paging issues. The virtual storage changes along with other DB2 10 capabilities could allow for reduced DB2 subsystem counts and improved performance.
Db2 10 memory management uk db2 user group june 2013 [read-only]Laura Hood
DB2 10 provides significant enhancements to memory management that allow for much greater scalability. Key changes include moving most objects above the 2GB bar, enabling larger buffer pools through 1MB page support, and enhanced real storage monitoring. Migrating to DB2 10 requires ensuring sufficient real storage is available, monitoring real storage usage, and addressing other limiting factors before taking advantage of new features to further scale vertically.
DB2 Design for High Availability and ScalabilitySurekha Parekh
Are you overwhelmed by the growing amount of data in your environment? Are you maximizing application availability? As the number of tables with billions of rows continues to grow, so do the management challenges. In this session, we will discuss the challenges and solutions for optimum availability and performance, with techniques to efficiently and effectively manage very large amounts of data.
IBM DB2 Analytics Accelerator Trends & Directions by Namik Hrle Surekha Parekh
IBM DB2 Analytics Accelerator has drawn lots of attention from DB2 for z/OS users. In many respects it presents itself as just another DB2 access path (but what a powerful one!) and its deep integration into DB2 as well as application transparency makes it one of the most exciting DB2 enhancements in years. The IBM DB2 Analytics Accelerator complements DB2 by adding industry leading data intensive complex query performance thanks to being powered by the Netezza engine and enhances DB2 to the ultimate database management system that delivers the best of both worlds: transactional as well as analytical workloads. This presentation brings the latest news from the IDAA development and shows the trends and directions in which this technology develops.
Educational seminar lessons learned from customer db2 for z os health check...John Campbell
This presentation presented at the Polish DB2 User Group introduces and discusses the most common issues uncovered by the DB2 for z/OS Development SWAT Team from 360 Degree DB2 for z/OS Continuous Availability Assessment (DB2 360) Studies.
DB2 10 Webcast #2 - Justifying The UpgradeLaura Hood
This document discusses justifying an upgrade from DB2 9 or 8 to DB2 10 for z/OS. It outlines potential CPU, productivity, and availability savings from the upgrade. CPU savings can come from improved performance in conversion mode through features like high performance database application transition support. Productivity savings may result from features that improve plan stability and temporal tables. Availability improvements like online reorganization of LOBs can reduce downtime costs. The presentation recommends using IBM's DB2 10 Business Value Assessment Estimator Tool to quantify specific savings for an organization.
DB2 11 for z/OS Migration Planning and Early Customer ExperiencesJohn Campbell
This extensive presentation provides help and guidance to help DB2 for z/OS customer migrate as quickly as possible, but safely to V11. The material will provide additional planning information, share customer customer experiences and best practices.
Db2 10 memory management uk db2 user group june 2013 [read-only]Laura Hood
DB2 10 provides significant enhancements to memory management that allow for much greater scalability. Key changes include moving most objects above the 2GB bar, enabling larger buffer pools through 1MB page support, and enhanced real storage monitoring. Migrating to DB2 10 requires ensuring sufficient real storage is available, monitoring real storage usage, and addressing other limiting factors before taking advantage of new features to further scale vertically.
DB2 Design for High Availability and ScalabilitySurekha Parekh
Are you overwhelmed by the growing amount of data in your environment? Are you maximizing application availability? As the number of tables with billions of rows continues to grow, so do the management challenges. In this session, we will discuss the challenges and solutions for optimum availability and performance, with techniques to efficiently and effectively manage very large amounts of data.
IBM DB2 Analytics Accelerator Trends & Directions by Namik Hrle Surekha Parekh
IBM DB2 Analytics Accelerator has drawn lots of attention from DB2 for z/OS users. In many respects it presents itself as just another DB2 access path (but what a powerful one!) and its deep integration into DB2 as well as application transparency makes it one of the most exciting DB2 enhancements in years. The IBM DB2 Analytics Accelerator complements DB2 by adding industry leading data intensive complex query performance thanks to being powered by the Netezza engine and enhances DB2 to the ultimate database management system that delivers the best of both worlds: transactional as well as analytical workloads. This presentation brings the latest news from the IDAA development and shows the trends and directions in which this technology develops.
Educational seminar lessons learned from customer db2 for z os health check...John Campbell
This presentation presented at the Polish DB2 User Group introduces and discusses the most common issues uncovered by the DB2 for z/OS Development SWAT Team from 360 Degree DB2 for z/OS Continuous Availability Assessment (DB2 360) Studies.
DB2 10 Webcast #2 - Justifying The UpgradeLaura Hood
This document discusses justifying an upgrade from DB2 9 or 8 to DB2 10 for z/OS. It outlines potential CPU, productivity, and availability savings from the upgrade. CPU savings can come from improved performance in conversion mode through features like high performance database application transition support. Productivity savings may result from features that improve plan stability and temporal tables. Availability improvements like online reorganization of LOBs can reduce downtime costs. The presentation recommends using IBM's DB2 10 Business Value Assessment Estimator Tool to quantify specific savings for an organization.
DB2 11 for z/OS Migration Planning and Early Customer ExperiencesJohn Campbell
This extensive presentation provides help and guidance to help DB2 for z/OS customer migrate as quickly as possible, but safely to V11. The material will provide additional planning information, share customer customer experiences and best practices.
This document provides information and recommendations for using the IMS Catalog. Key points include:
- The Catalog acts as a metadata repository but is not a full data dictionary. It lacks definitions for business elements.
- Catalog structures are based on time stamps rather than relationships between changes.
- Multiple datasets may be needed to partition the Catalog data by DBD and PSB.
- Operational procedures include the DFSU3ACB utility and CATPOP job to update the Catalog. Image copies are recommended.
The document discusses DB2's use of storage on the mainframe. It notes that DB2 uses VSAM data sets to store tablespaces, indexes, and other objects. These data sets can be managed by DB2 storage groups or SMS. Storage groups are lists of volumes where data sets are placed. The document recommends letting DB2 manage data sets using storage groups for less administrative work, but with less control, or defining your own data sets for more control but more work. It also provides details on where to find storage-related information in the DB2 catalog.
Best practices for DB2 for z/OS log based recoveryFlorence Dubois
The need to perform a DB2 log-based recovery of multiple objects is a very rare event, but statistically, it is more frequent than a true disaster recovery event (flood, fire, etc). Taking regular backups is necessary but far from sufficient for anything beyond minor application recovery. If not prepared, practiced and optimised, it can lead to extended application service downtimes – possibly many hours to several days. This presentation will provide many hints and tips on how to plan, design intelligently, stress test and optimise DB2 log-based recovery.
IBM recently announced the brand new Version of one of the industry's fastest Flash Storage Solution. The IBM Flashsystem 900. Now triple capacity and inline compression on top.
DB2 for z/OS - Starter's guide to memory monitoring and controlFlorence Dubois
DB2 for z/OS makes more and more use of REAL memory to improve performance and reduce cost. But if you don't carefully budget and monitor the use of REAL memory on your system, you could be putting your applications at risk. This presentation will go back to the basics and answer the most common questions about REAL memory management including: how does DB2 uses virtual and REAL memory? how to build a budget based on system settings and buffer pool sizes? how to size the LFAREA? what are the key performance indicators and how do I know I am running 'safely'? what can be done to protect the system?
DB2 for z/OS and DASD-based Disaster Recovery - Blowing away the mythsFlorence Dubois
Is your Disaster Recovery solution based on DASD replication functions? In most cases, all you will need to do is a normal restart of DB2 for z/OS. But this assumes the DASD copy is consistent. Otherwise, it is guaranteed data corruption that will have to be fixed up, possibly several weeks or months after the event. This presentation will tell you everything you need to know about the Copy Services for IBM System z and what is required to ensure data consistency. It will address the most common myths and misconceptions about these DASD replication solutions. It will also provide hints and tips on how to tune for fast DB2 restart and how to optimise GRECP/LPL recovery.
An Intro to Tuning Your SQL on DB2 for z/OSWillie Favero
This document provides an introduction to SQL tuning for a DB2 for z/OS environment. It was presented on March 1, 2011 by Willie Favero from IBM's Data Warehouse on System z Swat Team. The presentation covers various techniques for optimizing SQL queries and access paths in DB2 for z/OS, with the goal of improving query performance. It addresses topics such as monitoring wait times, buffer pool usage, checkpointing, WLM policies, sort techniques, and disk I/O optimization. The overall aim is to help database administrators understand how to analyze and "tune" queries to reduce response times and meet business performance objectives.
This document discusses IBM DB2 10.5 with BLU Acceleration. It introduces BLU Acceleration as a new technology that uses column-organized tables to provide significant improvements to storage, query performance, ease of use, and time-to-value for analytic workloads. The document outlines seven main ideas behind BLU Acceleration, including compute-friendly encoding and compression, keeping data compressed during evaluation, multiplying the power of CPUs using SIMD processing, core-friendly parallelism, working directly on columns to minimize I/O, and extreme data compression.
Planning and executing a DB2 11 for z/OS Migration by Ian Cook Surekha Parekh
This document discusses planning and executing a migration from DB2 10 to DB2 11 for z/OS. It begins with an overview of the DB2 11 Early Support Program (ESP) feedback, which was positive regarding performance, quality, and reliability. The presentation then covers key aspects of developing a migration project plan, including assembling a project team, identifying technical considerations, and creating a test plan. It emphasizes early elimination of risks and issues. Sample project frameworks are provided to help structure planning and testing across sandbox, development, and production environments. Attendees are advised to contact software vendors to coordinate DB2 version requirements.
A First Look at the DB2 10 DSNZPARM ChangesWillie Favero
This document discusses changes to DB2 subsystem parameter module (DSNZPARM) in DB2 10. It provides information on DSNZPARM macros, how parameters can be changed through installation panels or dynamically using -SET SYSPARM command, and differences between hidden, opaque and visible parameters. The document also introduces new documentation for opaque parameters and explains how to display current DSNZPARM settings using sample program DSN8ED7.
The document does not contain enough content to summarize. It only contains the word "Adv" which provides no meaningful context or information to extract a multi-sentence summary from.
DbB 10 Webcast #3 The Secrets Of ScalabilityLaura Hood
The third in the Migration Month webcast series looking at DB2 10 migration planning. This webcast goes into the scalability benefits available in DB2 10, with Julian Stuhler of Triton Consulting & Jeff Josten of IBM.
This document discusses justifying an upgrade from DB2 9 or 8 to DB2 10 for z/OS. It outlines potential CPU, productivity, and availability savings from the upgrade. CPU savings can come from improved performance in conversion mode through features like high performance database access threads. Productivity savings may result from reduced subsystem consolidation time. Availability improvements like online REORG for LOBs can reduce downtime costs. The presentation recommends using IBM's Business Value Assessment Estimator Tool to quantify specific savings for an organization.
DB2 10 Webcast #1 Overview And Migration PlanningCarol Davis-Mann
DB2 10 for z/OS provides many new features and performance enhancements over previous versions. Migrating to DB2 10 involves following standard upgrade procedures, meeting all technical prerequisites, moving to conversion mode, then enabling new functions mode. Customers on DB2 8 can also do a "skip migration" directly to DB2 10. IBM offers workshops to help customers plan their DB2 10 migrations.
DB2 for z/OS Real Storage Monitoring, Control and PlanningJohn Campbell
Just added another hot DB2 topic around DB2 for z/OS Real Storage Monitoring, Control and Planning - Check it out and make sure your system runs safely
IMS 14 includes many new features to improve agility, application deployment and management, integration with DB2, business growth capabilities, infrastructure enhancements, and database and transaction manager enhancements. Key highlights include enhancements to support dynamic database changes, catalog management of resources, OSAM and DEDB improvements, SQL aggregation functions, DBRC and FDBR enhancements, reduced TCO, and cascaded transaction support across LPARs.
This document provides information and recommendations for using the IMS Catalog. Key points include:
- The Catalog acts as a metadata repository but is not a full data dictionary. It lacks definitions for business elements.
- Catalog structures are based on time stamps rather than relationships between changes.
- Multiple datasets may be needed to partition the Catalog data by DBD and PSB.
- Operational procedures include the DFSU3ACB utility and CATPOP job to update the Catalog. Image copies are recommended.
The document discusses DB2's use of storage on the mainframe. It notes that DB2 uses VSAM data sets to store tablespaces, indexes, and other objects. These data sets can be managed by DB2 storage groups or SMS. Storage groups are lists of volumes where data sets are placed. The document recommends letting DB2 manage data sets using storage groups for less administrative work, but with less control, or defining your own data sets for more control but more work. It also provides details on where to find storage-related information in the DB2 catalog.
Best practices for DB2 for z/OS log based recoveryFlorence Dubois
The need to perform a DB2 log-based recovery of multiple objects is a very rare event, but statistically, it is more frequent than a true disaster recovery event (flood, fire, etc). Taking regular backups is necessary but far from sufficient for anything beyond minor application recovery. If not prepared, practiced and optimised, it can lead to extended application service downtimes – possibly many hours to several days. This presentation will provide many hints and tips on how to plan, design intelligently, stress test and optimise DB2 log-based recovery.
IBM recently announced the brand new Version of one of the industry's fastest Flash Storage Solution. The IBM Flashsystem 900. Now triple capacity and inline compression on top.
DB2 for z/OS - Starter's guide to memory monitoring and controlFlorence Dubois
DB2 for z/OS makes more and more use of REAL memory to improve performance and reduce cost. But if you don't carefully budget and monitor the use of REAL memory on your system, you could be putting your applications at risk. This presentation will go back to the basics and answer the most common questions about REAL memory management including: how does DB2 uses virtual and REAL memory? how to build a budget based on system settings and buffer pool sizes? how to size the LFAREA? what are the key performance indicators and how do I know I am running 'safely'? what can be done to protect the system?
DB2 for z/OS and DASD-based Disaster Recovery - Blowing away the mythsFlorence Dubois
Is your Disaster Recovery solution based on DASD replication functions? In most cases, all you will need to do is a normal restart of DB2 for z/OS. But this assumes the DASD copy is consistent. Otherwise, it is guaranteed data corruption that will have to be fixed up, possibly several weeks or months after the event. This presentation will tell you everything you need to know about the Copy Services for IBM System z and what is required to ensure data consistency. It will address the most common myths and misconceptions about these DASD replication solutions. It will also provide hints and tips on how to tune for fast DB2 restart and how to optimise GRECP/LPL recovery.
An Intro to Tuning Your SQL on DB2 for z/OSWillie Favero
This document provides an introduction to SQL tuning for a DB2 for z/OS environment. It was presented on March 1, 2011 by Willie Favero from IBM's Data Warehouse on System z Swat Team. The presentation covers various techniques for optimizing SQL queries and access paths in DB2 for z/OS, with the goal of improving query performance. It addresses topics such as monitoring wait times, buffer pool usage, checkpointing, WLM policies, sort techniques, and disk I/O optimization. The overall aim is to help database administrators understand how to analyze and "tune" queries to reduce response times and meet business performance objectives.
This document discusses IBM DB2 10.5 with BLU Acceleration. It introduces BLU Acceleration as a new technology that uses column-organized tables to provide significant improvements to storage, query performance, ease of use, and time-to-value for analytic workloads. The document outlines seven main ideas behind BLU Acceleration, including compute-friendly encoding and compression, keeping data compressed during evaluation, multiplying the power of CPUs using SIMD processing, core-friendly parallelism, working directly on columns to minimize I/O, and extreme data compression.
Planning and executing a DB2 11 for z/OS Migration by Ian Cook Surekha Parekh
This document discusses planning and executing a migration from DB2 10 to DB2 11 for z/OS. It begins with an overview of the DB2 11 Early Support Program (ESP) feedback, which was positive regarding performance, quality, and reliability. The presentation then covers key aspects of developing a migration project plan, including assembling a project team, identifying technical considerations, and creating a test plan. It emphasizes early elimination of risks and issues. Sample project frameworks are provided to help structure planning and testing across sandbox, development, and production environments. Attendees are advised to contact software vendors to coordinate DB2 version requirements.
A First Look at the DB2 10 DSNZPARM ChangesWillie Favero
This document discusses changes to DB2 subsystem parameter module (DSNZPARM) in DB2 10. It provides information on DSNZPARM macros, how parameters can be changed through installation panels or dynamically using -SET SYSPARM command, and differences between hidden, opaque and visible parameters. The document also introduces new documentation for opaque parameters and explains how to display current DSNZPARM settings using sample program DSN8ED7.
The document does not contain enough content to summarize. It only contains the word "Adv" which provides no meaningful context or information to extract a multi-sentence summary from.
DbB 10 Webcast #3 The Secrets Of ScalabilityLaura Hood
The third in the Migration Month webcast series looking at DB2 10 migration planning. This webcast goes into the scalability benefits available in DB2 10, with Julian Stuhler of Triton Consulting & Jeff Josten of IBM.
This document discusses justifying an upgrade from DB2 9 or 8 to DB2 10 for z/OS. It outlines potential CPU, productivity, and availability savings from the upgrade. CPU savings can come from improved performance in conversion mode through features like high performance database access threads. Productivity savings may result from reduced subsystem consolidation time. Availability improvements like online REORG for LOBs can reduce downtime costs. The presentation recommends using IBM's Business Value Assessment Estimator Tool to quantify specific savings for an organization.
DB2 10 Webcast #1 Overview And Migration PlanningCarol Davis-Mann
DB2 10 for z/OS provides many new features and performance enhancements over previous versions. Migrating to DB2 10 involves following standard upgrade procedures, meeting all technical prerequisites, moving to conversion mode, then enabling new functions mode. Customers on DB2 8 can also do a "skip migration" directly to DB2 10. IBM offers workshops to help customers plan their DB2 10 migrations.
DB2 for z/OS Real Storage Monitoring, Control and PlanningJohn Campbell
Just added another hot DB2 topic around DB2 for z/OS Real Storage Monitoring, Control and Planning - Check it out and make sure your system runs safely
IMS 14 includes many new features to improve agility, application deployment and management, integration with DB2, business growth capabilities, infrastructure enhancements, and database and transaction manager enhancements. Key highlights include enhancements to support dynamic database changes, catalog management of resources, OSAM and DEDB improvements, SQL aggregation functions, DBRC and FDBR enhancements, reduced TCO, and cascaded transaction support across LPARs.
IBM Analytics Accelerator Trends & Directions Namk Hrle Surekha Parekh
IBM DB2 Analytics Accelerator has drawn lots of attention from DB2 for z/OS users. In many respects it presents itself as just another DB2 access path (but what a powerful one!) and its deep integration into DB2 as well as application transparency makes it one of the most exciting DB2 enhancements in years. The IBM DB2 Analytics Accelerator complements DB2 by adding industry leading data intensive complex query performance thanks to being powered by the Netezza engine and enhances DB2 to the ultimate database management system that delivers the best of both worlds: transactional as well as analytical workloads. This presentation brings the latest news from the IDAA development and shows the trends and directions in which this technology develops.
DB210 Smarter Database IBM Tech Forum 2011Laura Hood
DB2 10 for z/OS is a new version of IBM's database software that provides significant performance improvements, new security and temporal data features, and easier migration paths from prior versions. Key enhancements in DB2 10 include 5-20% CPU reductions, up to 10x more threads per subsystem due to virtual storage improvements, row and column access controls, and built-in support for tracking historical data. Customers running DB2 8 or 9 can upgrade directly to DB2 10 using new "skip migration" functionality, or upgrade sequentially from earlier versions. Migrating to DB2 10 requires meeting prerequisites and following steps to move to conversion mode and then normal mode.
This document discusses the benefits of IBM DB2 software in SAP environments. It provides examples of customers like Colgate-Palmolive and Coca-Cola Bottling Co. that achieved significant cost savings and performance improvements after migrating their SAP systems from Oracle to IBM DB2. One Swiss customer tested DB2 and Oracle on comparable hardware and found DB2 performed 48% better while using 30% less memory. DB2 also provided greater data compression and backup compression. The document outlines other advantages of DB2 like reduced storage needs, improved OLTP and OLAP performance, and lower licensing costs.
DB2 pureScale provides a highly scalable and available database solution. It allows customers to start small and grow capacity easily by adding additional cluster members without disrupting applications or incurring extra costs. DB2 pureScale uses a shared nothing architecture with each member running on its own server. It provides a single system view to clients and automatically balances workload across members. Critical features include unlimited scalability, continuous availability even during member failures, and the ability to perform maintenance without outages.
DB2 for z/OS is well-suited for managing big data due to its ability to scale, high availability, strong security, and high performance. It has supported some of the largest databases and workloads in the world. Migrating to DB2 10 for z/OS provides improvements like reduced CPU usage, more concurrency, and online changes without downtime. DB2 for z/OS also has a long history and maturity as a mission-critical database.
Engage 2018: IBM Notes and Domino Performance Boost - Reloadedpanagenda
There is always room for improvement! Maximizing the IBM Notes client and Domino server performance doesn’t have to be complicated. Reloaded for the latest IBM Notes/Domino 9 version (9.0.1 Feature Pack 10 or later), join Chris and Luis to find out the best and latest performance tuning tips. Learn how to debug your clients(s) and server(s), deal with outdated ODS, network latency, application/mail performance issues and more. Improve your IBM Notes client installations to provide a better experience for happier administration and happier end users! As a special bonus, Chris will show you how to reduce the startup time of virtualized IBM Notes Clients (Citrix / VMWare / etc).
Engage 2018: IBM Notes and Domino Performance Boost - Reloaded Christoph Adler
Created by Christoph Adler (panagenda) & Luis Guirigay (IBM)
There is always room for improvement! Maximizing the IBM Notes client and Domino server performance doesn't have to be complicated. Reloaded for the latest IBM Notes/Domino 9 version (9.0.1 Feature Pack 10 or later), join Chris and Luis to find out the best and latest performance tuning tips. Learn how to debug your clients(s) and server(s), deal with outdated ODS, network latency, application/mail performance issues and more. Improve your IBM Notes client installations to provide a better experience for happier administration and happier end users! As a special bonus, Chris will show you how to reduce the startup time of virtualized IBM Notes Clients (Citrix / VMWare / etc).
System z Technology Summit Streamlining UtilitiesSurekha Parekh
Most DB2 applications are global non-stop, requiring almost
100% accessibility. Availability demands reduce the amount
of time available to perform necessary routine tasks, such as
utility maintenance on the underlying data and objects stored
in DB2 for z/OS that support critical business applications. In
addition, companies are looking for ways to streamline DB2 utility
processing to maximize system and personnel resources. How
valuable would it be to maximize your use of IBM DB2 Utilities
Suite for z/OS for both DB2 9 and DB2 10? What if you could
establish DB2 utility practices at a company level and know
that they would be monitored and adhered to? Do you want
to reduce your batch window during utility sort processing to
improve availability and performance? How important would it
be to run utilities only on objects when and if it’s necessary?
The answers to these questions and more will be revealed in
this session.
This document provides an overview of IBM's Hadoop solution on Power Systems, including:
- The basic architecture of IBM's Hadoop solution using Power Systems servers and GPFS storage.
- Considerations for sizing a Hadoop cluster, such as compression rates and space for shuffle/sort data.
- The IBM Solution for Hadoop POWER System edition and IBM Data Engine for Analytics solutions.
- Networking recommendations for Hadoop clusters including appropriate switches and cabling.
This document provides an overview of IBM DB2 9, including:
- The various editions of DB2 9 for different use cases and hardware configurations
- The common code shared across operating system platforms
- Additional products and features including add-ons, clients, extenders, and connectivity tools
- Descriptions of the main administration and development tools provided with DB2 9
This document discusses considerations for migrating to DB2 10 from earlier versions. It notes that IBM is ending support for DB2 V8 in 2012, prompting many organizations to migrate. Key topics covered include potential issues with skipping versions in migration, features deprecated in later versions, checking software prerequisites, and rebinding plans and packages to adjust to changes in access paths. The document aims to provide guidance on planning a smoother migration process.
1. DB2 Data Sharing allows applications running on multiple DB2 subsystems to concurrently read and write to the same data, providing high scalability, performance, and continuous availability.
2. It provides benefits like increased capacity, continuous availability during planned and unplanned outages, easier growth accommodation, and dynamic workload balancing.
3. The Parallel Sysplex and Data Sharing architecture, along with features like rolling maintenance and dynamic workload balancing, work to ensure continuous availability even if a DB2 subsystem or z/OS system fails.
Paradigm shift in IBM's OLAP solutions and look deeply at IBM Cognos 10.2 Dynamic Cubes. View the webinar video recording and download this deck: http://www.senturus.com/resources/dynamic-cubesin-cognos-10-2-jan/.
This webinar included discussions and demonstrations of IBM Cognos 10.2 Cube Designer infrastructure requirements and deployment proven practices, Dynamic Cube Designer, and the world of OLAP in 2013.
Senturus, a business analytics consulting firm, has a resource library with hundreds of free recorded webinars, trainings, demos and unbiased product reviews. Take a look and share them with your colleagues and friends: http://www.senturus.com/resources/.
A Time Traveller's Guide to DB2: Technology Themes for 2014 and BeyondLaura Hood
This document discusses technology themes for DB2 in 2014 and beyond, including cost reduction, high availability, in-memory computing, skills availability, database commoditization, and big data. It summarizes DB2's focus on these areas today and potential future directions, such as further optimization to reduce software licensing fees, expanded data sharing capabilities, increased memory capacities, evolving skills needs, and continued integration with big data platforms. The document aims to help DB2 professionals consider strategies for addressing these themes.
Similar to Db2 10 memory management uk db2 user group june 2013 (20)
In part 1 of our new series of DB2 Support Nightmares we look at the implications of only having one userid for all users to use and the frighteningly consequences.
DB2 User Day Keynote by Julian Stuhler. DB2 Trends and Directions, The Signal...Carol Davis-Mann
DB2 Day Keynote Presentation - DB2 Trends and Directions, The Signals are Talking from Julian Stuhler, Solutions Delivery Director at Triton Consulting, IBM Gold Consultant and IBM Champion.
What do you do when disaster strikes? In part 9 of our DB2 Support Nightmare series we look at another DB2 disaster scenario and how it was resolved by the experts at Triton Consulting.
This document discusses a common nightmare scenario for junior DBAs where a critical production database is accidentally dropped. It describes how a junior DBA, left in charge while the senior DBA was on holiday, mistakenly dropped the live production database thinking they were connected to the test system. Luckily, the Triton support team was able to assist with a full recovery, but complications resulted in nearly a full day of lost business. The document recommends color coding GUI/Telnet sessions, restricting direct access to production data, and having proper cover during absences to avoid such mistakes.
The document discusses improving DBA productivity through scripting database administration tasks. It recommends that DBAs perform tasks from the command line using scripts to make actions repeatable and recorded. While some DBAs may think this is overkill for a single database, it is critical for full development lifecycles to manage configurations effectively. The document also provides a tip to use db2look to verify database structure consistency across testing environments and concludes that striving for high application performance should not forget improving DBA productivity.
A junior DBA accidentally deleted all rows from a critical table in a pre-production environment. The DBA had connected to the wrong system and used the instance owner userid. The system administrator had enabled the FED_NOAUTH parameter, which bypasses authentication at the instance level. This meant any user could connect as any other user without the correct password and impact the database. The moral is that unintended consequences can occur from small configuration changes and it is important to get skilled DB2 support.
3. The Information Management Specialists
Agenda
• Introduction
• What’s Changed & Why?
• What Does It Mean for Me?
• Summary & Questions
Win a limited edition 30th
Anniversary DB2 Geek T-Shirt
for asking me a question!
4. The Information Management Specialists
Introduction
• Julian Stuhler
Director and Principal Consultant at Triton
Consulting
25 years DB2 experience, 20 as a consultant working with
customers in UK, Europe and the US
IBM Gold Consultant since 1999
IBM Information Champion
IDUG Past President
Author of IBM Redbooks, white papers and more recently
“flashbooks”
Designer of IBM’s DB2 10 Business Value Assessment Estimator
Tool
6. The Information Management Specialists
The Need for Scalability
• IT volumes continue to increase
More applications
More data
More transactions
• Performance is ever more important
Customers need to support workload growth without a drop-off in
performance
• Availability is ever more important
Pressure to reduce both planned and unplanned outages
• End result: each DB2 environment is being asked to work harder, with less
downtime
• Every DB2 release attempts to push back these boundaries, but major
progress has been made in DB2 10
7. The Information Management Specialists
DB2 Storage Usage – DBM1 storage
below the bar
0 231
(2GB)
232
(4GB)
“The Bar”
224
(16MB)
“The Line”
Typically 800 – 1900 MB
Available to DB2
Typically 7 – 9 MB
Available to DB2
8. The Information Management Specialists
Virtual Storage Enhancements
• V8 began a major project to
transform DB2 into a 64-bit RDBMS
Laid the groundwork and provided
some scalability improvements but a
lot of DBM1 objects remained below
the 2GB bar
• DB2 9 improved things a little, but
only by another 10-15% for most
customers
Practical limit of 300-500 threads per
DB2 subsystem
• DB2 10 moves 80-90% of the
remaining objects above the
bar, resulting in 5-10x improvement
in threads per subsystem (CM)
10. The Information Management Specialists
Real Storage Enhancements
• For prior releases, z/OS
always managed DB2
bufferpool pages as 4K
frames
• Move to 64-bit architecture
made much larger buffer
pools viable
Bufferpools can use many
millions of pages
Increased z/OS overheads
for page management
DB2 9 Buffer Pool
z/OS Storage
4K
Pages
4K
Pages
11. The Information Management Specialists
Real Storage Enhancements
• DB2 10 introduces support for 1MB
pages to reduce z/OS page
management overheads
Needs z10/z196/zEC12 server
Needs bufferpool to be defined
with PGFIX=YES
z/OS sysprogs must partition real
storage between 4K and 1MB
frames (IESYSnn in PARMLIB, needs
IPL) so wait until DB2 10 is bedded
in
• Key part of potential DB2 10 CPU
reduction
Customer testing during beta
program showed CPU reductions of
0-6% with this feature enabled
DB2 10 Buffer Pool
z/OS Storage
4K
Pages
1MB
Pages
13. The Information Management Specialists
Real Storage Availability
• DB2 10 removes most virtual storage
constraints, but you need sufficient
real storage to back any increased
virtual storage usage
Paging will still kill you in a 64-bit
environment, should be near zero
• Plan on additional 10-30% real memory for DB2 following
migration from DB2 9
Most customers will be at lower end of this range, but more will
be required once you start using some DB2 10 capabilities.
Skip migration customers will need more
14. The Information Management Specialists
Real Storage Availability
• Insufficient real storage to back usage of virtual leads to paging activity
• It is critical to ensure that page-in activity (aka “demand paging”) for DB2
address spaces is minimised (near zero)
No expanded storage in 64-bit environment, all paging is to disk (AUX)
Any page-in operation is very expensive in performance terms compared to
page hit in real storage
Note that page-out operations are normal for rarely-used pages and not
usually a cause for concern
• Real storage shortages can have serious impact on stability of overall
system
If all AUX is consumed, LPAR goes into wait state and may fail
Can lead to long system dump processing times, with high risk of system-wide
slowdowns and incomplete dumps
15. The Information Management Specialists
Real Storage Availability
• You also need to allow approx. 16GB for DB2 dump requirement (twice the
8GB value recommended for DB2 8 and 9)
MAXSPACE parameter defines max amount of virtual storage for SVC dump –
z/OS default is 500MB
Some customer horror stories due to insufficient storage being available for
dumps
• Good news if you’re on a z196, as the “technology dividend” means that
cost per GB is around 75% less than for a z10
Cheaper still for zEC12
• Many customers are already running lean on real storage even under V9,
and are building real storage increase costs into their DB2 10 financial
justifications
16. The Information Management Specialists
Real Storage Monitoring
• Statistics IFCID 225 has long been vital for DB2 storage monitoring
Part of Statistics Class 1 trace since PQ99658, so now enabled by default
• Once DB2 10 is implemented in your environment, focus should change
from virtual to real storage monitoring
• PM24723 and PM37647 introduce important real storage monitoring and
contraction enhancements
ICFID 225 enhanced with new fields to externalise real and auxiliary storage
consumption for storage objects in private, shared, and common areas above
the bar (see additional information at end of presentation)
Introduces two new DSNZPARMs to tell DB2 if and how to release any unused
real storage (REALSTORAGE_MANAGEMENT) and specify upper limit on DB2
real storage usage (REALSTORAGE_MAX) – see next slide
Some increase in MSTR CPU due to storage monitoring. Make sure PTFs for
z/OS APAR OA37821 and corresponding DB2 APAR PM49816 are also applied –
see later
17. The Information Management Specialists
Real Storage Monitoring
• Opaque DSNZPARMs introduced by PM24723 and PM37647
• REALSTORAGE_MANAGEMENT
ON – Unused backed real frames discarded when possible (CPU overhead)
OFF – DB2 will only discard unused frames when critical real storage or auxiliary storage usage
is detected
AUTO (default) – DB2 will discard unused frames when the system begins to page
Recommended value = AUTO
DSNV516I and DSNV517I written when DB2 enters and exits real storage contraction mode
• REALSTORAGE_MAX
Hard limit on real and auxiliary storage used by DB2 subsystem – DB2 will terminate if limit
reached
Valid values: NOLIMIT (default), 1 – 65,535 (GB)
Recommended value = 2 x amount of real and auxiliary storage that the subsystem might
reasonably consume
DSNS003I written when DB2 approaches the threshold and DSNS004I written to indicate relief
from this condition
18. The Information Management Specialists
Real Storage – Other Issues
• Ensure PTFs for z/OS APAR APAR OA37821 and corresponding DB2 APAR PM49816
are applied
Fixes MSTR CPU issue associated with MVS COUNTPAGES function used for real storage
monitoring (introduced by our good friend PM24723)
Especially noticable where more than one DB2 subsystem resides on same LPAR,or on an idle
system
Needs IPL to implement z/OS fix
Both APARs marked as HIPER – you are strongly advised to implement the associated PTFs
before migrating to DB2 10 in any production environments
• What about CONTSTOR and MINSTOR?
Enabling these ZPARMs in previous releases allowed you to spend a little more CPU in
exchange for improved virtual storage utilisation
Both ZPARMs apply to 31-bit storage only, so are less important in DB2 10
Recommendation is CONTSTOR=MINSTOR=NO once you have proven VSCR in DB2 10
19. The Information Management Specialists
Other Limiting Factors
• DBM1 Virtual Storage should no longer be an issue, but
other limiting factors on vertical scalability still remain
ESQA/ECSA (31-bit) storage
Active log write contention (LC19)
SMF volumes (DB2 10 SMF compression can help)
20. The Information Management Specialists
Use New DB2 10 Features
• Only consider use of new features when you are sure
you have fully considered all the previous items and
DB2 10 is properly “bedded in”
• Remember that some VSCR enhancements are
available in CM, but you need package rebind to get
maximum benefits
21. The Information Management Specialists
Use New DB2 10 Features
• Exploit 1MB real storage frames
Needs PGFIX=YES, but many customers still haven’t exploited
this feature in their DB2 8 and DB2 9 systems despite significant
potential CPU savings (up to 6% seen)
PGFIX=YES benefits dependent on I/O rate, and you need to
back pools 100% with real storage (scary if you’re already
running lean on real storage availability)
1MB page frames specified by LFAREA in IEASYSnn parmlib
member, and need IPL to implement
► Use /DISPLAY VIRTSTOR,LFAREA after implementation to ensure sizing
is OK, as conversion between 4K and 1MB frames costs CPU
Ensure you are up to date on z/OS maintenance before enabling
22. The Information Management Specialists
DB2 10 Real Storage Enhancements
• 1MB page frame support for buffer pools
CPU savings of up to 4% by reducing z/OS
page management overheads for big BPs
► DB2 BPs can be up to 1TB total in DB2 9 and
10, with limit of 2x available real storage
z/OS sysprogs must partition real storage
between 4K and 1MB frames
► LFAREA parm in IEASYSnn PARMLIB
(expressed in %, MB or GB, 80% max)
► Need IPL to change LFAREA, so ensure DB2 10
is properly “bedded in” before implementing!
23. The Information Management Specialists
DB2 10 Real Storage Enhancements
• z/OS can decompose 1MB pages into 256 x 4KB pages, or recombine 4KB pages
into 1MB pages if SOS condition occurs
Costs CPU and elapsed time so should be avoided by setting LFAREA appropriately
LFAREA
Decompose / recombine
24. The Information Management Specialists
Tuning – Setting LFAREA
• Sizing guideline
Review BPs and set PGFIX=YES where suitable
► Ensure sufficient real storage to back BP
► See BP tuning section earlier
Set LFAREA = SUM (page-fixed BPs) + 10%
► Assumes DB2 is only major user of 1MB page frames, but allows 10% “wriggle
room”
Verify sizing is correct (after IPL and DB2 BP allocation!)
► /DISPLAY VIRTSTOR,LFAREA (no decomposition)
► -DIS BUFFERPOOL(nn) SERVICE=4 (no 4K pages used for page-fixed buffer
pools)
• Review LFAREA whenever BP sizes, page-fix attribute etc is changed
Sysprogs and DBAs must co-ordinate activities (should be BAU!)
25. The Information Management Specialists
Real Storage Monitoring
• Monitor use of 1MB page frames used by a specific BP
-DISPLAY BUFFERPOOL(BPnn) SERVICE=4
Resultant DSNB999I message shows number of 1MB pages in use
-DBA1 DIS BUFFERPOOL(BP0) SERVICE=4
DSNB401I -DBA1 BUFFERPOOL NAME BP0, BUFFERPOOL ID 0, USE COUNT 246
DSNB402I -DBA1 BUFFER POOL SIZE = 5000 BUFFERS AUTOSIZE = NO 641
ALLOCATED = 5000 TO BE DELETED = 0
IN-USE/UPDATED = 172
DSNB406I -DBA1 PGFIX ATTRIBUTE - 642
CURRENT = NO
PENDING = NO
PAGE STEALING METHOD = LRU
DSNB404I -DBA1 THRESHOLDS - 643
VP SEQUENTIAL = 80
DEFERRED WRITE = 30 VERTICAL DEFERRED WRT = 5, 0
PARALLEL SEQUENTIAL =50 ASSISTING PARALLEL SEQT= 0
DSNB999I -DBA1 DSNB1DBP SERVICE( 4 )OUTPUT
DSNB999I -DBA1 4K PAGES 5000
DSNB999I -DBA1 1M PAGES 0
DSN9022I -DBA1 DSNB1CMD '-DIS BUFFERPOOL' NORMAL COMPLETION
26. The Information Management Specialists
Real Storage Monitoring
• Monitor use of 1MB page frames across LPAR
/DISPLAY VIRTSTOR,LFAREA (needs APAR OA31116)
IAR019I message shows breakdown of 4KB and 1MB page frames and
how much of each is currently available
HWM usage is also shown – useful for ensuring correct segmentation
of 4K and 1MB pages in z/OS
/DISPLAY VIRTSTOR,LFAREA
IAR019I 12.31.04 DISPLAY VIRTSTOR
SOURCE = GS
TOTAL LFAREA = 1024M
LFAREA AVAILABLE = 1023M
LFAREA ALLOCATED (1M) = 10M
LFAREA ALLOCATED (4K) = 2M
MAX LFAREA ALLOCATED (1M) = 10M
MAX LFAREA ALLOCATED (4K) = 2M
Current / HWM LFAREA
allocated for 4KB pages
(pages decomposed)
27. The Information Management Specialists
Use New DB2 10 Features
• Possibility for less DB2
subsystems (and possibly
less LPARs) in a data sharing
environment
Lower data sharing overhead
Less systems to manage /
maintain
Minimum of 4 members / 2
LPARs still recommended for
high availability
28. The Information Management Specialists
Use New DB2 10 Features
• More space for performance critical storage objects such as dynamic
statement cache
Improve DSC hit ratio and reduce CPU accordingly
Potential for significant MAXKEEPD increase is a key part of the overall DB2 10
value proposition for SAP customers
• Potential to reduce CPU cost through more use of persistent threads with
RELEASE(DEALLOCATE)
CICS protected entry threads
DB2 10 High-Performance DBATs
Remember trade-off on BIND/DDL concurrency with use of
RELEASE(DEALLOCATE)
• Don’t forget that you’ll need to allocate additional real storage to back any
increases above!
29. The Information Management Specialists
The Future
• IBM announced zEnterprise EC12 in August 2012
12th generation processor, running at 5.5GHz
Up to 101 configurable processors per server
Flash express – up to 6.4TB of SSD as a new
memory tier between RAIM and disk
• Several new memory-related features planned
DB2 code backed by 1MB page frames
Pageable 1MB page frames (no need for PGFIX=YES)
Support for (non pageable) 2GB page frames
Support for Flash express
• IBM statement of direction for DB2 exploitation of these features in a
future release
31. The Information Management Specialists
Summary
• Make sure you have enough real storage before upgrading to DB2
10
• Change your focus from monitoring virtual storage to monitoring
real storage
• If you are scaling vertically or consolidating subsystems, be aware of
other limiting factors that were previously invisible but may now
come to bite you
• Once you’ve addressed ALL of the above, start to make use of the
new DB2 10 storage-related features
Remember to add more real storage as required in order to prevent
paging
32. The Information Management Specialists
Feedback / Questions
Julian Stuhler – julian.stuhler@triton.co.uk
Triton Consulting
25 Bank Plain
Norwich NR2 4SF
www.triton.co.uk
34. The Information Management Specialists
Real Storage Monitoring – New IFCID
225 Counters
ADDRESS SPACE SUMMARY – DBM1
EXTENDED REGION SIZE (MAX) : 1587544064 24-BIT LOW PRIVATE : 221184
24-BIT HIGH PRIVATE : 450560 31-BIT EXTENDED LOW PRIVATE : 69603328
31-BIT EXTENDED HIGH PRIVATE : 38600704 CURR HIGH ADDR 24-BIT PRIV REGION : X’0003C000’
CURR HIGH ADDR 31-BIT PRIV REGION : X’270E9000’ 31-BIT RESERVED FOR MUST COMPLETE : 158754406
31-BIT RESERVED FOR MVS : 25827760 STORAGE CUSHION WARNING TO CONTRACT: 158754406
TOTAL 31-BIT GETMAINED STACK : 4341760 TOTAL 31-BIT STACK IN USE : 3997696
TOTAL 31-BIT VARIABLE POOL : 12836864 TOTAL 31-BIT FIXED POOL : 86016
TOTAL 31-BIT GETMAINED : 1002384 AMOUNT OF AVAILABLE 31-BIT : 1479335936
SYSTEM AGENT STACK STORAGE IN USE : 1234567
TOTAL 64-BIT VARIABLE POOL : 10162176 TOTAL 64-BIT FIXED : 7503872
TOTAL 64-BIT GETMAINED : 438127168 TOTAL 64-BIT PRIVATE FOR STOR MANAG: 1925120
REAL 4K FRAMES IN USE : 20577 AUXILIARY SLOTS IN USE : 41227
64-BIT REAL 4K FRAMES IN USE : 12129 64-BIT 4K AUX SLOTS IN USE : 27055
ABOVE VALUE W/O BP STORAGE : 10000 ABOVE VALUE W/O BP STORAGE : 4096
HWM 64-BIT REAL 4K FRAMES IN USE : 43047 HWM 64-BIT AUX SLOTS IN USE : 27059
QW0225CTLP (S) : OFF QW0225CTLS (S) : OFF
35. The Information Management Specialists
Real Storage Monitoring – New IFCID
225 Counters
SHARED/COMMON STORAGE SUMMARY
EXTENDED CSA SIZE : 315179008 31-BIT COMMON FIXED POOL : 1122304
31-BIT COMMON VARIABLE POOL : 716800 31-BIT COMMON GETMAINED : 79661
64-BIT COMMON FIXED POOL : 3641344 64-BIT COMMON VARIABLE POOL : 37748736
64-BIT COMMON GETMAINED : 0 64-BIT COMMON FOR STOR MANAG : 1400832
64-BIT SHARED VARIABLE POOL : 13545472 64-BIT SHARED FIXED : 3129344
64-BIT SHARED GETMAINED : 4220208 64-BIT SHARED FOR STOR MANAG : 2056192
64-BIT SHR SYSTEM AGENT STACK (AS) : 268435456 64-BIT SHR SYSTEM AS IN USE : 33554432
64-BIT SHR NON-SYSTEM AS : 805306368 64-BIT SHR NON-SYSTEM AS IN USE : 1048576
SHARED MEMORY OBJECTS : 5
64-BIT SHARED MEMORY PAGES : 117440512 HWM 64-BIT SHARED BYTES : 481036337152
64-BIT SHARED PAGES BACKED IN REAL : 9395 AUX SLOTS USED FOR 64-BIT SHARED : 5385
64-BIT PAGES PAGED IN FROM AUX STO : 5317 64-BIT PAGES PAGED OUT TO AUX STO : 41577
64-BIT SHR STG REAL 4K FRMS IN USE : 12344459 64-BIT SHR STG 4K AUX SLTS IN USE : 512
64-BIT STK STG REAL 4K FRMS IN USE : 12345789 64-BIT STK STG 4K AUX SLTS IN USE : 256
64-BIT COM STG REAL 4K FRMS IN USE : 12345123456789 64-BIT COM STG 4K AUX SLTS IN USE : 1234555555
SERVICE INFORMATION:
QW0225_WARN : 0 QW0225_REALAVAIL : 0
QW0225_REALAVAILLO : 0 QW0225_REALAVAILOK : 0
QW0225_ESQAS : 0 QW0225_ESQA_ALLOC : 0
QW0225_ESQA_HWM : 0 QW0225_ECSA_ALLOC : 0
QW0225_ECSA_HWM : 0 QW0225_ECSA_CONV : 0
QW0225_CTGP : OFF QW0225_DISC : OFF
36. The Information Management Specialists
Further Reading
• IBM DB2 10 Home Page
http://www-01.ibm.com/software/data/db2/zos/db2-10/
• White Paper – DB2 10: A Smarter Database for a Smarter Planet
https://www14.software.ibm.com/webapp/iwm/web/signup.do?source=s
w-infomgt&S_PKG=wp-z-db2-smarter
Also available as part of a “flashbook” - ISBN: 1583473610
• DB2 10 for z/OS Performance Topics Redbook (SG24-7942)
http://www.redbooks.ibm.com/abstracts/sg247942.html?Open
• IDUG – International DB2 User Group
http://www.idug.org/
Editor's Notes
Up to 1TB total in DB2 9 and 10, with limit of 2x available real storage.Max real storage of 3TB per server, 1TB per LPAR for z196/EC12
Some customer horror stories due to insufficient storage being available for dumps (incomplete dumps, long dump capture times, performance issues)If normal auxiliary storage utilization is above 30%, the system might be subject to severe performance impacts. The system might even experience a WAIT03C state when SVC dumping occurs, which indicates that the system ran out of available paging slots. Hilariously our chums at a well known high street bank finally got beaten in to sorting this out for their V8 services (c. 8GB). Then they absorbed the storage for other things. Now they’re installing 10 for another package. Guess how much storage they’re adding? Until very recently, our zPDT LPARs had more storage than their production services…75% cost reduction on real storage on z196 (USD1.5K vs. USD6K)
REALSTORAGE_MANAGEMENT in macro DSN6SPRM Specifies whether DB2 should manage real storage consumption. Valid values are ON, OFF, and AUTO.A value of ON means that DB2 always discards unused real storage frames. Discarding the frames results in some CPU overhead, and this option is intended for systems in which the availability of real storage is limited. This value would most likely be appropriate for LPARs that have many DB2 subsystems, such as a development LPAR.A value of OFF means that DB2 does not discard unused real storage frames until one of the following conditions is met:The LPAR had reached an auxiliary critical state.The total real and auxiliary storage has reached 80% of the value of the REALSTORAGE_MAX subsystem parameter.A value of AUTO means that DB2 discards unused real storage frames when a significant amount of paging activity is detected. By discarding frames, DB2 tries to bring the system to a point where paging is limited or nonexistent. However, it might not be possible to bring the system to that point if other applications on the same LPAR cause the shortage of real storage frames.The default setting is AUTO.REALSTORAGE_MAX in macro DSN6SPRM Specifies the maximum GB of real and auxiliary storage that DB2 can consume. Valid values are NOLIMIT and 1 to 65535.The default value, NOLIMIT, means that DB2’s real and auxiliary storage consumption is not bounded.If a numerical value is specified for this parameter and the total real and auxiliary storage exceeds that limit, DB2 is terminated.The recommendation is to set this parameter to twice the amount of real and auxiliary storage that the subsystem might reasonably consume.
The CONTSTOR parameter controls whether DB2® is to periodically contract each thread's working storage area. If YES is used, DB2 examines threads at commit points and periodically returns storage that is no longer in use to the operating system. Storage that a thread acquires is normally allocated to that thread until deallocation.The MINSTOR subsystem parameter controls whether DB2® is to use storage management algorithms that minimize the amount of working storage that is consumed by individual threads. In general, you should expect approximately 1% CPU overhead with MINSTOR set to YES. However, applications that consume a relatively higher percentage of CPU time in acquiring and releasing storage might experience greater CPU overhead. If the CPU overhead is unacceptable and the DBM1 address space does not have virtual storage constraint issues, you can change MINSTOR to NO
Support for 1MB non page-fixed bufferpools is possible in a future release• 1MB size page frames are non-pageable• If 1MB size page frames are overcommitted, DB2 will use 4KB size page frames
Up to 1TB total in DB2 9 and 10, with limit of 2x available real storage.Max real storage of 3TB per server, 1TB per LPAR for z196/zEC12