can you publish more details. how do you invoke the statements.. ?
command line - tool ?
what are the clp options ...
what are you trying todo ? what do you expect ?
and finally : publishing level and platform would not harm
Best Regards, Guy Przytula
Database Software Consultant
Good DBAs are not formed in a week or a month. They are created little by little, day by day. Protracted and patient effort is needed to develop good DBAs.
Spoon feeding : To treat (another) in a way that discourages independent thought or action, as by overindulgence.
DB2 UDB LUW Certified V7-V8-V9-V9.7-V10.1-V10.5 DB Admin - Advanced DBA -Dprop..
Information Server Datastage Certified http://www.infocura.be
thank you Andy for the hints. I am working with db2 9.7, with no manipulation of auto-commit, so I think my configuration for auto-commit is on.
Now, it will be a little bit complicated with my fantasy regarding commit:
I learnt in the university, that a DBMS implements a choosen, good transaction protocoll to keep ACID in consistency. For example: strict 2PL.
This protocoll will "arrange" itself which transaction should be in which time commited and so on.
if I explicitely commit an Unit of Work by typing:
Isnt it "dangerous" to commit explicitely, so that the ACID not guaranteed anymore?
No, committing explicitly can be a good thing, sometime a necessary thing. Suppose you have business logic that inserts rows into multiple tables. You obviously cannot insert into them all in one statement, so you need several statements to do the work. Now you are going to want to make sure that either all of the work gets done or none of it. So you turn off auto-commit, then do each insert statement. If an error occurs somewhere in the process, then you explicitly rollback. Otherwise when the inserts are complete, you explicitly commit.