This is a discussion on How to avoid Tran Fail Log error with update statements within the DB2 forums, part of the Database Server Software category; --> I have an update statement which updates 100,00 records and most often I end up in a tran fail ...
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| I have an update statement which updates 100,00 records and most often I end up in a tran fail log error , is there any option which would enable me to commit the updates in batches. Please let me know if there are any work arounds. Thanks, Vj. |
| ||||
| What type of logging are you using? If it's circular; then you've filled up all of the primary and secondary logs. A simple solution is to increase the log size or the number of logs. If this is a production system; circular logging has other (negative) recovery implications. You could use a WHERE predicate to restrict your updates to a portion of your rows. Multiple UPDATES can be coded with a COMMIT between them. Phil Sherman vj wrote: > I have an update statement which updates 100,00 records and most often > I end up in a tran fail log error , is there any option which would > enable me to commit the updates in batches. > > Please let me know if there are any work arounds. > > Thanks, > Vj. > |