All those calculations are fine. I am interested in knowing if we can calculate the amount of data written in a weeks time. Circular logging will allocate all the primary logs initially and on demand the secondary will also be allocated.
We need to know how much log data is generated in a weeks time. The amount of log space allocated does not tell us that. May be we will need to review how the log rba progresses over a weeks worth of elapsed time. Not sure exactly where we will get that but it certainly should be available.
well, in circular logging, you can't really determine because DB2 would just use the logs again...
it really depends on the number of commits / rollbacks done on the database... it would be better if you turn the LOGRETAIN on and record the current log files used until the active log file after a week... then probably you'll have an estimate
better yet.... get the Administration Guide: Planning (db2d1e80) redbook from IBM
There are 10 kinds of people,
those who know binary and those who don't.
How about this way? more than enough Primary logs so that you do not run out of log space by a long running transaction.NO secondary logs. Every 15 minutes or so a cronjob to append to a file the logfilehead.
db2 get db cfg for crmp|grep "First active">>logoutf
After a week you know how many times the primary pool is cycled; hence how much lg space