When we are deleting logs in TSM every week, we encounter very poor
performance for deleting > 1000 logs for each DB2 partition. There
are 131 DB2 partitions. Deleting the same amount of logs with dsmc del .
. . . . works much faster. We assume db2adutl deletes log by log
sequentially per DB2 partition. The command is "delete logs older than
<logfile> db <db> dbpartitionnum X without prompting" We
call db2adutl with db2_all per single DB2 partition in configurable
chunks (8 - 16 DB2 partitions in parallel)"
Wanted to know if db2adutl can be multi threaded and can do this operation in parallel?
|Who would benefit from this IDEA?||Faster product|
How should it work?
The question is if db2adutl can delete logs in parallel per
partition as db2_all will send it on all the partitions but it can still
be serial. For "db2adutl delete log older than <logfile>" on one
partition, if logs to be deleted is more than one, db2adutl will delete
them sequentially rather than in parallel, that is, db2adutl will delete
logs one at a time and one by one. If the customer wants db2adutl to
delete logs in parallel, an RFE is an option for them to request this
|Priority Justification||When this deletion is running with db2adutl the TSM server has such a high load, that regular Log archiving takes very long and is thus generating errors.|
NOTICE TO EU RESIDENTS: per EU Data Protection Policy, if you wish to remove your personal information from the IBM ideas portal, please login to the ideas portal using your previously registered information then change your email to "email@example.com" and first name to "anonymous" and last name to "anonymous". This will ensure that IBM will not send any emails to you about all idea submissions