Which is the client causing log space to be overcommitted.? are u running any DB2 sessions. As i experienced , DB2 client casuing lot of problems for log space due to incorrect size estimate.
Try doing dumpdb/loaddb/audit db ....this may resolve your problem. John Bremer <jbremer@LANL. To: [EMAIL PROTECTED] GOV> cc: Sent by: Subject: Re: anyone else notice, log doesn't clear "ADSM: Dist during expiration...(even w ith logmode normal) Stor Manager" <[EMAIL PROTECTED] IST.EDU> 11/09/2001 02:16 Please respond to "ADSM: Dist Stor Manager" Yes this has bitten us on a few occasions and requires the usual temporary log extension, re-start, database backup, log reduction, etc. At 09:25 AM 11/8/01 -0600, you wrote: >anyone else notice that with the server > >Storage Management Server for AIX-RS/6000 - Version 4, Release 1, Level 4.0 > >even with log mode normal, the log doesn't clear for the ENTIRE duration of >expiration... > > >When expiration runs for 6-8+ hours a day and clients initiate a half >million sessions per month (pretty much round the clock daily) and and and >a person can run out of log space frequently... > >not even the ol' ckpt will force check point things & clear the log... > >and I've also had a server, for two days in a row now, get something hung >and the log wouldn't clear (with only a very few client sessions running...) >for no apparent reason, log space kept getting sucked up until it hit 100.1 >%, issued about a million (so it seemed in clearing alerts on my pager) >messages about the log being filled, and then BOOM, it cleared up all by >itself... we might call in a problem on this one if we can get more info >on it/why??? but right now I'm just whine'n > >I should have stayed with 3.7 :-/ > >Dwight