I've seen the log fill in Normal if you have a client running that's not
sending commits often enough. Clients with NICs set to Autonegotiate, then
ending up at 100/Half Duplex (or 10/Half duplex, a couple of times) will
pin the log due to not getting to a commit point. Add in expiration on
an
the reason.
Thanks
regds
Raghu
-Original Message-
From: Joni Moyer [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 15, 2003 7:02 AM
To: [EMAIL PROTECTED]
Subject: recovery log filling up rapidly: Please help: EMERGENCY!
My recovery log is filling up at a rapid rate. I am running TSM
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
:
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
: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
