When changing the logging method to circular logging from
archive logging, old log files on the primary logpath are
cleaned up before allocating new log files(S0000000.LOG -).
However, the old log files on the mirror logpath are removed
after new log files are allocated. It may cause the disk full
problem when the filesystem for the mirror logpath does not have
enough space to store twice the size of logprimary.
For example:
logfilsiz=2560 (10MB)
logprimary=30
- before changing logarchmeth1
logpath:
SQLLPATH.TAG
S0000100.LOG
S0000101.LOG
...
S0000129.LOG
mirrorlogpath:
SQLLPATH.TAG
S0000100.LOG
S0000101.LOG
...
S0000129.LOG
- changed to circular logging. during activation, all logs in
the primary logpath are deleted
logpath:
SQLLPATH.TAG
mirrorlogpath:
SQLLPATH.TAG
S0000100.LOG
S0000101.LOG
...
S0000129.LOG
- then new logs are being allocated ( S0000000 in primary,
S0000000 in mirror, S0000001 in primary, ...)
logpath:
SQLLPATH.TAG
S0000000.LOG
mirrorlogpath:
SQLLPATH.TAG
S0000000.LOG
S0000100.LOG
S0000101.LOG
...
S0000129.LOG
- all new logs are allocated. At this time, 60 logs temporarily
exist in mirror logpath
logpath:
SQLLPATH.TAG
S0000000.LOG
...
S0000029.LOG
mirrorlogpath:
SQLLPATH.TAG
S0000000.LOG
...
S0000029.LOG
S0000100.LOG
S0000101.LOG
...
S0000129.LOG
- then S0000000 - 29.LOG are removed from mirror logpath
logpath:
SQLLPATH.TAG
S0000000.LOG
...
S0000029.LOG
mirrorlogpath:
SQLLPATH.TAG
S0000000.LOG
...
S0000029.LOG
After the database activation is complete, the number of logs in
both paths are the same. However, if the filesystem size for
mirror logpath is less than 600MB in this example, "DIA8312C
Disk was full" occurs during db activation. |
