DB2 8.2 New log file management, FixPak 10

[Former Member]

Hello, we changed to the new log file management. When we lose our TSM connection the logfiles still stay in the log_dir. There is no move to the failarchpath. Normally the database should try to move the logfiles to the failarchpath, aber five times trying (parameter NUMARCHRETRY=5) to move the files to TSM (LOGARCHMETH1=TSM:SAP). Any explanation for that?

Thanks

Alexander Türk

(LOGARCHMETH1) = TSM:SAP

(LOGARCHOPT1) =

(LOGARCHMETH2) = OFF

(LOGARCHOPT2) =

FAILARCHPATH) = /db2/T03/log_archive/

NUMARCHRETRY) = 5

(ARCHRETRYDELAY) = 20

[Former Member]

Hi Alexander,

have you checked the permissions on the path referenced by FAILARCHPATH ? (can you touch a file as db2/NODExxxx/ ?

Does the db2diag.log tell anything ?

... just questions, but I hope they help to identify the problem.

Hans-Jürgen

[Former Member]

Hello Hans-Juergen,

it was my own fault. The logfiles where under /db2/sid/log_archive/db2<sid>/<sid>/NODE0000/C0000001 which was mountet on a different logical volume. I was only looking in /db2/sid/log_archive and wondering why no logs appeared.

Thanks for the help.

Alexander