db2stop force 挂起问题求助！

zou_hope

2007-07-02-13.29.09.907281+480 I32577656A583      LEVEL: Error
PID     : 1093654              TID  : 1           PROC : db2logmgr (NCBPROD) 0
INSTANCE: db2inst1             NODE : 000
FUNCTION: DB2 UDB, data protection, sqlpCloseVendorDevice, probe:2800
MESSAGE : Vendor return code from sqlpCloseVendorDevice:
DATA #1 : Hexdump, 48 bytes
0x0FFFFFFFFFFFC758 : 0000 0029 3134 3737 2034 3100 0000 0000    ...)1477 41.....
0x0FFFFFFFFFFFC768 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
0x0FFFFFFFFFFFC778 : 0000 0000 0000 0000 0000 0000 0000 0000    ................

2007-07-02-13.29.09.907424+480 I32578240A397      LEVEL: Error
PID     : 1093654              TID  : 1           PROC : db2logmgr (NCBPROD) 0
INSTANCE: db2inst1             NODE : 000
FUNCTION: DB2 UDB, data protection, sqlpgArchiveLogVendor, probe:2870
MESSAGE : Unable to close VendorDev due to rc
DATA #1 : Hexdump, 4 bytes
0x0FFFFFFFFFFFC828 : 0000 0011                                  ....

2007-07-02-13.29.09.907556+480 I32578638A378      LEVEL: Error
PID     : 1093654              TID  : 1           PROC : db2logmgr (NCBPROD) 0
INSTANCE: db2inst1             NODE : 000
FUNCTION: DB2 UDB, data protection, sqlpgArchiveLogFile, probe:3160
MESSAGE : Failed to archive log file S0001612.LOG to TSM chain 0 from
          /ncbdblogdir/ncbprod/NODE0000/ with rc = 17.

2007-07-02-13.29.13.521769+480 I32579017A325      LEVEL: Warning
PID     : 1110048              TID  : 1           PROC : db2loggr (NCBPROD) 0
INSTANCE: db2inst1             NODE : 000
FUNCTION: DB2 UDB, data protection, sqlpgLoggrInitDelOldLog, probe:1440
MESSAGE : Cleaning up logs from RenameArchNum 1611 to delLimit 1612

2007-07-02-13.29.28.414591+480 I32579343A401      LEVEL: Error
PID     : 1093656              TID  : 1           PROC : db2logmgr (NCBPROD) 0
INSTANCE: db2inst1             NODE : 000
FUNCTION: DB2 UDB, data protection, sqlpCloseVendorDevice, probe:2800
MESSAGE : Return code from sqlpCloseVendorDevice:
DATA #1 : Hexdump, 4 bytes
0x0FFFFFFFFFFFC610 : 0000 0011                                  ....

2007-07-02-13.29.28.415295+480 I32579745A583      LEVEL: Error
PID     : 1093656              TID  : 1           PROC : db2logmgr (NCBPROD) 0
INSTANCE: db2inst1             NODE : 000
FUNCTION: DB2 UDB, data protection, sqlpCloseVendorDevice, probe:2800
MESSAGE : Vendor return code from sqlpCloseVendorDevice:
DATA #1 : Hexdump, 48 bytes
0x0FFFFFFFFFFFC618 : 0000 0029 3134 3737 2034 3100 0000 0000    ...)1477 41.....
0x0FFFFFFFFFFFC628 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
0x0FFFFFFFFFFFC638 : 0000 0000 0000 0000 0000 0000 0000 0000    ................

2007-07-02-13.29.28.415459+480 I32580329A397      LEVEL: Error
PID     : 1093656              TID  : 1           PROC : db2logmgr (NCBPROD) 0
INSTANCE: db2inst1             NODE : 000
FUNCTION: DB2 UDB, data protection, sqlpgArchiveLogVendor, probe:2870
MESSAGE : Unable to close VendorDev due to rc
DATA #1 : Hexdump, 4 bytes
0x0FFFFFFFFFFFC6E8 : 0000 0011                                  ....

