Remains in recover mode.
Posted in 1994
Topics: Stored Procedures & SPL
Hi netters, My sad tale. Running V 4.10 on Sequent S200, about 50 terminals. Entered a select in isql to return a few rows into temp file with no log. Unfortunately, due to bad input it returned 1000's, and soon ran out of log space. (why? I did say with no log). With terminals dying all around I killed the isql. The turbosql remained, valiantly rolling back the log I expect. As all the terminals were still jammed (I cannot tell a lie) I killed the turbosql, and informix died. ....... Next, of course, I tried to start informix, using the tbmonitor. It entered recovery mode, politely displayed "please wait" and started drawing dots at the bottom of the screen. A sad previous experience led me to believe that things would stay that way for 24+ hours, so after 2 hours, with the user threatening my life, I restored from the previous days archive - thereby losing half a day's work. While admitting guilt (to forgive is devine but not co policy) - what should I have done. I did not want the temp table anyway. Is there a way to start informix and skip recover? I have seen tbzero referred to in previous em's, is this the only answer? Thanx in advance for any help (perhaps I should start reading those @#$%^&* job ads that keep cluttering the net). ______/ ______/ _ | ______/ / / / | / toms@erl.aldis.com.au / ____/ / | / / / / /___ | / Tel (613) 647 9720 ________/ _______/ __/ __| ________/ Fax (613) 647 9799