DB00321I - LOG LXX WRAP, DURATION ++:++:++ LEAST ++:++:++

Products

• Datacom
• Datacom/AD
• Datacom/DB

Issue/Introduction

We ran across the above message multiple times in our MUF log.  We looked up the message but were unable to understand it completely and why it happened.

Resolution

The DB00321I message occurs each time the log area LXX wraps from its physical end to its physical start. This wrapping was always occurring but now we tell you when it happens. It is just informational and does not necessarily mean the LXX needs to be resized. However, the information in the message can help you to decide if it does need to be resized.

Here is a complete explanation of DB00321I message:

First, the way that the LXX (Log file) works is that it is a wraparound file. As logging records are written they will fill the lowest available block and continue until the physical end of the file is reached. At that point, writing will continue back at the beginning of the physical file (block #1), and will continue on. This action from writing the last block and then writing the first block is called a wrap.

Next, when you run a SPILL job, it will start at the lowest available block following the previous spill, and it will move all blocks of committed transactions from the LXX to the RXX (Recovery file). It will then make these blocks available for future use.

What this DB00321 message indicates is that at the time of the message, the LXX writing wrapped around to block #1. The DURATION of ++... means that it has been more than 100 hours (over 4 days) since the last wrap occurred, and the LEAST value of ++... means that the shortest time for the LXX to wrap since it was initialized or extended was more than 100 hours also.