[ADSM-L] TSM Recovery log is pinning since upgrade to 5.5.5.0 code
2011-04-16 23:42:41
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 clients. I
haven't found any hits on new bugs related to our issue and I just opened
up a case with support but was wondering if anyone had a similar issue
with this level of server and client code or know of any APARS this might
fit? Our recovery log has always been set to 13GB so I can't expand it
anymore. Running a database backup doesn't free any space while the
client database backup is running either. We run 1 full TSM database
backup and multiple incrementals throughout the day. The only difference
is the upgrade to the latest code. I'm not seeing any other errors, just
showing different database clients pinning the log after issuing show log
pinned command. Sometimes the client backup finishes before hitting 80%
and sometimes TSM server cancels the longest running backup that is
pinning the log.
example of error:
29857)
04/16/11 04:03:26 ANR0524W Transaction failed for session 24418 for
node
DEVNODE_API (SQL-BACKTRACK) - data transfer
interrupted.
(SESSION: 24418)
04/16/11 04:03:26 ANR2997W The server log is 81 percent full. The
server
will delay transactions by 3 milliseconds.
(SESSION:
29846)
TSM Background:
TSM Server: 5.5.5.0
TSM OS: AIX 5300 -12
TSM Clients: 5.5.2.0
TSM Client OS: AIX 5.3 (UDB-DB2 & SQL-Backtrack Sybase seen so far)
Thank You,
Nancy Leugemors
Enterprise Systems
HealthNow, NY
716-887-7979
CONFIDENTIALITY NOTICE: This email message and any attachments are for the sole
use of the intended recipient(s) and may contain proprietary, confidential,
trade secret or privileged information. Any unauthorized review, use,
disclosure or distribution is prohibited and may be a violation of law. If you
are not the intended recipient or a person responsible for delivering this
message to an intended recipient, please contact the sender by reply email and
destroy all copies of the original
message.
|
|
|