Re: Informix 4GL Version 1.10 bcheck fails

Peter Lancashire wrote: > Jim Oser wrote: > > I am helping a client, who has > > Informix-4GL Version 1.10 on an ATT 6386 WGS, which > > is a 80386 at 25 MHz, running ATT Unix Rel 3.2 Version 2.3 > > > > bcheck -y > > is passing on all files except chg_tra189.dat > > which is giving > > Error 226 > > Error 4996 > > Error 82851 > > Error 4128 > > It then says "Recreating index 2" and waits for 2 minutes > > before aborting. > > > > Question: > > 1) How can I get bcheck to pass? With difficulty, in all probability. > > 2) Customer only kept 3 days of backup and the system was not > > working 3 days ago. Careless. > > 3) Customer is moving to NT and does not want to stay on UNIX. > > However, I was wondering if it would be possible to move > > the existing database to SCO OpenServer 3 or 5. Can I simply > > cpio the /usr/informix directory and the /usr/system/resort.dbs > > and put it on the SCO box. > > Will Informix realize it is on a different Intel box > > with a different operating system? As you are staying with an Intel architecture, you would probably be OK. If you moved to a 680x0 architecture, you'd run into problems with FLOAT and SMALLFLOAT fields, but everything else would transfer OK. > > Jim Oser > > oserj@netcom.com > > > > > The fact that you are running bcheck gives a clue that you must be using > the SE database engine. Which version? Actually, I4GL 1.10 precedes SE -- back then, you got "SE" when you bought either ISQL or I4GL; Turbo didn't yet exist (unless the sub-version is 1.10.03x). > I'd investigate the first message. As it says, check disk space. > Permissions might be a problem but less likely. Is the problem table a > particularly big one? > > I have no idea whether SCO Unix is compatible with ATT Unix. SCO Unix probably won't run the AT&T binaries, but the database should transfer OK. > Informix might take the view that you were violating the terms > of your license by moving to another operating system and hardware. I don't think so. At worst, you'd be doing something unsupported, but since I4GL 1.10 is unsupported, you're no worse off than you were before trying the transfer. > A better solution might be to upgrade to a newer version of the > database engine and 4GL. Yes. > I suspect support has long since lapsed for versions as old as this. It has. -- Jonathan Leffler (jleffler@informix.com, jleffler@earthlink.net) Guardian of DBD::Informix v0.60 -- see http://www.perl.com/CPAN #include <disclaimer.h>