or this behaviour.Let me know if you could
find 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 re
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
s
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 at 4.1.3
on
the ma
Run an incremental to dump the log.
Paul D. Seay, Jr.
Technical Specialist
Naptheon Inc.
757-688-8180
-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
>...I usually run a full DB backup every day at 4:30. What can I do? ...
First, determine what's eating your Recovery Log by doing periodic queries
through the day of the Recovery Log, Processes, and Sessions. Judicious
scheduling of the whoppers will help.
Do Incremental backups of your TSM DB
: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
:
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
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