2007-07-02-13.29.28.415592+480 I32580727A378      LEVEL: Error
PID     : 1093656              TID  : 1           PROC : db2logmgr (NCBPROD) 0
INSTANCE: db2inst1             NODE : 000
FUNCTION: DB2 UDB, data protection, sqlpgArchiveLogFile, probe:3160
MESSAGE : Failed to archive log file S0001612.LOG to TSM chain 0 from
          /ncbdblogdir/ncbprod/NODE0000/ with rc = 17.

2007-07-02-13.29.28.415756+480 I32581106A314      LEVEL: Error
PID     : 1093656              TID  : 1           PROC : db2logmgr (NCBPROD) 0
INSTANCE: db2inst1             NODE : 000
FUNCTION: DB2 UDB, data protection, sqlpgArchivePendingLogs, probe:1500
MESSAGE : Log archive failed with rc 17 for LOGARCHMETH1.

2007-07-02-13.29.34.724578+480 I32581421A392      LEVEL: Warning
PID     : 811148               TID  : 1           PROC : db2logmgr (ABSTEST) 0
INSTANCE: db2inst1             NODE : 000
FUNCTION: DB2 UDB, data protection, sqlpgArchiveLogFile, probe:3180
MESSAGE : Successfully archived log file S0000292.LOG to TSM chain 0 from
          /home/db2inst1/db2inst1/NODE0000/SQL00001/SQLOGDIR/.

2007-07-02-13.29.34.853295+480 I32581814A368      LEVEL: Error
PID     : 811148               TID  : 1           PROC : db2logmgr (ABSTEST) 0
INSTANCE: db2inst1             NODE : 000
FUNCTION: DB2 UDB, data protection, sqlpgArchiveLogVendor, probe:1630
RETCODE : ZRC=0x860F000A=-2045837302=SQLO_FNEX "File not found."
          DIA8411C A file "" could not be found.

2007-07-02-13.29.34.853708+480 I32582183A428      LEVEL: Error
PID     : 811148               TID  : 1           PROC : db2logmgr (ABSTEST) 0
INSTANCE: db2inst1             NODE : 000
FUNCTION: DB2 UDB, data protection, sqlpgArchiveLogFile, probe:3160
MESSAGE : Failed to archive log file S0000286.LOG to TSM chain 0 from
          /home/db2inst1/arclogdir/db2inst1/ABSTEST/NODE0000/C0000000/ with rc
          = -2045837302.

2007-07-02-13.29.34.853888+480 I32582612A390      LEVEL: Warning
PID     : 811148               TID  : 1           PROC : db2logmgr (ABSTEST) 0
INSTANCE: db2inst1             NODE : 000
FUNCTION: DB2 UDB, data protection, sqlpgCleanFailArchPath, probe:4930
MESSAGE : Unable to find log file 286 for LOGARCHMETH1 using method 2 and
          target .  Assume log was archived and continue.

2007-07-02-13.29.36.780372+480 I32583003A383      LEVEL: Error
PID     : 811148               TID  : 1387        PROC : db2logmgr (ABSTEST) 0
INSTANCE: db2inst1             NODE : 000
FUNCTION: DB2 UDB, database utilities, sqluvintCall, probe:10
MESSAGE : Signal encountered in sqluvint
DATA #1 : Hexdump, 4 bytes
0x0FFFFFFFFFFFC540 : 800F 00AF                                  ....

2007-07-02-13.29.36.780976+480 I32583387A560      LEVEL: Error
PID     : 811148               TID  : 1387        PROC : db2logmgr (ABSTEST) 0
INSTANCE: db2inst1             NODE : 000
FUNCTION: DB2 UDB, data protection, sqlpInitVendorDevice, probe:1030
MESSAGE : Init failed!  Vendor rc:
DATA #1 : Hexdump, 48 bytes
0x0FFFFFFFFFFFC600 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
0x0FFFFFFFFFFFC610 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
0x0FFFFFFFFFFFC620 : 0000 0000 1880 0000 0000 0000 0000 0000    ................

2007-07-02-13.29.36.781151+480 I32583948A335      LEVEL: Error
PID     : 811148               TID  : 1387        PROC : db2logmgr (ABSTEST) 0
INSTANCE: db2inst1             NODE : 000
FUNCTION: DB2 UDB, data protection, sqlpInitVendorDevice, probe:1050
RETCODE : ZRC=0x0000001E=30
          DIA8030C Invalid filename "" was specified.

