Db2 Experts on a Data Science Quest
I have recently encountered an interesting issue – after an IPS (Intrusion Prevention System) upgrade, client applications suddenly stopped being able to connect to some database instances – not all of them, but just a to a subset.… Read the rest
Continue reading »
When I was in my early thirties, I was diagnosed with a learning disability. This really put my learning style into perspective. Teaching myself via a book was incredibly hard, and still is in some ways. Where I thrived was with hands on labs and engaging speakers.… Read the rest
Continue reading »
Sometimes configuration needs to be kept in sync between two or more Db2 systems. There are a variety of reasons – sometimes this is for keeping two HADR servers in sync, and other times it may be for keeping a dev, QA, or Staging system in sync with production.… Read the rest
Continue reading »
Corrected on 9/8/2017 to reflect correct syntax to eliminate just the one table.
The application in this case – SPSS – maintains an exclusive lock at all times on one table. I think this is poor application design, but IBM was not willing to change it when we brought it to their attention in a PMR.… Read the rest
Continue reading »
Updated 11/22/2017: instructions on how to run the SQL statement
There are a number of places where we can store and change configuration for a Db2 server. I wanted to walk through the main areas and a few details about them.… Read the rest
Continue reading »
The package cache is just one memory area that DB2 offers to tune memory usage for a DB2 database. This article is a deep dive into this memory area.
The package cache is an area of memory that DB2 uses to store access plans.… Read the rest
Continue reading »
There are an astonishing number of vendor solutions available with specific interfaces for DB2. Working with a variety of clients, I see and help to evaluate and implement a variety of backup solutions. I thought I’d share some of the things I look for and work on as part of an implementation.… Read the rest
Continue reading »I thought I’d share some issues with STMM that I’ve seen on Linux lately. I’ve mostly been a fan of STMM, and I still am for small environments that are largely transaction processing and have only one instance on a server.… Read the rest
Continue reading »Note: updated 7/21 to reflect location of the package cache high water mark in the MON_GET* table functions
I have long been a fan of a smaller package cache size, particularly for transaction processing databases. I have seen STMM choose a very large size for the package cache, and this presents several problems:
Parameter markers involve telling DB2 that the same query may be executed many times with slightly different values, and that DB2 should use the same access plan, no matter what the values supplied are.… Read the rest
Continue reading »I’m a control freak. I think that control freaks tend to make good DBAs as long as they don’t take it too far. My position for years has been that I would rather control my runstats, reorgs, and backups directly than trust DB2’s automatic facilities.… Read the rest
Continue reading »
Today we are going to talk about some random DB2 features that can’t stand in a blog of their own, but are worth discussing nonetheless. These are tidbits I had discovered during “DB2’s Got Talent” presentations, IDUG conferences, or “Hey, look what I discovered” moments.… Read the rest
I mostly like and use DB2’s Self Tuning Memory Memory Manager (STMM) for my OLTP databases where I have only one DB2 Instance/Database on a database server. I do have some areas that I do not let it set for me.… Read the rest
Continue reading »