Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
connected to target database: CGS (DBID=1043687573)
connected to recovery catalog database
RMAN> run{
2> allocate channel ch00 type 'sbt_tape' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
3> allocate channel ch01 type 'sbt_tape' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
4> sql 'alter system archive log current';
5> backup
6> format 'CG_arch_%s_%p_%T'
7> archivelog all;
8> release channel ch00;
9> release channel ch01;
10> }
11>
allocated channel: ch00
channel ch00: sid=183 devtype=SBT_TAPE
channel ch00: Tivoli Data Protection for Oracle: version 5.2.0.0
allocated channel: ch01
channel ch01: sid=185 devtype=SBT_TAPE
channel ch01: Tivoli Data Protection for Oracle: version 5.2.0.0
sql statement: alter system archive log current
Starting backup at 23-OCT-07
current log archived
channel ch00: starting archive log backupset
channel ch00: specifying archive log(s) in backup set
input archive log thread=1 sequence=980 recid=2016 stamp=636305230
input archive log thread=1 sequence=981 recid=2018 stamp=636305041
input archive log thread=1 sequence=982 recid=2019 stamp=636391419
input archive log thread=1 sequence=983 recid=2022 stamp=636391429
input archive log thread=1 sequence=984 recid=2023 stamp=636477830
input archive log thread=1 sequence=985 recid=2026 stamp=636477842
input archive log thread=1 sequence=986 recid=2028 stamp=636564245
input archive log thread=1 sequence=987 recid=2029 stamp=636564254
input archive log thread=1 sequence=988 recid=2031 stamp=636650626
input archive log thread=1 sequence=989 recid=2034 stamp=636650627
input archive log thread=1 sequence=990 recid=2035 stamp=636737042
input archive log thread=1 sequence=991 recid=2038 stamp=636737049
channel ch00: starting piece 1 at 23-OCT-07
channel ch01: starting archive log backupset
channel ch01: specifying archive log(s) in backup set
input archive log thread=2 sequence=1001 recid=2015 stamp=636305230
input archive log thread=2 sequence=1002 recid=2017 stamp=636305232
input archive log thread=2 sequence=1003 recid=2020 stamp=636391615
input archive log thread=2 sequence=1004 recid=2021 stamp=636391620
input archive log thread=2 sequence=1005 recid=2024 stamp=636478024
input archive log thread=2 sequence=1006 recid=2025 stamp=636478033
input archive log thread=2 sequence=1007 recid=2027 stamp=636564437
input archive log thread=2 sequence=1008 recid=2030 stamp=636564449
input archive log thread=2 sequence=1009 recid=2032 stamp=636650820
input archive log thread=2 sequence=1010 recid=2033 stamp=636650821
input archive log thread=2 sequence=1011 recid=2036 stamp=636737236
channel ch01: starting piece 1 at 23-OCT-07
channel ch00: finished piece 1 at 23-OCT-07
piece handle=CG_arch_2536_1_20071023 comment=API Version 2.0,MMS Version 5.2.0.0
channel ch00: backup set complete, elapsed time: 00:01:36
channel ch00: starting archive log backupset
channel ch00: specifying archive log(s) in backup set
input archive log thread=2 sequence=1012 recid=2037 stamp=636737242
channel ch00: starting piece 1 at 23-OCT-07
channel ch00: finished piece 1 at 23-OCT-07
piece handle=CG_arch_2538_1_20071023 comment=API Version 2.0,MMS Version 5.2.0.0
channel ch00: backup set complete, elapsed time: 00:00:36
released channel: ch00
released channel: ch01
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ch01 channel at 10/23/2007 15:31:09
ORA-19502: write error on file "CG_arch_2537_1_20071023", blockno 4097 (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
Recovery Manager complete.
---------------------
大家帮看看怎么解决
都好几天了作者: yddll 时间: 2007-10-24 22:12
ANS1312E (RC12) Server media mount not possible
在TSM的guide里查这个错误作者: piml_lv 时间: 2007-10-25 10:47
只在有关文档上看到了一下内容：
The data is written to the copy storage pool and primary storage pool
simultaneously. The backup performance will only be as good as the slowest
device being used for any of the pools. There also have to be enough mount
points available; otherwise, only the client, not the server, will issue the
ANS1312E message:
ANS1312E Server media mount not possible作者: w3wu 时间: 2007-10-25 12:05
空间够吗？