In article <f3e9a051.0401230708.2576b04@posting.google.com> , I like AIX wrote:
> Mike <mikee@mikee.ath.cx> wrote in message news:<10122ve1li8h274@corp.supernews.com>...
>> In article <f3e9a051.0401221219.1102ace1@posting.google.com >, I like AIX wrote:
>> > Mike <mikee@mikee.ath.cx> wrote in message news:<100tgburak7cnb8@corp.supernews.com>...
>> >> In article <2bcd6fe2.0401210804.79f634f7@posting.google.com >, Krishna wrote:
>> >> > Hi,
>> >> >
>> >> > Please explain the step by step procedure for upgrading AIX P series
>> >> > to AIX 5.2 version.
>> >> >
>> >> > Is it possible to change over to 5.2 from 4.3.3 ??? or we need to
>> >> > upgrade it to 5.1 and then only we can upgrade it to 5.2
>> >>
>> >> I did many (~15) upgrades from 4.3.3 to 5.2.0. I'm now in the process
>> >> of planning the upgrade of 5.2.0 -> 5.2.2.
>> >
>> > Mike, did you meet some problems when you upgraded? If so, what's
>> > those? Would you please give us somem advice?Thanks
>>
>> Once we wrote a script (as in play) for the sequence of steps to
>> reach the end goal, the whole deal was easy. Now I'm working on
>> a script to add maintenance level upgrades to each of the servers.
>> I can post my script if it would help.
>
>
> It would be helpful for us to share your script. thanks

Certainly. I don't think my company would have a problem with that.
It's not pretty and formatted. It's a checklist of what I did for the
upgrade.


# prepare for upgrade
mount txwast01a:/export/nim/mksysb /mnt
rm /mnt/txspf111_mksysb
time mksysb -i /mnt/txspf111_mksysb
umount /mnt
time mksysb -i /dev/rmt0
make tsm backup (dsmc i)
unmirrorvg -c 1 rootvg hdisk1
bosboot -ad /dev/hdisk0
lsvg -l rootvg
lsvg -p rootvg
sysdumpdev -l
mklv -c 1 -t sysdump -y dumplv3 rootvg 8 hdisk0
sumpdumpdev -P -p /dev/dumplv3
rmlv -p hdisk1 dumplv2
reducevg rootvg hdisk1
lsvg -l rootvg
lsvg -p rootvg
lspv hdisk1
bootlist -m normal hdisk0
bootlist -m normal -o

# do the upgrade
nimadm
bootlist -m normal hdisk1 hdisk0
bootlist -m normal -o

# load the new os and test
reboot to hdisk1
oslevel (should read 5.2.0.0)

# go forward after the upgrade
bosboot -ad /dev/hdisk1
copy /usr/sbin/alt_disk_install from nimadm master to nimadm client
chmod 755 alt_disk_install
alt_disk_install -X old_rootvg
lsvg (old_rootvg is gone)
lspv (hdisk0 is not assigned to a vg)
extendvg -f rootvg hdisk0
mirrorvg -c 2 rootvg hdisk0
lsvg -l rootvg to check for stale
bosboot -ad /dev/hdisk0
bosboot -ad /dev/hdisk1
bootlist -m normal hdisk0 hdisk1
* for every stale lv run syncvg -l STALELV

# fallback to the previous os
bootlist -m normal hdisk0 hdisk1
reboot to previous os
oslevel (should read 4.3.3.0)
smitty (to remove failed os vg)
extendvg rootvg hdisk1
mirrorvg -c rootvg hdisk1
bosboot -ad /dev/hdisk0

# restore the dump partition
sysdumpdev -l
mklv -c 1 -t sysdump -y dumplv rootvg 9 hdisk0
sysdumpdev -P -p /dev/dumplv
rmlv -p hdisk1 dumplv3