ITPub博客

首页 > Linux操作系统 > Linux操作系统 > 更换带库的坏Driver后,在TSM 做的配置操作

更换带库的坏Driver后,在TSM 做的配置操作

原创 Linux操作系统 作者:mengzhaoliang 时间:2009-05-22 18:53:17 0 删除 编辑

1、 TSM的活动日志:

ANR8963E 无法找到与为库 3310LIB 中的驱动器 3310DRV02 定义的序列号相匹配的路径。 (会话: 15) 2009-5-12 2:01:49
ANR0406I 节点 TDPOMS(TDP Oracle AIX)(Tcp/Ip 10.62.61.102(34414))的会话 16 已启动。 (会话: 16) 2009-5-12 2:01:50
ANR8300E 库 3310LIB 上的 I/O 错误(OP=8401C058,CC=207,KEY=FF,ASC=FF,ASCQ=FF, SENSE=**NONE**, 描述=设备没有处于可执行请求的状态)。请参见“消息”手册中的附录 C 以获取建议的操作。 (会话: 15) 2009-5-12 2:01:52
ANR8381E LTO 卷 Z16080L3 不可装入到驱动器 3310DRV02 (mt1.0.0.5)。 (会话: 15) 2009-5-12 2:01:54
ANR1401W 卷 Z16080L3 的安装请求被拒绝 - 安装失败。 (会话: 15) 2009-5-12 2:01:54
ANR8963E 无法找到与为库 3310LIB 中的驱动器 3310DRV02 定义的序列号相匹配的路径。 (会话: 15) 2009-5-12 2:01:55
ANR8300E 库 3310LIB 上的 I/O 错误(OP=8401C058,CC=207,KEY=FF,ASC=FF,ASCQ=FF, SENSE=**NONE**, 描述=设备没有处于可执行请求的状态)。请参见“消息”手册中的附录 C 以获取建议的操作。 (会话: 15) 2009-5-12 2:02:13
ANR8381E LTO 卷 Z16080L3 不可装入到驱动器 3310DRV02 (mt1.0.0.5)。 (会话: 15) 2009-5-12 2:02:15
ANR1401W 卷 Z16080L3 的安装请求被拒绝 - 安装失败。 (会话: 15) 2009-5-12 2:02:15
ANR8963E 无法找到与为库 3310LIB 中的驱动器 3310DRV02 定义的序列号相匹配的路径。 (会话: 15) 2009-5-12 2:02:15
ANR8300E 库 3310LIB 上的 I/O 错误(OP=8401C058,CC=207,KEY=FF,ASC=FF,ASCQ=FF, SENSE=**NONE**, 描述=设备没有处于可执行请求的状态)。请参见“消息”手册中的附录 C 以获取建议的操作。 (会话: 15) 2009-5-12 2:02:17
ANR8381E LTO 卷 Z16084L3 不可装入到驱动器 3310DRV02 (mt1.0.0.5)。 (会话: 15) 2009-5-12 2:02:19
ANR1401W 卷 Z16084L3 的安装请求被拒绝 - 安装失败。 (会话: 15) 2009-5-12 2:02:19

2、RMAN日志:

RMAN备份的日志
Recovery Manager: Release 10.2.0.1.0 - Production on Tue May 12 02:01:37 2009

Copyright (c) 1982, 2005, Oracle.  All rights reserved.

connected to target database: DQOMS (DBID=4131026225)

RMAN> run{ 
2>  allocate channel t1 type 'sbt_tape' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)'; 
3>  allocate channel t2 type 'sbt_tape' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)'; 
4>  BACKUP INCREMENTAL LEVEL 1 CUMULATIVE FILESPERSET 10   
5>  FORMAT 'incr_%T_%s_%p' DATABASE;   
6>  sql 'alter system archive log current';
7>  BACKUP FILESPERSET 10 MAXSETSIZE 10G    
8>  FORMAT 'arch_%T_%s_%p'    
9>  SKIP INACCESSIBLE   
10>  ARCHIVELOG ALL DELETE INPUT;   
11>  release channel t1; 
12>  release channel t2;
13> }
14>
15>
using target database control file instead of recovery catalog
allocated channel: t1
channel t1: sid=531 devtype=SBT_TAPE
channel t1: Data Protection for Oracle: version 5.4.1.0

