Well, this is becoming a very annoying and crazy problem. Since upgrading my Linux TSM server from 5.5.3.0 to 5.5.4.1, I am having constant problems with the log filling and pinning. The latest set of tools and diagnostics being used to monitor the log say little to nothing.
I implemented the suggested cron job to monitor the log%used. For the past few nights, it has been hitting 95%+. It usually seems to back down on its own and then spike again. However, the "show logpinned" doesn't show any session/process that is pinning the log. The most common message from "show logpinned" at 5-minute intervals is: The recovery log is pinned by a dirty page in the data base buffer pool. Check the buffer pool statistics. If the associated transaction is still active then more information will be displayed about that transaction. I am going to alter the script to include the other 10-commands suggested in the PERL script from IBM. Any thoughts on what is going on? As I said, I never had these problems before 5.5.4.1. I have held off upgrading my other 5.5 servers until I get a handle on what is going on. Looks/smells like a defect to me. Nothing in my workload has changed within the past 2-months. Zoltan Forray TSM Software & Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html
