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

<saramathi@gmail.com> wrote in message
news:1159253161.489229.169010@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.