Thank you very much, Darin. Really appreciate that.
I think the steps I am going to take is:
--download Fixpak 9 on the 4 physical servers
--install the Fixkpak 9 on the 4 servers
--issue db2iupdt on 4 servers respectively ( from logical port 0 on
each server)
db2nodes.cfg looks like:
0 xxxxx01-svc 0 xxxxx01
1 xxxxx01-svc 1 xxxxx01
2 xxxxx01-svc 2 xxxxx01
3 xxxxx01-svc 3 xxxxx01
4 xxxxx01-svc 4 xxxxx01
5 xxxxx02-svc 0 xxxxx02
6 xxxxx02-svc 1 xxxxx02
7 xxxxx02-svc 2 xxxxx02
8 xxxxx02-svc 3 xxxxx02
9 xxxxx03-svc 0 xxxxx03
10 xxxxx03-svc 1 xxxxx03
11 xxxxx03-svc 2 xxxxx03
12 xxxxx03-svc 3 xxxxx03
13 xxxxx04-svc 0 xxxxx04
14 xxxxx04-svc 1 xxxxx04
15 xxxxx04-svc 2 xxxxx04
16 xxxxx04-svc 3 xxxxx04
16 partitions on 4 physical server.
> Thank you very much, Darin. Really appreciate that.
>
> I think the steps I am going to take is:
> --download Fixpak 9 on the 4 physical servers
If you download it into your instance's home directory, it'll be immediately
accessible on all machines. Just a little trick I've learned. (Normally
the instance's home directory is cross-mounted, although you technically
only need the sqllib to be cross-mounted (makes things a bit harder
though), if that's your setup, just put it inside the sqllib somewhere
temporarily.)
> --install the Fixkpak 9 on the 4 servers
Correct.
> --issue db2iupdt on 4 servers respectively ( from logical port 0 on
> each server)
This is not needed. You only need to update on a single node - my
recommendation is whichever node has the instance running locally (where
the home directory physically resides rather than being NFS mounted). If
no node has the instance locally (e.g., it's physically on a NAS or SAN),
then any node will do.
That said, it doesn't hurt anything except waste time, bandwidth, and
unnecessary hard disk activity.
> db2nodes.cfg looks like:
>
[quoted text clipped - 17 lines]
>
> 16 partitions on 4 physical server.
That would be 17 partitions. ;-) The 01 server has 5 partitions (0-4).