2007-07-02-13.29.36.781853+480 I32584284A336      LEVEL: Error
PID     : 811148               TID  : 1387        PROC : db2logmgr (ABSTEST) 0
INSTANCE: db2inst1             NODE : 000
FUNCTION: DB2 UDB, data protection, sqlpgArchiveLogVendor, probe:1820
RETCODE : ZRC=0x0000001E=30
          DIA8030C Invalid filename "" was specified.

2007-07-02-13.29.36.782083+480 I32584621A399      LEVEL: Error
PID     : 811148               TID  : 1387        PROC : db2logmgr (ABSTEST) 0
INSTANCE: db2inst1             NODE : 000
FUNCTION: DB2 UDB, data protection, sqlpgArchiveLogFile, probe:3160
MESSAGE : Failed to archive log file S0000293.LOG to TSM chain 0 from
          /home/db2inst1/db2inst1/NODE0000/SQL00001/SQLOGDIR/ with rc = 30.

2007-07-02-13.29.36.782259+480 I32585021A314      LEVEL: Error
PID     : 811148               TID  : 1387        PROC : db2logmgr (ABSTEST) 0
INSTANCE: db2inst1             NODE : 000
FUNCTION: DB2 UDB, data protection, sqlpgArchivePendingLogs, probe:1500
MESSAGE : Log archive failed with rc 30 for LOGARCHMETH1.

2007-07-02-13.29.36.782476+480 I32585336A368      LEVEL: Error
PID     : 811148               TID  : 1387        PROC : db2logmgr (ABSTEST) 0
INSTANCE: db2inst1             NODE : 000
FUNCTION: DB2 UDB, data protection, sqlpgArchiveLogVendor, probe:1630
RETCODE : ZRC=0x860F000A=-2045837302=SQLO_FNEX "File not found."
          DIA8411C A file "" could not be found.

2007-07-02-13.29.36.782670+480 I32585705A428      LEVEL: Error
PID     : 811148               TID  : 1387        PROC : db2logmgr (ABSTEST) 0
INSTANCE: db2inst1             NODE : 000
FUNCTION: DB2 UDB, data protection, sqlpgArchiveLogFile, probe:3160
MESSAGE : Failed to archive log file S0000287.LOG to TSM chain 0 from
          /home/db2inst1/arclogdir/db2inst1/ABSTEST/NODE0000/C0000000/ with rc
          = -2045837302.

2007-07-02-13.29.36.782840+480 I32586134A390      LEVEL: Warning
PID     : 811148               TID  : 1387        PROC : db2logmgr (ABSTEST) 0
INSTANCE: db2inst1             NODE : 000
FUNCTION: DB2 UDB, data protection, sqlpgCleanFailArchPath, probe:4930
MESSAGE : Unable to find log file 287 for LOGARCHMETH1 using method 2 and
          target .  Assume log was archived and continue.

2007-07-02-13.29.37.816424+480 I32586525A560      LEVEL: Error
PID     : 811148               TID  : 1387        PROC : db2logmgr (ABSTEST) 0
INSTANCE: db2inst1             NODE : 000
FUNCTION: DB2 UDB, data protection, sqlpInitVendorDevice, probe:1030
MESSAGE : Init failed!  Vendor rc:
DATA #1 : Hexdump, 48 bytes
0x0FFFFFFFFFFFC600 : 0000 07F9 3433 3520 3230 3431 0000 0000    ....435 2041....
0x0FFFFFFFFFFFC610 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
0x0FFFFFFFFFFFC620 : 0000 0000 1880 0000 0000 0000 0000 0000    ................

2007-07-02-13.29.37.816625+480 I32587086A281      LEVEL: Error
PID     : 811148               TID  : 1387        PROC : db2logmgr (ABSTEST) 0
INSTANCE: db2inst1             NODE : 000
FUNCTION: DB2 UDB, data protection, sqlpInitVendorDevice, probe:1050
RETCODE : ZRC=0x0000000B=11

