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

Archive Logging

P: n/a
Hi,

A few points to confirm as I am still new with DB2.

1. What will happen if archive logging is used, however there is no
userexit or manual process to move those online archived logs to
another directory. At this moment my LOGPRIMARY is set to 3. Will the
logging hang?

2. Does LOGSECOND apply to circular logging only? If if use archive
logging, will the LOGSECOND be used when my LOGPRIMARY are filled up
for a long running transactions?

3. When you specify the NEWLOGPATH, will both the active logs and
archive logs be moved over to the new directory?

4. What happen when the entire mirror logs directory are down? How
will DB2 write to logs? Will it just ignore the missing directory?

Thanks
DB2 Convert
Nov 12 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
Ian
DB2 Convert wrote:
Hi,

A few points to confirm as I am still new with DB2.

1. What will happen if archive logging is used, however there is no
userexit or manual process to move those online archived logs to
another directory. At this moment my LOGPRIMARY is set to 3. Will the
logging hang?
The online archive logs will remain in the active log path, until you
fill up the filesystem holding the log files.

How DB2 handles a disk full situation for the logpath is controlled by
the BLK_LOG_DSK_FUL database configuration parameter.
2. Does LOGSECOND apply to circular logging only? If if use archive
logging, will the LOGSECOND be used when my LOGPRIMARY are filled up
for a long running transactions?
LOGSECOND is valid for both circular and archive logging. And yes, it
controls the maximum size of all uncommitted (or long-running)
transactions. V8 added support for "infinite" active logs (logsecond
= -1).
3. When you specify the NEWLOGPATH, will both the active logs and
archive logs be moved over to the new directory?
This parameter is not effective until the database is deactivated (which
closes all active log files). When the database is activated again,
new log files will be created in the new log path -- archive logs will
be left in the old location.
4. What happen when the entire mirror logs directory are down? How
will DB2 write to logs? Will it just ignore the missing directory?


I would imagine the same thing that happens if the primary log path
is down -- DB2 continues to function normally, but registers errors.

-----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----
http://www.newsfeeds.com - The #1 Newsgroup Service in the World!
-----== Over 100,000 Newsgroups - 19 Different Servers! =-----
Nov 12 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.