When a long-running transaction starts, it can "pin" data in the log. Then even a DBBACKUP cannot clear the log until that long-running transaction completes.
Look in your server activity log and see what OTHER activity is going on at the time your DB backup runs. Look for: - EXPIRATION - long-runing reclamation job - a very long-running client backup One of these is usually what causes the problem. (In older versions of TSM there was also a bug that delayed clearing of the log, but I haven't heard of this happening in 4.2.) -----Original Message----- From: Thida Chin [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 06, 2002 10:55 AM To: [EMAIL PROTECTED] Subject: Re: Anybody can help me on this?? Please help!!!! dbbackup does not help to reduce log pct.... Yes, I do. Now system is up and running but still do not understand why sometimes backup database help to reduce pct log but sometimes not. The log mode is rollforward and versions of TSM is 4200 -----Original Message----- From: Gill, Geoffrey L. [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 06, 2002 11:02 PM To: Chintawongvanich, Thida T SITI-ITDSPS3101 Subject: RE: Anybody can help me on this?? Please help!!!! dbbackup does not help to reduce log pct.... Thida, You can format space and extend the size of your recovery log without having TSM up, check the administrators guide for the proper syntax, it's quite easy. After that you should be able to bring up TSM. I would suggest getting up level on your server version so it won't happen again, I'm sure there is a fix for this. It's good to have some extra space out there to extend the log quickly in case this happens again. With TSM 4.2 your log can be up to 13gb. Geoff Gill TSM Administrator NT Systems Support Engineer SAIC E-Mail: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> Phone: (858) 826-4062 Pager: (888) 997-9614
