Each logical-log on a co-server, whether backed up to media or not, has a log unique ID. The sequence begins with 1 for the first logical-log filled after you initialize the database server disk space. When the current logical-log file becomes full, the database server switches to the next logical-log file and increments the unique ID number for the new log by one.
The actual disk space allocated for each logical-log file has an identification number known as the lognum. For example, if you configure six logical-log files, these files have log file numbers one through six. As logical-logs are backed up and freed, the database server reuses the disk space for the logical-log files. However, the database server continues to increment the unique IDs of the logs contained in those files by one. Table 25 illustrates the relationship between the log file numbers and the log unique IDs.
| Log File Number | First Rotation Unique ID | Second Rotation Unique ID | Third Rotation Unique ID | Fourth Rotation Unique ID |
|---|---|---|---|---|
| 1 | 1 | 7 | 13 | 19 |
| 2 | 2 | 8 | 14 | 20 |
| 3 | 3 | 9 | 15 | 21 |
| 4 | 4 | 10 | 16 | 22 |
| 5 | 5 | 11 | 17 | 23 |
| 6 | 6 | 12 | 18 | 24 |
For information on how to display the unique ID and logid numbers of a logical-log file, refer to Monitoring the Logical Log for Fullness.
Home | [ Top of Page | Previous Page | Next Page | Contents | Index ]