473,325 Members | 2,828 Online
Bytes | Software Development & Data Engineering Community
Post Job

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 473,325 software developers and data experts.

update from V8.1 Fixpak 8 to Fixpak 9

We are considering to update from V8.1 Fixpak 8 to Fixpak 9.

Operating System Information:
OSName: AIX
NodeName: mdxxx01, mdxxx02, mdxxx03, mdxxx04
Version: 5
Release: 2

64 bits and DB2 code release SQL08021 with level identifier 03020106
Informational tokens are DB2 v8.1.1.80, special_13100, U800400_13100,
FixPak 8.

With DPF: 4 nodes with 16 partitions.
With 4 instances.
My concern:
--do i need to install Fixpak binary code FixPak9 on four nodes
individually?
-- do i need to update each instance on 4 nodes ?
--Where can i find documentation on update DB2 with DPF in a cluster
server?

Thank you.

Jan 24 '06 #1
9 2329
mike_li wrote:
We are considering to update from V8.1 Fixpak 8 to Fixpak 9.

Operating System Information:
OSName: AIX
NodeName: mdxxx01, mdxxx02, mdxxx03, mdxxx04
Version: 5
Release: 2

64 bits and DB2 code release SQL08021 with level identifier 03020106
Informational tokens are DB2 v8.1.1.80, special_13100, U800400_13100,
FixPak 8.

With DPF: 4 nodes with 16 partitions.
With 4 instances.
My concern:
--do i need to install Fixpak binary code FixPak9 on four nodes
individually?
-- do i need to update each instance on 4 nodes ?
I would do both to be on the safe side.

Are these logical or physical nodes? For logical nodes, you just update all
the machines where DB2 runs on and then all instances involved in your
setup.
--Where can i find documentation on update DB2 with DPF in a cluster
server?


Have you looked at the README file that comes with each FP?

--
Knut Stolze
DB2 Information Integration Development
IBM Germany
Jan 24 '06 #2
Thanks for your response.

They are phyiscal nodes, 4 separate servers.

So we need to install the binary codes on 4 servers.


Knut Stolze wrote:
mike_li wrote:
We are considering to update from V8.1 Fixpak 8 to Fixpak 9.

Operating System Information:
OSName: AIX
NodeName: mdxxx01, mdxxx02, mdxxx03, mdxxx04
Version: 5
Release: 2

64 bits and DB2 code release SQL08021 with level identifier 03020106
Informational tokens are DB2 v8.1.1.80, special_13100, U800400_13100,
FixPak 8.

With DPF: 4 nodes with 16 partitions.
With 4 instances.
My concern:
--do i need to install Fixpak binary code FixPak9 on four nodes
individually?
-- do i need to update each instance on 4 nodes ?


I would do both to be on the safe side.

Are these logical or physical nodes? For logical nodes, you just update all
the machines where DB2 runs on and then all instances involved in your
setup.
--Where can i find documentation on update DB2 with DPF in a cluster
server?


Have you looked at the README file that comes with each FP?

--
Knut Stolze
DB2 Information Integration Development
IBM Germany


Jan 24 '06 #3
mike_li wrote:
Thanks for your response.

They are phyiscal nodes, 4 separate servers.

So we need to install the binary codes on 4 servers.


I have never done this myself (just worked with logical nodes so far), but
given that each server is independent of the others, yes, you will have to
install the FP on each one of them.

--
Knut Stolze
DB2 Information Integration Development
IBM Germany
Jan 24 '06 #4
mike_li wrote:
Thanks for your response.

They are phyiscal nodes, 4 separate servers.

So we need to install the binary codes on 4 servers.

Well.. depends if the filesystem for the binary code is cross mounted
then only one install of course.

Cheers
Serge

--
Serge Rielau
DB2 Solutions Development
DB2 UDB for Linux, Unix, Windows
IBM Toronto Lab
Jan 24 '06 #5
mike_li wrote:
We are considering to update from V8.1 Fixpak 8 to Fixpak 9.

