RMAN Script Failure
Hi,everybody!
My RMAN script get the following output:
# more mes_czmes02_ora.sh.out
Script /usr/openv/netbackup/dbext/mes_czmes02_ora.sh
==== started on Fri May 11 14:16:45 CST 2012 ====
RMAN: /u1/oracle/product/10gr2/db_1/bin/rman
ORACLE_SID: rac2
ORACLE_USER: oracle
ORACLE_HOME: /u1/oracle/product/10gr2/db_1
NB_ORA_FULL: 1
NB_ORA_INCR: 0
NB_ORA_CINC: 0
NB_ORA_SERV: tsczbak02.trinasolar.com
NB_ORA_POLICY: MES_CZMES02_ORA
Full backup requested
Sun Microsystems Inc. SunOS 5.10 Generic January 2005
You have new mail.
RMAN> 2> 3> 4> 5> 6> 7> 8> 9> 10> 11> 12> 13> 14> 15> 16> 17> 18> 19> 20> 21> 22> 23>
24> 25> 26> 27> 28> 29> 30> 31> 32> 33> 34> 35> 36> 37> 38> RMAN> rget database: RAC
(DBID=2261274443)
using target database control file instead of recovery catalog
RMAN> 2> 3> 4> 5> 6> 7> 8> 9> 10> 11> 12> 13> 14> 15> 16> 17> 18> 19> 20> 21> 22> 23>
24> 25> 26> 27> 28> 29> 30> 31> 32> 33> 34> 35> 36> 37> 38>
allocated channel: ch00
channel ch00: sid=1804 instance=rac2 devtype=SBT_TAPE
channel ch00: Veritas NetBackup for Oracle - Release 7.1 (2011020313)
allocated channel: ch01
channel ch01: sid=1831 instance=rac2 devtype=SBT_TAPE
channel ch01: Veritas NetBackup for Oracle - Release 7.1 (2011020313)
Starting backup at 2012-05-11 14-16-49
channel ch00: starting incremental level 0 datafile backupset
channel ch00: specifying datafile(s) in backupset
input datafile fno=00006 name=+DATA1/rac/datafile/mesproddb00.dbf
input datafile fno=00012 name=+DATA1/rac/datafile/mesproddb04.dbf
input datafile fno=00016 name=+DATA1/rac/datafile/mesproddb08.dbf
input datafile fno=00001 name=+DATA1/rac/datafile/system.dbf
input datafile fno=00002 name=+DATA1/rac/datafile/undotbs1.dbf
channel ch00: starting piece 1 at 2012-05-11 14-16-50
channel ch01: starting incremental level 0 datafile backupset
channel ch01: specifying datafile(s) in backupset
input datafile fno=00025 name=+DATA1/rac/datafile/mesproddb14.dbf
input datafile fno=00033 name=+DATA1/rac/datafile/mesproddb19.dbf
input datafile fno=00019 name=+DATA1/rac/datafile/mesreptdb02.dbf
input datafile fno=00039 name=+DATA1/rac/datafile/undotbs1_3.dbf
input datafile fno=00026 name=+DATA1/rac/datafile/streams01.dbf
channel ch01: starting piece 1 at 2012-05-11 14-16-50
RMAN-03009: failure of backup command on ch00 channel at 05/11/2012 14:17:45
ORA-19506: failed to create sequential file, name="bk_10829_1_783008210", parms=""
ORA-27028: skgfqcre: sbtbackup returned error
ORA-19511: Error received from media manager layer, error text:
VxBSAValidateFeatureId: Failed with error:
Server Status: cannot connect on socket
channel ch00 disabled, job failed on it will be run on another channel
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 05/11/2012 14:17:45
ORA-19506: failed to create sequential file, name="bk_10830_1_783008210", parms=""
ORA-27028: skgfqcre: sbtbackup returned error
ORA-19511: Error received from media manager layer, error text:
VxBSAValidateFeatureId: Failed with error:
Server Status: cannot connect on socket
RMAN>
Recovery Manager complete.
Script /usr/openv/netbackup/dbext/mes_czmes02_ora.sh
==== ended in error on Fri May 11 14:17:45 CST 2012 ====
# more /usr/openv/netbackup/bp.conf
SERVER = tsczbak02
SERVER = tsczbak03
CLIENT_NAME = czmes02
CONNECT_OPTIONS = localhost 1 0 2
# more /usr/openv/netbackup/logs/dbclient ---------> see attached file
NBU 7.1
master server:windows2008R2
client:solaris10 SPARC
Thanks!!
Double-check bp.conf on the client - these entries are read from bp.conf:
dbc_GetServerClientConfig: ServerName: <czmes03>, ClientName: <czmes02>
This says to me that czmes03 is 1st in the SERVER list.
Master server must ALWAYS be 1st in the list. This is how the Client knows where to send backup request.Check 'normal' bp.conf in /usr/openv/netbackup as well as Oracle user's home directory.
The policy is probably hard-coded in (user's) bp.conf as well.