Author: Gerhard Rentschler <g.rentschler AT RUS.UNI-STUTTGART DOT DE>
Date: Tue, 29 May 2001 10:29:39 +0200
Hi, some time ago I complained in a mail to this list that the recovery log utilization is not reset after a database backup. APAR IC30181 was generated for this problem. Its status is "open". Best r
Author: Suad Musovich <suad AT CCU1.AUCKLAND.AC DOT NZ>
Date: Wed, 30 May 2001 18:28:44 +1200
I complained about the problem too. The response I got was, when the system was too busy it took a while for it to happen. I have done this when no sessions/processes were running on the system and
Yes, the server will start terminating sessions at 100%. If this resolves the issue, it will usually recover, else it will core dump with a LOGSEG error. Jeff Bach Home Office Open Systems Engineerin
Author: David Longo <David.Longo AT HEALTH-FIRST DOT ORG>
Date: Wed, 30 May 2001 09:14:55 -0400
When your recovery log hits 100%, basically one of two things happens. 1. If there is "Available Space" greater than "Assigned Capacity" then log will acquire some of this additional space. 2. When a
Author: Angela Hughes <hughesa1989 AT YAHOO DOT COM>
Date: Wed, 30 May 2001 06:31:41 -0700
This problem can also be eliminated by performing a full DB backup daily which I've always done and if the environment is very large with a lot of activity you can perform incremental DB backups with
Author: Paul Zarnowski <vkm AT CORNELLC.CIT.CORNELL DOT EDU>
Date: Thu, 31 May 2001 12:19:33 -0400
We run into this problem a lot. I believe there are a couple of issues here. One issue, that Gerhard mentioned, is that the log utilization does not drop quickly when the db backup apparently finishe