---------------------------- Top of message ---------------------------- >>--> 01-16-03 09:11 S.SHEPPARD (SHS) recovery log filling up r
The Database Backup Trigger IS available on the OS/390 server. We've been using it for years. Command is: DEFine DBBackuptrigger DEVclass=device-class LOGFullpct=nn NUMincr=n Unfortunately, it is only used if the log is in ROLLFORWARD mode. Sam Sheppard San Diego Data Processing Corp. (858)-581-9668 -----------------------------------------------------------------------` ---------------------------- Top of message ---------------------------- >>--> 01-15-03 04:03 ..NETMAIL () recovery log filling up r Date: Wed, 15 Jan 2003 07:01:33 -0500 From: "Joni Moyer" <[EMAIL PROTECTED]> Subject: recovery log filling up rapidly: Please help: EMERGENCY!!!!! To: [EMAIL PROTECTED] _________________________________Top_of_Message_________________________________ 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 [EMAIL PROTECTED] (717)975-8338 -----------------------------------------------------------------------`
