Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!mit-eddie!mintaka!olivea!samsung!sdd.hp.com!elroy.jpl.nasa.gov!ncar!asuvax!anasaz!qip!devin
From: devin@qip.UUCP (Devin Wala)
Newsgroups: comp.databases
Subject: Transactions, logging, and Online
Message-ID: <5394@qip.UUCP>
Date: 9 Nov 90 22:43:48 GMT
Distribution: usa
Organization: Anasazi, Inc., Phoenix Az.
Lines: 43



We have run across an oddity in INFORMIX ONLINE.  

1) We create a database with logging turned on.  So far so good.

   A) We can then LOAD data into the database through isql without
   issuing BEGIN/COMMIT/ROLLBACK WORK.  Informix does this without
   returning an error, even though the LOAD statement is clearly
   not in a transaction.

   B) We can write ESQL/C programs which use INSERT, DELETE and UPDATE
   without issuing a BEGIN/COMMIT/ROLLBACK WORK.  The programs run
   though to completion without ever once returning an error code.

   C) If we write the ESQL/C program to use DECLARE CURSOR .. FOR UPDATE
   Informix will return a "NOT IN TRANSACTION" error like one would
   expect.

2) After one particular program we have which does not have BEGIN/COMMIT/
   ROLLBACK is run against a database with logging turned on, Informix 
   is left in a crippled state.  
   
   Any current users of Informix are able to continue working.  However, 
   any users wishing to start running Informix from this point on receive 
   the classic "An invalid message has been returned by a sqlexec process". 



We are running INFORMIX ONLINE vers UD4 on a PYRAMID 9846 and
thought others might be interested.

-Devin Wala


-- 
------------------------------------------------------------------------------
   o oo o                                           
  o \||/ o     Anasazi, Inc                         
 o--****--o      7500 N. Dreamy Draw Drive, Ste 120 
 o--****--o      Phoenix, AZ. 85020                 
  o /||\ o                                         
   o oo o   {asuvax or mcdphx}!anasaz!devin (Devin Wala) (602)943-4449