Q: Informix and Disk Full errors

Hi. I have some questions regarding the behavior of Informix under 'disk full' conditions. We're running Informix-SE 4.1 on Sun Sparc machines. We have a situation where the disk containing the database and the transaction log gets full; we were wondering how Informix recovers in this situation. For the sake of the discussion, assume that there are 120,000 records which need to be deleted. At some point, the 'delete' fails, forcing a rollback. The rollback fails, because it can't write to the transaction log. Next, the 'close' fails, because of an outstanding transaction. 1) What is the 'rollback' attempting to write into the transaction log? 2) Has the rollback restored anything to the database before it failed? 3) Since the 'rollback' and 'close database' failed, what state is the database left in? 4) If our next action in this situation is to remove the transaction log, can the database be left in an unstable state? Any help is appreciated. If I've left out some information, please let me know. Thanks in advance! -- Joseph Tokarski, Principal Engineer |"This ain't no technological breakdown General DataComm, Middlebury, CT 06762 | Oh no, this is the Road to Hell." phone: (203) 758-1811 ext. 7684 | email: tokarski@gdc.com | - Chris Rea, "The Road to Hell"