I have been experiencing frequent "log pinned" situations on a v6.2.5.0
server - by this I mean my monitoring program starts alerting me about the
active log reaching >75% (currently at 50GB).
Yes, I have identified the node causing this but want to know how to
diagnose and resolve why this node i
On 04/16/2013 08:59 AM, Zoltan Forray wrote:
>
> The active session is only up to 222GB so it isn't volume - just one long
> transaction, I guess?
(reliatively) Big files, transmitted (relatively) slowly, are my most
common log-pin culprit.
- Allen S. Rout
But, how do you address/resolve this kind of problem?
On Tue, Apr 16, 2013 at 9:22 AM, Allen S. Rout wrote:
> On 04/16/2013 08:59 AM, Zoltan Forray wrote:
> >
> > The active session is only up to 222GB so it isn't volume - just one long
> > transaction, I guess?
>
> (reliatively) Big files, tran
We address it with a larger log file. Our is 100G.
David
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Zoltan
Forray
Sent: Tuesday, April 16, 2013 9:37 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Addressing "log pinned" co
ip'ed into a smaller file? Can
the node be moved to a different TSM instance that doesn't have as much
activity. Does the file even need to be backed up?
Rick
From: Zoltan Forray
To: ADSM-L@VM.MARIST.EDU
Date: 04/16/2013 09:37 AM
Subject: Re: Addressing "log
rom: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Richard Rhodes
Sent: Tuesday, April 16, 2013 11:36 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Addressing "log pinned" condition on V6 server
Most of our problems like this are SQL db backups that are one big f
uot;?
>
> Thanks for any info!
>
> Wanda
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
> Richard Rhodes
> Sent: Tuesday, April 16, 2013 11:36 AM
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: [ADSM-L] Addressing "lo
> Rick, that is interesting -
> How do they accomplish "gets written in ... smaller pieces"?
>
> Is this some TDP tuning parameters you invoke, or is it a matter of
> backing up 1 DB at a time instead of doing "backup *"?
>
> Thanks for any info!
>
> Wanda
>
I don't know myself, but some quick se
On 04/16/2013 09:36 AM, Zoltan Forray wrote:
> On Tue, Apr 16, 2013 at 9:22 AM, Allen S. Rout wrote:
>> On 04/16/2013 08:59 AM, Zoltan Forray wrote:
>>>
>>> The active session is only up to 222GB so it isn't volume - just one long
>>> transaction, I guess?
>>
>> (reliatively) Big files, transmitte
Back in the day, it almost always used to be a duplex mismatch. "Get off
my lawn!" :-)
On 4/16/2013 6:36 AM, Zoltan Forray wrote:
But, how do you address/resolve this kind of problem?
On Tue, Apr 16, 2013 at 9:22 AM, Allen S. Rout wrote:
On 04/16/2013 08:59 AM, Zoltan Forray wrote:
The act
On 04/16/2013 04:58 PM, Alex Paschal wrote:
> Back in the day, it almost always used to be a duplex mismatch. "Get off
> my lawn!" :-)
That answers the description of 'transmitted relatively slowly', now,
doesn't it? :)
- Allen S. Rout
- Throwing down with ADSM 2.1, yo yo. ;)
11 matches
Mail list logo
