you can use command export DB2OPTIONS='+c' to turn off auto commit and
make sure you put commits at approriate places.
if autocommit is on , commit will be issued after the statement activate not logged initially and then table is no longer in no loggin mode, so the next update
statement will be logged.








"kiran" <db2udbdba-ezmlmshield-x67995191.[Email address protected]
06/30/05 02:24 AM


To: "LazyDBA Discussion" <[Email address protected]
cc:
Subject: Turn off autocommit

Hi all,

We are getting log full errors while updating many tables. It is just a
cleaning up process which needn't be logged. We have used the alter table
activate not logged initially before the update statement. But the user
which runs the script have autocommit turned on. I tried db2set
db2options=+c as the instance owner. But it didn't turn off the autocommit
for the user running the script. Has the logging something to do with the
autocommit? If so how do I turn it off for the user running the script?
Any help is highly appreciated. Thanks!

Regards
Kiran
Disclaimer:

This e-mail, and any files transmitted with it are confidential to Marlabs
Inc. and intended solely for the use of the individual or entity to whom
it is addressed. If you are not the intended recipient you are notified
that disclosing, copying, distributing or taking any action in reliance on
the contents of this information is strictly prohibited.


---------------------------------------------------------------------
PLEASE CLICK REPLY-ALL TO SEND A REPLY TO EVERYONE
website: http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html



This email is confidential. If you are not the addressee tell the sender immediately and destroy this email without using, sending or storing it. Emails are not secure and may suffer errors, viruses, delay, interception and amendment. Standard Chartered PLC and subsidiaries ("SCGroup") do not accept liability for damage caused by this email and may monitor email traffic.

This email is confidential. If you are not the addressee tell the sender immediately and destroy this email without using, sending or storing it. Emails are not secure and may suffer errors, viruses, delay, interception and amendment. Standard Chartered PLC and subsidiaries ("SCGroup") do not accept liability for damage caused by this email and may monitor email traffic.


DB2 & UDB email list listserv db2-l LazyDBA home page