home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!gossip.pyramid.com!pyramid!infmx!davek
- From: davek@informix.com (David Kosenko)
- Newsgroups: comp.databases.informix
- Subject: Re: Upgrading Informix to 4.1 (SQL and 4GL)
- Message-ID: <1993Jan21.175203.22359@informix.com>
- Date: 21 Jan 93 17:52:03 GMT
- References: <1ji9hqINNkv4@emory.mathcs.emory.edu>
- Sender: news@informix.com (Usenet News)
- Organization: Informix Software, Inc.
- Lines: 26
-
- Alan Popiel writes:
- >
- >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
-
-
- Note that this will only work if you happen to have one of the few
- releases that use .lok files (Sun versions, primarily).
-
- Better is the method anothe rposter suggested, setting the
- RESETLOCK environment variable. As of 5.0, we no longer use .lok
- files for any platforms.
-
- Dave
- --
- Disclaimer: These opinions are not those of Informix Software, Inc.
- **************************************************************************
- "I look back with some satisfaction on what an idiot I was when I was 25,
- but when I do that, I'm assuming I'm no longer an idiot." - Andy Rooney
-