Informix and ODBC
A poster asked whether an ODBC driver exists to reach a very old Informix (thought to be 3.x) on an NCR 386/486 Unix box, so images on optical platters could be moved into Sybase. One reply suggested the Informix Client SDK (from intraware.com) plus INet/I-Star on the server. Jonathan Leffler warned that '3.x' is ambiguous: Informix 3.30 was a pre-SQL product (look for dbname.dbd files), while SE uses dbname.dbs directories, and asked for the exact version/product before advising further. The poster only had a 'Turbo 3.1' manual and no definitive version, so no resolution is recorded. One off-topic reply about killing a process holding the ODBC manager was later retracted as misposted.
Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.
Hello All, Is there an ODBC driver available that I can useto connect to and older version of Informix I believe it's Informix 3.x on on NCR 386/486 Unix server. I work for a company that has an old imaging system and they want to extract images that are stored on optical platters into they're Sybase DB. I would imagine it would be easier if I had an ODBC driver for Windows, so I could just pull it from one Informix to put it into Sybase. If anyone has any insight on this, it would greatly appreciated. Thanks Tyson Oswald
On Mon, 30 Aug 1999 18:33:22 -0400, Tyson Oswald <tysono@iserv.net> wrote: >Hello All, > > Is there an ODBC driver available that I can useto connect to and >older version of Informix I believe it's Informix 3.x on on NCR 386/486 >Unix server. I work for a company that has an old imaging system and >they want to extract images that are stored on optical platters into >they're Sybase DB. I would imagine it would be easier if I had an ODBC >driver for Windows, so I could just pull it from one Informix to put it >into Sybase. > >If anyone has any insight on this, it would greatly appreciated. > >Thanks > >Tyson Oswald Don't you just hate this! The sure-fire way to sort it out is to grab a copy of NTHandleEx from www.sysinternals.com, and use it to determine what process has the ODBC manager stuff open - then kill that process. Happy hacking! Ciao Fuzzy :-)
Go to intraware.com and get the Informix Client SDK. However, you also have to get INet/IStar for your server. Tyson Oswald wrote: > Hello All, > > Is there an ODBC driver available that I can useto connect to and > older version of Informix I believe it's Informix 3.x on on NCR 386/486 > Unix server. I work for a company that has an old imaging system and > they want to extract images that are stored on optical platters into > they're Sybase DB. I would imagine it would be easier if I had an ODBC > driver for Windows, so I could just pull it from one Informix to put it > into Sybase. > > If anyone has any insight on this, it would greatly appreciated. > > Thanks > > Tyson Oswald
Tyson Oswald wrote: > Is there an ODBC driver available that I can useto connect to and > older version of Informix I believe it's Informix 3.x on on NCR > 386/486 Unix server. I work for a company that has an old imaging > system and they want to extract images that are stored on optical > platters into they're Sybase DB. I would imagine it would be easier > if I had an ODBC driver for Windows, so I could just pull it from > one Informix to put it into Sybase. > > If anyone has any insight on this, it would greatly appreciated. You need to establish what that version is; 3.30 is a red flag. Once upon a long time ago (like more than 13 years ago), Informix (then called RDS) had a product called Informix 3.30. It was a relational database, but it did not use SQL. If you've got that database, then you've got big problems -- contact me at the office, but after the Labour Day holiday. If there are files called dbname.dbd hanging around (where dbname is the name of your database), you've got Informix 3.30. If it is a 386/486 server, we can hope that you have an SQL system after all. Is it SE? Do you have directories called dbname.dbs? Or is it Turbo? I think it will be SE if it is anything, and the version would probably be 2.10.03, but I'm guessing. The only products released with a 3.x version were the old Informix product, C-ISAM (3.10.03 went with ISQL 2.10.03, for example), and IIRC, the ESQL/C version was also 3.10.03 when ISQL was at 2.10.03. All the other products skipped from 1.10.03 or 2.10.03 direct to 4.00, precisely to avoid confusion with Informix 3.30. If they are using optical images and they were stored via the database, it could be OnLine 4.x -- though many platforms did not support OnLine/Optical. You will have to be more precise about your version before I'm able to help any more. I'm sceptical about storing images in Informix 3.30 or anything prior to version 4.00, but your mention of 3.x has me in a spin... -- Jonathan Leffler (jleffler@informix.com, jleffler@earthlink.net) Guardian of DBD::Informix v0.60 -- see http://www.perl.com/CPAN #include <disclaimer.h>
Thanks alot for your help, I'll check them out and let ya know. Tyson Tyson Oswald wrote: > Hello All, > > Is there an ODBC driver available that I can useto connect to and > older version of Informix I believe it's Informix 3.x on on NCR 386/486 > Unix server. I work for a company that has an old imaging system and > they want to extract images that are stored on optical platters into > they're Sybase DB. I would imagine it would be easier if I had an ODBC > driver for Windows, so I could just pull it from one Informix to put it > into Sybase. > > If anyone has any insight on this, it would greatly appreciated. > > Thanks > > Tyson Oswald
I know it uses sql I've seen some scipts on the volume. and as far as version I'm still not sure, how can I find out. I do have a small manual thats is for Informix Turbo 3.1. Tyson Jonathan Leffler wrote: > Tyson Oswald wrote: > > Is there an ODBC driver available that I can useto connect to and > > older version of Informix I believe it's Informix 3.x on on NCR > > 386/486 Unix server. I work for a company that has an old imaging > > system and they want to extract images that are stored on optical > > platters into they're Sybase DB. I would imagine it would be easier > > if I had an ODBC driver for Windows, so I could just pull it from > > one Informix to put it into Sybase. > > > > If anyone has any insight on this, it would greatly appreciated. > > You need to establish what that version is; 3.30 is a red flag. > Once upon a long time ago (like more than 13 years ago), Informix > (then called RDS) had a product called Informix 3.30. It was a > relational database, but it did not use SQL. If you've got that > database, then you've got big problems -- contact me at the office, > but after the Labour Day holiday. If there are files called > dbname.dbd hanging around (where dbname is the name of your database), > you've got Informix 3.30. > > If it is a 386/486 server, we can hope that you have an SQL system > after all. Is it SE? Do you have directories called dbname.dbs? > Or is it Turbo? I think it will be SE if it is anything, and the > version would probably be 2.10.03, but I'm guessing. The only > products released with a 3.x version were the old Informix product, > C-ISAM (3.10.03 went with ISQL 2.10.03, for example), and IIRC, > the ESQL/C version was also 3.10.03 when ISQL was at 2.10.03. All > the other products skipped from 1.10.03 or 2.10.03 direct to 4.00, > precisely to avoid confusion with Informix 3.30. If they are using > optical images and they were stored via the database, it could be > OnLine 4.x -- though many platforms did not support OnLine/Optical. > You will have to be more precise about your version before I'm able > to help any more. > > I'm sceptical about storing images in Informix 3.30 or anything > prior to version 4.00, but your mention of 3.x has me in a spin... > > -- > Jonathan Leffler (jleffler@informix.com, jleffler@earthlink.net) > Guardian of DBD::Informix v0.60 -- see http://www.perl.com/CPAN > #include <disclaimer.h>
On Tue, 31 Aug 1999 00:38:13 GMT, granta@nospam.student.canberra.edu.au (Fuzzy) wrote: >Don't you just hate this! The sure-fire way to sort it out is to grab >a copy of NTHandleEx from www.sysinternals.com, and use it to >determine what process has the ODBC manager stuff open - then kill >that process. Oops - sorry, replied to the wrong message! Ciao Fuzzy :-)