Operating System Information:
OSName: AIX
NodeName: mdxxx01, mdxxx02, mdxxx03, mdxxx04
Version: 5
Release: 2

64 bits and DB2 code release SQL08021 with level identifier 03020106
Informational tokens are DB2 v8.1.1.80, special_13100, U800400_13100,
FixPak 8.

With DPF: 4 nodes with 16 partitions.
With 4 instances.
My concern:
--do i need to install Fixpak binary code FixPak9 on four nodes
individually?
Yes.
-- do i need to update each instance on 4 nodes ?
No. The instance-owning node (aka the one where the instance is "local" -
the rest of the nodes should have the first node's home directory mounted,
usually via NFS) only.
--Where can i find documentation on update DB2 with DPF in a cluster
server?


There should be plenty of documentation in the online books.
Jan 25 '06 #6
There are many online books on upgrade , but not specific on upgrading
instances with DPF.
Could you give a link? Thanks.

Mike

Darin McBride wrote:
mike_li wrote:
We are considering to update from V8.1 Fixpak 8 to Fixpak 9.

Operating System Information:
OSName: AIX
NodeName: mdxxx01, mdxxx02, mdxxx03, mdxxx04
Version: 5
Release: 2

64 bits and DB2 code release SQL08021 with level identifier 03020106
Informational tokens are DB2 v8.1.1.80, special_13100, U800400_13100,
FixPak 8.

With DPF: 4 nodes with 16 partitions.
With 4 instances.
My concern:
--do i need to install Fixpak binary code FixPak9 on four nodes
individually?


Yes.
-- do i need to update each instance on 4 nodes ?


No. The instance-owning node (aka the one where the instance is "local" -
the rest of the nodes should have the first node's home directory mounted,
usually via NFS) only.
--Where can i find documentation on update DB2 with DPF in a cluster
server?


There should be plenty of documentation in the online books.


Jan 25 '06 #7
mike_li wrote:
There are many online books on upgrade , but not specific on upgrading
instances with DPF.
Could you give a link? Thanks.

Mike

Darin McBride wrote:
mike_li wrote:
[snip]
> --Where can i find documentation on update DB2 with DPF in a cluster
> server?


There should be plenty of documentation in the online books.


http://publib.boulder.ibm.com/infoce.../v8//index.jsp

-> Installing
-> Database systems
-> DB2 servers
-> DB2 UDB Enterprise Server Edition (partitioned)
-> AIX

After you've opened up all the twisties to this point, you should see plenty
of information on setting up a partitioned cluster. This should help
explain the set up of DPF - the only question left is whether applying a
fixpak to a single node applies it to all nodes. That information should
be in the fixpak readme. However, even without reading the fixpak readme,
the implication is that if you need to install to all nodes, you need to
apply a fixpak to all nodes. And since you only run db2icrt on a single
node, you only need to run db2iupdt on a single node. Those implications
are, in fact, true.

I hope that helps.
Jan 26 '06 #8
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.
Darin McBride wrote:
mike_li wrote:
There are many online books on upgrade , but not specific on upgrading
instances with DPF.
Could you give a link? Thanks.

Mike

Darin McBride wrote:
mike_li wrote:
[snip]
--Where can i find documentation on update DB2 with DPF in a cluster
> server?

There should be plenty of documentation in the online books.


http://publib.boulder.ibm.com/infoce.../v8//index.jsp

-> Installing
-> Database systems
-> DB2 servers
-> DB2 UDB Enterprise Server Edition (partitioned)
-> AIX

After you've opened up all the twisties to this point, you should see plenty
of information on setting up a partitioned cluster. This should help
explain the set up of DPF - the only question left is whether applying a
fixpak to a single node applies it to all nodes. That information should
be in the fixpak readme. However, even without reading the fixpak readme,
the implication is that if you need to install to all nodes, you need to
apply a fixpak to all nodes. And since you only run db2icrt on a single
node, you only need to run db2iupdt on a single node. Those implications
are, in fact, true.

I hope that helps.


Jan 26 '06 #9
mike_li wrote:
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:

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.


