RE: Turn off autocommit

RE: Turn off autocommit

 

  





Well then PUT IN SOME COMMITS!!!!!!!

Dan Callahan IT Specialist
603-472-4121 t/l 525-4121
[Email address protected]




"kiran"
<db2udbdba-ezmlms
hield-x34595454.x To
[Email Address Removed] "LazyDBA Discussion"
a.com> <[Email address protected]
cc
06/29/2005 05:30
PM Subject
RE: Turn off autocommit










Thank you all for all your suggestions.

The script has a statements like this

alter table <tabname1> ACTIVATE NOT LOGGED INITIALLY;
update <tabname1> set value = new value;

alter table <tabname2> ACTIVATE NOT LOGGED INITIALLY;
update <tabname2> set value = new value;

There are no commits specified in the script. And more over I have
currently specified the maximum number of logs (primary + secondary =256).
And we really dont want to increase the logfilsiz as it is already
reaching the file system limit. So my doubt is that whether the logging is
enabled due to the fact that autocommit is on?

Regards
Kiran


>
>
>
>
> As soon as the first commit occurs the alter table not logged initially
> doesnt take affect anymore. I would suggest looking at what you are doing
> and
> like Mike says, increase your commit frequency. If autocommit is on, then
> you should not be filling up and running out of logs, because they are
> no longer needed after the autocommit. My take is that you are not
> committing at all and updating lots of records, or your logs ae not sized
> correctly.
>
>
>
>
>
>
> "Abel Mike J "
> <db2udbdba-ezmlms
> hield-x96841021.x
To
> [Email Address Removed] "LazyDBA Discussion"
> a.com> <[Email address protected]
>
cc
> 06/29/2005 03:40
> PM
Subject
> RE: Turn off autocommit
>
>
>
>
>
>
>
>
>
>
>
> Everything in udb gets logged - you have no choice. Turning autocommit
> on/off just affects when the commit is issued - at the end of each
> statement or when one explicitly issues a commit. Is the user running the
> script via Command Center? If so, your can turn off autocommit in the
> tools
> settings. You can also set autocommit=1 or autocommit=0 in the db2cli.ini
> on the client for the specific connection alias. If your running a large
> number of updates, you probably want autocommit to be on unless you
> explicitly commit frequently.
>
> Have you considered increasing the number/size of the logs - or better
> still, going with Linear logging?
>
> -----Original Message-----
> From: kiran
> [mailto:db2udbdba-ezmlmshield-x67995191.[Email address protected]
> Sent: Wednesday, June 29, 2005 1:24 PM
> To: LazyDBA Discussion
> 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
>
>
>
> CONFIDENTIALITY NOTICE
>
> This e-mail and any attachments, as well as any documents from a file
> server of International Truck
> and Engine Corporation or its affiliates, are intended for the addressee
> and may contain information
> that is privileged, confidential, proprietary, or otherwise protected by
> law. Any dissemination,
> distribution, or copying is prohibited. If a confidentiality or
> nondisclosure agreement exists
> between International and the recipient or the recipient's employer, this
> e-mail and any attachments
> hereto, as well as any documents from a file server of International
Truck
> and Engine Corporation or
> its affiliates, this notice serves as marking as CONFIDENTIAL information
> of International Truck and
> Engine Corporation or its affiliates. If you have received this
> communication in error, please
> contact the original sender.
>
>
> ---------------------------------------------------------------------
> PLEASE CLICK REPLY-ALL TO SEND A REPLY TO EVERYONE
> website: http://www.LazyDBA.com
> To unsubscribe: http://www.lazydba.com/unsubscribe.html
>
>
>
>
>
> ---------------------------------------------------------------------
> PLEASE CLICK REPLY-ALL TO SEND A REPLY TO EVERYONE
> website: http://www.LazyDBA.com
> To unsubscribe: http://www.lazydba.com/unsubscribe.html
>
>

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




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