Hi Joni

Its strange to see recovery log filling up to 5GB level in NORMAL mode (
you mentioned that in ur previous mail).

In NORMALMODE recovery log doesn't keep transactions, it deletes
transaction as soon as it committed to database.Thats why only
Point-in-Retsore ( till the last consistent database backup)  possible with
recovery log in NORMAL mode.

You can't use database backup trigger with recovery log in NORMAL mode.

with TSM 5.x Recovery Log max size is 13GB.

I can't figure out the reason for this behaviour.Let me know if you could
find the reason.

Thanks

regds

Raghu

-----Original Message-----
From: Joni Moyer [mailto:joni.moyer AT HIGHMARK DOT COM]
Sent: Wednesday, January 15, 2003 7:02 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: recovery log filling up rapidly: Please help: EMERGENCY!!!!!


My recovery log is filling up at a rapid rate.  I am running TSM at 4.1.3
on
the mainframe.  It is 4.6 GB and my DB is 48 GB with 46 GB in use.  I am
not
running expiration of the inventory yet due to a previous deletion of a
nodes data, could that be the cause?  I noticed that the log is reaching
about 95% full before I run another full backup.  I usually run a full DB
backup every day at 4:30.  What can I do?  I can't increase the recovery
log
because I guess on this version it can only go to 5 GB?  What version is
this no longer true for?  I really need help and I can't find anyone from
IBM to return my calls.  My previous problem with the recovery log is no
longer true.  It does now reset back to 0% after a full backup, but I am
running out of space.  I do have the log fully extended and with the 5 GB
limit I am stuck.  Also, I can't set up a DB backup trigger because I am on
the mainframe and that feature of TSM is not available.  Thank you in
advance for any help you can give me!!!!


Joni Moyer
Systems Programmer
joni.moyer AT highmark DOT com
(717)975-8338