Actually a change from one *release* to the next will require the UPGRADEDB. It is only when going between PTFs and patches of the same release that the UPGRADEDB is not required.
Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] (change eye to i to reply) The only dumb question is the one that goes unasked. The command line is your friend. "Good enough" is the enemy of excellence. Sias Dealy <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 03/04/2003 08:44 Please respond to hnre To: [EMAIL PROTECTED] cc: Subject: Re: TSM AIX server upgrade 5.1.1.0 to 5.1.6.2 Going from 5.1.1.0 to 5.1.6.2 you do not need to worry about the upgradedb. The nomanclature is version.release.modification.patch . If you are going from one version to another is when you would encounter the upgradedb. Technically this is suppose to happen automatically during the upgrade. For some odd reason this does not happen all the time. Then just manually issue dsmerv upgradedb. Sias ________________________________________________ Get your own "800" number Voicemail, fax, email, and a lot more http://www.ureach.com/reg/tag ---- On , Zoltan Forray/AC/VCU ([EMAIL PROTECTED]) wrote: > Going to upgrade my production TSM AIX server from 5.1.1.0 to 5.1.6.2, > this weekend. > > I have been running the 5.1.6.2 level on a test server, with no issues > (other than it deleting the library definition during the install). > > I don't recall doing any UPGRADEDBs (it has been a while since the upgrade > form 5.1.1.x to 5.1.5/x) on our test TSM server ! > > Any suggestions/recommendations/experiences I should be aware of ? > > Of course, I will perform 2-DB FULL backups ! > >