The first professional technical presentation I ever gave was on March 31, 2003. I had been a DBA for just less than 2 years. It was at an event called “SDC West Geek Fest”. It was an internal IBM event within Global Services where the technical folks delivering services got together to share technical expertise. The title was something along the lines of “10 ways to improve physical performance in Db2”. This was just after version 8.1 was released.
For more than 5 years I’ve managed to average at least one blog entry a week through fluctuating workloads and even through changing employers. And then came this autumn. The combination of a couple of large clients and going into holiday peak period for a couple of retail clients, collided with the IDUG EMEA conference where I was presenting two new sessions nearly combined to do me in.
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.
IBM has published a document with some additional best practices for configuring TSAMP, so I thought I would add an article to my TSA series covering these settings.
Critical to recovering a database, but largely invisible, it is a good idea to understand the recovery history file, what it contains, and how to access it.
Connecting to a database is required before most actions can be taken on the database. A Db2 connection is made at the database level, and not at the instance or server level. This entry focuses on how to establish a connection to work with a Db2 database. It applies to Db2 for Linux, UNIX, or Windows.
IBM released fix pack 3, mod pack 3 for Db2 11.1 earlier this year, and there was a high-severity problem in the initial version of that fix pack. IBM fixed the problem and re-released the fix pack within about a day, but the bug was reported far and wide, while I’m not sure the resolution of the bug was, so I thought I’d cover it quickly.
Database servers these days sometimes have a profusion of IP Addresses. IP V4, V6, management networks, and Virtual IP addresses all add to the ways applications connect in to a database server. I ran into an issue recently where I really needed to know what IP address was being used by an application, and thought I would share what I learned.
DB2 has one or two ports that it is listening on for each and every Db2 instance. Two Db2 instances cannot share a port to listen on. Remember that Db2 allows multiple instances per server and also multiple databases per instance, and has for years.
To list the database authorities held by an ID or group – authorities, not privileges. This information is not available in sysibmadm.privileges. The format of syscat.dbauth has columns with ‘Y’ or ‘N’ in them, and reading that quickly to answer the question “What permissions does this ID have?” can be a bit frustrating. This SQL could also be union-ed with SQL to query sysibmadm.privileges to include the privileges on database objects in one result set.
Last year I crossed the line. The IDUG conference in Europe is now my favorite. But the North American technical conference is a very close second. Nowhere else can you get this level of detail and the contacts with IBMers and peers. I now get two favorite weeks a year!