RE: Strange warning message on Commit work in dbaccess (and isql)

I've seen it in 9.30.hc3 as well...spooked me the first time I saw it . . . .but yes, the data does get committed. executing "commit work" in the dbaccess screen will prevent this message from appearing... -----Original Message----- From: Danny Wright [mailto:dwright@sherwoodfoods.com] Sent: Monday, November 17, 2003 12:32 PM To: ids@iiug.org Subject: Strange warning message on Commit work in dbaccess (and isql) [2181] I only see this when I commit work by exitting and choose Commit from = the Transaction: ring menu. The message is: Warning:Data Commit is a result of an unhandled exception in TXN = PROC/FUNC/TRI Anyone know what this is? I don't recall ever seeing it before = upgrading to 7.31.UD6, but it goes by so quickly, maybe I never noticed = it? (I don't commit work this way that often). IDS: 7.31.UD6 AIX: 4.3.3.0 The data did get committed. Thanks, Danny "CONFIDENTIALITY NOTICE: This message originates from WHSmith USA Travel Retail. This email message and all attachments may contain legally privileged and confidential information intended solely for the use of the addressee. If you are not the intended recipient, you should immediately stop reading this message and delete it from the system. Any unauthorized reading, distribution, copying, or other use of this message or its attachments is strictly prohibited. All personal messages express solely the sender's views and not those of WHSmith USA Travel Retail. This message may not be copied or distributed without this disclaimer."

Hi This message is present in 7.31UD5 NOT BEFORE and in 9.30 and 9.40 NOT in 9.20 or 9.21 In fact, when you use dbaccess in interactief mode is only a info, but if you use dbaccess in a script then you can have some surprise. This message mean that you have a open transaction and by default it commit in place do to the rollback For example try this Version IDS 9.40.FC1 and IDS.9.40.FC2 on Solaris 8 > > Hereby the code of a stored procedure > > drop procedure testproc; > create procedure testproc() > on exception> rollback work; > end exception; > > set debug file to "/tmp/test.log"; > trace on ; > > begin work; > select * from mon_tables into temp t1 ; --> mon_tables : some table that is large enough to be able to press > "Control+C" > while reading it. > drop table test;> commit work; > > end procedure; > If we run this procedure and interrupt with "Control+C" during the select > of > the table the procedure doesn't fall into the "on exception"-routine. > Result : Warning given : Warning:Data Commit is a result of an unhandled > exception in TXN PROC/FUNC/TRI an implicit commit is given while he should > do a rollback. > > Screenshot > nformix@solmgt:/export/home/informix> dbaccess -e monitor < test.sql > > Database selected. > > ^Cexecute procedure testproc(); > 213: Statement interrupted by user. > Error in line 1> Near character position 27 > > Warning:Data Commit is a result of an unhandled exception in > TXN PROC/FUNC/TRI > > Data committed. > > Database closed. > > informix@solmgt:/export/home/informix> > > Debug info > > trace on > > > begin work; > > select * > from mon_tables > into temp t1;> exception : looking for handler > SQL error = -213 ISAM error = 0 error string = ="" > exception : no appropriate handler > > When eg. You run the procedure twice and let the select finfish the "drop > test table" errors : the on exception works ok. > > Debug info : > > trace on > > > begin work; > > drop table test;> exception : looking for handler > SQL error = -206 ISAM error = -111 error string = = "test"> exception : handler FOUND > > rollback work; > procedure testproc returned no data > So we have a case open on this problem but we receive a first answer and i ask more information but an this state of discusion support said it's normal and i said a database must never commit by default. Other problem, you can not trap the error code -213 because you recive always exception : no appropriate handler I wait more info from Support. > Best regards >