Kinda weird...i had the exact same thing happen yesterday and I've never seen it before either. We had to halt/restart to fix the problem......
-----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Mark Stapleton Sent: Wednesday, February 07, 2007 11:35 AM To: [email protected] Subject: Re: [ADSM-L] Recovery Log Pinned From: ADSM: Dist Stor Manager on behalf of Choudarapu, Ramakrishna (GTI) Looks like this pin is 'stubborn', as the successful completion of the database backup for last three days, did not clear the log. AFAIK, this has not happened before. What would happen to the uncommitted transactions if the TSM service is recycled? [SNIP] Can't say, although I've never lost any TSM db data when forced to run HALT on the server; I suspect that forces a log commit as part of an orderly shutdown. If you've got time, I'd log a call with Tivoli support and set a ticket for this. They may want to gather some data on the situation, time and your situation permitting. This is the first "stubborn" log pin with no obvious cause I've heard of since 5.3 came into being. What size is your recovery log? -- Mark Stapleton ([EMAIL PROTECTED]) Senior consultant This email and any files transmitted with it are confidential and intended solely for the use of the addressee. If you are not the intended addressee, then you have received this email in error and any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. Please notify us immediately of your unintended receipt by reply and then delete this email and your reply. Tyson Foods, Inc. and its subsidiaries and affiliates will not be held liable to any person resulting from the unintended or unauthorized use of any information contained in this email or as a result of any additions or deletions of information originally contained in this email.