2007-07-02-13.29.37.816832+480 I32587368A282      LEVEL: Error
PID     : 811148               TID  : 1387        PROC : db2logmgr (ABSTEST) 0
INSTANCE: db2inst1             NODE : 000
FUNCTION: DB2 UDB, data protection, sqlpgArchiveLogVendor, probe:1820
RETCODE : ZRC=0x0000000B=11

2007-07-02-13.29.37.817036+480 I32587651A399      LEVEL: Error
PID     : 811148               TID  : 1387        PROC : db2logmgr (ABSTEST) 0
INSTANCE: db2inst1             NODE : 000
FUNCTION: DB2 UDB, data protection, sqlpgArchiveLogFile, probe:3160
MESSAGE : Failed to archive log file S0000294.LOG to TSM chain 0 from
          /home/db2inst1/db2inst1/NODE0000/SQL00001/SQLOGDIR/ with rc = 11.

2007-07-02-13.29.37.817226+480 I32588051A314      LEVEL: Error
PID     : 811148               TID  : 1387        PROC : db2logmgr (ABSTEST) 0
INSTANCE: db2inst1             NODE : 000
FUNCTION: DB2 UDB, data protection, sqlpgArchivePendingLogs, probe:1500
MESSAGE : Log archive failed with rc 11 for LOGARCHMETH1.

2007-07-02-13.29.38.836587+480 I32588366A560      LEVEL: Error
PID     : 811148               TID  : 1387        PROC : db2logmgr (ABSTEST) 0
INSTANCE: db2inst1             NODE : 000
FUNCTION: DB2 UDB, data protection, sqlpInitVendorDevice, probe:1030
MESSAGE : Init failed!  Vendor rc:
DATA #1 : Hexdump, 48 bytes
0x0FFFFFFFFFFFC600 : 0000 07F9 3433 3520 3230 3431 0000 0000    ....435 2041....
0x0FFFFFFFFFFFC610 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
0x0FFFFFFFFFFFC620 : 0000 0000 1880 0000 0000 0000 0000 0000    ................

2007-07-02-13.29.38.836785+480 I32588927A281      LEVEL: Error
PID     : 811148               TID  : 1387        PROC : db2logmgr (ABSTEST) 0
INSTANCE: db2inst1             NODE : 000
FUNCTION: DB2 UDB, data protection, sqlpInitVendorDevice, probe:1050
RETCODE : ZRC=0x0000000B=11

2007-07-02-13.29.38.836989+480 I32589209A282      LEVEL: Error

zou_hope

在13:00左右db2_kill了所有进程，重启实例成功。在13:20左右db2实例停止，原因不详，重启实例后再没出问题。据客户说，两周前进行类似动作，也发生过相同问题。

我将TSM归档日志也贴在下面，实例有两个数据库abstest和ncbprod
abstest日志较少，平时只有2个日志。但7月2日13：00左右，我重启实例后却有十几个日志归档，难以理解。

TSM 6月22日失效，29日才修复。缺这几天归档日志。

zou_hope

