ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Migration DB2 from V8.2 to V9.1/V9.5

Post new topic  Reply to topic
 Migration DB2 from V8.2 to V9.1/V9.5 « View previous topic :: View next topic » 
Author Message
maven
PostPosted: Mon Feb 23, 2009 10:59 pm    Post subject: Migration DB2 from V8.2 to V9.1/V9.5 Reply with quote

Novice

Joined: 03 Jun 2007
Posts: 15

hi,

Wanted to know if i'm migrating db2 from v8.5 to v9.1 / 9.5, will it have any impact on my mq(v6 and v7) and broker(v6.1).
Also can u refer me links where i can find the details for it.
Back to top
View user's profile Send private message
smdavies99
PostPosted: Mon Feb 23, 2009 11:16 pm    Post subject: Reply with quote

Jedi Council

Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.

AFAIK, there is no such product as DB2 8.5...
Lets assume that you are migrating from DB2 8.1/8.2 to V9.x

The DB2 Documentation has a complete section on how to do this. It is a good idea to test this on a separate system first though as ther is no going back unless your backups are really, really good.

The DB2 upgrade won't affect WMQ at all so that bit is ok.
As far as broker is concerned, as long as you have done the migration properly and made sure that the ODBC definitions were ok it should work fine.

That said, I had to do this a few months back and after some testing we decided NOT to migrate the databases at all.
We exported the user DB contents and then dropped the broker completely. After upgrading DB2, we re-created the databases with a few tweaks to alter the storage and performance. This was all done with scripts so it was an easy job.
Then we recreated the broker and did a complete re-deploy. Again everything was scripted and the whole process from start to finish took less than an hour.
However, this system did not use Pub/Sub at all so we didn't have to sorry about retained publications & subscription retentionetc. This might be different on your system.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995

Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions.
Back to top
View user's profile Send private message
askvorak
PostPosted: Mon Mar 02, 2009 7:25 am    Post subject: Reply with quote

Newbie

Joined: 23 May 2005
Posts: 3

smdavies99 - just wondering why you chose to drop and re-create your broker for your db2 upgrade.... ?

We just migrated a test server last week from db2 v8.1 to v9.5 and all we did was stop the broker, have the DBA's upgrade the database, then we restarted the broker and everything worked exactly as it had before - including the 100+ subscriptions that we have. We are on WMB V6.1 csd 3.

Just curious as we prepare to do this in our PROD environments.... Thanks!
Back to top
View user's profile Send private message
smdavies99
PostPosted: Mon Mar 02, 2009 10:17 am    Post subject: Reply with quote

Jedi Council

Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.

If you are not using Pub/Sub AND have your Database & Broker Creation scripts, it is quicker and more straightforward (less manual stuff to go wrong) to drop the broker, drom the db, upgrade DB2 and then rerun the DB creation script and broker creation script.
If you (and I see you are) using PUB/SUB then the situation is a bit more complex and it may well be worth doing the upgrade as you did.

Every site is different.

I would like a tool/something that could easily dump all the Publication & Subscriptions in a re-usable form. This would make setting up a decently running copy of an existing system much easier (for testing/debug purposes)
This would also satisfy the auditors of one system I know about.

I'm glad you got it upgrded without problem.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995

Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions.
Back to top
View user's profile Send private message
Pats21
PostPosted: Tue Mar 03, 2009 5:12 am    Post subject: Reply with quote

Disciple

Joined: 08 Sep 2006
Posts: 154

Just one note here ...

DB2v9.5 does not support Globally coordinated transaction support (‘XA’).
So if you are using this fnctionality then maybe you would like to give a rethink.


Below is the link that gives you the detailed system requirements for broker version 6.1
http://www-01.ibm.com/software/integration/wbimessagebroker/requirements/

I have checked this link for Solaris and AIX maybe you would like to check for your OS.

Happy migrating ...

Pats ...
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Migration DB2 from V8.2 to V9.1/V9.5
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.