On Apr 17, 2011, at 6:08 PM, Steve Harris wrote:
> For anyone looking to go to TSM server 5.5.5.0, be aware of a nasty bug
> that requires SQL identifiers to be 18 characters or less in length and
> may break your scripts. IC71586 was fixed at 5.5.5.1
And 5.5.5.2 was just released; this has, amo
For anyone looking to go to TSM server 5.5.5.0, be aware of a nasty bug
that requires SQL identifiers to be 18 characters or less in length and
may break your scripts. IC71586 was fixed at 5.5.5.1
Regards
Steve
Steven Harris
TSM Admin,
Canberra Australia
On Sun, 17 Apr 2011 10:18:25 -0700,
We have seen the same log pinning issue once we upgraded from TSM 5.4.3 to
5.5.4.x. We have had a couple of TSM crashed due to log fill. The workaround
was to:
-set logmode normal
-scripts to monitor logs>80% every 15 mins. and kill process like NDMP ba
stgp, to get log usage down
-get woken up in
On Sat, Apr 16, 2011 at 11:41:13PM -0400, Nancy L Leugemors wrote:
> Hello,
>
> We just upgraded our TSM Server this from 5.5.4.0 to 5.5.5.0 to fix APAR
> IC66116. Since the server upgrade we have experienced several recovery
> log pinning incidents from a few different database backup client
Nancy
Not a fix for your problem, but I'd strongly urge you to reduce your log
from the 13GB max to maybe 12GB - reason being is that if you do hit the
situation where the log gets to 100% and the instance stops, the only way
to get it back is to do an emegency log growth. If your already at the
