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, I would expand the analogy to include “one sibling holding on to a candy bar they care nothing about just because they don’t want the other sibling getting to it”.… Read the restContinue reading »
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 of them use syntax like this for the date component:
(days(CURRENT TIMESTAMP) - days(prevlastsession)) = ?… 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 restContinue reading »
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 because of standards that client DBAs adhere to or because they actually are busy enough for I/O and separate buffer pools to matter.… Read the rest
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 ever).… Read the restContinue reading »
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 a result, this post is only applicable to WebSphere Commerce 7 and above, and some of the content is identical between the two posts.… Read the restContinue reading »
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 something we started back on Commerce 5.6.… Read the restContinue reading »
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 optimistic locking.… Read the restContinue reading »
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 is that Commerce was not creating the Commerce database as the dbaUser specified in createInstance.properties file, but was instead using the id that was running the Commerce Instance creation.… Read the restContinue reading »