Log file: S0000171.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-05-01-00.57.37
   Log file: S0000215.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-05-01-07.29.26
   Log file: S0000172.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-05-02-01.00.27
   Log file: S0000173.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-05-03-01.03.30
   Log file: S0000174.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-05-03-19.42.48
   Log file: S0000175.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-05-04-00.55.44
   Log file: S0000176.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-05-05-00.59.54
   Log file: S0000177.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-05-05-19.50.59
   Log file: S0000178.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-05-06-00.56.23
   Log file: S0000179.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-05-07-01.02.33
   Log file: S0000180.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-05-07-18.13.03
   Log file: S0000181.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-05-08-00.56.10
   Log file: S0000182.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-05-08-20.25.50
   Log file: S0000183.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-05-09-00.58.21
   Log file: S0000184.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-05-09-19.26.43
   Log file: S0000185.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-05-10-00.55.50
   Log file: S0000186.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-05-10-19.28.20
   Log file: S0000187.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-05-11-00.56.09
   Log file: S0000188.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-05-11-18.33.35
   Log file: S0000189.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-05-11-19.02.01
   Log file: S0000190.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-05-12-00.56.38
   Log file: S0000191.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-05-13-00.59.01
   Log file: S0000192.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-05-14-00.56.07
   Log file: S0000193.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-05-14-20.05.29
   Log file: S0000194.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-05-14-20.16.59
   Log file: S0000195.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-05-14-20.17.33
   Log file: S0000196.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-05-15-00.56.27
   Log file: S0000197.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-05-15-19.23.42
   Log file: S0000198.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-05-16-00.55.26
   Log file: S0000199.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-05-16-18.56.02
   Log file: S0000200.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-05-17-00.56.25
   Log file: S0000201.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-05-17-20.49.27
   Log file: S0000202.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-05-18-00.58.01
   Log file: S0000203.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-05-18-20.18.53
   Log file: S0000204.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-05-18-21.18.39
   Log file: S0000205.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-05-19-00.57.26
   Log file: S0000206.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-05-19-21.37.35
   Log file: S0000207.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-05-20-00.56.39
   Log file: S0000208.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-05-21-00.55.39
   Log file: S0000209.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-05-21-19.17.30
   Log file: S0000210.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-05-21-21.00.33
   Log file: S0000211.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-05-22-00.56.14
   Log file: S0000216.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-05-22-07.33.00
   Log file: S0000217.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-05-22-07.36.33
   Log file: S0000218.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-05-22-07.37.17
   Log file: S0000219.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-05-22-07.38.01
   Log file: S0000220.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-05-22-07.38.45
   Log file: S0000221.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-05-22-07.39.29
   Log file: S0000222.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-05-22-07.40.13
   Log file: S0000223.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-05-22-07.40.58
   Log file: S0000224.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-05-22-07.41.42
   Log file: S0000225.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-05-22-07.42.26
   Log file: S0000226.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-05-22-07.43.09
   Log file: S0000227.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-05-22-07.43.54
   Log file: S0000212.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-05-22-19.28.28
   Log file: S0000213.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-05-22-21.24.41
   Log file: S0000214.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-05-23-00.55.27
   Log file: S0000230.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-05-29-20.06.11
   Log file: S0000231.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-05-29-20.23.45
   Log file: S0000232.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-05-29-20.24.31
   Log file: S0000233.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-05-29-22.28.03
   Log file: S0000234.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-05-30-00.56.16
   Log file: S0000235.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-05-30-19.13.45
   Log file: S0000236.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-05-31-15.15.41
   Log file: S0000237.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-05-31-19.18.31
   Log file: S0000238.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-01-01.43.33
   Log file: S0000239.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-01-18.29.23
   Log file: S0000240.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-01-19.35.30
   Log file: S0000241.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-03-03.40.35
   Log file: S0000242.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-04-15.05.36
   Log file: S0000243.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-04-18.19.29
   Log file: S0000244.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-05-14.00.33
   Log file: S0000245.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-05-18.56.14
   Log file: S0000246.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-06-09.05.01
   Log file: S0000247.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-06-19.49.29
   Log file: S0000248.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-07-13.55.32
   Log file: S0000249.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-07-18.31.38
   Log file: S0000250.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-08-12.50.33
   Log file: S0000251.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-08-19.26.28
   Log file: S0000252.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-09-18.00.30
   Log file: S0000253.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-10-02.20.30
   Log file: S0000254.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-11-15.39.07
   Log file: S0000255.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-11-19.39.51
   Log file: S0000256.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-12-12.40.30
   Log file: S0000257.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-12-19.54.57
   Log file: S0000258.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-13-11.35.34
   Log file: S0000259.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-13-18.51.47
   Log file: S0000260.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-14-11.54.09
   Log file: S0000261.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-14-20.57.43
   Log file: S0000262.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-14-21.32.58
   Log file: S0000263.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-14-21.33.48
   Log file: S0000264.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-15-11.25.09
   Log file: S0000265.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-15-22.06.23
   Log file: S0000266.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-15-22.34.43
   Log file: S0000267.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-17-05.10.26
   Log file: S0000268.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-18-16.44.24
   Log file: S0000269.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-18-20.23.49
   Log file: S0000270.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-19-13.25.25
   Log file: S0000271.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-19-18.56.07
   Log file: S0000272.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-20-12.20.26
   Log file: S0000273.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-20-19.07.59
   Log file: S0000274.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-29-00.51.21
   Log file: S0000275.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-07-02-13.05.02
   Log file: S0000276.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-07-02-13.08.16
   Log file: S0000277.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-07-02-13.09.02
   Log file: S0000278.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-07-02-13.09.49
   Log file: S0000279.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-07-02-13.10.36
   Log file: S0000280.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-07-02-13.11.29
   Log file: S0000281.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-07-02-13.12.17
   Log file: S0000282.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-07-02-13.13.07
   Log file: S0000283.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-07-02-13.13.55
   Log file: S0000284.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-07-02-13.14.43
   Log file: S0000285.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-07-02-13.15.30
   Log file: S0000286.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-07-02-13.16.18
   Log file: S0000287.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-07-02-13.17.05
   Log file: S0000288.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-07-02-13.17.53
   Log file: S0000289.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-07-02-13.18.41
   Log file: S0000290.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-07-02-13.19.28
   Log file: S0000291.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-07-02-13.20.16
   Log file: S0000292.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-07-02-13.21.04
   Log file: S0000288.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-07-02-14.23.42
   Log file: S0000289.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-07-02-14.24.33
   Log file: S0000290.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-07-02-14.25.20
   Log file: S0000291.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-07-02-14.26.08
   Log file: S0000292.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-07-02-14.26.56
   Log file: S0000293.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-07-02-14.27.43
   Log file: S0000294.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-07-02-14.28.30
   Log file: S0000295.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-07-02-14.29.

