Re: Upgrade to 3.1.2.0

Jennifer,

It is my understanding (and confirmed at the ADSM Conference at Karlsruhe)
that DB tables are updated and to back out of 3.1.2.1 would require a DB
to restored ... so it is essential to take a FULL DB backup first.

I have upgraded a test system (production one tomorrow!) on AIX and it is
not at all obvious that the DB was upgraded automatically.

But the information is in README.SRV.txt ...

----------------------------------------------------------------------
* NOTE * NOTE * NOTE * NOTE * NOTE * NOTE * NOTE * NOTE * NOTE *
* NOTE * NOTE * NOTE * NOTE * NOTE * NOTE * NOTE * NOTE * NOTE *

This server provides enhanced recovery log fault-tolerance and new
database entries to support enhanced functions.  If you start this
server over an existing ADSM database, you will not be able to remove
this server program and run the older server over the existing
database/recovery log.

IBM recommends that you perform a full database backup on any
ADSM server over which you plan to install this code, so you can
restore the database to the appropriate level should you decide to
remove this code.

* NOTE * NOTE * NOTE * NOTE * NOTE * NOTE * NOTE * NOTE * NOTE *
----------------------------------------------------------------------
Regards, Sheelagh
Regards, Sheelagh
------------------------------------------------------------------------------
Sheelagh Treweek                         Email: sheelagh.treweek AT oucs.ox.ac 
DOT uk
Sheelagh Treweek                         Email: sheelagh.treweek AT oucs.ox.ac 
DOT uk
Oxford University Computing Services     Tel:   +44 (0)1865 273205
13 Banbury Road, Oxford, OX2 6NN, UK     Fax:   +44 (0)1865 273275
------------------------------------------------------------------------------
> From owner-adsm-l AT vm.marist DOT edu  Fri Oct  9 03:56:23 1998
> From owner-adsm-l AT vm.marist DOT edu  Fri Oct  9 03:56:23 1998
> X-Sender: jedavis AT dfw DOT net
> Mime-Version: 1.0
> Date: Thu, 8 Oct 1998 21:53:43 -0500
> From: Jennifer Davis <jedavis AT DFW DOT NET>
> Subject: Re: Upgrade to 3.1.2.0
> To: ADSM-L AT VM.MARIST DOT EDU
>
> Thanks TOM for the information.... one more related question.........
>
> Since the UPGRADEDB is required, I would presume that there are some updates
> to the database tables (or something along those lines). If I wanted to
> deinstall 3.1.2.0 code, leaving my database and recovery log in place, and
> then install my base code again (plus pre 3.1.2.0 ptfs) for any reason, can
> I just restore a pre 3.1.2.0 backup over the existing DB and log to getback
> to a pre 3.1.2.0 state? Or do I have do issue a dsmserv format before the
> restore db?
>
> Thanks for your clarification!!
> P.S. Do you have any influence with getting the README files updated to
> reflect this great information that you have clarified for us?
>
> Jenn
>
>
> At 01:41 PM 10/8/98 PDT, you wrote:
> >OK, here is the word on Upgradedb to 3.1.2.0. UPGRADEDB is required! However,
> >on AIX it is done automatically from the scripts provided with ADSM install
> >process. Once the upgrade is done, the server halts. For N/T, the UPGRADEDB
> >is also done automatically. If the DSMSERV command includes UPGRADEDB and
> >RUNFILE as parameters, the server is halted after the upgrade. If RUNFILE is
> >not included, the server stays up after the upgrade. For MVS and SUN, the
> >UPGRADEDB must be explicilty specified. I'm not sure about the HP server.
> >If in doubt, specify the UPGRADEDB parameter. It will be ignored if the
> >upgrade has already taken place. Or, start the server, either background or
> >foreground. If the parameter is required but not specified, the server will
> >not start, but will issue a message to forgeround attempts. Also, the
> >UPGRADEDB requirement is discussed in the Quick Start Guide.
> >
> >Tom Brooks
> >ADSM Development
> >
> >