Not only was this delete running unreasonably slow – it was also causing lock timeouts on the MEMBER table while running because of the slowness. This post contains application specific details that you don’t need to understand the underlying concept here, which applies across many SQL statements in the real world.
The Problem I often lean on analogies when I speak to non-technical people about technical topics. For example, I would explain database locking as “two kids fighting for the same candy bar”. If you introduce isolation levels into the conversation,…
While this post is specific to WebSphere Commerce, it covers concepts that may apply to tuning other delete statements as well. Using Functions in the Best Place The CLEANCONF table stores the delete statements that are used by DBCLEAN. Most…
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,…
Like many applications, WebSphere Commerce puts all tables in USERSPACE1 unless they need larger page sizes. This actually works just fine for smaller and midrange implementations, but we have about one build a year that requires something else – either…
This post is specific to WebSphere Commerce. I’m usually pretty critical of the IBM webcasts about WebSphere Commerce. There have been some pretty bad or incomplete ones in relation to WebSphere Commerce databases(“run dbclean” is the most frustrating, general advice…
This post is specific to WebSphere Commerce. We’ve reported this issue to IBM, but since we’ve run into it several times across more than a year, and in multiple different Fix Packs of Commerce, I thought I’d share it in…
One of my most popular posts that’s specific to WebSphere Commerce is The 10 Commerce Tables You Should Be Familiar With. This is an updated version of that post, since the preferred method of dealing with attributes has changed. As…
This post is specific to WebSphere Commerce. In my experience, usually when Clients upgrade from one WebSphere Commerce version to another (with 6 to 7 being the current focus), they also upgrade or change DB2, the OS, the Hardware –…
This post is specific to WebSphere Commerce. NEVER drop a WebSphere Commerce base index. I believe I’ve stated this in at least one previous blog entry. But I’m always growing and learning and trying new things, and that policy was…
This post is specific to WebSphere Commerce. If you’ve always assumed that stagingprop copied the whole row and every change, I’ve found an execption. Stagingprop does not copy the OPTCOUNTER column. What is OPTCOUNTER? OPTCOUNTER is a column used in…
This post is specific to WebSphere Commerce. We spent a fair amount of time on this, both on a SUSE server and a Red Hat Server. The problem manifested in different ways. The main thing that became obvious to me…