TSM RC=0x0000006A=106

DB2归档日志没有被TSM备份

a3inr2fb@b03cxnp46026:/db/a3inr2fb/db2backup# db2adutl query full

Query for database R2FAPP


Retrieving FULL DATABASE BACKUP information.
  No FULL DATABASE BACKUP images found for R2FAPP


Retrieving INCREMENTAL DATABASE BACKUP information.
  No INCREMENTAL DATABASE BACKUP images found for R2FAPP


Retrieving DELTA DATABASE BACKUP information.
  No DELTA DATABASE BACKUP images found for R2FAPP

在db2diag.log中有以下错误

2011-09-02-07.44.23.114538+000 E859182A347        LEVEL: Error
PID     : 13500666             TID  : 1           PROC : db2vend
INSTANCE: a3inr2fb             NODE : 000
EDUID   : 1
FUNCTION: DB2 UDB, database utilities, sqluvint, probe:374
DATA #1 : TSM RC, PD_DB2_TYPE_TSM_RC, 4 bytes
TSM RC=0x0000006A=106 -- see TSM API Reference for meaning.

查了一下information center
http://publib.boulder.ibm.com/infocenter/tsminfo/v6r2/index.jsp?topic=%2Fcom.ibm.itsm.srv.install.doc%2Ft_srv_prep_dbmgr.html

define DSM_RC_ACCESS_DENIED       106 /* denied due to improper permission */
#

说是权限问题，但是确认过DSMI_LOG等路径下的权限已经足够大

看到有如下链接
https://www-304.ibm.com/support/docview.wss?uid=swg21399011

引用

The API return code 106 means DSM_RC_ACCESS_DENIED and is referring to the error log file in the DSMI_LOG environment variable.

DSMI_LOG下的error log文件权限足够，不过是空的

a3inr2fb@b03cxnp46026:/db/a3inr2fb/db2backup/apilogs# ls -atrl 
total 8
drwxr-xr-x    4 a3inr2fb dbadmin        4096 Sep  1 08:24 ..
-rwxrwxrwx    1 a3inr2fb dbadmin           0 Sep  1 08:27 dsierror.log
drwxrwxr-x    2 a3inr2fb dbadmin         256 Sep  1 08:27 .

再看看dsm.sys文件下面的设置

a3inr2fb@b03cxnp46026:/db/a3inr2fb/db2diag# grep ERROR /usr/tivoli/tsm/client/api/bin64/dsm.sys

没有设置ERRORLOGNAME,尝试手动设置

ERRORLOGName        /usr/tivoli/tsm/client/ba/bin/dsmerror.log
ERRORLOGRetention   2 D

备份就恢复正常了

看来这是因为TSM客户端无法写错误日志，所以无法进行备份

a3inr2fb@b03cxnp46026:/db/a3inr2fb/arclog_bpedb# db2adutl query db BPEPPDB

Query for database BPEPPDB


Retrieving FULL DATABASE BACKUP information.
  No FULL DATABASE BACKUP images found for BPEPPDB


Retrieving INCREMENTAL DATABASE BACKUP information.
  No INCREMENTAL DATABASE BACKUP images found for BPEPPDB


Retrieving DELTA DATABASE BACKUP information.
  No DELTA DATABASE BACKUP images found for BPEPPDB


Retrieving TABLESPACE BACKUP information.
  No TABLESPACE BACKUP images found for BPEPPDB


Retrieving INCREMENTAL TABLESPACE BACKUP information.
  No INCREMENTAL TABLESPACE BACKUP images found for BPEPPDB


Retrieving DELTA TABLESPACE BACKUP information.
  No DELTA TABLESPACE BACKUP images found for BPEPPDB


Retrieving LOAD COPY information.
  No LOAD COPY images found for BPEPPDB


Retrieving LOG ARCHIVE information.
   Log file: S0009508.LOG, Chain Num: 1, DB Partition Number: 0, Taken at: 2011-09-02-03.44.45
   Log file: S0009509.LOG, Chain Num: 1, DB Partition Number: 0, Taken at: 2011-09-02-03.45.07
   Log file: S0009510.LOG, Chain Num: 1, DB Partition Number: 0, Taken at: 2011-09-02-03.45.28
   Log file: S0009511.LOG, Chain Num: 1, DB Partition Number: 0, Taken at: 2011-09-02-03.45.48
   Log file: S0009512.LOG, Chain Num: 1, DB Partition Number: 0, Taken at: 2011-09-02-03.46.09
   Log file: S0009513.LOG, Chain Num: 1, DB Partition Number: 0, Taken at: 2011-09-02-03.46.30
   Log file: S0009514.LOG, Chain Num: 1, DB Partition Number: 0, Taken at: 2011-09-02-03.46.51
   Log file: S0009515.LOG, Chain Num: 1, DB Partition Number: 0, Taken at: 2011-09-02-03.47.12
   Log file: S0009516.LOG, Chain Num: 1, DB Partition Number: 0, Taken at: 2011-09-02-03.47.34
   Log file: S0009517.LOG, Chain Num: 1, DB Partition Number: 0, Taken at: 2011-09-02-03.47.55
   Log file: S0009518.LOG, Chain Num: 1, DB Partition Number: 0, Taken at: 2011-09-02-03.48.16