Circular log buffer requested the records stored in log order to cycle the
main log file is written.Once the main log file is filled, and is still marked
as "unavailable", DB2 database manager will allocate secondary log files,
and will record write them.Allowed the total number of secondary log files
logsecond by the database configuration file parameters control.
Owned building in the log file, and circular logging is similar to store log
records in the log buffer is written to the main pre-assigned log
file.However, the difference is that with circular logging, the log files will
never be reused.Every time the main log file is filled, when the log file will
be another major distribution, so the log file to use the main number
(specified by the database configuration parameter logprimary) will always
be obtained.As long as there is disk space, this process will continue.
Top of Form
Sa jezika:
engleski
▼
Na jezik:
hrvatski
▼
Prevedi
Bottom of Form
Prijevod (engleski > hrvatski)
Kada se baza podataka prvi je stvoren, postoje tri log datoteke, log
datoteke, poznat uglavnom kao dio procesa stvaranja je allocated.In Linux i
Unix platformi, ukupno 1.000 ovih log datotekama 4KB veličina stranice,
Windows platformi, te log datoteke, ukupno 250 stranica veličine
4KB.However, glavni log datoteke se koriste broja, sa svakim moći smjestiti
količinu podataka, su baze podataka konfiguracijsku datoteku parametara
kontrole logprimary i logfilsiz.All glavni log datoteku napravljenu uz
korištenje zapisnika za strategiju baze izbor decisions.There su dvije
različite strategije mogu se koristiti, jedna je kružna prijavom, datoteka u
vlasništvu graditi log.However, aktivnosti trupaca, poznat kao beskonačni
mješavina pristup možda neće raditi najbolje.
of a transaction, even though you can keep allocating as many log files as
your storage can
hold. If a transaction exhausts the sum of the log files represented in the
two parameters,
DB2 halts the transaction. This can even happen at a lower point if either
the MAX_LOG or
There are times when it’s nice not to worry about the minutiae of how
much logging is
you’re blessed with abundant storage, and an efficient régime for log
archival and retrieval,
you might want to tell DB2 to use only as many log files as required to
keep your transactions
activate USEREXIT and archive logging if it was not already set in your
database. With infinite
logging in place, DB2 uses the primary log files in a typical fashion; if any
transaction requires
more space, DB2 continues to allocate secondary log files until the unit of
work commits or
storage is exhausted.
■Caution It is tempting to think you should just set infinite logging to free
yourself of another housekeep-
ing task. I offer a word of warning here to dent your potential enthusiasm
a little. With infinite logging
enabled I’ve seen log storage blow out to consume all available space
dozens of times. In almost every case,
the culprit wasn’t a large bona fide transaction; instead, it was due to
developer error, typing errors in writing
It might sound like a good idea, but remember the old Chinese proverb,
“Be careful what you wish for—it
To complete the logging foundation for later use in backups and recovery,
there are two more
details worth knowing. In all the discussions about logging, you’ll have
noticed that logs are
written to disk when the Log Buffer is flushed. And you’re probably aware
that disks are the
DB2 provides a method to mirror your log files, so DB2 writes identical log
file informa-
protecting against disk failure, your path for mirrored log files should point
to a completely
separate disk drive. Be especially careful if your environment uses RAID or
some form of stor-
age array, in which different logical volumes used under your file systems
might actually
Sometimes it’s important to make sure that information possibly still being
tracked in an
active log file (one that hasn’t been filled and archived) is securely closed
off and processed
upgrade or as part of some quality assurance task. You can manually force
DB2 to archive a
This command forces the Log Buffers to flush and it also forces existing
transactions to
switch over to a new log file, thus freeing the current log files on disk for
archiving.
DB2 Backups
It’s time! Time to back up your database. You created it, added objects,
changed data, tweaked
Enough talk. It’s time for action. Run to your command line (don’t walk!)
and type the follow-
ing commands:
Authorization ID = DB2INST1
Local instance alias = DB2INST1