Utility manager log records
The utility manager produces log records associated with the following Db2® utilities: database upgrade; load; backup; table space rollforward.
The log records signify the beginning or the end of the requested activity. Only propagatable log records for these utilities are documented.
System catalog migration begin log record
During database upgrade, the system catalog objects are converted to the new release format. This log record indicates the start of system catalog migration.
| Description | Type | Offset (Bytes) |
|---|---|---|
| Log header | LogManagerLogRecordHeader | 0 (40) |
| Start time | char[ ] | 40 (10) |
| Previous release | unsigned short | 50 (2) |
| New release | unsigned short | 52 (2) |
| Total Length: 54 bytes | ||
System catalog migration end log record
During database upgrade, the system catalog objects are converted to the new release format. This log record indicates the successful completion of system catalog migration.
| Description | Type | Offset (Bytes) |
|---|---|---|
| Log header | LogManagerLogRecordHeader | 0 (40) |
| End time | char[ ] | 40 (10) |
| New release | unsigned short | 50 (2) |
| Total Length: 52 bytes | ||
Load start log record
This log record is associated with the beginning of a load.
It is the only Load log record that is propagatable.
For the purpose of log record propagation, it is recommended that after reading a Log Start log record you not continue to propagate log records for the specific table to a target table. After a Load Start log record, all propagatable log records that belong to the table being loaded can be ignored regardless of the transaction boundary, until such a time that a cold restart has taken place. A cold restart is required to synchronize the source and target tables.
| Description | Type | Offset (Bytes) |
|---|---|---|
| Log header | LogManagerLogRecordHeader | 0 (40) |
| Log record identifier | sqluint32 | 40 (4) |
| Pool identifier | unsigned short | 44 (2) |
| Object identifier | unsigned short | 46 (2) |
| Flag | sqluint32 | 48 (4) |
| Object pool list | variable | 52 (variable) |
| Total length: 52 bytes plus variable | ||
Backup end log record
This log record is associated with the end of a successful backup.
| Description | Type | Offset (Bytes) |
|---|---|---|
| Log header | LogManagerLogRecordHeader | 0 (40) |
| Backup end time | sqluint64 | 40 (8) |
| Total Length: 48 bytes | ||
Table space rolled forward log record
This log record is associated with table space ROLLFORWARD recovery. It is written for each table space that is successfully rolled forward.
| Description | Type | Offset (Bytes) |
|---|---|---|
| Log header | LogManagerLogRecordHeader | 0 (40) |
| Table space identifier | sqluint32 | 40 (4) |
| Total length: 44 bytes | ||
Table space roll forward to point in time starts log record
This log record is associated with table space ROLLFORWARD recovery. It marks the beginning of a table space roll forward to a point in time.
| Description | Type | Offset (Bytes) |
|---|---|---|
| Log header | LogManagerLogRecordHeader | 0 (40) |
| Time stamp for this log record | sqluint64 | 40 (8) |
| Time stamp to which table spaces are being rolled forward | sqluint32 | 48 (4) |
| Number of pools being rolled forward | sqluint32 | 52 (4) |
| Total length: 56 bytes | ||
Table space roll forward to point in time ends log record
This log record is associated with table space ROLLFORWARD recovery. It marks the end of a table space roll forward to a point in time.
| Description | Type | Offset (Bytes) |
|---|---|---|
| Log header | LogManagerLogRecordHeader | 0 (40) |
| Time stamp for this log record | sqluint64 | 40 (8) |
| Time stamp to which table spaces were rolled forward | sqluint32 | 48 (4) |
A flag whose value is TRUE if the roll forward
was successful, or FALSE if the roll forward was
cancelled. |
sqluint32 | 52 (4) |
| Total length: 56 bytes | ||
Two timestamp fields are required to provide adequate precision so that event log event timing can be differentiated. The first timestamp uses 8 bytes to indicate the time when the log was written to a precision of seconds. The first 4 bytes of this timestamp indicate the seconds portion. Since many actions can take place in one second, to understand the ordering of events it is necessary to have further precision. The second timestamp field provides 4 bytes that are used as a counter to indicate the ordering of the log records that occur within the same second. If the log record timestamps of two log records are identical, the additional 4 byte timestamp counter field can be used to determine the ordering of the associated log events.
Database migration begin log record
During database upgrade, the database objects are converted to the new release format. This log record indicates the start of database migration.
| Description | Type | Offset (Bytes) |
|---|---|---|
| Log header | LogManagerLogRecordHeader | 0 (40) |
| Timestamp | sqluint64 | 40 (8) |
| Internal | Internal | 48 (128) |
| Previous release | unsigned short | 176 (2) |
| New release | unsigned short | 178 (2) |
| Migration flags | unsigned short | 180 (2) |
| Reserved | char[ ] | 182 (50) |
| Total length: 232 bytes | ||
Database migration end log record
During database upgrade, the database objects are converted to the new release format. This log record indicates the successful completion of database migration.
| Description | Type | Offset (Bytes) |
|---|---|---|
| Log header | LogManagerLogRecordHeader | 0 (40) |
| Timestamp | sqluint64 | 40 (8) |
| New release | unsigned short | 48 (2) |
| Reserved | char[ ] | 50 (22) |
| Total length: 72 bytes | ||