ADSM-L

Re: [ADSM-L] Internal error TBUNDO012 question

2008-02-14 14:54:48
Subject: Re: [ADSM-L] Internal error TBUNDO012 question
From: "Strand, Neil B." <NBStrand AT LMUS.LEGGMASON DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 14 Feb 2008 14:54:12 -0500
I found out what a TBUNDO012 error means - It is IBM speak for "You are
Screwed" - your database is corrupt and you need to dump/load/audit.

This process should complete in about a week.  Fortunately, we have just
built out several new TSM servers and have moved all of the nodes(250)
to different servers.  The corrupt database was 195GB in size and was
running on AIX 5.3 on an F80.

I am looking forward to TSM on DB2.

Have a happy day!
Neil Strand
Storage Engineer - Legg Mason
Baltimore, MD.
(410) 580-7491
Whatever you can do or believe you can, begin it.
Boldness has genius, power and magic.


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Stapleton, Mark
Sent: Tuesday, February 12, 2008 1:47 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Internal error TBUNDO012 question

>From searching the IBM site:

http://www.ibm.com/Search/?q=ANR7837S&v=16&lang=en&cc=us&en=utf&Search=S
earch

See if any of the descriptions match your environment. You may have a
pinned recovery log.

--
Mark Stapleton
CDW Berbee
System engineer
7145 Boone Avenue North, Suite 140
Brooklyn Park MN 55428-1511
763-592-5963
www.berbee.com


> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
Of
> Strand, Neil B.
> Sent: Tuesday, February 12, 2008 12:18 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: [ADSM-L] Internal error TBUNDO012 question
>
> I have a TSM instance v5.3.4.0 running on AIX 5.3 ML4 The TSM instance

> has crashed with the following:
>
> 2/12/2008 10:15:21  ANR7838S Server operation terminated.
> 02/12/2008 10:15:21  ANR7837S Internal error TBUNDO012 detected.
>
> I recovered the server yesterday and all appeared fine but this
morning
> it crashed again with the identical error.
> The TSM DB size is 195GB.
>
> Has anyone run across this with TSM V5.3.4?  I have seen a few
> references with TSM V4.x and 3.x. but nothing more current.
>
> Cheers,
> Neil Strand
> Storage Engineer - Legg Mason
> Baltimore, MD.
> (410) 580-7491
> Whatever you can do or believe you can, begin it.
> Boldness has genius, power and magic.
>
> IMPORTANT:  E-mail sent through the Internet is not secure. Legg Mason

> therefore recommends that you do not send any confidential or
sensitive
> information to us via electronic mail, including social security
numbers,
> account numbers, or personal identification numbers. Delivery, and or
> timely delivery of Internet mail is not guaranteed. Legg Mason
therefore
> recommends that you do not send time sensitive or action-oriented
> messages to us via electronic mail.
>
> This message is intended for the addressee only and may contain
privileged
> or confidential information. Unless you are the intended recipient,
you
> may not use, copy or disclose to anyone any information contained in
this
> message. If you have received this message in error, please notify the

> author by replying to this message and then kindly delete the message.
> Thank you.

IMPORTANT:  E-mail sent through the Internet is not secure. Legg Mason 
therefore recommends that you do not send any confidential or sensitive 
information to us via electronic mail, including social security numbers, 
account numbers, or personal identification numbers. Delivery, and or timely 
delivery of Internet mail is not guaranteed. Legg Mason therefore recommends 
that you do not send time sensitive 
or action-oriented messages to us via electronic mail.

This message is intended for the addressee only and may contain privileged or 
confidential information. Unless you are the intended recipient, you may not 
use, copy or disclose to anyone any information contained in this message. If 
you have received this message in error, please notify the author by replying 
to this message and then kindly delete the message. Thank you.