Backup job terminated because Log space is exhausted on TSM server

ANR0130E dbieval.c(825): Server LOG space exhausted. (SESSION: 351)
ANR0162W Supplemental database diagnostic information

Client backup is terminated although the Activelogsize value is updated in dsmserv.opt to a greater value.
The problem is that Num_log_span isn´t updated in db2 database.


To manually update Num_Log_Span

update the db2 database to correctly set NUM_LOG_SPAN.
Calculate correct value of NUM_LOG_SPAN
Each log size is fixed at 512MB.
1. Take the new value of activelogsize in dsmserv.opt in and
divide that by 512MB. This value is the total number of log
volumes reflected in db2 value LOGPRIMARY.
2. Multiple LOGPRIMARY by 90%. This value should be reflected in

NUM_LOG_SPAN.

(alternate method involving slightly less arithmetic)
Calculate correct value of NUM_LOG_SPAN
1. Use the following db2 command to determine the number of log
volumes used:
db2 get db cfg for TSMDB1
2. Multiply the value for the LOGPRIMARY parameter by 90%. This

value should be reflected in NUM_LOG_SPAN.
Update NUM_LOG_SPAN by issuing the following db2 command:
db2 update db cfg for TSMDB1 using NUM_LOG_SPAN
You may need to restart the TSM server, which will restart the
db2 database as well.

for example
Activelogsize 8192

db2 update db cfg for TSMDB1 using NUM_LOG_SPAN 7

This problem is currently projected to be fixed in level 6.1.3

http://www-01.ibm.com/support/docview.wss?rs=663&context=SSGSG7&q1=ic63373&uid=swg1IC63373&loc=en_US&cs=utf-8&lang=en