Re: Upgrading Informix to 4.1 (SQL and 4GL)
Posted in 1993
Ruchi Patel <RUCHI%CFRVM.bitnet@CUNYVM.CUNY.EDU> writes:
->Comments: Converted from OfficeVision to RFC822 by PUMP V2.2X
->Date: Tue, 19 Jan 93 16:31:31 EST
->From: Ruchi Patel <RUCHI%CFRVM.bitnet@CUNYVM.CUNY.EDU>
->X-Prolog: University of South Florida
->X-Prolog: Phone (813) 974-3570
->Subject: Upgrading Informix to 4.1 (SQL and 4GL)
->Reply-To: Ruchi Patel <RUCHI%CFRVM.bitnet@CUNYVM.CUNY.EDU>
->
->We upgraded the SQL, 4GL and SE from 4.0 to 4.1 with 5.0 SE. I can't seem
->to select the old database from new version of Informix. I get the
->following error:
->
->312: Cannot update system catalog (systables).
->107: ISAM error: record is locked.
->
->Informix told me that I need to do dbschema and then unload and reload data
->from new informix. According to document, I need to recompile only programs,
->forms and reports. So, why can't I select the database? Any suggestions? or
->comments?
->
->Thanks.
->
->Ruchi Patel
->Senior Programmer Analyst Email: ruchi@cfrvm.cfr.usf.edu
->Division of Telecommunications, OPM 128
->Tampa, FL 33820-7549
Alan Popiel (alan@den.mmc.com) replies:
To release locks that are "hanging around" for a table in an SE database,
the OWNER of the database / table should do the following:
1. cd to the directory holding the database, i.e. to directory <dbname>.dbs in
one of the directories within $DBPATH. Because of permissions, you may have
trouble getting into the directory. Have root open the permissions if
necessary.
2. then:
cp /dev/null <tblfilname>.lok
Ruchi, in your case <tblfilname>.lok is systables.lok; all of the Informix
system catalog files are named with the table name. In the general case,
the file name would be a combination of the first 7 characters of the table
name followed by the tabid number. "_" is used to pad short table names to
7 characters.
Copying /dev/null to the file replaces the lock file with a zero length file.
Zeroing the lock file deletes ALL locks, so you probably don't want to do this
while users are active in the database. Informix will rebuild the lock file
the next time it creates a lock. This may work for you, however ...
It may actually be necessary for you to dbexport the database under 4.0 and
then dbimport it under 4.1. Some releases of the DB engine are backward
compatible to prior databases, some are not. I don't remember exactly
which release combinations ARE compatible.
Regards,
Alan
+------------------------------+---------------------------------------+
| R. Alan Popiel | Internet: alan@den.mmc.com |
| Martin Marietta, LSC | ( Please note: My opinions do not ) |
| P.O. Box 179, M/S 5422 | ( represent official Martin policy. ) |
| Denver, Colorado 80201-0179 | Voice: 303-977-9998 |
+------------------------------+---------------------------------------+