DB2 is particularly good at running complex query and analytical processing. Since all modern hardware contains multiple cores and CPUs, and many systems are composed of multiple machines, it is critical that DB2 run individual queries across all available computing resources.
Do you really understand what might change in your Db2 world as a result of moving to an encrypted database? To help avoid unpleasant surprises, here's a little cheat-sheet on things to consider before using Db2 Native Encryption.
This article will help DB2 DBAs and Users to proactively monitor their most critical and live systems on continuous basis without any impact to production and analyze the data on key points to identify any possible DB2 health/hang/performance issues and fix them.
As a DBA you are rather frequently asked whether the database is the same structure-wise all over the different environments. Whenever a decent release management is in place you can be very relaxed answer that this is the fact.
This article will explain how to compare based on SQL.
I have a question about the total_extended_latch_wait_time monitor element. We recently saw high values of total_extended_latch_wait_time and we'd like to understand how to interpret this.