msi toc

I’m not sure when if it drops out but I would not be comfortable until I do both of these:

– initialize DB

– recreate monitorShmemFile

so whenever we do one of the following:

– delete a thread

– rename a thread

– create a thread

first we shutdown the site and kill lock manager and monitor daemon

then we make the change and do

– rm -f $HCISITEDIR/exec/monitorShmemFile

– run our clear_db.ksh script which initializes the DB

– hcimsiutil -R

– start monitor daemon and lock manager

– bring up site processes and threads

Since this can be disruptive to a running site we have a site versioning process that allows us to clone the active site and make changes to the cloned site and when ready deactivate the orginal site and activate the cloned site.

This way the impact is reasonably short plus the clone can be thouroughly tested prior to its actual use.

Russ and company,

We run on AIX 6.1 TL 7 and have been running on previous versions of both Cloverleaf Integrator and AIX.  When we add, delete, rename, or reorganize a process cluster (transfer threads), after the changes, we just cycle the monitorD program to refresh its MSI (shared memory region).

That has served us well so far to our current engine release 5.8.6.0.

Just thought to add to this conversation.

Bob:

I hadn’t thought about what could happen when reorganizing process clusters and agree that I should treat it similarly.

Thanks for broading my thinking.