That would be 17 partitions. ;-) The 01 server has 5 partitions (0-4).

Jan 26 '06 #10

This thread has been closed and replies have been disabled. Please start a new discussion.

Similar topics

0
by: Carl Castrianni | last post by:
I have UDB ESE fixpak 2 installed on a Windows XP Pro machine. I downloaded ESE fixpak 3 (and fixpak 4) from the IBM Web site. When I run the fixpak 3 installer (or the fixpak 4 installer for...
3
by: jacelyn Yswan via DBMonster.com | last post by:
db2 version 6.1 (Sun Solaris 7) when i try to update use the FixPak 11 db2admin start, it will hang.. why this will happen.. and what should i do to solve this problem?? ps: Help!!! thanks a...
5
by: Mary Lei | last post by:
I have problems connecting to ftp server to obtain the solaris fixpak to upgrade to DB2 8.2.1 ...
2
by: Christos Kalantzis | last post by:
Hello Gentlemen, I have a table which is the highest level table in my DB design...ie...all tables have foreign keys that if the chain is followed, lead to this table. This table had quite a...
6
by: chrisg | last post by:
I have installed (what I thought was) DB2 7.2 FP5 (as my starting point, it was 7.2 with FP5 applied) on my AIX 4.3.3 boxes. This is what I get. # lslpp -L | grep db2 db2_07_01.cj ...
4
by: jsorianop | last post by:
-------------------------------------------------------------------------------- I have HP-UX ia64 and db2 version 8.1 fp 6, i want to upgrade to 8.1 fixpak 11, but when i tried to install it, i...
8
by: Christopher Keller | last post by:
Hello, does anyone know why on the IBM download section of the UDB Support page http://www-306.ibm.com/software/data/db2/udb/support/ FP 13, 11 and 10 are listed prominently, but not FP12. We...
1
by: aj | last post by:
I'm currently on DB2 LUW v8.1 fixpack 5 DB21085I Instance "xxxx" uses "32" bits and DB2 code release "SQL08015" with level identifier "02060106". Informational tokens are "DB2 v8.1.0.48",...
1
by: VikingDK | last post by:
Hi all I recently updated my DB2 Enterprise Server from fixpak 3 to fixpak 4. Everything seemed to go smoothly, but a few hours after the update, I found out that I could no longer connect to our...
0
by: DolphinDB | last post by:
Tired of spending countless mintues downsampling your data? Look no further! In this article, you’ll learn how to efficiently downsample 6.48 billion high-frequency records to 61 million...
0
by: jfyes | last post by:
As a hardware engineer, after seeing that CEIWEI recently released a new tool for Modbus RTU Over TCP/UDP filtering and monitoring, I actively went to its official website to take a look. It turned...
0
by: ArrayDB | last post by:
The error message I've encountered is; ERROR:root:Error generating model response: exception: access violation writing 0x0000000000005140, which seems to be indicative of an access violation...
1
by: PapaRatzi | last post by:
Hello, I am teaching myself MS Access forms design and Visual Basic. I've created a table to capture a list of Top 30 singles and forms to capture new entries. The final step is a form (unbound)...
1
by: CloudSolutions | last post by:
Introduction: For many beginners and individual users, requiring a credit card and email registration may pose a barrier when starting to use cloud servers. However, some cloud server providers now...
1
by: Defcon1945 | last post by:
I'm trying to learn Python using Pycharm but import shutil doesn't work
1
by: Shællîpôpï 09 | last post by:
If u are using a keypad phone, how do u turn on JavaScript, to access features like WhatsApp, Facebook, Instagram....
0
by: Faith0G | last post by:
I am starting a new it consulting business and it's been a while since I setup a new website. Is wordpress still the best web based software for hosting a 5 page website? The webpages will be...
0
isladogs
by: isladogs | last post by:
The next Access Europe User Group meeting will be on Wednesday 3 Apr 2024 starting at 18:00 UK time (6PM UTC+1) and finishing by 19:30 (7.30PM). In this session, we are pleased to welcome former...

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.