Re: Sizing logical logs

Hi, You should run the update on just a few records and then go to the logical logs to see the records. One of the attributes in the log record is the length. You can scale this to the number of rows in the table and you'll have a good idea of what you need. See the onlog utility for how to get the information. Denham.M@amstr.com wrote: } } All } } Anybody know a good way to size the logical logs for an update of 1 } column in all the rows of a large table? It is necessary for the } update to occur in a single transaction. There are no other large } jobs to take into consideration for sizing the logs. } } The table is being locked exclusively, and the indexes on the table } are dropped prior to the update. } } I am fed up of running the transaction and having it run out of } logical log space. } } Thanks } } Mark } Denham.M@amstr.com (work) } markd08@ibm.net (goofing off..)