银行AIX
How to remove broken filesets?
How to remove broken filesets?
This post shows how to deal with the BROKEN file sets.
lppchk -v
lppchk: The following filesets need to be installed or corrected to bring the system to a consistent state:
cluster.es.cspoc.cmds 5.2.0.4 (BROKEN)
cluster.es.cspoc.dsh 5.2.0.2 (BROKEN)
cluster.es.cspoc.rte 5.2.0.4 (BROKEN)
To repair this “situation” you have to modify the ODM of your host, so let’s start with making its backup.
cd /
tar -cvf /tmp/odm.tar ./etc/objrepos ./usr/lib/objrepos
ODM data is stored in few places, for these operations we have to use the one residing at:
export ODMDIR=/usr/lib/objrepos
So we can establish the lpp_id of the broken fileset.
odmget -q "name=cluster.es.cspoc.cmds" lpp
lpp:
name = "cluster.es.cspoc.cmds"
size = 0
state = 7
cp_flag = 273
group = ""
magic_letter = "I"
ver = 5
rel = 2
mod = 0
fix = 0
description = "ES CSPOC Commands"
lpp_id = 509
lpp:
name = "cluster.es.cspoc.cmds"
size = 0
state = 5
cp_flag = 273
group = ""
magic_letter = "I"
ver = 5
rel = 3
mod = 0
fix = 0
description = "ES CSPOC Commands"
lpp_id = 624
Examining the last output, you notice that ODM “knows” about two releases of this fileset. One is release 2 and the other release 3. It is the release 2 that is broken which needs to be removed. I take note that its lpp_id=509 and start ODM cleanup which takes several steps.
odmdelete -q "name=cluster.es.cspoc.cmds and rel=2" -o lpp
0518-307 odmdelete: 1 objects deleted.
odmdelete -q "lpp_name=cluster.es.cspoc.rte and rel=2" -o product
0518-307 odmdelete: 2 objects deleted.
odmdelete -q lpp_id=509 -o history
0518-307 odmdelete: 8 objects deleted.
odmdelete -q lpp_id=509 -o inventory
0518-307 odmdelete: 179 objects deleted.
Have the issue been fixed?
lppchk -vm3
Apparently, there are no more messages indicating this fileset is BROKEN. I have to repeat the same process with the remaining filesets
Well, it is not always as smooth as I presented it above. Few times, I had to logout, login and repeat the process in order to remove a broken fileset. Just rememebr to set the right ODM “side” before you start.
This post shows how to deal with the BROKEN file sets.
lppchk -v
lppchk: The following filesets need to be installed or corrected to bring the system to a consistent state:
cluster.es.cspoc.cmds 5.2.0.4 (BROKEN)
cluster.es.cspoc.dsh 5.2.0.2 (BROKEN)
cluster.es.cspoc.rte 5.2.0.4 (BROKEN)
To repair this “situation” you have to modify the ODM of your host, so let’s start with making its backup.
cd /
tar -cvf /tmp/odm.tar ./etc/objrepos ./usr/lib/objrepos
ODM data is stored in few places, for these operations we have to use the one residing at:
export ODMDIR=/usr/lib/objrepos
So we can establish the lpp_id of the broken fileset.
odmget -q "name=cluster.es.cspoc.cmds" lpp
lpp:
name = "cluster.es.cspoc.cmds"
size = 0
state = 7
cp_flag = 273
group = ""
magic_letter = "I"
ver = 5
rel = 2
mod = 0
fix = 0
description = "ES CSPOC Commands"
lpp_id = 509
lpp:
name = "cluster.es.cspoc.cmds"
size = 0
state = 5
cp_flag = 273
group = ""
magic_letter = "I"
ver = 5
rel = 3
mod = 0
fix = 0
description = "ES CSPOC Commands"
lpp_id = 624
Examining the last output, you notice that ODM “knows” about two releases of this fileset. One is release 2 and the other release 3. It is the release 2 that is broken which needs to be removed. I take note that its lpp_id=509 and start ODM cleanup which takes several steps.
odmdelete -q "name=cluster.es.cspoc.cmds and rel=2" -o lpp
0518-307 odmdelete: 1 objects deleted.
odmdelete -q "lpp_name=cluster.es.cspoc.rte and rel=2" -o product
0518-307 odmdelete: 2 objects deleted.
odmdelete -q lpp_id=509 -o history
0518-307 odmdelete: 8 objects deleted.
odmdelete -q lpp_id=509 -o inventory
0518-307 odmdelete: 179 objects deleted.
Have the issue been fixed?
lppchk -vm3
Apparently, there are no more messages indicating this fileset is BROKEN. I have to repeat the same process with the remaining filesets
Well, it is not always as smooth as I presented it above. Few times, I had to logout, login and repeat the process in order to remove a broken fileset. Just rememebr to set the right ODM “side” before you start.
