Between Miguel Celi, Judith Kibler and Paul Martin, the "normal" steps are covered.
After running the migrates, you can run db2level to check your DB2 level FixPak 4 is some cases, will have a signature of "DB2 v7.1.0.50", even though the documentation says it should be "DB2 v7.1.0.51" FixPak 5 should have a signature of "DB2 v7.1.0.55" Here are some additional steps that you may have to deal with. If you are using TSM (Tivoli Storage Manager) with DB2, check the db2profile file (its in sqllib) and see if the dsm variables were put in that file. db2imigr appears to remove them from the db2profile file and if those variables are not somewhere else, TSM and DB2 will not communicate properly. db2imigr makes a copy of db2profile and names it db2profile.old. A line is now inserted into db2profile that says do not edit this file, but if the file has already been edited, you should be prepared to either put the dsm variables elsewhere or be ready to add them back. We found that using dasimigr will successfully migrate the DAS instance. I'm pretty sure db2imgr won't work for DAS. If you happen to forget what your fenced id is, look in sqllib/ctrl/.fencedID. If your SA prefers to use SMIT to "manually" upgrade db2 code rather than using db2setup you may run into one or more of the issues below. Judith says "5) Probably need to update your DB2 product license (see page 28, Quick Beginnings)" If you have a problem with the DB2 product license you will see messages in db2diag.log indicating you are now using a "Try and Buy" license or a SQL8017W The number of processors on the machine exceeds the defined entitlement of "1" for the product. Run db2licm -l to see what you are now licensed for. If you have the "Try and Buy" problem you can fix that by running db2licm -a <license filename> The license file is on the install CD (but I can't remember where) The instance owner has authority to run db2licm to make changes. If you have the processor issue, you first need to know how many processors you have. On AIX you can use the following command to find that out: lsdev -C | grep -i proc | wc -l If you are in a EEE environment use: rah "lsdev -C | grep -i proc | wc -l" Then you use the following command to fix the license: db2licm -n <product password> <number of processors> You get the <product password> from the output of db2licm -l If you are working with EEE, you need to run the db2licm -n on every node and it is possible that you have different numbers of processors on each node, which is why you need to use the rah command to run lsdev -C. You may run into a really strange looking problem, when running a CLP command or connecting to a database doesn't work. If you hit this problem it is likely to be an issue with the links for DB2 files. From sqllib/bin you can run: dump -H db2. This shows the libraries that the executables are using. There are also links in /usr/lib and /usr/include that you can look at. If you see references to V6 and V7 code then there is a link issue If you even suspect a link issue, you can run db2ln from /usr/lpp/db2_07_01/cfg/db2ln (on AIX at least). If you are working with EEE you will need to do this for all the nodes, probably with a dsh command. Running db2ln requires root authority. In the Quick Beginnings book there is a section on Migrating Explain Tables, using the db2exmig. This step is NOT needed if migrating from Version 6 to Version 7 and will fail if you try to run it. "Martin, Paul" wrote: > > In addition to the steps Judith identified you may also want to add step 7.a > bind the db2ubind and db2cli packages on your databases > > -----Original Message----- > From: [EMAIL PROTECTED] > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Sent: 3/7/02 5:15 PM > Subject: Re: [DB2EUG] Migrating from version 6.1 to version 7.2 > > Hi Tim, > > I just did this last December with DB2 UDB EE on AIX. Here is what I > did (as > closely as I can remember...) > > 1) db2stop > 2) Offline backup > 3) Install v7.2 > 4) Install FP5 > 5) Probably need to update your DB2 product license (see page 28, Quick > Beginnings) > 6) Run db2imigr to migrate your instance(s). It says to also run the > db2imigr > on the DAS instance, but I had trouble with that. I ended up dropping > and > recreating a new v7.2 instance. > 7) db2start > 8) Test! > 9) Another offline backup > > Note: You don't have to migrate the database(s) if you are going from > v6.1 to > v7.2, per page 71 in the Quick Beginnings manual. > > I am going from memory and I have slept since then, so I may not be > remembering > everything. I think it is at least close! Others will chime in if I > forgot > something! > > Good luck! > Judy > > [EMAIL PROTECTED] on 03/07/2002 11:42:42 AM > > Please respond to [EMAIL PROTECTED] > > > > To: [EMAIL PROTECTED] > > cc: (bcc: Judy Kibler/Nashville) > > > > Subject: [DB2EUG] Migrating from version 6.1 to version 7.2 > > > Hello list, > > I am currently planning on upgrading some DB2 UDB servers to version 7.1 > fixpack 5(7.2) of DB2. I have been > looking through the Quick beginnings manual for migrating to version 6.1 > and was wondering if the process is the > same for migrating to version 7.2. Also, I notice the db2uiddl is an > optional feature in this manual when > upgrading to 6.1, I was wondering if that is still the same for > upgrading > to 7.2. If it is still optional, how important > of a task is it? > > Currently, this is my plan : > Take an offline backup of all of the databases > Execute db2stop > Execute db2ckmig against all of the databases and verify results > Install the new db2 version > Execute db2 migrate command against all of the databases > Execute db2start > > Does this sound correct? Any other things to watch out for would be > appreciated. > > Thanks, > Tim > > - > ::: When replying to the list, please use 'Reply-All' and make sure > ::: a copy goes to the list ([EMAIL PROTECTED]). > *** You are subscribed to [EMAIL PROTECTED] > *** To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED] > > - > ::: When replying to the list, please use 'Reply-All' and make sure > ::: a copy goes to the list ([EMAIL PROTECTED]). > *** You are subscribed to [EMAIL PROTECTED] > *** To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED] > - > ::: When replying to the list, please use 'Reply-All' and make sure > ::: a copy goes to the list ([EMAIL PROTECTED]). > *** You are subscribed to [EMAIL PROTECTED] > *** To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED] - ::: When replying to the list, please use 'Reply-All' and make sure ::: a copy goes to the list ([EMAIL PROTECTED]). *** You are subscribed to [EMAIL PROTECTED] *** To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED]
