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

Confused about the archive parameters

P: n/a
I am a little confused about the archive parameters work together. We
currently have LOGRETAIN=RECOVERY and LOGARCHMETH1=USEREXIT.

It appears that the logarchmeth1 can be set to DISK:<path>. Does this
mean that we can use DISK (rather than USEREXIT) and replace the <path>
to our existing archive log path, set USEREXIT OFF and db2 will
automatically copy files to this directory?

Thanks for any help.

Naru Mangalath

Sep 26 '06 #1
Share this Question
Share on Google+
1 Reply


P: n/a
<sa*******@gmail.comwrote in message
news:11**********************@h48g2000cwc.googlegr oups.com...
>I am a little confused about the archive parameters work together. We
currently have LOGRETAIN=RECOVERY and LOGARCHMETH1=USEREXIT.

It appears that the logarchmeth1 can be set to DISK:<path>. Does this
mean that we can use DISK (rather than USEREXIT) and replace the <path>
to our existing archive log path, set USEREXIT OFF and db2 will
automatically copy files to this directory?

Thanks for any help.

Naru Mangalath
If you set either LOGRETAIN, USEREXIT, or LOGARCHMETH1 to a value other than
the default, then DB2 will retain the logs (not use circular logging).

Starting in 8.2, you can use LOGARCHMETH1 to specify the location of where
archived logs are to be moved, instead of having to compile and use a
USEREXIT program. You just specify DISK:\archive_log_path if you want the
archived logs to go to that path. You can use LOGARCHMETH2 if you are using
mirrored logs and want mirror archive logs.
Sep 26 '06 #2

This discussion thread is closed

Replies have been disabled for this discussion.