AIX

I had a lengthy reply - but it never made it out - sigh.

Just note that RSCT activity is normal, even necessary, to have DLPAR aka Dynamic Resource Management working.

Code:

root@x062:[/]oslevel -s
7100-03-05-1524
root@x062:[/]lssrc -a | grep rsct
 ctrmc            rsct             6160584      active
 IBM.HostRM       rsct_rm          6947044      active
 IBM.DRM          rsct_rm          7078142      active
 IBM.MgmtDomainRM rsct_rm          6684680      active
 IBM.ServiceRM    rsct_rm          5963970      active
 ctcas            rsct                          inoperative
 IBM.ERRM         rsct_rm                       inoperative
 IBM.AuditRM      rsct_rm                       inoperative
 IBM.FSRM         rsct_rm                       inoperative
 IBM.SensorRM     rsct_rm                       inoperative
 IBM.ConfigRM     rsct_rm                       inoperative
 IBM.WLMRM        rsct_rm                       inoperative
 IBM.StorageRM    rsct_rm                       inoperative
 IBM.LPRM         rsct_rm                       inoperative
 IBM.MicroSensorRM rsct_rm                       inoperative

As much has changed in RSCT between the different versions of AIX 5.3 and AIX 7.1 (soon to include AIX 7.2) - your mileage may vary. In any case, ctrmc is supposed to be active all the time. And for years, the cluster manager demon that PowerHA installs is supposed to be active - all the time (in state ST_idle perhaps!).

For a lot of bla bla about what ctrmc is doing try:

Code:

root@x062:[/]lssrc -s ctrmc -l

My experience with DB2 and installs on AIX is that DB2 (read software group) does add specific stuff for AIX (they use neither installp nor rpm for their install method) - and when AIX changes enough that there modification/specification no longer fits - install may fail, or - more frequently - a warning message that is no longer applicable.

If the install is "uninstalling" itself, rather than just complaining check around in the sub-directory (was named db2_setup if I recall correctly) and see if you can find the test, change the logic (or comment it out) - and see if it works.

Please note - the last time I was doing modifications like this it was still db2 version 9.something.