home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!oracle!pyramid!infmx!davek
- From: davek@informix.com (David Kosenko)
- Newsgroups: comp.databases.informix
- Subject: Re: Informix logs read-only queries? can't handle 'not-exists'?
- Message-ID: <1992Nov13.170508.6980@informix.com>
- Date: 13 Nov 92 17:05:08 GMT
- References: <1992Nov11.184142.4749@cs.wisc.edu> <1992Nov12.161943.21876@informix.com> <1992Nov12.210641.7143@cs.wisc.edu>
- Sender: news@informix.com (Usenet News)
- Organization: Informix Software, Inc.
- Lines: 27
-
- Ron Choi writes:
- >>I agree wholeheartedly that a query should not corrupt the database. What
- >>exactly become corrupted and how?
- >
- >after i ran the query above the system could not restart (or recover). that
- >is, i tried to restart it using tbmonitor/mode/startup, but it spent over
- >5 hours printing out "recovering. please wait...." message. i had to restore
- >the database from the tape. i don't know what exactly got corrupted. i
-
- While you could argue the definition of "corrupted", in this case your
- database was not corrupted; your logs were full, thus the system being
- stuck in recovery mode.
-
- Now, unless this happened due to a long transaction (LTX), you should be
- able to get around this by running a tbtape while the system is in
- recovery mode (this works). That will free up any logs possible and
- allow recovery to continue, hopefully to completion. If, however, an
- active transaction spans all the logs, then recovery from tape is the
- only alternative.
-
- 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
-