Vince I'm not sure where you got that reference number from, but my bookmarked page of Richard's quick facts gives the following references.
IBM Technotes: 1084167; 1105651; 1105830 I have just done a quick check on the IBM website and all 3 of the above are still available. I don't know the full specifics of your problem, but generally a recovery log gets pinned by a long running backup or long running process. If there are other high db transaction processes occurring at the same time, this is where your long starts to fill up and the 'concern' starts to set in. If you have a backup session running over a low bandwidth comms link and it is currently backing up a large file (ie Exchange database), this could pin the log. It could also be a session backing up over a 100Mbps link, but the link is not performing as it should (ie duplex mismatch) and therefore a large file backup is taking considerably longer and thus pinning the log. It could also be a process (migration, reclamation) that is transferring a single large file and it is taking longer than it should. (ie tape problem causing poor tape throughput). The command 'show logpinned' should give you the session id or process id of the offending operation. Cancel the session or process and the log will drop back down to a manageable amount. If you are unable to cancel the session or process, cancel any high db transaction processes that are adding to the log (ie expiration), this could give you breathing space. Lastly, if your log is not at the maximum size, you could consider extending it temporarily to allow the processes/sessions to complete, without the log filling. Hope that this is of some use. Leigh -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Vincent RATAJSZCZAK Sent: 14 November 2005 10:27 To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Recovery Log Pinned Hi TSM Cow Boys/Girls I would like to abuse of your busy time. I discover that 2 of my several servers have a recovery Log pinned. I use the TSM/ADSM QuickFacts which point me to "IBM site article swg21054574" I'm unable to find this article on the net, neither the IBM site. Someone would be kind enough to send me this article or shortly explain me how to resolve a log pinned, please ? Regards Vince