ADSM-L

Recovery Log Pinned

2007-02-07 12:10:13
Subject: Recovery Log Pinned
From: "Choudarapu, Ramakrishna (GTI)" <Ramakrishna_Choudarapu AT ML DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 7 Feb 2007 12:09:39 -0500
Hi All,

We had a recovery log pinning problem and the log was growing since last
4 days and currently is at 72% util...
TSM Server 5.3.3.0 running on z/OS.

Below is the SHOW LOGPINNED output:

tsm>show logpinned
Dirty page Lsn=1463720.82.404, Last DB backup Lsn=1463720.117.3419,
Transaction table Lsn=1459621.38.800,
Running DB backup Lsn=0.0.0, Log truncation Lsn=1459621.38.800

Lsn=1459621.38.800, Owner=DB, Length=257
Type=Update, Flags=C2, Action=ExtInsert, Page=135546, Tsn=0:114182445,
PrevLsn=0.0.0, UndoNextLsn=0.0.0,
UpdtLsn=1459621.30.3992 ===> ObjName=AS.Segments, Index=4, RootAddr=14,
PartKeyLen=3, NonPartKeyLen=4,
DataLen=150
(81205) Generating SM Context Report: 
(81205)  *** no sessions found ***
(81206) Generating SM Context Report: 
(81206)  *** no sessions found ***
(81204) Generating SM Context Report: 
(81204)  *** no sessions found ***
No session or process assoicated with this transaction can be located,
or one or more session and process
found.

How to commit the pinned transactions to the database and release the
log space?

Regards,
Rama
--------------------------------------------------------

If you are not an intended recipient of this e-mail, please notify the sender, 
delete it and do not read, act upon, print, disclose, copy, retain or 
redistribute it. Click here for important additional terms relating to this 
e-mail.     http://www.ml.com/email_terms/
--------------------------------------------------------

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