Testing the 'free' versions - moving from Dev edition to Innovator-C
Malc P asked how to replace a Linux Developer edition with Innovator-C. Art Kagel said to install over it with the engine offline, or install to a new directory, copy ONCONFIG and sqlhosts, and relink INFORMIXDIR (suggesting a symbolic link). Malc used a separate directory and it worked. He then found Innovator-C rejects cross-instance queries like stores@inst2_soc:customer with error 908, calling it unfit.
Auto-generated by Claude from the posts below — may be imperfect; read the full thread.
Just a quick wisdom request - I have the Developer edition on a Linux box and want to replace it with Innovator-C; what's the best method to do this? Just untar the new version over the old and run 'ids_install' again, or should I remove the old Dev edition first?
You can either install Innovator over Developer (with the engine offline of course) and restart the instance or install into a new directory, copy the ONCONFIG and sqlhosts files from the developer installation to the innovator installation, then shutdown developer, relink INFORMIXDIR to point to the Innovator installation, and restart the instance. It really is that simple. Art Art S. Kagel Advanced DataTools (www.advancedatatools.com) Blog: http://informix-myview.blogspot.com/ Disclaimer: Please keep in mind that my own opinions are my own opinions and do not reflect on my employer, Advanced DataTools, the IIUG, nor any other organization with which I am associated either explicitly, implicitly, or by inference. Neither do those opinions reflect those of other individuals affiliated with any entity with which I am affiliated nor those of the entities themselves. On Mon, Jan 23, 2012 at 11:50 AM, Malc P <malcrp@googlemail.com> wrote: > Just a quick wisdom request - I have the Developer edition on a Linux box > and want to replace it with Innovator-C; what's the best method to do this? > Just untar the new version over the old and run 'ids_install' again, or > should I remove the old Dev edition first? > _______________________________________________ > Informix-list mailing list > Informix-list@iiug.org > http://www.iiug.org/mailman/listinfo/informix-list >
Art, thanks - I've gone for the separate INFORMIXDIR install (just had to change $INFORMIXDIR, $PATH and some paths in $ONCONFIG) and it's come up just fine.
Great! To make life a bit easier (so you don't have to change INFORMIXDIR or PATH in any users profile or in various scripts and cron jobs, make the value pointed to by INFORMIXDIR be a symbolic link that you can redirect to the new directory and always set PATH and LD_LIBRARY_PATH using $INFORMIXDIR. Saves lots of grief when that script you forgot to modify that runs once a year wakes up next month and fails. ;-) Art Art S. Kagel Advanced DataTools (www.advancedatatools.com) Blog: http://informix-myview.blogspot.com/ Disclaimer: Please keep in mind that my own opinions are my own opinions and do not reflect on my employer, Advanced DataTools, the IIUG, nor any other organization with which I am associated either explicitly, implicitly, or by inference. Neither do those opinions reflect those of other individuals affiliated with any entity with which I am affiliated nor those of the entities themselves. On Tue, Jan 24, 2012 at 8:30 AM, Malc P <malcrp@googlemail.com> wrote: > > > Art, thanks - I've gone for the separate INFORMIXDIR install (just had to > change $INFORMIXDIR, $PATH and some paths in $ONCONFIG) and it's come up > just fine. > _______________________________________________ > Informix-list mailing list > Informix-list@iiug.org > http://www.iiug.org/mailman/listinfo/informix-list >
OK looks like some *really* crippling feature exclusions, the most annoying being the unavailability of connecting from one instance to another even on the same box;
e.g.
Set up two instances, inst1_soc and inst2_soc on the same box.
Connect to inst1_soc with dbaccess and then issue an SQL that tries to connect to the second:
SELECT * FROM stores@inst2_soc:customer
This returns "908: Attempt to connect to database server (inst2_soc) failed"
Oddly, there are no relevant messages in the online log.
Although it will allow:
CONNECT TO 'stores@inst2_soc'
Means Innovator-C is not really fit for purpose. Ho-hum.