You can't unless it's something obvious. I raised an enhancement request for this. There MAY be something written sometime in version 5 apparently.
Mit freundlichen Grüßen - With best regards Serdeczne pozdrowienia - Slan agus beannacht Paul Baines TSM/ADSM Consultant -----Ursprüngliche Nachricht----- Von: Talafous, John G. [mailto:[EMAIL PROTECTED]] Gesendet: Dienstag, 18. Dezember 2001 16:49 An: [EMAIL PROTECTED] Betreff: Re: Recover log at 5120MB and full - Cannot start TSM 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 **********************************************************************
