This is called "pinning the log." It happens when a single transaction takes a long time. The log is circular starting anywhere within the log volumes. When a transaction starts an entry is placed into the log. Other entries, for other transactions, follow. Finally, when the first transaction is complete, the transaction is committed to the database. That frees the beginning of the log to move forward. So very long running transactions, like client database backups, will pin the log. In high transaction rate enviroments this can become a problem. One way to avoid this (to some extent) is to separate long running backups from high volume backups: start your database backups after or long before your file server backups, for instance. It isn't the long running guy that gets you but rather all the little ones while it's running.
Kelly J. Lipp Storage Solutions Specialists, Inc. PO Box 51313 Colorado Springs, CO 80949 [EMAIL PROTECTED] or [EMAIL PROTECTED] www.storsol.com or www.storserver.com (719)531-5926 Fax: (240)539-7175 -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of David Longo Sent: Tuesday, December 18, 2001 9:40 AM To: [EMAIL PROTECTED] Subject: Re: Recover log at 5120MB and full - Cannot start TSM I have my log in NORMAL mode too and I have found the main thing that consumes the log is clinet DB backups. I have an Oracle on AIX vi RMAN that drivesa it the most. TDP for MSSQL can too. (I have one client that has about 15GB DB MSSQL and normally causes no problem. One time there was a problem with client network and it had slow comm and that drove log way up. I guess the thing is that an individual DB or file has to complete and it not completing uses log space.) I have little problem with the number of clients running at once, it's just the items above that cause any use of log space. I have 3.7.4.0 server on AIX with 130GB Disk pool and 2 GB Recovery Log. About 120 clients and backup 250-300 GB a day. David Longo >>> [EMAIL PROTECTED] 12/18/01 10:49AM >>> I should have specified that our TSM server is in NORMAL log mode. How can I determine what is using recovery log space? John G. Talafous IS Technical Principal The Timken Company Global Software Support P.O. Box 6927 Data Management 1835 Dueber Ave. S.W. Phone: (330)-471-3390 Canton, Ohio USA 44706-0927 Fax : (330)-471-4034 [EMAIL PROTECTED] http://www.timken.com -----Original Message----- From: Talafous, John G. [mailto:[EMAIL PROTECTED]] Sent: Tuesday, December 18, 2001 9:51 AM To: [EMAIL PROTECTED] Subject: Re: Recover log at 5120MB and full - Cannot start TSM Thanks to all who responded and helped get our server back up and running. Now comes the task of figuring out what caused the recovery log to fill up in the first place and prevent it from happening again. Does anyone have any tips and tricks on determining what/who is using recovery log space? TIA, John G. Talafous IS Technical Principal The Timken Company Global Software Support P.O. Box 6927 Data Management 1835 Dueber Ave. S.W. Phone: (330)-471-3390 Canton, Ohio USA 44706-0927 Fax : (330)-471-4034 [EMAIL PROTECTED] http://www.timken.com -----Original Message----- From: Nancy Reeves [mailto:[EMAIL PROTECTED]] Sent: Monday, December 17, 2001 2:56 PM To: [EMAIL PROTECTED] Subject: Re: Recover log at 5120MB and full - Cannot start TSM Here is what I do when the recovery log fills, also on AIX. My notes agree with the person who said that the Extend size has to be a multiple of 4 and 1 less than the DSMFMT size. (What the other person said about max size being 5G, might cause this to not work, though.) If server will not start because the recovery log is full: 1) Find a location for an extra recovery log file 2) DSMFMT -LOG <fullfn> <size1> -- where size1 = 4x+1, where x => 2 3) DSMSERV EXTEND LOG <fullfn> <size2> -- where size2 = size1-1 4) DSMSERV -- to start the server normally 5) Solve the problem that caused the recovery log to fill. 6) After the server is up, either create a mirror for this recovery log or preferably remove it from use. Nancy Reeves Technical Support, Wichita State University [EMAIL PROTECTED] 316-978-3860 ********************************************************************** This message and any attachments are intended for the individual or entity named above. If you are not the intended recipient, please do not read, copy, use or disclose this communication to others; also please notify the sender by replying to this message, and then delete it from your system. The Timken Company ********************************************************************** "MMS <health-first.org>" made the following annotations on 12/18/01 11:52:41 ---------------------------------------------------------------------------- -- This message is for the named person's use only. It may contain confidential, proprietary, or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it, and notify the sender. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. Health First reserves the right to monitor all e-mail communications through its networks. Any views or opinions expressed in this message are solely those of the individual sender, except (1) where the message states such views or opinions are on behalf of a particular entity; and (2) the sender is authorized by the entity to give such views or opinions. ============================================================================ ==
