RE: 7.30 to 7.31 IDS upgrade
Posted in 2000
Someone asked whether upgrading IDS 7.30 to 7.31 needs more than installing the new engine and restarting, since the printed manuals say nothing. Answer: the procedure is in the release notes shipped with the product ($INFORMIXDIR/release/.../SERVERS_7.3) — go to single-user mode, onmode -l and -c so the last log holds only a checkpoint, run oncheck, take a level-0 backup, shut down, start the new server, update statistics, re-check and take another level-0 backup, watching online.log. Contributors also advised installing into a version-specific directory with INFORMIXDIR as a symlink (and using LD_LIBRARY_PATH) so reversion is quick, plus testing on a separate instance first.
Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.
Topics: Installation, Setup & Upgrades, Server Administration, Licensing & Editions, Versions, Editions & End-of-Life
Read Release Notes, which come with your IDS 7.31 release.
Our IDS 7.31.UC3-1 release contained the following instructions in
$INFORMIXDIR/release/en_us/0333/SERVERS_7.3. Similar instructions were
provided when I upgraded from IDS 7.24 to 7.30.
Conversion and Reversion
------------------------
The 7.31.UC1 and 7.31.TC1 releases support automatic data
conversion from previous versions to 7.31 INFORMIX versions, as well as
automatic data reversion from 7.31 to older versions.
To convert or revert existing data, use the following guidelines:
CONVERSION
----------------------
Source
----------------------
*Single user mode
onmode -sy
onmode -l
onmode -c
*Data integrity check
oncheck
*Level-0 backup
*Server shutdown
onmode -yuk
---------------------
Target
---------------------
Server startup
oninit*Update statistics
highly recommended
*Data integrity check
oncheck options
*Level-0 backup
REVERSION
..(clipped)..
During the conversion or reversion process, monitor the server
online.log activity.
-----Original Message-----
From: Surfer!
To: informix-list@iiug.org
Sent: 2/26/00 8:19 AM
Subject: 7.30 to 7.31 IDS upgrade
I've been trying to find out if there is anything beyond installing the
new engine and starting it up for this upgrade, which is what I would
have expected based on moving from 7.24 to 7.30 - in other words about
30 minutes work at the outside most of which is installing the three IDS
licences to ensure that '.snfile' is correct. I'm not including the
time for the level 0 archive which I would want done beforehand!
The recent postings about upgrade to 7.31 made me wonder.
I've RTFM to no avail!
TIA
--
Surfer!
Thanks. In other words I don't get the correct FM to read until I've
read the software onto a computer! So I need to read it onto another
machine (can probably do that in the office) or into a difference
directory on the customers machine!
Thanks, Informix. If ever there was something to put in the little
printed manual in the brown box....
In article <899ccr$2r$1@news.xmission.com>, Bernstein, Rick
<rbernste@alarismed.com> writes
>
>Read Release Notes, which come with your IDS 7.31 release.
>
>Our IDS 7.31.UC3-1 release contained the following instructions in
>$INFORMIXDIR/release/en_us/0333/SERVERS_7.3. Similar instructions were
>provided when I upgraded from IDS 7.24 to 7.30.
>
> Conversion and Reversion
> ------------------------
>
> The 7.31.UC1 and 7.31.TC1 releases support automatic data
> conversion from previous versions to 7.31 INFORMIX versions, as well as
> automatic data reversion from 7.31 to older versions.
>
> To convert or revert existing data, use the following guidelines:
>
> CONVERSION
> ----------------------
> Source
> ----------------------
>*Single user mode
> onmode -sy
> onmode -l
> onmode -c>
>*Data integrity check
> oncheck
>*Level-0 backup>
>*Server shutdown
> onmode -yuk>
> ---------------------
> Target
> ---------------------
> Server startup
> oninit>*Update statistics
> highly recommended
>*Data integrity check
> oncheck options
>*Level-0 backup
>
> REVERSION
> ..(clipped)..
>
>During the conversion or reversion process, monitor the server
>online.log activity.
Monitor for what? Its a bit like the vague statement in a course I am
taking 'browse to chapter 3' without saying why!
>
>
>-----Original Message-----
>From: Surfer!
>To: informix-list@iiug.org
>Sent: 2/26/00 8:19 AM
>Subject: 7.30 to 7.31 IDS upgrade
>
>
>I've been trying to find out if there is anything beyond installing the
>new engine and starting it up for this upgrade, which is what I would
>have expected based on moving from 7.24 to 7.30 - in other words about
>30 minutes work at the outside most of which is installing the three IDS
>licences to ensure that '.snfile' is correct. I'm not including the
>time for the level 0 archive which I would want done beforehand!
>
>The recent postings about upgrade to 7.31 made me wonder.
>
>I've RTFM to no avail!
>
>TIA
>
--
Surfer!
In article <d+tSFBAkJEu4EwJL@nevis-view.demon.co.uk>, Surfer! <nevis-
view@nospam.demon.co.uk> writes
>
>Thanks. In other words I don't get the correct FM to read until I've
>read the software onto a computer! So I need to read it onto another
>machine (can probably do that in the office) or into a difference
>directory on the customers machine!
>
Correct. But you should be installing it into a separate directory
/machine and
a) Reading the release notes
b) TESTING it against a test instance before you make it live.
>Thanks, Informix. If ever there was something to put in the little
>printed manual in the brown box....
>
>
>In article <899ccr$2r$1@news.xmission.com>, Bernstein, Rick
><rbernste@alarismed.com> writes
>>
>>Read Release Notes, which come with your IDS 7.31 release.
>>
>>Our IDS 7.31.UC3-1 release contained the following instructions in
>>$INFORMIXDIR/release/en_us/0333/SERVERS_7.3. Similar instructions were
>>provided when I upgraded from IDS 7.24 to 7.30.
>>
>> Conversion and Reversion
>> ------------------------
>>
>> The 7.31.UC1 and 7.31.TC1 releases support automatic data
>> conversion from previous versions to 7.31 INFORMIX versions, as well as
>> automatic data reversion from 7.31 to older versions.
>>
>> To convert or revert existing data, use the following guidelines:
>>
>> CONVERSION
>> ----------------------
>> Source
>> ----------------------
>>*Single user mode
>> onmode -sy
>> onmode -l
>> onmode -c
Don't forget this to ensure that the last logical log contains only
a checkpoint record. This is required and according to Informix
UK Tech Support should be done prior to ANY upgrade. It makes
patching the instance MUCH easier if needed.
>>
>>*Data integrity check
>> oncheck
>>*Level-0 backup Don't forget this even if the upgrade has worked for 15 other
customers prior to this upgrade...
>>
>>*Server shutdown
>> onmode -yuk>>
>> ---------------------
>> Target
>> ---------------------
>> Server startup
>> oninit>>*Update statistics
>> highly recommended
>>*Data integrity check
>> oncheck options
>>*Level-0 backup
Don't forget this either. You need to be able to get back to here
if you get a problem. The rule is checkpoint where you are all
the time.
>>
>> REVERSION
>> ..(clipped)..
>>
>>During the conversion or reversion process, monitor the server
>>online.log activity.
>
>Monitor for what? Its a bit like the vague statement in a course I am
>taking 'browse to chapter 3' without saying why!
>
>>
>>
>>-----Original Message-----
>>From: Surfer!
>>To: informix-list@iiug.org
>>Sent: 2/26/00 8:19 AM
>>Subject: 7.30 to 7.31 IDS upgrade
>>
>>
>>I've been trying to find out if there is anything beyond installing the
>>new engine and starting it up for this upgrade, which is what I would
>>have expected based on moving from 7.24 to 7.30 - in other words about
>>30 minutes work at the outside most of which is installing the three IDS
>>licences to ensure that '.snfile' is correct. I'm not including the
>>time for the level 0 archive which I would want done beforehand!
>>
>>The recent postings about upgrade to 7.31 made me wonder.
>>
>>I've RTFM to no avail!
>>
>>TIA
>>
>
--
David Williams
Yah dude, like, don't even *think* about installing a new release over the
current one before testing and benchmarking all your applications on it first!
David Williams wrote:
> In article <d+tSFBAkJEu4EwJL@nevis-view.demon.co.uk>, Surfer! <nevis-
> view@nospam.demon.co.uk> writes
> >
> >Thanks. In other words I don't get the correct FM to read until I've
> >read the software onto a computer! So I need to read it onto another
> >machine (can probably do that in the office) or into a difference
> >directory on the customers machine!
> >
>
> Correct. But you should be installing it into a separate directory
> /machine and
>
> a) Reading the release notes
> b) TESTING it against a test instance before you make it live.
>
> >Thanks, Informix. If ever there was something to put in the little
> >printed manual in the brown box....
> >
> >
> >In article <899ccr$2r$1@news.xmission.com>, Bernstein, Rick
> ><rbernste@alarismed.com> writes
> >>
> >>Read Release Notes, which come with your IDS 7.31 release.
> >>
> >>Our IDS 7.31.UC3-1 release contained the following instructions in
> >>$INFORMIXDIR/release/en_us/0333/SERVERS_7.3. Similar instructions were
> >>provided when I upgraded from IDS 7.24 to 7.30.
> >>
> >> Conversion and Reversion
> >> ------------------------
> >>
> >> The 7.31.UC1 and 7.31.TC1 releases support automatic data
> >> conversion from previous versions to 7.31 INFORMIX versions, as well as
> >> automatic data reversion from 7.31 to older versions.
> >>
> >> To convert or revert existing data, use the following guidelines:
> >>
> >> CONVERSION
> >> ----------------------
> >> Source
> >> ----------------------
> >>*Single user mode
> >> onmode -sy
> >> onmode -l
> >> onmode -c>
> Don't forget this to ensure that the last logical log contains only
> a checkpoint record. This is required and according to Informix
> UK Tech Support should be done prior to ANY upgrade. It makes
> patching the instance MUCH easier if needed.
>
> >>
> >>*Data integrity check
> >> oncheck
> >>*Level-0 backup> Don't forget this even if the upgrade has worked for 15 other
> customers prior to this upgrade...
>
> >>
> >>*Server shutdown
> >> onmode -yuk> >>
> >> ---------------------
> >> Target
> >> ---------------------
> >> Server startup
> >> oninit> >>*Update statistics
> >> highly recommended
> >>*Data integrity check
> >> oncheck options
> >>*Level-0 backup
>
> Don't forget this either. You need to be able to get back to here
> if you get a problem. The rule is checkpoint where you are all
> the time.
>
> >>
> >> REVERSION
> >> ..(clipped)..
> >>
> >>During the conversion or reversion process, monitor the server
> >>online.log activity.
> >
> >Monitor for what? Its a bit like the vague statement in a course I am
> >taking 'browse to chapter 3' without saying why!
> >
> >>
> >>
> >>-----Original Message-----
> >>From: Surfer!
> >>To: informix-list@iiug.org
> >>Sent: 2/26/00 8:19 AM
> >>Subject: 7.30 to 7.31 IDS upgrade
> >>
> >>
> >>I've been trying to find out if there is anything beyond installing the
> >>new engine and starting it up for this upgrade, which is what I would
> >>have expected based on moving from 7.24 to 7.30 - in other words about
> >>30 minutes work at the outside most of which is installing the three IDS
> >>licences to ensure that '.snfile' is correct. I'm not including the
> >>time for the level 0 archive which I would want done beforehand!
> >>
> >>The recent postings about upgrade to 7.31 made me wonder.
> >>
> >>I've RTFM to no avail!
> >>
> >>TIA
> >>
> >
>
> --
> David Williams
--
Richard C. Auslander
Database Manager
AirFlash, Inc.
1733 Woodside Rd., Suite #110
Redwood City, CA 94061
(650) 556-7928
www.airflash.com
Surfer! wrote:
>
> Thanks. In other words I don't get the correct FM to read until I've
> read the software onto a computer! So I need to read it onto another
> machine (can probably do that in the office) or into a difference
> directory on the customers machine!
>
> Thanks, Informix. If ever there was something to put in the little
> printed manual in the brown box....
>
> In article <899ccr$2r$1@news.xmission.com>, Bernstein, Rick
> <rbernste@alarismed.com> writes
> >
> >Read Release Notes, which come with your IDS 7.31 release.
> >
> >Our IDS 7.31.UC3-1 release contained the following instructions in
> >$INFORMIXDIR/release/en_us/0333/SERVERS_7.3. Similar instructions were
> >provided when I upgraded from IDS 7.24 to 7.30.
> >
> > Conversion and Reversion
> > ------------------------
> >
> > The 7.31.UC1 and 7.31.TC1 releases support automatic data
> > conversion from previous versions to 7.31 INFORMIX versions, as well as
> > automatic data reversion from 7.31 to older versions.
> >
> > To convert or revert existing data, use the following guidelines:
> >
> > CONVERSION
> > ----------------------
> > Source
> > ----------------------
> >*Single user mode
> > onmode -sy
> > onmode -l
> > onmode -c> >
> >*Data integrity check
> > oncheck
> >*Level-0 backup> >
> >*Server shutdown
> > onmode -yuk> >
> > ---------------------
> > Target
> > ---------------------
> > Server startup
> > oninit> >*Update statistics
> > highly recommended
> >*Data integrity check
> > oncheck options
> >*Level-0 backup
> >
> > REVERSION
> > ..(clipped)..
> >
> >During the conversion or reversion process, monitor the server
> >online.log activity.
>
> Monitor for what? Its a bit like the vague statement in a course I am
> taking 'browse to chapter 3' without saying why!
>
> >
> >
> >-----Original Message-----
> >From: Surfer!
> >To: informix-list@iiug.org
> >Sent: 2/26/00 8:19 AM
> >Subject: 7.30 to 7.31 IDS upgrade
> >
> >
> >I've been trying to find out if there is anything beyond installing the
> >new engine and starting it up for this upgrade, which is what I would
> >have expected based on moving from 7.24 to 7.30 - in other words about
> >30 minutes work at the outside most of which is installing the three IDS
> >licences to ensure that '.snfile' is correct. I'm not including the
> >time for the level 0 archive which I would want done beforehand!
It is always best to install new versions into a new directory
parallel to the older version so you can quickly and easily revert
without having to perform a new install of the old software which
takes 30+ minutes. If your INFORMIXDIR is hardwired in too many
places just rename the old INFORMIXDIR to a version specific name,
name the new install directory a version specific name, set
INFORMIXDIR to the new directory JUST for the install, then make a
symbolic link using the original INFORMIXDIR pointing to the new
install directory and complete the conversion. Now if you need to
revert just run the reversion, shutdown, relink INFORMIXDIR to the
old (renamed) install directory, and restart the older version.
> >The recent postings about upgrade to 7.31 made me wonder.
> >
> >I've RTFM to no avail!
--
Art S. Kagel & Family
kagel@erols.com
In article <38DB7A99.972E2245@erols.com>, Art S. Kagel & Family <kagel@erols.com> writes >Surfer! wrote: >> >> Thanks. In other words I don't get the correct FM to read until I've >> read the software onto a computer! So I need to read it onto another >> machine (can probably do that in the office) or into a difference >> directory on the customers machine! <snip> > >It is always best to install new versions into a new directory >parallel to the older version so you can quickly and easily revert >without having to perform a new install of the old software which >takes 30+ minutes. This is much harder now that the install puts symbolic links into /usr/bin (or some similar place) pointing into INFORMIXDIR. It was my normal practise! It also makes having different versions on the same machine an interesting proposition. > If your INFORMIXDIR is hardwired in too many >places just rename the old INFORMIXDIR to a version specific name, >name the new install directory a version specific name, set >INFORMIXDIR to the new directory JUST for the install, then make a >symbolic link using the original INFORMIXDIR pointing to the new >install directory and complete the conversion. Now if you need to >revert just run the reversion, shutdown, relink INFORMIXDIR to the >old (renamed) install directory, and restart the older version. > >> >The recent postings about upgrade to 7.31 made me wonder. >> > >> >I've RTFM to no avail! > -- Surfer!
Surfer! wrote:
>
> In article <38DB7A99.972E2245@erols.com>, Art S. Kagel & Family
> <kagel@erols.com> writes
> >Surfer! wrote:
> >>
> >> Thanks. In other words I don't get the correct FM to read until I've
> >> read the software onto a computer! So I need to read it onto another
> >> machine (can probably do that in the office) or into a difference
> >> directory on the customers machine!
> <snip>
> >
> >It is always best to install new versions into a new directory
> >parallel to the older version so you can quickly and easily revert
> >without having to perform a new install of the old software which
> >takes 30+ minutes.
>
> This is much harder now that the install puts symbolic links into
> /usr/bin (or some similar place) pointing into INFORMIXDIR. It was my
> normal practise! It also makes having different versions on the same
> machine an interesting proposition.
Having multiple versions on the same machine has always been an
interesting proposition, but in the words of Leonard McCoy,
"Interesting is a word and a half word...". As to the library links,
I'd ignore or remove them using LD_LIBRARY_PATH instead to point to
the correct $INFORMIXDIR/lib. In that way the most vexing of your
version problems is easily solved. Just have each version's
environment setup script set LD_LIBRARY_PATH when it sets the correct
INFORMIXDIR.
Besides, if you read carefully, multiple versions aside, I said to set
INFORMIXDIR to a generic directory name which will be a symbolic link
to the CURRENT verions you are using. In this way the install will
create the links to new libraries and warn you about the existence of
libraries that have not changed names between versions. If you have to
revert relinking the generic name to the older actual directory the
libraries will still all be found! Personally I install in directories
like /usr/informix/IDS7.31UC2X1 but set
INFORMIXDIR=/usr/informix/IDS7 to accomodate multiple servers runningdifferent versions you could make that IDS7.S1 and IDS7.S2 or somesuch.
> > If your INFORMIXDIR is hardwired in too many
> >places just rename the old INFORMIXDIR to a version specific name,
> >name the new install directory a version specific name, set
> >INFORMIXDIR to the new directory JUST for the install, then make a
> >symbolic link using the original INFORMIXDIR pointing to the new
> >install directory and complete the conversion. Now if you need to
> >revert just run the reversion, shutdown, relink INFORMIXDIR to the
> >old (renamed) install directory, and restart the older version.
> >
> >> >The recent postings about upgrade to 7.31 made me wonder.
> >> >
> >> >I've RTFM to no avail!
> >
>
> --
> Surfer!
--
Art S. Kagel & Family
kagel@erols.com
In article <mj$XHDA5Dbu4Ew$c@smooth1.demon.co.uk>, David Williams <djw@smooth1.demon.co.uk> writes >In article <d+tSFBAkJEu4EwJL@nevis-view.demon.co.uk>, Surfer! <nevis- >view@nospam.demon.co.uk> writes >> >>Thanks. In other words I don't get the correct FM to read until I've >>read the software onto a computer! So I need to read it onto another >>machine (can probably do that in the office) or into a difference >>directory on the customers machine! >> > > Correct. But you should be installing it into a separate directory > /machine and > > a) Reading the release notes > b) TESTING it against a test instance before you make it live. We should be so lucky. The customer has one machine with an Online instance running the live and SE running test! I keep suggesting a second machine and being told it's too expensive. <snip> -- Surfer!