You could try running the "show logpinned" command, you should be able to identify what is pinning the log.
________________________________ From: ADSM: Dist Stor Manager on behalf of John C Dury Sent: Thu 5/5/2005 10:58 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Recovery log filling up quickly, too quickly. Ideas? I have v5311 AIX server installed. The DB is not in roll forward mode. There isn't anything that has changed recently that would be causing this. It seems it might be a bug in v5311 that doesn't let the recovery log empty as it happens sporadically. Expiration which runs daily is suddenly taking a much longer time to run also but also sporadically. I checked the number of objects per node in the DB to see if any have increased a significant amount which would cause expiration to run longer, but everything looks normal. My recovery log is 12296 MB(90% full) and my DB is 56480 MB (38.3% full). Any clues on what is going on here? How about a way to empty the recovery log? J. ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________
