Technical Blog Post
Abstract
Enable Seq cache explicitly in pureScale database for Maximo
Body
In a large scaled Maximo environment, some of us would use IBM DB2 pureScale database. As the more nodes you have, the more contentions there are on every kind of resources. Normally, Maximo is using Sequence object inside database to avoid the locking issues that are associated with other more heavier approaches In a standard database, Maximo usually cache some sequence values in memory to improve response time.
While in a DB2 pureScale environment, if both CACHE and ORDER are specified, the specification of ORDER overrides the specification of CACHE and instead NO CACHE will be in effect. So for most of sequences in Maximo, especially those used for row-stamps, whose sequence numbers are not strictly required to be generated in order of request, could gain significant performance benefits by preallocating and storing values in the cache.
"ALTER SEQUENCE XXXX_SEQ CACHE 100 NO ORDER"
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSLKT6","label":"IBM Maximo Asset Management"},"Component":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]
UID
ibm11134045