Expiration shouldn't be running during the backup window. Make sure
expire interval is set to 0 and schedule this processing to avoid high
db utilisation times.

_____________________________
Ian Smith
SAN/TSM Specialist
Hitachi Data Systems Certified Professional
IBM Tivoli Storage Manager Certified Consultant



-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Joni Moyer
Sent: 29 August 2006 12:41
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] HELP: TSM has recycled itself...

Hi Ian,

The process that you referenced was a NAS NDMP differential backup.  I
also had regular client backups occurring throughout all platforms of
servers such as windows, solaris, aix, etc.

I haven't changed anything in the current environment for approximately
a year, so nothing major has changed.  I also see that expiration was
running and I can see some of the "internal server error detected"
messages, but I'm not sure how to pinpoint what was causing it.

Any suggestions?

Thanks!

********************************
Joni Moyer
Highmark
Storage Systems, Senior Systems Programmer Phone Number: (717)302-9966
Fax: (717) 302-9826
joni.moyer AT highmark DOT com
********************************



"Smith, I (Ian)" <Ian.Smith AT RABOBANK DOT COM> Sent by: "ADSM: Dist Stor
Manager" <ADSM-L AT VM.MARIST DOT EDU>
08/29/2006 07:31 AM
Please respond to
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To
ADSM-L AT VM.MARIST DOT EDU
cc

Subject
Re: HELP: TSM has recycled itself...







What was happening at the time? Check earlier in the act log...

i.e. session 23037 and process 659?

_____________________________
Ian Smith
SAN/TSM Specialist
Hitachi Data Systems Certified Professional IBM Tivoli Storage Manager
Certified Consultant



-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Joni Moyer
Sent: 29 August 2006 12:27
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] HELP: TSM has recycled itself...

Hi Everyone,

I have a TSM server on AIX 5.3 at 5.2.7.1.  This morning it recycled
itself.  The only message I could find that was suspicious was the
following:

08/29/06 03:30:21     ANR9999D pkthread.c(601): ThreadId<1145> Run-time
                       assertion failed: "inLen >= 0", Thread 1145, File

                       tbcol.c, Line 631. Callchain of previous message:

                       0x0000000100017e90 outDiagf <- 0x0000000100009934

                       pkLogicAbort <- 0x00000001000b12d8 TbDecodeCols
<-

                       0x00000001000a24b4 tbFetchNext <-
0x00000001003f4168
                       TocGetNdmpFileData <- 0x0000000100319c38 ssStore
<-

                       0x00000001002d7114 DfCreate <- 0x00000001002c9c80

                       CreateBitfile <- 0x00000001002cd258 bfCreate <-
                       0x00000001003f538c tocWriteNdmpToc <-
0x00000001003efc0c
                       CreateToc <- 0x00000001003f2bd4
AfStoreRemoteThread
<-
                       0x00000001000080c4 StartThread <-
0x09000000004042f8
                       _pthread_body <-  (SESSION: 23037, PROCESS: 659)

Does anybody have any suggestions/ideas on what caused the software to
recycle?  Or where can I look to find out?

Thanks in advance!

********************************
Joni Moyer
Highmark
Storage Systems, Senior Systems Programmer Phone Number: (717)302-9966
Fax: (717) 302-9826
joni.moyer AT highmark DOT com
********************************
_____________________________________________________________

This email (including any attachments to it) is confidential, legally
privileged, subject to copyright and is sent for the personal attention
of the intended recipient only. If you have received this email in
error, please advise us immediately and delete it. You are notified that
disclosing, copying, distributing or taking any action in reliance on
the contents of this information is strictly prohibited. Although we
have taken reasonable precautions to ensure no viruses are present in
this email, we cannot accept responsibility for any loss or damage
arising from the viruses in this email or attachments. We exclude any
liability for the content of this email, or for the consequences of any
actions taken on the basis of the information provided in this email or
its attachments, unless that information is subsequently confirmed in
writing. If this email contains an offer, that should be considered as
an invitation to treat.
_____________________________________________________________