Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

HACMP 5.3 migration to 5.4 -> lppchk give BROKEN

Status
Not open for further replies.

alexia32

Technical User
Jul 31, 2007
156
NZ
Hello
I just try to do an update from hacmp 5.2 to 5.4.0 (first) then I will apply the fixpack 5.4.1.

I have stop the cluster and use smitty update_all to update HACMP (rsct already on 2.4.9).

I had most of them successfully updated (smitty update_all -> status ok) but then when I do lslpp cluster*
I have some of them not important still on 5.2 (I guess I can install those one manually on 5.4 if I can find it)
lslpp -l cluster*
Fileset Level State Description
----------------------------------------------------------------------------
Path: /usr/lib/objrepos
cluster.adt.es.client.include
5.4.0.0 COMMITTED ES Client Include Files
cluster.es.cfs.rte 5.4.0.0 COMMITTED ES Cluster File System Support
cluster.es.client.lib 5.4.0.0 COMMITTED ES Client Libraries
cluster.es.client.rte 5.4.0.0 COMMITTED ES Client Runtime
cluster.es.client.utils 5.4.0.0 COMMITTED ES Client Utilities
cluster.es.client.wsm 5.4.0.0 COMMITTED Web based Smit
cluster.es.cspoc.cmds 5.4.0.0 COMMITTED ES CSPOC Commands
cluster.es.cspoc.dsh 5.4.0.0 COMMITTED ES CSPOC dsh
cluster.es.cspoc.rte 5.4.0.0 COMMITTED ES CSPOC Runtime Commands
cluster.es.plugins.dhcp 5.4.0.0 COMMITTED ES Plugins - dhcp
cluster.es.plugins.dns 5.4.0.0 COMMITTED ES Plugins - Name Server
cluster.es.plugins.printserver
5.4.0.0 COMMITTED ES Plugins - Print Server
cluster.es.server.cfgast 5.4.0.0 COMMITTED ES Two-Node Configuration
Assistant
cluster.es.server.diag 5.4.0.0 COMMITTED ES Server Diags
cluster.es.server.events 5.4.0.0 COMMITTED ES Server Events
cluster.es.server.rte 5.4.0.0 COMMITTED ES Base Server Runtime
cluster.es.server.testtool
5.4.0.0 COMMITTED ES Cluster Test Tool
cluster.es.server.utils 5.4.0.0 COMMITTED ES Server Utilities
cluster.es.worksheets 5.4.0.0 COMMITTED Online Planning Worksheets
cluster.license 5.4.0.0 COMMITTED HACMP Electronic License
cluster.msg.En_US.cspoc 5.4.0.0 COMMITTED HACMP CSPOC Messages - U.S.
English IBM-850
cluster.msg.en_US.cspoc 5.2.0.0 COMMITTED HACMP CSPOC Messages - U.S.
English
cluster.msg.en_US.es.client
5.2.0.0 COMMITTED ES Client Messages - U.S.
English
cluster.msg.en_US.es.server
5.2.0.0 COMMITTED ES Recovery Driver Messages -
U.S. English

Path: /etc/objrepos
cluster.es.client.lib 5.4.0.0 COMMITTED ES Client Libraries
cluster.es.client.rte 5.4.0.0 COMMITTED ES Client Runtime
cluster.es.cspoc.rte 5.4.0.0 COMMITTED ES CSPOC Runtime Commands
cluster.es.server.diag 5.4.0.0 COMMITTED ES Server Diags
cluster.es.server.events 5.4.0.0 COMMITTED ES Server Events
cluster.es.server.rte 5.4.0.0 COMMITTED ES Base Server Runtime
cluster.es.server.utils 5.4.0.0 COMMITTED ES Server Utilities

Path: /usr/share/lib/objrepos
cluster.man.en_US.es.data 5.4.0.0 COMMITTED ES Man Pages - U.S. English

but the output of lppch is not good on some filesets appears BROKEN
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.7 (BROKEN)
cluster.es.cspoc.dsh 5.2.0.2 (BROKEN)
cluster.es.cspoc.rte 5.2.0.0 (not installed; requisite fileset)
cluster.es.cspoc.rte 5.2.0.6 (BROKEN)


but If I check those filesets on the system:
lslpp -l cluster.es.cspoc*
Fileset Level State Description
----------------------------------------------------------------------------
Path: /usr/lib/objrepos
cluster.es.cspoc.cmds 5.4.0.0 COMMITTED ES CSPOC Commands
cluster.es.cspoc.dsh 5.4.0.0 COMMITTED ES CSPOC dsh
cluster.es.cspoc.rte 5.4.0.0 COMMITTED ES CSPOC Runtime Commands

Path: /etc/objrepos
cluster.es.cspoc.rte 5.4.0.0 COMMITTED ES CSPOC Runtime Commands

there are all on 5.4.0.0 ... Is this normal ???

I didn;t reboot yet the server.

I don;t know if this means it is successfull or not... I don;t want to reboot and start the update on the primary node prio to be sure it is fine.

Any ideas how to fix BROKEN status ?
Cheers
Al
 
forget to precise aix version AIX 5.3 TL8 (5300-08-03-0831)
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top