zou_hope

上面是abstest数据库的归当日志

下面是ncbprod数据库的归档日志

zou_hope

Log file: S0001517.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-29-15.42.52
   Log file: S0001518.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-29-16.15.55
   Log file: S0001519.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-29-16.51.45
   Log file: S0001520.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-29-17.53.13
   Log file: S0001521.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-29-19.49.59
   Log file: S0001522.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-29-23.57.11
   Log file: S0001523.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-30-00.16.36
   Log file: S0001524.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-30-00.18.56
   Log file: S0001525.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-30-00.22.08
   Log file: S0001526.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-30-00.23.09
   Log file: S0001527.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-30-00.24.06
   Log file: S0001528.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-30-00.24.50
   Log file: S0001529.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-30-00.25.39
   Log file: S0001530.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-30-00.26.33
   Log file: S0001531.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-30-00.27.31
   Log file: S0001532.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-30-00.28.31
   Log file: S0001533.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-30-00.29.41
   Log file: S0001534.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-30-00.37.16
   Log file: S0001535.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-30-00.53.48
   Log file: S0001536.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-30-00.54.39
   Log file: S0001537.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-30-00.55.16
   Log file: S0001538.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-30-00.55.51
   Log file: S0001539.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-30-00.56.23
   Log file: S0001540.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-30-00.56.52
   Log file: S0001541.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-30-00.57.21
   Log file: S0001542.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-30-00.57.48
   Log file: S0001543.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-30-00.58.12
   Log file: S0001544.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-30-00.58.35
   Log file: S0001545.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-30-00.58.58
   Log file: S0001546.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-30-00.59.59
   Log file: S0001547.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-30-01.01.36
   Log file: S0001548.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-30-01.02.21
   Log file: S0001549.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-30-01.49.20
   Log file: S0001550.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-30-09.14.06
   Log file: S0001551.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-30-10.17.54
   Log file: S0001552.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-30-11.35.55
   Log file: S0001553.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-30-14.08.53
   Log file: S0001554.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-30-15.58.10
   Log file: S0001555.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-30-17.58.01
   Log file: S0001556.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-30-21.09.30
   Log file: S0001557.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-30-21.52.13
   Log file: S0001558.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-30-21.55.58
   Log file: S0001559.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-30-21.56.59
   Log file: S0001560.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-30-21.57.52
   Log file: S0001561.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-30-21.58.40
   Log file: S0001562.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-30-21.59.21
   Log file: S0001563.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-30-22.00.18
   Log file: S0001564.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-30-22.01.17
   Log file: S0001565.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-30-22.02.07
   Log file: S0001566.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-30-22.03.14
   Log file: S0001567.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-30-22.04.54
   Log file: S0001568.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-30-22.15.53
   Log file: S0001569.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-30-22.37.08
   Log file: S0001570.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-30-22.37.49
   Log file: S0001571.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-30-22.38.22
   Log file: S0001572.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-30-22.38.45
   Log file: S0001573.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-30-22.40.30
   Log file: S0001574.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-30-22.53.35
   Log file: S0001575.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-30-22.55.04
   Log file: S0001576.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-30-23.00.01
   Log file: S0001577.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-06-30-23.21.09
   Log file: S0001578.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-07-01-09.01.05
   Log file: S0001579.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-07-01-10.23.22
   Log file: S0001580.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-07-01-12.21.52
   Log file: S0001581.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-07-01-14.56.56
   Log file: S0001582.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-07-01-16.46.54
   Log file: S0001583.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-07-01-19.46.41
   Log file: S0001584.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-07-01-19.59.26
   Log file: S0001585.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-07-01-20.03.41
   Log file: S0001586.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-07-01-20.06.39
   Log file: S0001587.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-07-01-20.07.39
   Log file: S0001588.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-07-01-20.08.38
   Log file: S0001589.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-07-01-20.09.20
   Log file: S0001590.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-07-01-20.10.10
   Log file: S0001591.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-07-01-20.11.05
   Log file: S0001592.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-07-01-20.12.03
   Log file: S0001593.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-07-01-20.12.59
   Log file: S0001594.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-07-01-20.14.05
   Log file: S0001595.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-07-01-20.22.33
   Log file: S0001596.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-07-01-20.28.33
   Log file: S0001597.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-07-01-20.29.01
   Log file: S0001598.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-07-01-20.29.37
   Log file: S0001599.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-07-01-20.30.01
   Log file: S0001600.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-07-01-20.30.45
   Log file: S0001601.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-07-01-20.36.51
   Log file: S0001602.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-07-02-08.21.15
   Log file: S0001603.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-07-02-08.52.56
   Log file: S0001604.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-07-02-08.53.25
   Log file: S0001605.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-07-02-08.53.58
   Log file: S0001606.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-07-02-08.54.32
   Log file: S0001607.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-07-02-09.11.59
   Log file: S0001608.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-07-02-09.50.53
   Log file: S0001609.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-07-02-10.28.54
   Log file: S0001610.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-07-02-11.10.34
   Log file: S0001611.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-07-02-11.53.19
   Log file: S0001612.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-07-02-13.24.27
   Log file: S0001613.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-07-02-14.39.46
   Log file: S0001614.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-07-02-15.09.24
   Log file: S0001615.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-07-02-15.35.06
   Log file: S0001616.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-07-02-16.03.30
   Log file: S0001617.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-07-02-16.30.06
   Log file: S0001618.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-07-02-17.05.00
   Log file: S0001619.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-07-02-17.38.01
   Log file: S0001620.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-07-02-19.33.16
   Log file: S0001621.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-07-02-19.36.27
   Log file: S0001622.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-07-02-19.37.15
   Log file: S0001623.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-07-02-19.38.04
   Log file: S0001624.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-07-02-19.38.54
   Log file: S0001625.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-07-02-19.39.43
   Log file: S0001626.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2007-07-02-19.40.34

