Re: Order of installation: ODS, r4gl & fgldb

Nils Myklebust wrote: > On Fri, 07 Aug 1998 20:41:31 -0400, "Manuel A. Daponte Santiago" > <mdaponte@prtc.net> wrote: > > >We have a fine installation with ODS 7.2 and the i4gl RDS but WITHOUT > >the fgldb, and now we need to buy and install the fgldb. > > > >Can we just install the debuger and everything will work fine? I'm > >asking this because I remember that I had a lot of problems when I > >installed something (like i4gl) after the engine with OnLine 5 (that > >time we had to reinstall the engine at the end) > > Unfortunately you allways have to install tools first and the engine > last. It's mainly some message files and possibly some other things > that will get messed up if you don't. Primarily message files. > We have been able to install new tools (ESQL/C in our case) in a new > directory first and then bring over all other files from the original > install directory by hand. There have also been some posts about more > automatic ways of doing this that you may be able to find at > http://www.dejanews.com (posted by Jonathan Leffler I think). Yes. Check out utils_jl in the DBA section at the IIUG web site: http://www.iiug.org/ There's one hiccup which I haven't yet resolved, namely that the ixcreate command doesn't properly handle renamed files -- this affects the 4gl.iem, 4glusr.iem, forms.iem (and I think one other similar file) in the msg/en_us/0333 directory when installing GLS (7.2x or later) versions of OnLine (IDS, whatever). The files are stored on the original distribution as n4gl.iem, etc, and ixcreate creates links to (or copies) the n4gl.iem file which no longer exists. I fix this up manually -- its a nuisance but I haven't worked out a general solution to the problem. > What you should do is to install from the original media into a new > directory, Yes. I strongly recommend doing this every time. I'll install a bunch of tools products (ie ISQL, I4GL, I4GL-RDS, I4GL-ID) or a bunch of server products (eg OnLine, SE and ESQL/C) which are all at the same release number (down to the .UCn) into a new directory. I then copy the relevant files into a working INFORMIXDIR (actually, I usually use symlinks rather than copying, but the principal is the same). Be aware that this does not copy $INFORMIXDIR/etc/.snfile around; it isn't listed in any of the product file lists. This doesn't affect the way the software works. It might give someone auditing your system conniptions, though. > bring over the configuration files (and log files if they > aren't placed somewhere else) and rename the directories (or your > environment variables) when you have established that everything > works as it should. Or change the symbolic link /usr/informix from pointing to the old installation to pointing to the new installation. -- Jonathan Leffler (jleffler@informix.com, jleffler@earthlink.net) Guardian of DBD::Informix v0.59 -- see http://www.perl.com/CPAN #include <disclaimer.h>