Re: Upgrade to 3.1.2.0
1998-10-07 12:46:38
I just did the upgrade from 3.1.1.5 to 3.1.2.0 on our AIX-server.
The upgrade is done automagically during the installation.
However, neither the documentation, nor the script itself tells you what
is happening/what to do.
Information on this should be included to avoid confusion.
On Wed, 7 Oct 1998, Roger Hohmann wrote:
> As far as I understood the IBM'ers at ADSM Conference in Karlsruhe 2 weeks
> ago, an upgrate db is necessary in ANY case when upgrading to 3.1.2 because
> the database IS changed. Maybe one of the IBM'ers can solve this confusion?
>
> -----Original Message-----
> From: Jennifer Davis [SMTP:jedavis AT DFW DOT NET]
> Sent: Wednesday, October 07, 1998 4:08 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: Upgrade to 3.1.2.0
>
> To All of those who responded to this email indicating that the upgradebd
> parameter WAS required, could you write back exactly what your ADSM code
> levels were BEFORE your upgrade to 3.1.2.0.
>
> I had a V2 server that I upgraded to 3.1.2.0 and, yes, it did require the
> upgradedb parm (which makes sense because the act of going from 2 to 3
> requires this). However, my 3.1.1.0 server did not require this parm to
> start and run. Now, I am really confused - is something wrong with my V3 to
> V3.1.2.0 server since it did not require this parm - all of yours did?
>
> What indicatation did you have that told you that this was necessary since
> the server READMEs that I checked make no mention of this requirement?
>
> Thanks,
>
> Jennifer :-(
>
>
> At 08:37 AM 10/7/98 -0400, you wrote:
> >Yes, the Upgrade from 3.1.1.3 to 3.1.2.0 on the NT platform involved a
> >\dsmserv.exe upgradedb command before the database could be opened.
> >
> >Regards,
> >John Stephens
> >**********************************
> >Date: Tue, 6 Oct 1998 16:12:02 -0500
> >From: Julie Phinney <jphinney AT HUMANA DOT COM>
> >Subject: Upgrade to 3.1.2.0
> >
> >Does anyone know if the server upgrade from 3.1.1.3 to 3.1.2.0 requires an
> >/UPGRADEDB? I can't seem to find that in the doc, but it was in a hold
> >system action on the PTF for MVS.
> >Thanks,
> >Julie
> >
> >----------------------------------------------------------------
> >The information transmitted is intended only for the person or entity to
> >which it is addressed and may contain confidential and/or privileged
> >material. Any review, retransmission, dissemination or other use of, or
> >taking of any action in reliance upon, this information by persons or
> >entities other than the intended recipient is prohibited. If you
> received
> >this in error, please contact the sender and delete the material from any
> >computer.
> >
> >
>
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- Upgrade to 3.1.2.0, Julie Phinney
- Re: Upgrade to 3.1.2.0, Steven P Roder
- Upgrade to 3.1.2.0, John W. Stephens
- Re: Upgrade to 3.1.2.0, Buechler, Becky
- Re: Upgrade to 3.1.2.0, Jennifer Davis
- Re: Upgrade to 3.1.2.0, Buechler, Becky
- Re: Upgrade to 3.1.2.0, Andrew Raibeck
- Re: Upgrade to 3.1.2.0, Dirk Kastens
- Re: Upgrade to 3.1.2.0, Roger Hohmann
- Re: Upgrade to 3.1.2.0, Steven P Roder
- Re: Upgrade to 3.1.2.0,
Tom Tann{s <=
- Re: Upgrade to 3.1.2.0, Dirk Kastens
- Re: Upgrade to 3.1.2.0, Tom Tann{s
- Re: Upgrade to 3.1.2.0, John W. Stephens
- Upgrade to 3.1.2.0, Tom Brooks
- Re: Upgrade to 3.1.2.0, Jennifer Davis
- Re: Upgrade to 3.1.2.0, Sheelagh Treweek
- Re: Upgrade to 3.1.2.0, Jennifer Davis [SMTP:jedavis
|
|
|