I agree with Gunther. We backup our database daily
(unfortunately, due to the size of the DB, we're forced to do
incremental backups and fulls only once a week) and we regularly
push up near this 5GB limit. I'm particularly perturbed b/c I
have a 9.1GB disk for the recovery log, of which I can only use a
little over half.

Why does this limit exist? It seems arbitrary--and incredibly
small, given that 500GB was the figure quoted as the max for a
database. I can't imagine you could run in roll-forward with
anything larger than 50GB without having to do DB backups several
times per day.

This brings me to another point: is there a reason why ADSM can't
be smart when the log *does* fill up (I know, it shouldn't
happen, but given the number of times the question gets asked on
this list, we all know that it does). When Oracle doesn't have a
log volume to which it can switch, it doesn't crash. It merely
prevents all database activity from continuing until the
administrator rectifies the problem. I particularly like the idea
of a set of log files which are switched when they fill up.

 -- Tom

"It's a dog eat dog world,                Thomas A. La Porte
 and I'm wearing milkbone underwear."     DreamWorks SKG
              - Norm Peterson             <tlaporte AT anim.dreamworks DOT com>

On Fri, 20 Mar 1998, H.G.Borrmann wrote:

>> Subject:  Maximum recovery log capacity?

[...]

>
>This limit is too small. We backup our database each day and we come near the
>limit with the size of our logfile!
>
>Gunther
>._________________________________________________________________________.
>|H.G.Borrmann                           |Tel.: (0761) 203-4652            |
>|Rechenzentrum der Universitaet Freiburg|Fax:  (0761) 203-4643            |
>|Hermann-Herder-Str. 10                 |email:                           |
>|D79104 FREIBURG                        |borrmann AT ruf.uni-freiburg DOT de   
>  |
>|_________________________________________________________________________|
>