Hi Joni,
I have been there. I am on the Mainframe also. The DB backup
trigger does work. I started to do an incremental DB backup just before
the backup would start in the evening. It helped me out a lot. The version
you are on 4.1.x has the log limit of 5GB. Version 4.2 and above it is
11GB.
IF YOUR LOG FILLs YOU LOCK UP. Then you will have to extend your
log, make sure NOTHING ELSE BY THE DB BACKUP RUNS, then let everything
start up. I personally would stop absolutely everything but the DB backup
right now! Do a CANCEL PROC XXXX on that deletion you have running. Stop
the backups if you can, stop the migrations or any other services and pray
that you have enough log space left to do the DB backup.
MAtt
-----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
|
