Old Informix media

I have a colleague that needs to move an Informix implementation from one server to another. The old server is NT4, the new is Win2k. Since there is a change in platform he suspects he'll need to reinstall Informix, but doesnt have the installation media. He has a valid license for the original product but can't find a place to get the media - download or otherwise. He's looking for IDS 7.22 Any ideas? tia

Be warned, IDS 7.22 will probably not work on Windows 2000 because of bug 99534: "7.23 FOR NT WILL NOT COME ONLINE AFTER LSA2FIXI.EXE HAS BEEN RUN. 7.30 WILL COME ONLINE BUT MESSAGE SERVICE WILL NOT START." "lsa2fixi.exe" was a Microsoft security patch which was part of NT service pack 4 and is in Win 2000. For this reason you probably need to consider upgrading to at least 7.23.TC14 - even then I'm not sure anyone's tested 7.23 on a Win 2000 box with recent OS patches. The latest 7.31 would be the lowest version I'd recommend. IDS versions above 7.30 are also easier to move from one machine to another using the buildreg utility. Regards Guy pan wrote: > I have a colleague that needs to move an Informix implementation from > one server to another. The old server is NT4, the new is Win2k. Since > there is a change in platform he suspects he'll need to reinstall > Informix, but doesnt have the installation media. He has a valid > license for the original product but can't find a place to get the > media - download or otherwise. He's looking for IDS 7.22 > > Any ideas? > > tia >

Great info. Any significant compatibility issues between 7.22 and 31? I'm assuming since this is a minor rev it's mostly bug fixes etc. This is for a small non-profit org where the IT budget is rolled up into things like fence repair, so there is no staff immediately available for anything but relatively trivial migration and no one to look at code if a migration to a new version does not work. Thus the motivation for 7.22. Sounds like 7.31 for W2K is the way to go. Thanks, pan

pan wrote: > Great info. Any significant compatibility issues between 7.22 and 31? You should be able to upgrade and not worry about it. Since you're moving to another machine aswell perhaps the most worry free thing to do would be to dbexport all your databases (depending how much you have), create the dbspaces you need on the new system, make sure you have sufficient physical and logical logs allocated, and dbimport the databases to the new system, paying attention to the dbimport/dbexport options to make sure you either use the same dbspaces or specify new ones as desired. A read of the Migration Guide is recommended. > I'm assuming since this is a minor rev it's mostly bug fixes etc. well.... there were a few new features in 7.30: * Alter Fragment Attach/Detach enhancements * In-place Alter Table Modify/Drop * Restartable restore * External backup/restore * Optimizer directives * Select first 'n' rows * Ordered merge * Memory resident tables * Correlated subquery enhancements * Keyfirst index scan * Subquery flattenning * New functions for case insensitive search: UPPER, LOWER, INITCAP * New functions for string manipulations: REPLACE, SUBSTR, LPAD, and RPAD * The CREATE VIEW statement now includes UNION * New CASE expression * New NVL and DECODE functions * New date conversion functions: TO_CHAR and TO_DATE * New environment variable: IFX_UPDDESC * Informix Storage Manager (ISM). * ER Enhanced GLS support: ability to replicate within a locale. * ER Command-line utility. * New CONNECT and DISCONNECT functions in the Enterprise Replication API * NT Specific Features o Multiple residency o Raw device support o High Performance Loader o ON-Bar XBSA certification o ON-Bar parallelism o Optical Subsystem o Non-domain Administrator install o Microsoft Cluster Support o Local connection support using named pipes and 7.31: * Retain Update Locks. * ANSI Join. * Nonlogging Tables (TYPE reserved word). * Rename Index. * Up to 3GB Shared Memory Support on NT. * Password encryption. * ER Data Compression * IFX_NETBUF_PVTPOOL_SIZE and IFX_NETBUF_SIZE Environment Variables. * ISM 2.0. if all you're looking for is backward compatability you can ignore the above, as long as you're not using any of the new reserved words (like TYPE) as table/column names. Regards Guy > > This is for a small non-profit org where the IT budget is rolled up > into things like fence repair, so there is no staff immediately > available for anything but relatively trivial migration and no one to > look at code if a migration to a new version does not work. Thus the > motivation for 7.22. Sounds like 7.31 for W2K is the way to go. > > Thanks, > > pan >

This is perfect. At this point the concern is entirely backward compatibility. They're concerned about an application written by a development organization that no longer exists. They can duplicate the system on another NT machine, so they're pretty confident about making the switch to the W2K box, but they were concerned about application compatibility with the later IDS rev. Looks like they're covered on that. Stellar feedback, thanks again. pan