Actually, "show log" is what is happening when you do "show log pin". The
"pin" is just ignored.
I asked today for the APARs not included in 4.2.3.0 that were in previous
patch 4.2.2.13.
I think it is legitimate to ask what APARs or missing things are not in
5.1.5.1 that were in 5.1.1.6. Who wants to be the bad guy to demand this
information as well?
Paul D. Seay, Jr.
Technical Specialist
Naptheon Inc.
757-688-8180
-----Original Message-----
From: Gretchen L. Thiele [mailto:[email protected]]
Sent: Tuesday, October 15, 2002 8:52 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: show logpin vs. show log pin
>> SHOW LOGPIN is not in v5.1.1.6. It was added back in on the newest
>> maintenance/patch - v5.1.5.1.
>
>The command is:
>
>show log pin
>
>...and it works on 5.1.1.6 on AIX
But it's not the 'same' command. 'show log pin' is different from 'show
logpin'. For example, on a v4.2.2.12 system (looks the same on v5.1.5.1):
show log pin
Log status information: HeadLsn: 2735079.236.3435 TruncLsn:
735079.223.313 Log record read statistics: NumRandReq=352207,
NumRandRead=8
997 (Hit 77.00%) Sampled batch read time (ms): *** no sampled data
***
Sampled read batch size (#pages): *** no sampled data *** Sampled
random
age read time (ms): *** no sampled data *** Log record write
statistics:
NumForces=226331, NumForceWait=154618 (Hit 31.69%) NumPushes=2348501,
NumPus
Wait=0 (Hit 100.00%) Sampled append time (ms): *** no sampled data
***
Sampled push time (ms): *** no sampled data *** Sampled force time
(ms):
*** no sampled data *** Sampled log bytes between forces: *** no
sampl
d data *** Log Writer thread statistics: Sampled full batch write time
(ms)
*** no sampled data *** Sampled full batch size (#pages): *** no
sam
led data *** Estimated mean page write time (ms): 0.00
show logpin
Dirty page Lsn=2735079.232.2161, Last DB backup Lsn=2735079.236.3843,
Transaction table Lsn=0.0.0, Running DB backup Lsn=0.0.0, Log truncation
Lsn=2735079.223.313
Lsn=2735079.223.313, Owner=DB, Length=190 Type=Update, Flags=C2,
Action=ExtInse t, Page=228, Tsn=0:69060303, PrevLsn=0.0.0,
UndoNextLsn=0.0.0, UpdtLsn=2735079.222.3355 ===> ObjName=Activity.Log,
Index=32, RootAddr=49, PartKeyLen=0, NonPartKeyLen=9, DataLen=81 The
recovery log is not pinned. Space in the recovery log will be freed at the
next checkpoint
The latter command, show logpin, is the one that is missing in v5.1.1.6 on
all platforms - I pointed this out to support and they verified that it was
missing and said it would be added back in the next maintenance release,
v5.1.5.0.
'sho logpin', if the log is actually pinned, will show you
who the culprit is or what process is pinning the log. It's very useful
command. 'sho log pin' doesn't do much for me!
Gretchen Thiele
Princeton University
|
