Peter,
You are right, active log is copied to archlog, but after that the
actlog is "in scratch status", that mean it can be reused.
It is very similar to SMF SYS1.MANx datasets.
And yes, after succesful copy actlog -> archlog the data will be
searched in archlog. Actlog is logically empty (until reuse).
Regarding buffers I think you ar wrong. Buffers are heavily used for
tables, but not for log. Due to transaction integrity active log is
immediately written to DASD.
--
Radoslaw Skorupka
Lodz, Poland
W dniu 2016-02-10 o 13:17, Peter Hunkeler pisze:
I understand there is a DB2 forum somewhere (IDUG?), but I'd rather not
subscribe for this single question someone might be able to answer here.
I understand DB2 keeps its log data first in buffers, then writes it to one of
a set of active log data set. Finally the data will be written to archive data
sets when active log data sets fill up. The active data sets are used round
robin.
I found a sentence in a DB2 manual stating that the data is being copied from
the active to the archive data set.
I'm guessing that "copy" means the physical part not the logical view of where the data
is. That would be "move". It is not clear whether the data in the active data set would
still be used by DB2 after it has been copied to the archive data set.
I doubt DB2 will physically delete the data from the active data set after
writing it to an archive data set. The question is, does DB2 remember that the
data is still also available in the active data set, as long as it has not
started reusing it? I think not. A block of log data will only ever be in one
place, buffer, active *or* archive data set.
Some insight, anyone? Pointers to the right FM would be nice, too. May need to
be able to point someone to a FM so he can read hinself.
--
Peter Hunkeler
--
Peter Hunkeler
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
--
Tre tej wiadomoci moe zawiera informacje prawnie chronione Banku
przeznaczone wycznie do uytku subowego adresata. Odbiorc moe by jedynie
jej adresat z wyczeniem dostpu osób trzecich. Jeeli nie jeste adresatem
niniejszej wiadomoci lub pracownikiem upowanionym do jej przekazania
adresatowi, informujemy, e jej rozpowszechnianie, kopiowanie, rozprowadzanie
lub inne dziaanie o podobnym charakterze jest prawnie zabronione i moe by
karalne. Jeeli otrzymae t wiadomo omykowo, prosimy niezwocznie
zawiadomi nadawc wysyajc odpowied oraz trwale usun t wiadomo
wczajc w to wszelkie jej kopie wydrukowane lub zapisane na dysku.
This e-mail may contain legally privileged information of the Bank and is
intended solely for business use of the addressee. This e-mail may only be
received by the addressee and may not be disclosed to any third parties. If you
are not the intended addressee of this e-mail or the employee authorized to
forward it to the addressee, be advised that any dissemination, copying,
distribution or any other similar activity is legally prohibited and may be
punishable. If you received this e-mail by mistake please advise the sender
immediately by using the reply facility in your e-mail software and delete
permanently this e-mail including any copies of it either printed or saved to
hard drive.
mBank S.A. z siedzib w Warszawie, ul. Senatorska 18, 00-950 Warszawa,
www.mBank.pl, e-mail: kont...@mbank.pl
Sd Rejonowy dla m. st. Warszawy XII Wydzia Gospodarczy Krajowego Rejestru
Sdowego, nr rejestru przedsibiorców KRS 0000025237, NIP: 526-021-50-88.
Wedug stanu na dzie 01.01.2016 r. kapita zakadowy mBanku S.A. (w caoci
wpacony) wynosi 168.955.696 zotych.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
