In the last entry posted to this blog , I described the mechanisms (including PUNC bits and commit log sequence numbers, aka CLSNs) used by Db2 for z/OS for lock avoidance purposes (lock avoidance here refers to a capability whereby Db2 can, in many cases, verify the committed state of a data value without having to get an S-lock – i.e., a read lock – on the page or row in which the value is located). As lock and unlock requests consume CPU cycles, lock avoidance is a CPU efficiency booster for Db2 …read more
Related Articles
What happened to Toad® for Oracle Freeware? It’s a matter of focus.
Following our decades-long tradition of putting Quest® Toad® for Oracle Freeware user feedback first, we’ve come to a difficult but necessary decision. We need to provide its users, and all single use...
Database as a Service using Enterprise Manager – Part XIII
In this popular article series, we are exploring the capabilities of Oracle Enterprise Manager Cloud Control 13c for the private Database-as-a-Service (DBaaS) cloud – including the setup of such a clo...
Db2 for z/OS: Opportunities for CPU Efficiency When Data Clustering is...
Not long ago, a veteran Db2 for z/OS DBA contacted me with an interesting question. He had, in the system he supported, a table with a clustering index, and he wanted to know how he could get Db2 to a...
