ADSM-L

Können wir mal drüber reden

2005-07-25 03:03:21
Subject: Können wir mal drüber reden
From: Heinz-Joachim Staerke <a.staerke AT FKF.MPG DOT DE>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Mon, 25 Jul 2005 08:47:54 +0200
Karl,

wissen wir selber, oder ?

Achim

> -----Ursprüngliche Nachricht-----
> Von: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]Im Auftrag 
> von
> Tab Trepagnier
> Gesendet: Freitag, 22. Juli 2005 19:39
> An: ADSM-L AT VM.MARIST DOT EDU
> Betreff: Re: ANR9999D pkthread.c(1037): ThreadId<31> Unable to cr eate
> new Thread....
>
>
> Jane,
>
> I know of no such limit.  I'm running a 1 GB buffer pool on my 4 GB TSM
> AIX server with no issues.  The only thing to watch is that the buffer
> pool is considered "process" memory by AIX.  So the default MaxPerm% of
> 80% means that AIX allows process to have priority on 1 GB with the other
> 3 GB given preference for files.  Because in my case, process memory is
> 25% + whatever AIX and TSM themselves use, quite a lot of memory would be
> paged out to disk.  So you have to adjust MaxPerm% down to allow AIX and
> TSM to have enough process memory to avoid that paging activity.  If you
> understand what's going on that should be a one-time operation.
>
> Good luck.
>
> Tab Trepagnier
> TSM Administrator
> Laitram, L.L.C.
>
>
> "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 07/21/2005
> 05:13:54 AM:
>
> > Hi -
> >
> > In the Performance Tuning Guide this states that the 'buffer pool size
> may
> > not exceed 10% of physical memory on AIX'....
> >
> > Also, Recommended values are included in a table dependent on your
> amount of
> > physical memory, but max in MB is 256 assuming you have 2048MB of
> memory.
> >
> > They may have something that has been updated that goes up for higher
> > memory??
> >
> > Jane.
> >
> >
> > -----Original Message-----
> > From: Henrik Wahlstedt [mailto:SHWL AT STATOIL DOT COM]
> > Sent: 21 July 2005 11:11
> > To: ADSM-L AT VM.MARIST DOT EDU
> > Subject: Re: [ADSM-L] ANR9999D pkthread.c(1037): ThreadId<31> Unable to
> > create new Thread....
> >
> > Hi,
> >
> > I´m not sure if there are some upper limit on Bufpoolsize, but 1024000
> seems
> > rather high to me... One of our p650, aix, with 16GB of ram just use a
> > bufpoolsize of 786432.
> >
> > What happens if you reset bufpool to it´s original value, and re-run the
> > backups?
> >
> >
> > //Henrik
> >
> >
> >
> > -----Original Message-----
> > From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On 
> > Behalf Of
> > Nielsen, Bo
> > Sent: den 21 juli 2005 10:54
> > To: ADSM-L AT VM.MARIST DOT EDU
> > Subject: ANR9999D pkthread.c(1037): ThreadId<31> Unable to create new
> > Thread....
> >
> > Hi
> >
> > last night I have a couple of nodes, who failed with
> >    Server Detected Error.
> > In TSM server activity log I found these message:
> >
> > 07/21/2005 03:28:03 ANR9999D pkthread.c(1037): ThreadId<31> Unable to
> create
> > new Thread. CreateThread error.Callchain: 104EAD79 outTextf()+1529 <-
> > 10007040 pkLogicAbort()+A30 <- 15E3D688 Unknown <- 10A7CC08
> > outTextf()+5933B8 <-
> > 07/21/2005 03:28:04 (31) Context report 07/21/2005 03:28:04 (31) Thread
> > SessionThread (23) is a child thread related to: 31 07/21/2005 03:28:04
> (23)
> > Generating TM Context Report: (struct=tmTxnDesc) (slots=256) 07/21/2005
> > 03:28:04 (23) *** no                 transactions found
> > ***
> > 07/21/2005 03:28:04 (23) Generating Database Transaction Table Context:
> > 07/21/2005 03:28:04 (23) *** no transactions found
> > ***
> > 07/21/2005 03:28:04 (23) Generating SM Context Report: 07/21/2005
> 03:28:04
> > (23) Session 195354: Type=Node, Id=CDKALB030 07/21/2005 03:28:04 (23)
> > Platform=WinNT, NodeId=254, Owner= 07/21/2005 03:28:04 (23) SessType=5,
> > Index=37, TermReason=0 07/21/2005 03:28:04 (23) RecvWaitTime=0.000
> > (samples=0) 07/21/2005 03:28:04 (23) Backup Objects ( bytes ) Inserted:
> 0 (
> > 0.0 ) 07/21/2005 03:28:04 (23) Backup Objects ( bytes ) Restored: 0 (
> 0.0 )
> > 07/21/2005 03:28:04 (23) Archive Objects ( bytes ) Inserted: 0 ( 0.0 )
> > 07/21/2005 03:28:04 (23) Archive Objects ( bytes ) Retrieved: 0 ( 0.0 )
> > 07/21/2005 03:28:04 (23) Last Verb ( Ping ), Last Verb State ( Sent )
> > 07/21/2005 03:28:04 (23) Generating AS Vol Context Report:
> > 07/21/2005 03:28:04 (23) No mounted (or mount in progress) volumes.
> > 07/21/2005 03:28:04 (23) Generating ssSession Context Report:
> > 07/21/2005 03:28:04 (23) Storage Service Sessions:
> > 07/21/2005 03:28:04 (23) Session 134454 --> BufConfig=None,
> TransBufSize=0,
> > SplitBuf=False, WrCount=0, WrBufIsEmpty=False,
> > WrBufIsFull=False, SourceRc=0, SinkRc=0, AuxCreated=Fals- e,
> AuxBegin=False,
> > AuxIsSink=False,                 AuxIdle=False,
> > AuxTerminate=False
> > 07/21/2005 03:28:04 (23) Leased Volumes:
> > 07/21/2005 03:28:04 (23) (none)
> > 07/21/2005 03:28:04 (23) Excluded VolIds:
> > 07/21/2005 03:28:04 (23) (none)
> > 07/21/2005 03:28:04
> > 07/21/2005 03:28:04 (23) Generating ssOpenSeg Context Report:
> > 07/21/2005 03:28:04 (23) No storage service segments found.
> > 07/21/2005 03:28:04 (23) Generating BF Copy Control Context Report:
> > 07/21/2005 03:28:04 (23) No global copy control blocks.
> > 07/21/2005 03:28:04 07/21/2005 03:28:05 (31) Thread SessionThread (24)
> is a
> > child thread related to: 31
> > 07/21/2005 03:28:05 (24) Generating TM Context Report:
> (struct=tmTxnDesc)
> > (slots=256)
> > 07/21/2005 03:28:05 (24) *** no transactions found ***
> > 07/21/2005 03:28:05 (24) Failed attempt #1 to get DBV->mutex
> > 07/21/2005 03:28:05 (24) Failed attempt #2 to get DBV->mutex
> > 07/21/2005 03:28:05 (24) Generating Database Transaction Table Context:
> > 07/21/2005 03:28:05 (24) *** no transactions found ***
> > 07/21/2005 03:28:05 (24) Generating SM Context Report:
> > 07/21/2005 03:28:05 (24) Session 195326: Type=Node, Id=CDKALB018_SQL5.2
> > 07/21/2005 03:28:05 (24) Platform=WinNT, NodeId=289, Owner=
> > 07/21/2005 03:28:05 (24) SessType=5, Index=32, TermReason=0
> > 07/21/2005 03:28:05 (24) RecvWaitTime=0.000 (samples=0)
> > 07/21/2005 03:28:05 (24) Backup Objects ( bytes ) Inserted: 0 ( 0.0 )
> > 07/21/2005 03:28:05 (24) Backup Objects ( bytes ) Restored: 0 ( 0.0 )
> > 07/21/2005 03:28:05 (24) Archive Objects ( bytes ) Inserted: 0 ( 0.0 )
> > 07/21/2005 03:28:05 (24) Archive Objects ( bytes ) Retrieved: 0 ( 0.0 )
> > 07/21/2005 03:28:05 (24) Last Verb ( ConfirmResp ), Last Verb State (
> Sent )
> > 07/21/2005 03:28:05 (24) Generating AS Vol Context Report:
> > 07/21/2005 03:28:05 (24) No mounted (or mount in progress) volumes.
> > 07/21/2005 03:28:05 (24) Generating ssSession Context Report:
> > 07/21/2005 03:28:05 (24) Storage Service Sessions:
> > 07/21/2005 03:28:05 (24) Session 134426 --> BufConfig=None,
> TransBufSize=0,
> > SplitBuf=False, WrCount=0, WrBufIsEmpty=False,
> > WrBufIsFull=False, SourceRc=0, SinkRc=0, AuxCreated=Fals- e,
> AuxBegin=False,
> > AuxIsSink=False,                 AuxIdle=False,
> > AuxTerminate=False
> > 07/21/2005 03:28:05 (24) Leased Volumes:
> > 07/21/2005 03:28:05 (24) (none)
> > 07/21/2005 03:28:05 (24) Excluded VolIds:
> > 07/21/2005 03:28:05 (24) (none)
> > 07/21/2005 03:28:05
> > 07/21/2005 03:28:05 (24) Generating ssOpenSeg Context Report:
> > 07/21/2005 03:28:05 (24) No storage service segments found.
> > 07/21/2005 03:28:05 (24) Generating BF Copy Control Context Report:
> > 07/21/2005 03:28:05 (24) No global copy control blocks.
> > 07/21/2005 03:28:05
> > 07/21/2005 03:28:05 (31) Thread SessionThread (36) is a child thread
> related
> > to: 31 .
> > .
> > .
> > .
> > 07/21/2005 03:28:40
> >
> > 07/21/2005 03:28:40   (31) acceptorThread : ANR9999D calling thread
> >
> > 07/21/2005 03:28:40   (31) Generating TM Context Report:
> (struct=tmTxnDesc)
> >
> >                        (slots=256)
> >
> > 07/21/2005 03:28:40   (31)  *** no transactions found ***
> >
> > 07/21/2005 03:28:40   (31) Generating Database Transaction Table
> Context:
> >
> > 07/21/2005 03:28:40   (31)  *** no transactions found ***
> >
> > 07/21/2005 03:28:40   (31) Generating SM Context Report:
> >
> > 07/21/2005 03:28:40   (31)  *** no sessions found ***
> >
> > 07/21/2005 03:28:40   (31) Generating AS Vol Context Report:
> >
> > 07/21/2005 03:28:40   (31)  No mounted (or mount in progress) volumes.
> >
> > 07/21/2005 03:28:40   (31) Generating ssSession Context Report:
> >
> > 07/21/2005 03:28:40   (31)  No storage service sessions active.
> >
> > 07/21/2005 03:28:40   (31) Generating ssOpenSeg Context Report:
> >
> > 07/21/2005 03:28:40   (31)  No storage service segments found.
> >
> > 07/21/2005 03:28:40   (31) Generating BF Copy Control Context Report:
> >
> > 07/21/2005 03:28:40   (31)  No global copy control blocks.
> >
> > 07/21/2005 03:28:40
> >
> > 07/21/2005 03:28:40   (31) End Context report
> >
> >
> >
> > I can't find any logs.
> >
> > Yesterday I set option BUFPOOLSIZE to 1024000 ( 256000 pages), because
> of
> > low DB Cache Hit Pct.
> >
> > TSM server is W2K3 vers. 5.2.3.
> > The Windows server have 4 Gb Memory and 4 CPUs.
> >
> >
> >
> >  Regards
> >  Bo Nielsen
> >                                                   * +45 4386 4671
> >  Coop Norden IT                              * (Internt
> > postcenter): 6244
> > Data & Storage Center                       *
> > mailto:bo.nielsen AT coop DOT dk
> >
> > Remember, a dead fish can float downstream, But it takes a live one to
> svim
> > upstream. - W.C. Fields.
> >
> >
> > -------------------------------------------------------------------
> > The information contained in this message may be CONFIDENTIAL and is
> > intended for the addressee only. Any unauthorised use, dissemination of
> the
> > information or copying of this message is prohibited. If you are not the
> > addressee, please notify the sender immediately by return e-mail and
> delete
> > this message.
> > Thank you.
> >
> > Please check that this email is addressed to you,
> > If not, you should delete it immediately as its contents may be
> > confidential and its disclosure, copying or distribution unlawful.
> > C. & J. Clark International Limited takes steps to prevent the
> > transmission of electronic viruses but responsibility for screening
> > incoming messages and the risk of such transmission lies with the
> recipient.
> > This email has been scanned for viruses by FrontBridge.com
> >
>

<Prev in Thread] Current Thread [Next in Thread>