RE: Fast recovery

We recently had a tbzero (truncate logical logs) done on our system. I had a down dbspace and the engine wouldn't come up, no matter what we did. The only way out was for Tech Support to do the tbzero. They did warn me that we might have problems afterwards, but so far so good. It's been a couple of weeks now. We had a problem with the logical logs the first time we brought the engine up again. Because of the tb0, the database got confused and did not know which logical log was the current logical log. Luckily Tech Support could fix it, otherwise we would have had to restore. We had 2 or 3 assert failures, but other than that it was fine. Ask Tech Support to bring the engine up and run some checks on it, make a full backup and hope for the best. This was on IDS 9.21FC1 (HP-UX 11.00) Regards Dirk -----Original Message----- From: owner-informix-list@iiug.iiug.org [mailto:owner-informix-list@iiug.iiug.org]On Behalf Of Neil Truby Sent: Monday, January 29, 2001 11:15 PM To: informix-list@iiug.org Subject: Fast recovery Pursuant to my question earlier regarding the dropping of an index; the engine was brought down shortly after the first index drop completed, after a few minutes of the second. It's probable that these two are in the same transaction so I expect they'll both get backed out. The fast recovery is taking an interminible time. Informix USA say they can bring the engine up and truncate the logical recovery. Can anyone advise on the advisability of this? It's a production system, so I can't afford internal corruption, but on the other hand I can't afford for the system to be done for another 48 hours, or however long it takes to fast recover. Advice gratefully received at neil.truby@londis.co.uk