allocated channel: t2
channel t2: sid=520 devtype=SBT_TAPE
channel t2: Data Protection for Oracle: version 5.4.1.0

Starting backup at 12-MAY-09
channel t1: starting incremental level 1 datafile backupset
channel t1: specifying datafile(s) in backupset
input datafile fno=00007 name=/oracle/oms/oradata/log/Log_Norm_data000.dbf
input datafile fno=00009 name=/oracle/oms/oradata/drill/Drill_Norm_data000.dbf
input datafile fno=00015 name=/oracle/oms/oradata/gpe/GPE_NORM_data000.dbf
input datafile fno=00014 name=/oracle/oms/oradata/bbs/BBS_data000.dbf
input datafile fno=00004 name=/oracle/oms/oradata/sysdata/users01.dbf
input datafile fno=00022 name=/oracle/oms/oradata/temp/perfstat.dbf
input datafile fno=00001 name=/oracle/oms/oradata/sysdata/system01.dbf
input datafile fno=00002 name=/oracle/oms/oradata/undo/undotbs01.dbf
channel t1: starting piece 1 at 12-MAY-09
channel t2: starting incremental level 1 datafile backupset
channel t2: specifying datafile(s) in backupset
input datafile fno=00008 name=/oracle/oms/oradata/mlog/Mlog_Norm_data000.dbf
input datafile fno=00010 name=/oracle/oms/oradata/dh/DH_Norm_data000.dbf
input datafile fno=00006 name=/oracle/oms/oradata/pub/Pub_Norm_data000.dbf
input datafile fno=00011 name=/oracle/oms/oradata/wps/WPS_data000.dbf
input datafile fno=00012 name=/oracle/oms/oradata/jbpm/Jbpm_data000.dbf
input datafile fno=00013 name=/oracle/oms/oradata/srvreg/SrvReg_data000.dbf
input datafile fno=00005 name=/oracle/oms/oradata/sysdata/RMAN_data000.dbf
input datafile fno=00003 name=/oracle/oms/oradata/sysdata/sysaux01.dbf
channel t2: starting piece 1 at 12-MAY-09
RMAN-03009: failure of backup command on t1 channel at 05/12/2009 02:03:39
ORA-19502: write error on file "incr_20090512_8366_1", blockno 202753 (blocksize=512)
ORA-27030: skgfwrt: sbtwrite2 returned error
ORA-19511: Error received from media manager layer, error text:
   ANS1312E (RC12)   Server media mount not possible
channel t1 disabled, job failed on it will be run on another channel
channel t2: finished piece 1 at 12-MAY-09
piece handle=incr_20090512_8367_1 tag=TAG20090512T020143 comment=API Version 2.0,MMS Version 5.4.1.0
channel t2: backup set complete, elapsed time: 00:07:54
channel t2: starting incremental level 1 datafile backupset
channel t2: specifying datafile(s) in backupset
input datafile fno=00007 name=/oracle/oms/oradata/log/Log_Norm_data000.dbf
input datafile fno=00009 name=/oracle/oms/oradata/drill/Drill_Norm_data000.dbf
input datafile fno=00015 name=/oracle/oms/oradata/gpe/GPE_NORM_data000.dbf
input datafile fno=00014 name=/oracle/oms/oradata/bbs/BBS_data000.dbf
input datafile fno=00004 name=/oracle/oms/oradata/sysdata/users01.dbf
input datafile fno=00022 name=/oracle/oms/oradata/temp/perfstat.dbf
input datafile fno=00001 name=/oracle/oms/oradata/sysdata/system01.dbf
input datafile fno=00002 name=/oracle/oms/oradata/undo/undotbs01.dbf
channel t2: starting piece 1 at 12-MAY-09
channel t2: finished piece 1 at 12-MAY-09
piece handle=incr_20090512_8368_1 tag=TAG20090512T020143 comment=API Version 2.0,MMS Version 5.4.1.0
channel t2: backup set complete, elapsed time: 00:05:55
channel t2: starting incremental level 1 datafile backupset
channel t2: specifying datafile(s) in backupset
input datafile fno=00017 name=/oracle/oms/oradata/log/Log_Lob_data000.dbf
input datafile fno=00019 name=/oracle/oms/oradata/drill/Drill_Lob_data000.dbf
input datafile fno=00020 name=/oracle/oms/oradata/dh/DH_Lob_data000.dbf
channel t2: starting piece 1 at 12-MAY-09
channel t2: finished piece 1 at 12-MAY-09
piece handle=incr_20090512_8369_1 tag=TAG20090512T020143 comment=API Version 2.0,MMS Version 5.4.1.0
channel t2: backup set complete, elapsed time: 00:05:55
channel t2: starting incremental level 1 datafile backupset
channel t2: specifying datafile(s) in backupset
input datafile fno=00016 name=/oracle/oms/oradata/gpe/Gpe_Lob_data000.dbf
input datafile fno=00018 name=/oracle/oms/oradata/mlog/Mlog_Lob_data000.dbf
input datafile fno=00021 name=/oracle/oms/oradata/pub/Pub_Lob_data000.dbf
channel t2: starting piece 1 at 12-MAY-09
channel t2: finished piece 1 at 12-MAY-09
piece handle=incr_20090512_8370_1 tag=TAG20090512T020143 comment=API Version 2.0,MMS Version 5.4.1.0
channel t2: backup set complete, elapsed time: 00:05:36
Finished backup at 12-MAY-09

