Re: Online Recovery problem

Tony, I don't think you are wrong. If you look at their online log there is the message aborting long transaction. Now as this is during the recovery what must have happened is that originally a long transaction aborted online. They restarted it and it rolled everything back to its last checkpoint it then rolled things forward again including the long transaction this couldn't complete as the logs are full so it was aborted again the rollback cant work as the logs are full... etc, etc, etc, etc.... What is required is either a method of adding new logical logs before starting the recovery or (more difficult) rollback should avoid placing things in the logical log in this situation this would allow the rollback to complete successfully at which point the full logical logs could be archived. What about it Informix? This is a major problem!! Is it fixed in 4.1? Sorry Niels I know of no solution than to rebuild your entire Online system from the last available backup. The database will be consistent but will be missing the committed transactions in the logical logs that you were unable to archive because they contain this long transaction. ONLINE USERS BEWARE. NEVER START A LARGE TRANSACTION THAT MAY NOT HAVE ENOUGH LOGICAL LOG SPACE TO COMPLETE. You may get away with it but if it is a large transaction the last logical log (When the transaction enters this it is automatically aborted) may not be big enough to contain the rollback log information + any other log information being entered by other users. If it isn't the whole online system will crash and can only be recovered from the last backup tapes. Cheers, Jim -------------------------------------------------------------------- Name: Jim Gordon Internet: jgordon@ssf-sys.DHL.COM Company: DHL Systems Inc Phone: (415) 358-5911 Address: 1700 S. Amphlett Blvd. Fax: (415) 571-6429 San Mateo, CA 94402 --------------------------------------------------------------------