By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
440,440 Members | 1,872 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 440,440 IT Pros & Developers. It's quick & easy.

Archive logs?

P: n/a
Hi,

we have an application which uses online backups, so archive logging
is a requirement. We have a small/moderate size database (a few
hundred megabytes isn't much by today's standards) with relatively low
insert/update activity (a few thousand per day).

How should I set up archive logging (number of primary and secondary
logs files, size of each log file)?

Also, we set log archiving to manual. What log files are safe to
archive? Currently we create an online backup every day at 2:00 AM
(the backup includes log files), keep the last 10 such backups, and
delete all log files older than the oldest backup.

The backup command is
BACKUP DB mydata TO d:\db2_backup COMPRESS UTIL_IMPACT_PRIORITY 1
INCLUDE LOGS

Logging is set up as
UPDATE DB CFG FOR mydata USING logarchmeth1 LOGRETAIN logprimary 16
logsecond 240 logfilsiz 4096 newlogpath d:\db2_logs

It is my understanding that this sets up 16 files, 16 MB each, for a
total of 256 MB, with the possibility to go up to a total of 256
files, or 4 GB, but only if needed (the application is installed at
multiple remote servers whom we cannot access every day, so I thought
this would be on the safe side). In 10 days, the logs files use up
about 20 GB. What do you recommend to keep the size lower? Is it safe
to remove all log files older than the youngest backup? Should I
change logfilesiz or logprimary/logsecond?

TIA,
Kofa
Jun 27 '08 #1
Share this Question
Share on Google+
3 Replies


P: n/a
"Kofa" <ko*******@gmail.comwrote in message
news:40**********************************@b64g2000 hsa.googlegroups.com...
Hi,

we have an application which uses online backups, so archive logging
is a requirement. We have a small/moderate size database (a few
hundred megabytes isn't much by today's standards) with relatively low
insert/update activity (a few thousand per day).

How should I set up archive logging (number of primary and secondary
logs files, size of each log file)?

Also, we set log archiving to manual. What log files are safe to
archive? Currently we create an online backup every day at 2:00 AM
(the backup includes log files), keep the last 10 such backups, and
delete all log files older than the oldest backup.

The backup command is
BACKUP DB mydata TO d:\db2_backup COMPRESS UTIL_IMPACT_PRIORITY 1
INCLUDE LOGS

Logging is set up as
UPDATE DB CFG FOR mydata USING logarchmeth1 LOGRETAIN logprimary 16
logsecond 240 logfilsiz 4096 newlogpath d:\db2_logs

It is my understanding that this sets up 16 files, 16 MB each, for a
total of 256 MB, with the possibility to go up to a total of 256
files, or 4 GB, but only if needed (the application is installed at
multiple remote servers whom we cannot access every day, so I thought
this would be on the safe side). In 10 days, the logs files use up
about 20 GB. What do you recommend to keep the size lower? Is it safe
to remove all log files older than the youngest backup? Should I
change logfilesiz or logprimary/logsecond?

TIA,
Kofa
I would recommend that you use LOGARCHMETH1 for log archiving.
Jun 27 '08 #2

P: n/a
On máj. 11, 04:31, "Mark A" <nob...@nowhere.comwrote:
I would recommend that you use LOGARCHMETH1 for log archiving.
Could you please elaborate on that?
According to the docs, an archived log file may be renamed and reused.
Should I use a LOGARCHMETH1 like
DISK:some-path? Would that result in unused (not active) logs files
being copied to some-path, and then reused? Or could I supply a user
exit that 'archives' log files by deleting them?

TIA,
Kofa
Jun 27 '08 #3

P: n/a
"Kofa" <ko*******@gmail.comwrote in message
Could you please elaborate on that?
According to the docs, an archived log file may be renamed and reused.
Should I use a LOGARCHMETH1 like
DISK:some-path? Would that result in unused (not active) logs files
being copied to some-path, and then reused? Or could I supply a user
exit that 'archives' log files by deleting them?
The syntax you would probably want to use is DISK:/path... The archive logs
will automatically be copied from the active log path to that path specified
in the LOGARCHMETH1 parm. You do not need any exit program if you use this
parm.

It is always possible that an archived log file might need to be used. For
example if you needed to restore from a backup and roll forward the logs.

You will need to manually purge the archive logs (unless you have Version
9.5) via a cron script (an exit program is not needed). You will want to
keep the archive logs at least until before the last backup (so you can roll
the logs forward from the backup time to the current time or end of logs),
and maybe longer if you need to ever restore the next-to-last backup and
then roll forward.
Jun 27 '08 #4

This discussion thread is closed

Replies have been disabled for this discussion.