zou_hope

下面是执行db2stop force挂起的原因

zou_hope

2007-07-02-12.18.47.642077+480 I32542495A336      LEVEL: Warning
PID     : 524484               TID  : 1           PROC : db2loggr (ABSTEST) 0
INSTANCE: db2inst1             NODE : 000
FUNCTION: DB2 UDB, data protection, sqlpghck, probe:1390
MESSAGE : ExtNum 295, state 401, baselsn 0000000084918000 nextlsn
          0000000084BB30A3

2007-07-02-12.19.42.665628+480 I32542832A297      LEVEL: Warning
PID     : 524484               TID  : 1           PROC : db2loggr (ABSTEST) 0
INSTANCE: db2inst1             NODE : 000
FUNCTION: DB2 UDB, data protection, sqlpghck, probe:1780
MESSAGE : DB2 is waiting for log files to be archived.

2007-07-02-12.20.42.666018+480 I32543130A297      LEVEL: Warning
PID     : 524484               TID  : 1           PROC : db2loggr (ABSTEST) 0
INSTANCE: db2inst1             NODE : 000
FUNCTION: DB2 UDB, data protection, sqlpghck, probe:1780
MESSAGE : DB2 is waiting for log files to be archived.

2007-07-02-12.21.42.666424+480 I32543428A297      LEVEL: Warning
PID     : 524484               TID  : 1           PROC : db2loggr (ABSTEST) 0
INSTANCE: db2inst1             NODE : 000
FUNCTION: DB2 UDB, data protection, sqlpghck, probe:1780
MESSAGE : DB2 is waiting for log files to be archived.

