Dear folks,

My company got a time critical DB2 system which got some complaints on
SQL delay recently. After investigation, it is found that the delay
probably caused by log switching (i.e the timestamps match for the
delays happened). However, the db2diag.log shows the log switch took
only a few ms to complete... It is believed that delay caused by new
log creation before the switching (i.e. the delay time did improve
when we reduced the log size to 100M though our customer is still
experiencing delay up to 10s occasionally). Though we think change the
disks may help, however, this could not be happened in a short
time....So, I need to look for some tunings in DB2 first. I am facing
the questions below and please shed some light on them for me if
possible.

How could I measure the new log creation time in DB2?
Would it be possible to create new logs before the DB2 need them?
Any other DB2 tunings could help on the situation?

Thanks in advance!

Henry

On 11.09.11 3:50 , Guest wrote:
In fact old log files are reused, so no logfiles are actually allocated. That
is for primary log files. Only, if your primary log files are exhausted and
secondaries are created, DB2 will allocate them one at the time.
Otherwise DB2 will rename the oldest log file and start using it right away.

I will be on vacation for the next two weeks, so I probably won't read email,
newsgroups or do anything else which is computer related...

Will be back in 2 weeks. :-)

--
Helmut K. C. Tessarek
DB2 Performance and Development
IBM Toronto Lab