So I plan to go through some of the stagingprop problems I've seen - especially the more common ones. This is probably the most common of all, especially if the java developers you're working with have not used Commerce and particularly stagingprop before.
So every client I support has issues with stagingprop at some point. The vast majority of them are due to mistakes made in the development process. Many developers do not fully understand what stagingprop does, so here's a general description that might help.
I was happy to see the new workload registry variable in Commerce 7/DB2 9. Mostly out of laziness – it requires fewer variables to be set manually, but it also ensures that nothing major is missed (I imagine they may…
I'm just this guy, you know? Ok, so I'm female, but I don't work for IBM and I'm not trying to sell you anything.
DB2 GUIs Suck for a variety of reasons - use the command line.
IN-lists are poor performers. Here's what they look like in explain plans and why they perform poorly.
Several times I've figured things out in my career and thought "how did I ever call myself a DBA without knowing that?"
I am at this point an expert on DB2, and on the aspects of DB2 that interact with Commerce, and frequently train clients and new DBAs on how to do what I do, so it's time to share.
SQL30082N Security processing failed with reason "42" ("ROOT CAPABILITY REQUIRED"). SQLSTATE=08001