> Second, look for a client node who is doing this to you. Build a script
> to capture the output of SHOW LOGPIN periodically and look for trends -
> you may see one particular client node doing this to you over and over.
Here is what we use. Our daily report, generated at 6am, pulls data from
another script that runs every hour and collects log info and logpin info.
After creating the report, it zeros out the info and watches for another
24 hours.
There is another monitoring scripts that watches for the log getting to
90%. If it does, it automatically runs "show logpin cancel".
It has been a great help in figuring out problems with logpins.
We are NOT in roll forward mode, and have 12.5gb of log.
At one time, we used to wrap the log several times . . . showing up as
log comsumption of over 20gb.
== r050 ===============================================================
== log consumption and utilization
== Mon Oct 29 06:03:11 EDT 2007
=======================================================================
date log-consumption pct-util max-pct-util
200710280700 127.75 6.7 6.7
200710280800 211.28 1.3 7.2
200710280900 249.45 0.3 7.2
200710281000 522.69 2.4 7.2
200710281100 699.17 3.8 7.2
200710281200 790.71 4.6 7.2
200710281300 863.24 0.0 7.2
200710281400 1,310.61 0.1 7.2
200710281500 1,509.29 0.1 7.2
200710281600 1,926.78 0.1 7.2
200710281700 2,086.57 0.6 7.2
200710281800 2,282.52 0.4 7.2
200710281900 2,611.49 2.3 7.2
200710282000 3,101.14 5.3 7.2
200710282100 3,568.90 9.2 9.2
200710282200 4,593.10 16.6 17.5
200710282300 5,069.75 20.5 20.5
200710290000 5,424.45 4.3 21.7
200710290100 5,790.99 7.4 21.7
200710290200 6,327.59 9.2 21.7
200710290300 6,797.84 3.9 21.7
200710290400 7,154.47 6.7 21.7
200710290500 7,501.78 7.9 21.7
200710290600 7,698.12 9.5 21.7
== r055 ===============================================================
== log pin info
== Mon Oct 29 06:03:11 EDT 2007
=======================================================================
==> 200710280700
(48) Session 1087462: Type=Node, Id=ELPI
==> 200710280800
(43) Session 1094510: Type=Node, Id=ELPI
==> 200710280900
(50) Session 1097039: Type=Node, Id=ELPI
==> 200710281000
(59) Session 1098595: Type=Node, Id=ELPI
==> 200710281100
(59) Session 1098595: Type=Node, Id=ELPI
==> 200710281200
(59) Session 1098595: Type=Node, Id=ELPI
==> 200710281300
==> 200710281400
==> 200710281500
==> 200710281600
==> 200710281700
(51) Session 1110558: Type=Node, Id=PROD-EL-GENG
==> 200710281800
(51) Session 1110558: Type=Node, Id=PROD-EL-GENG
==> 200710281900
The recovery log is pinned by a data base backup that is currently running.
==> 200710282000
(74) Session 1115248: Type=Node, Id=PROD-SAM-DATAF
==> 200710282100
(74) Session 1115248: Type=Node, Id=PROD-SAM-DATAF
==> 200710282200
(167) Session 1116083: Type=Node, Id=PROD-BAY-PI
==> 200710282300
(167) Session 1116083: Type=Node, Id=PROD-BAY-PI
==> 200710290000
(165) Session 1116076: Type=Node, Id=PROD-BAY-GENG
==> 200710290100
(165) Session 1116076: Type=Node, Id=PROD-BAY-GENG
==> 200710290200
(171) Session 1116082: Type=Node, Id=PROD-BAY-DFTS
==> 200710290300
(284) Session 1129677: Type=Node, Id=MAT_OPX
==> 200710290400
(285) Session 1129682: Type=Node, Id=SENECA-PI
==> 200710290500
(82) Session 1130496: Type=Node, Id=ELPI
==> 200710290600
(82) Session 1130496: Type=Node, Id=ELPI
-----------------------------------------
The information contained in this message is intended only for the
personal and confidential use of the recipient(s) named above. If
the reader of this message is not the intended recipient or an
agent responsible for delivering it to the intended recipient, you
are hereby notified that you have received this document in error
and that any review, dissemination, distribution, or copying of
this message is strictly prohibited. If you have received this
communication in error, please notify us immediately, and delete
the original message.
|