2007-07-02-12.22.42.666825+480 I32543726A297      LEVEL: Warning
PID     : 524484               TID  : 1           PROC : db2loggr (ABSTEST) 0
INSTANCE: db2inst1             NODE : 000
FUNCTION: DB2 UDB, data protection, sqlpghck, probe:1780
MESSAGE : DB2 is waiting for log files to be archived.

2007-07-02-12.23.42.667245+480 I32544024A402      LEVEL: Warning
PID     : 524484               TID  : 1           PROC : db2loggr (ABSTEST) 0
INSTANCE: db2inst1             NODE : 000
FUNCTION: DB2 UDB, data protection, sqlpghck, probe:1800
DATA #1 : String, 131 bytes
DB2 was unable to confirm logs were archived.
Return code -2029059911, FirstArchNum 274, FirstArchNum2 4294967295, HeadExtentID 296

2007-07-02-12.28.44.681513+480 I32544427A383      LEVEL: Warning
PID     : 921672               TID  : 1           PROC : db2agent (idle) 0
INSTANCE: db2inst1             NODE : 000         DB   : ABSTEST
APPHDL  : 0-50                 APPID: *LOCAL.db2inst1.070628165841
FUNCTION: DB2 UDB, data protection, sqlpterm, probe:2330
MESSAGE : Some daemon is taking too long to shut down

2007-07-02-12.33.46.631926+480 I32544811A383      LEVEL: Warning
PID     : 921672               TID  : 1           PROC : db2agent (idle) 0
INSTANCE: db2inst1             NODE : 000         DB   : ABSTEST
APPHDL  : 0-50                 APPID: *LOCAL.db2inst1.070628165841
FUNCTION: DB2 UDB, data protection, sqlpterm, probe:2330
MESSAGE : Some daemon is taking too long to shut down

zou_hope

另一个一直存在的问题
这是数据abstest的日志目录
/home/db2inst1/db2inst1/NODE0000/SQL00001/SQLOGDIR/
下面是TSM归档失败后的暂存目录faillog
/home/db2inst1/arclogdir/

日志文件S0000278.LOG已经从目录/home/db2inst1/db2inst1/NODE0000/SQL00001/SQLOGDIR/归档成功,但系统还是会在db2daig.log里提示在/home/db2inst1/arclogdir/找不到这个日志.
这时不应该再到/home/db2inst1/arclogdir/找这个日志文件.

2007-07-02-13.18.14.537577+480 I32555965A392      LEVEL: Warning
PID     : 811148               TID  : 1           PROC : db2logmgr (ABSTEST) 0
INSTANCE: db2inst1             NODE : 000
FUNCTION: DB2 UDB, data protection, sqlpgArchiveLogFile, probe:3180
MESSAGE : Successfully archived log file S0000278.LOG to TSM chain 0 from
          /home/db2inst1/db2inst1/NODE0000/SQL00001/SQLOGDIR/.



2007-07-02-13.23.08.469746+480 I32565022A428      LEVEL: Error
PID     : 811148               TID  : 1           PROC : db2logmgr (ABSTEST) 0
INSTANCE: db2inst1             NODE : 000
FUNCTION: DB2 UDB, data protection, sqlpgArchiveLogFile, probe:3160
MESSAGE : Failed to archive log file S0000278.LOG to TSM chain 0 from
          /home/db2inst1/arclogdir/db2inst1/ABSTEST/NODE0000/C0000000/ with rc
          = -2045837302.

jackson198574

这个问题最后究竟是怎么处理的？