Oops,
Seems as though one of our TSM servers has not been looked after
properly, has tried to overrun its recovery log and fallen over on its
face with the usual ANR7837S LOGSEQ errors. Our friendly second-level
guy went ahead and created a new log vol and tried to dsmserv extend to
get it in, but it failed with such errors as:
ANR9999D tbundo.c(256): Error1 on insert from table
Backup.Objects for undo.
ANR7837S Internal error TBUNDO012 detected
It's a Win2K AS server running at lowly 4.1.3 - now as I remember, TSM
recovery log hits a ceiling at around 5GB until after 4.2. I think, from
looking at the logvols already assigned, that we're at that ceiling now,
and aren't able to extend it any further. The logvol that was attempted
to be added was only 20MB so I'm guessing we're *right* up to that
ceiling - not good I know...
So team, any ideas for how to get the TSM server back up again?
Rgds,
David McClelland
Global Management Systems
Reuters Ltd
--------------------------------------------------------------- -
Visit our Internet site at http://www.reuters.com
Get closer to the financial markets with Reuters Messaging - for more
information and to register, visit http://www.reuters.com/messaging
Any views expressed in this message are those of the individual
sender, except where the sender specifically states them to be
the views of Reuters Ltd.
