DB2 and TDP/R3 log archive time mismatch

[Former Member]

Hello.

Im my databases im inspect strange situation with log archive time logging in DB2 history file and TDP backom utility log.

Log's are archived to TSM disk pool

In DB2 history for archiving log file S0001437.LOG are presented :

Op Obj Timestamp+Sequence Type Dev Earliest Log Current Log Backup ID

X D 20080602060857 1 O S0001437.LOG C0000000

Comment: /db2/NBP/tdp_r3/vendor.env

Start Time: 20080602060857

End Time: 20080602114031

Status: A

EID: 1799 Location: /usr/tivoli/tsm/tdp_r3/db264/libtdpdb264.a

In backom log file for this operation are presented :

BKI8800I: The command is: ARCHIVE

BKI8801I: Time: 2008-06-02-11.39.48.0549 --- PID: 499748

BKI8807I: Archive log file 'S0001437.LOG' of chain 'C0000000'.

BKI8803I: The DB2 UDB image size for this session is about '63.992 MB'.

BKI2017I: Blocksize is set to 131072 bytes

BKI5016I: Time: 06/02/08 11:39:52 New TSM session created: MGMNT-CLASS: MGCAR_COM1, TSM-Server: INFRA_ODD, type: SIMPLE

BKI5016I: Time: 06/02/08 11:39:53 New TSM session created: MGMNT-CLASS: MGCAR_COM2, TSM-Server: INFRA_ODD, type: SIMPLE

BKI0057I: Time: 06/02/08 11:40:29 Object: /:db2nbp.NBP.NODE0000.20080602113948.C0000000_S0001437.LOG with: 63.992 MB saved with description NBP___A0FGYR4I5D_INFRA_ODD@MGCAR_COM2#525538 2.COPY 00243.

BKI0057I: Time: 06/02/08 11:40:29 Object: /:db2nbp.NBP.NODE0000.20080602113948.C0000000_S0001437.LOG with: 63.992 MB saved with description NBP___A0FGYR4I5D_INFRA_ODD@MGCAR_COM1#525537 1.COPY 00243.

So. DB2 think what log file archiving taken approximately 5 hours and 32 minutes !!??

But backom think what this taken approximately 40 sec

Why it so diference ? And who are rigth DB2 or backom ?

Big thank's

With best regards, Dmitry

[Former Member]

Hi, Edgardo

Thank you for your help .

[Former Member]

Hi Dmitry,

The document "IBM DB2 Universal Database for UNIX and Windows: New Log File Management" (page 18) provides the following description for the fields in an archive log entry in the history file:

*TimestampSequence*+

A 14-digit timestamp that indicates the log file creation time during normal operation. The sequence number is not used. If the log file entry was created during rollforward, the field contains the time when the log file was applied.

Starttime

Same as Timestamp-Sequence

Endtime

14-digit timestamp that indicates when log file was archived.

Therefore, the Starttime field does not imply, that the log archive operation would have started 5 hours and 32 minutes before the Endtime. The Starttime, being the same as the Timestamp+Sequence, represents the time when the log was created by DB2.

It may be possible, that there was not much activity at that time and therefore, the log was archived 5 hours later, when it was full for example. This would be also the reason why you do not find any error messages in the db2diag.log regarding a failed log archive.

You can download the document "IBM DB2 Universal Database for UNIX and Windows: New Log File Management" from the following link:

[New Log File Management|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/280b4546-0a01-0010-7d8c-82abb2296e1c]

Best regards, Edgardo

Edited by: Edgardo Koenig on Jun 5, 2008 12:25 PM

Edited by: Edgardo Koenig on Jun 5, 2008 12:26 PM

[Former Member]

Hi, Anil

Thank's for your answer.

I recheck db2diag.log for this period and can't expect any errors/warnings for log archiving or other.

May be this is normal db2 log files archiving behavior for non heavily databases when log file is open for archiving and wait over last commitment for log file full up?

[Former Member]

Dmitry - Both DB2 and backom are correct and I will try my best to explain.

DB2 marked log1437 for archival to TSM at 06:08 hrs, but db2 process was not able to send that log file successfully to TSM due to backom process was not able to establish TSM session until 11.39.48.0549 with PID: 499748. After session established, it took only 40 sec to send log file to TSM.

I think if you check db2diag.log file for errors during that 5 hr 32 mins time frame, you should see error saying log 1437 failed to archive.

Hope this information helps.

-AL

[Former Member]

Dmitry:

Would you please confirm that you see "log 1437 failed to archive" (or similar) in db2diag.log?

Thanks!