VIOS Update failed for "bos.perf.pmaix"

VIO update from 2.2.5.20 to 2.2.6.10.

This techdoc will provide both the "workaround" to stop the error
and the steps to "recover" from the 'FAILED" "bos.perf.pmaix 6.1.9.300" update.

After updating the VIO Server to 2.2.6.10 from VIO 2.2.5.20
the fileset "bos.perf.pmaix 6.1.9.300" may report "FAILED".

This error will be under the "Installation Summary" section
of the "install.log" for the "bos.perf.pmaix" fileset.

Sample line:
------------
bos.perf.pmaix 6.1.9.300 ROOT APPLY FAILED

This error is seen when the daemon "pmperfrec" was running during the update.

==============================================================
Workaround (to stop the Failed fileset update):
==============================================================

Stop the daemon "stopsrc -s pmperfrec" before doing the updateios command.

Summary: 3 steps (The commands are run from "padmin" shell)
1) Check if the daemon is running.
$ lssrc -s pmperfrec
2) Stop the pmperfrec daemon.
$ echo " stopsrc -s pmperfrec " | oem_setup_env
3) Check that the daemon has been stopped.
$ lssrc -s pmperfrec
4) Do the desired VIO Update "updateios".

Details:

1) Check for the daemon using "ps" or "lssrc" command.
---------------------------------------------------------

$ ps -ef | grep pmperfrec
root 2222222 1111111 0 01:01:01 - 0:00 /var/perf/pm/bin/pmperfrec

--- or ---

$ lssrc -s pmperfrec
Subsystem Group PID Status
pmperfrec 9371702 active

*** The lssrc may also report "inoperative" or
*** "0513-085 The pmperfrec Subsystem is not on file."


2) Stop the daemon if it is running.
---------------------------------------------------------
If it is not running there is no problem and the update
to VIO 2.2.6.10 may be move forward (step 4 updateios).

$ echo " stopsrc -s pmperfrec " | oem_setup_env
0513-044 The pmperfrec Subsystem was requested to stop.


3) Confirm the daemon has been stopped "inoperative".
---------------------------------------------------------

$ lssrc -s pmperfrec
Subsystem Group PID Status
pmperfrec inoperative



4) Run the desired updateios command.
---------------------------------------------------------
Run the update to 2.2.6.10 (daemon turned off).

$ updateios -dev /home/padmin/FP/2.2.6.10_directory -accept -install



==============================================================
Recovery after the FAILED "bos.perf.pmaix 6.1.9.300" update
==============================================================
After the update has been done and it is discovered that
"bos.perf.pmaix" fileset "FAILED" the steps below should
fixed (returned "bos.perf.pmaix" to a "consistent" state.

Summary:
1) Confirm that fileset "bos.perf.pmaix" is inconsistent.
# lppchk -v
2) Stop the "pmperfrec" daemon.
$ echo " stopsrc -s pmperfrec " | oem_setup_env
3) Update the "bos.perf.pmaix" fileset.
Use "updateios" command, or use "installp" command.
4) Confirm that "bos.perf.pmaix" is updated.
# lppchk -v -- or -- # lslpp -hac

Details:
1) confirm the problem has occurred on the VIO server
run the "lppchk -v " command:

$ oem_setup_env
# lppchk -v
---> bos.perf.pmaix 6.1.9.300 .... (... root not installed)
#

2) Stop the "pmperfrec" daemon.

$ echo " stopsrc -s pmperfrec " | oem_setup_env
0513-044 The pmperfrec Subsystem was requested to stop.

3) Update the "bos.perf.pmaix" fileset.
Either using "updateios" or "installp".

a) Use "updateios -fs" to select the fileset to be updated.
$ updateios -fs bos.perf.pmaix -dev /home/padmin/FP/2.2.6.10_directory

b) Use "installp" from oem_setup_env to update the "root" part.
$ oem_setup_env
# installp -Or bos.perf.pmaix 6.1.9.300

4) Confirm that "bos.perf.pmaix" is updated.
# lppchk -v
--> should just return to the prompt
------- or -------
# lslpp -hac | grep bos.perf.pmaix
--> both "/usr/lib/objrepos" and "/etc/objrepos:bos.perf.pmaix"
--> should have "...:bos.perf.pmaix:6.1.9.300::APPLY..."

/usr/lib/objrepos:bos.perf.pmaix:6.1.9.300::APPLY:COMPLETE:11/06/17:21;39;57
/etc/objrepos:bos.perf.pmaix:6.1.9.300::APPLY:COMPLETE:11/06/17:21;39;58
#