3、检查带库后,发现带库有一个驱动已经不能正常使用了。

 

解决方法:

1、 IBM带库工程换了驱动,查看Library和Driver都是正常状态。
2、 发现在TSM Server的Windows2003系统不能识别带库,系统中的设备管理器中的“介质变换器”的带库驱动不正常,如下图:其中有一个驱动不正常。
 

3、 把上图的两个驱动都卸载,重新安装带库的驱动。
 

4、 上图可以显示TSM Server可以正常识别到带库。然后查看TSM Server中的带库Library、Driver状态,在“命令行”:q   libv  f=d 和q  path f=d  (q  driv f=d)
如果Driver 处于脱机(offline)状态,可以在ISC的控制台中把该Driver设置成联机(online)状态,如果不能设置成联机状态,可以把该驱动删除,重新创建。
 

5、 如果“驱动器路径”中的有些路径为脱机状态,可以直接设置成联机状态。
 

6、 在TSM Client(数据库)中kill所有 tsm的调度进程,然后重新启动调度进程。
DQXXDBS01:/usr/tivoli/tsm/script> ps -ef|grep dsm
    root  925822 1089670   0 18:15:52  pts/0  0:00 grep dsm
    root 1077260       1   0 17:35:59  pts/0  0:02 dsmc sched -servername=TSMoraserv

DQXXDBS01:/usr/tivoli/tsm/script>kill   1077260    (有多个,就杀死多个dsm进程)
重启调度进程:
DQXXDBS01:/usr/tivoli/tsm/script> ./backuparchive.sh &
[1]     1110158
最后查看起来的dsm调度进程:
DQXXDBS01:/usr/tivoli/tsm/script> ps -ef|grep dsm
7、 测试TSM Server的调度,如有问题可以在TSM Server的命令行查看最近三天活动日志“q actlog begind=-3”,
或者在TSM Client端查看活动日志,如下命令:
DQXXDBS01:/usr/tivoli/tsm/client/ba/bin> dsmadmc
IBM Tivoli Storage Manager
Command Line Administrative Interface - Version 5, Release 4, Level 1.0
(c) Copyright by IBM Corporation and other(s) 1990, 2007. All Rights Reserved.

Enter your user id:  admin

Enter your password:

Session established with server TSMSERVER: Windows
  Server Version 5, Release 4, Level 0.0
  Server date/time: 05/22/09   18:47:28  Last access: 05/22/09   18:18:48


tsm: TSMSERVER>q actlog

 

来自 “ ITPUB博客 ” ,链接:http://blog.itpub.net/12778571/viewspace-600865/,如需转载,请注明出处,否则将追究法律责任。

请登录后发表评论 登录
全部评论
暂无介绍

注册时间:2008-01-30

  • 博文量
    335
  • 访问量
    2914810