logging - DB2 - Archive mode - number of ARCHIVE logs larger than LOGPRIMARY -


Perhaps someone has a question about this psalmist; I read and set up a lot of documents:

LOGSECOND 4 LOGSECOND 4 LOGSECAND 4,096 logarchmeth1 disk - C: \ archive logpath C: \ active

Number of logs in C: \ active 6 is fine. But the current number of logs in C: \ archive is 40. How is this possible? I think the maximum primary log in C: \ archive would be 6 and then 4 LOGSECOND (if it is necessary, they are not already assigned).

The permitted log location is infringed but new logs are created continuously in C: \ archive. How is that possible? If someone can tell me this then I would be grateful. In this way I do not know how to complete the transaction log (if I'm coming out of the total disk space) Because the new log is created in C.

I'm starting up so please be sorry. Simple question. I did not find any answer on the internet. Logarchmeth1 is the destination for the archive log, I set them to the primary 6, then do I have 40 logs? Thank you

When you enable archive logging in a database, you are saying DB2 that you Want a copy of the transaction log processed all LOGPRIMARY and LOGSECOND can control how many active log files are used only in the active log path at any time.

Please read the documentation for more information.


Comments

Popular posts from this blog

ios - How do I use CFArrayRef in Swift? -

eclipse plugin - Run java code error: Workspace is closed -

c - Error on building source code in VC 6 -