In Normal mode, your recovery log usage should reduce on commits rather
than on DB Backups, which means your recovery log usage should constantly go
up and back down throughout the day. If you're maxing out your recovery
log, something is likely "pinning the tail" of the log. I would suggest you
find out what is pinning log and resolve that issue.
As an example, I had a user trying to back up a 20GB database flatfile
from an AIX client over Token Ring. As it was a backup of a single file,
the transaction never committed, so the transaction was pinning the log and
causing me to run out of recovery log space. My solution was to have them
to backup the file over the ATM backbone. The backup then didn't pin the
log long enough to fill the log.
Good luck,
Alex Paschal
Storage Administrator
Freightliner, LLC
(503) 745-6850 phone/vmail
-----Original Message-----
From: Van Ruler, Ruud R SSI-ISES-31
[mailto:[EMAIL PROTECTED]]
Sent: Monday, January 29, 2001 1:12 AM
To: [EMAIL PROTECTED]
Subject: Full Recovery Log
L&g
I am running TSM3.7 server on S/390.
Recovery log is in normal mode.
I am running a FULL DB backup every day.
At this moment the Recovery Log reached the maximum Available Space (MB).
There is however space to Extend (Maximum Extension (MB): 1,696).
But whatif at some point Maximum Extension (MB): 0 ????
I cannot define anymore log volumes because i have reached the maximum
Available Space !!!
please advise what to do ????
thanks.
Ruud van Ruler, Shell Services International BV - ISES/32
Our Data Storage Management home page:
http://sww2.shell.com/os390/
> Room 0C/G06
> Dokter van Zeelandstraat 1, 2285 BD Leidschendam NL
Tel : +31 (0)70 - 3034644, Fax 4011, Mobile +31 (0)6-55127646
Email Internet: [EMAIL PROTECTED]
[EMAIL PROTECTED]
R.vanRuler
