On 05/02/2016 12:11 PM, Maurice van 't Loo wrote: > Hello Zoltan, > > Indeed, this should be "to reduce the active log TO 8 GB" > In fact, the author also forgot that 8G = 8192 MB ;-) >
As far as I can tell, the dsmserv activelogsize is setting db2 update db config for [database] using logprimary [n/512] Is anyone using logsecondary to manage overflow space? - Allen S. Rout