PROBLEM - Backup ORACLE 11 + Symantec Netbackup 7.5.0.6
Hi all!
I have a problem with a Oracle Backup.
I tried to realize a FULL backup but appears a problem. I dont know if it isn´t compatible or what?
Windows Server 2003 ServicePack 2
Version DB: 11203
Symantec Netbackup Server: 7.5.0.6
Version of the client in the server: 7.5.0.6
I check the conectivity between the appliance and the server and everything its ok.
THANKS for your work!
The error:
==== started on 24/10/2014 11:00 ====
Script name: "D:\RMAN\SAPSMP_ORACLE.cmd"
#
RMAN : D:\oracle\SMP\11203\bin\rman.exe
NLS_LANG : american
ORACLE_HOME : D:\oracle\SMP\11203
ORACLE_SID : SMP
NLS_DATE_FORMAT : YYYY-MM-DD:hh24:mi:ss
RMAN_LOG_FILE : "D:\RMAN\SAPSMP_ORACLE.out"
NB_ORA_SERV : bkp103
NB_ORA_FULL : 1
NB_ORA_INCR : 0
NB_ORA_CINC : 0
NB_ORA_CLASS : SAPSSM_ORACLE
Recovery Manager: Release 11.2.0.3.0 - Production on Fri Oct 24 11:00:44 2014
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
connected to target database: SMP (DBID=584291626)
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>
allocated channel: ch00
channel ch00: SID=147 device type=SBT_TAPE
channel ch00: Veritas NetBackup for Oracle - Release 7.5 (20130610)
allocated channel: ch01
channel ch01: SID=31 device type=SBT_TAPE
channel ch01: Veritas NetBackup for Oracle - Release 7.5 (20130610)
sent command to channel: ch00
sent command to channel: ch01
Starting backup at 2014-10-24:11:00:47
channel ch00: starting incremental level 0 datafile backup set
channel ch00: specifying datafile(s) in backup set
input datafile file number=00017 name=E:\ORACLE\SMP\SAPDATA3\SR3700_4\SR3700.DATA4
input datafile file number=00002 name=E:\ORACLE\SMP\SAPDATA1\UNDO_1\UNDO.DATA1
input datafile file number=00016 name=E:\ORACLE\SMP\SAPDATA3\SR3700_3\SR3700.DATA3
input datafile file number=00009 name=E:\ORACLE\SMP\SAPDATA2\SR3_6\SR3.DATA6
input datafile file number=00008 name=E:\ORACLE\SMP\SAPDATA2\SR3_5\SR3.DATA5
input datafile file number=00012 name=E:\ORACLE\SMP\SAPDATA2\SR3_9\SR3.DATA9
input datafile file number=00004 name=E:\ORACLE\SMP\SAPDATA2\SR3_1\SR3.DATA1
input datafile file number=00013 name=E:\ORACLE\SMP\SAPDATA2\SR3_10\SR3.DATA10
input datafile file number=00022 name=E:\ORACLE\SMP\SAPDATA2\SR3_11\SR3.DATA11
input datafile file number=00020 name=E:\ORACLE\SMP\SAPDATA4\SR3DB_2\SR3DB.DATA2
input datafile file number=00018 name=E:\ORACLE\SMP\SAPDATA4\SR3USR_1\SR3USR.DATA1
input datafile file number=00003 name=E:\ORACLE\SMP\SAPDATA1\SYSAUX_1\SYSAUX.DATA1
channel ch00: starting piece 1 at 2014-10-24:11:00:48
channel ch01: starting incremental level 0 datafile backup set
channel ch01: specifying datafile(s) in backup set
input datafile file number=00023 name=E:\ORACLE\SMP\SAPDATA3\SR3700_5\SR3700.DATA5
input datafile file number=00015 name=E:\ORACLE\SMP\SAPDATA3\SR3700_2\SR3700.DATA2
input datafile file number=00014 name=E:\ORACLE\SMP\SAPDATA3\SR3700_1\SR3700.DATA1
input datafile file number=00007 name=E:\ORACLE\SMP\SAPDATA2\SR3_4\SR3.DATA4
input datafile file number=00010 name=E:\ORACLE\SMP\SAPDATA2\SR3_7\SR3.DATA7
input datafile file number=00011 name=E:\ORACLE\SMP\SAPDATA2\SR3_8\SR3.DATA8
input datafile file number=00006 name=E:\ORACLE\SMP\SAPDATA2\SR3_3\SR3.DATA3
input datafile file number=00005 name=E:\ORACLE\SMP\SAPDATA2\SR3_2\SR3.DATA2
input datafile file number=00019 name=E:\ORACLE\SMP\SAPDATA4\SR3DB_1\SR3DB.DATA1
input datafile file number=00021 name=E:\ORACLE\SMP\SAPDATA4\SR3DB_3\SR3DB.DATA3
input datafile file number=00001 name=E:\ORACLE\SMP\SAPDATA1\SYSTEM_1\SYSTEM.DATA1
channel ch01: starting piece 1 at 2014-10-24:11:00:48
RMAN-03009: failure of backup command on ch00 channel at 10/24/2014 11:00:55
ORA-19506: failed to create sequential file, name="bk_ugaplrqv0_s17930_p1_t861793248", parms=""
ORA-27028: skgfqcre: sbtbackup returned error
ORA-19511: Error received from media manager layer, error text:
VxBSACreateObject: Failed with error:
Server Status: the specified client does not exist in the specified policy
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 10/24/2014 11:00:55
ORA-19506: failed to create sequential file, name="bk_ugbplrqv0_s17931_p1_t861793248", parms=""
ORA-27028: skgfqcre: sbtbackup returned error
ORA-19511: Error received from media manager layer, error text:
VxBSACreateObject: Failed with error:
Server Status: the specified client does not exist in the specified policy
RMAN>
Recovery Manager complete.
#
--------------------
--------------------
--------------------
--------------------
-------------------------------------------------------------------------------------------
-------------------------------------------------------------------------------------------
My script to do the backup.
-------------------------------------------------------------------------------------------
-------------------------------------------------------------------------------------------
@REM $Header: hot_database_backup.cmd,v 1.3 2005/11/28 19:01:53 $
@REM bcpyrght
@REM ***************************************************************************
@REM * $VRTScprght: Copyright 1993 - 2007 Symantec Corporation, All Rights Reserved $ *
@REM ***************************************************************************
@REM ecpyrght
@REM
@REM ---------------------------------------------------------------------------
@REM hot_database_backup.cmd
@REM ---------------------------------------------------------------------------
@REM This script uses Recovery Manager to take a hot (inconsistent) database
@REM backup. A hot backup is inconsistent because portions of the database are
@REM being modified and written to the disk while the backup is progressing.
@REM You must run your database in ARCHIVELOG mode to make hot backups.
@REM
@REM NOTE information for running proxy backups has been included. These
@REM information sections begin with a comment line of PROXY
@REM ---------------------------------------------------------------------------
@setlocal ENABLEEXTENSIONS
@REM ---------------------------------------------------------------------------
@REM No need to echo the commands.
@REM ---------------------------------------------------------------------------
@echo off
@REM ---------------------------------------------------------------------------
@REM Put output in the same filename, different extension.
@REM ---------------------------------------------------------------------------
@set RMAN_LOG_FILE="%~dpn0.out"
@REM ---------------------------------------------------------------------------
@REM You may want to delete the output file so that backup information does
@REM not accumulate. If not, delete the following command.
@REM ---------------------------------------------------------------------------
@if exist %RMAN_LOG_FILE% del %RMAN_LOG_FILE%
@REM ---------------------------------------------------------------------------
@REM Replace H:\oracle\ora81, below, with the Oracle home path.
@REM ---------------------------------------------------------------------------
@set ORACLE_HOME=D:\oracle\SMP\11203
@REM ---------------------------------------------------------------------------
@REM Replace ora81, below, with the Oracle SID.
@REM ---------------------------------------------------------------------------
@set ORACLE_SID=SMP
@REM ---------------------------------------------------------------------------
@REM Replace sys/manager, below, with the target connect string.
@REM ---------------------------------------------------------------------------
@set TARGET_CONNECT_STR="/"
@REM ---------------------------------------------------------------------------
@REM Set the Oracle Recovery Manager.
@REM ---------------------------------------------------------------------------
@set RMAN=%ORACLE_HOME%\bin\rman.exe
@REM ---------------------------------------------------------------------------
@REM PROXY
@REM For a PROXY backup, uncomment the line below and replace the value.
@REM
@REM NB_ORA_PC_STREAMS - specifies the number of parallel backup streams
@REM to be started.
@REM ---------------------------------------------------------------------------
@REM @set NB_ORA_PC_STREAMS=3
@REM ---------------------------------------------------------------------------
@REM Log the start of this scripts.
@REM ---------------------------------------------------------------------------
@for /F "tokens=1*" %%p in ('date /T') do @set DATE=%%p %%q
@for /F %%p in ('time /T') do @set DATE=%DATE% %%p
@echo ==== started on %DATE% ==== >> %RMAN_LOG_FILE%
@echo Script name: %0 >> %RMAN_LOG_FILE%
@REM ---------------------------------------------------------------------------
@REM Several RMAN commands use time parameters that require NLS_LANG and
@REM NLS_DATE_FORMAT to be set. This example uses the standard date format.
@REM Replace below with the desired language values.
@REM ---------------------------------------------------------------------------
@set NLS_LANG=american
@set NLS_DATE_FORMAT=YYYY-MM-DD:hh24:mi:ss
@REM ---------------------------------------------------------------------------
@REM Print out environment variables set in this script.
@REM ---------------------------------------------------------------------------
@echo # >> %RMAN_LOG_FILE%
@echo RMAN : %RMAN% >> %RMAN_LOG_FILE%
@echo NLS_LANG : %NLS_LANG% >> %RMAN_LOG_FILE%
@echo ORACLE_HOME : %ORACLE_HOME% >> %RMAN_LOG_FILE%
@echo ORACLE_SID : %ORACLE_SID% >> %RMAN_LOG_FILE%
@echo NLS_DATE_FORMAT : %NLS_DATE_FORMAT% >> %RMAN_LOG_FILE%
@echo RMAN_LOG_FILE : %RMAN_LOG_FILE% >> %RMAN_LOG_FILE%
@REM ---------------------------------------------------------------------------
@REM PROXY
@REM For a PROXY backup, uncomment the line below.
@REM ---------------------------------------------------------------------------
@REM @echo NB_ORA_PC_STREAMS : %NB_ORA_PC_STREAMS% >> %RMAN_LOG_FILE%
@REM ---------------------------------------------------------------------------
@REM Print out environment variables set in bphdb.
@REM ---------------------------------------------------------------------------
@echo NB_ORA_SERV : %NB_ORA_SERV% >> %RMAN_LOG_FILE%
@echo NB_ORA_FULL : %NB_ORA_FULL% >> %RMAN_LOG_FILE%
@echo NB_ORA_INCR : %NB_ORA_INCR% >> %RMAN_LOG_FILE%
@echo NB_ORA_CINC : %NB_ORA_CINC% >> %RMAN_LOG_FILE%
@echo NB_ORA_CLASS : %NB_ORA_CLASS% >> %RMAN_LOG_FILE%
@REM ---------------------------------------------------------------------------
@REM We assume that the database is properly opened. If desired, this would
@REM be the place to verify that.
@REM ---------------------------------------------------------------------------
@REM ---------------------------------------------------------------------------
@REM If this script is executed from a NetBackup schedule, NetBackup
@REM sets an NB_ORA environment variable based on the schedule type.
@REM For example, when:
@REM schedule type is BACKUP_TYPE is
@REM ---------------- --------------
@REM Automatic Full INCREMENTAL LEVEL=0
@REM Automatic Differential Incremental INCREMENTAL LEVEL=1
@REM Automatic Cumulative Incremental INCREMENTAL LEVEL=1 CUMULATIVE
@REM
@REM For user initiated backups, BACKUP_TYPE defaults to incremental
@REM level 0 (Full). To change the default for a user initiated
@REM backup to incremental or incrementatl cumulative, uncomment
@REM one of the following two lines.
@REM @set BACKUP_TYPE="INCREMENTAL LEVEL=1"
@REM @set BACKUP_TYPE="INCREMENTAL LEVEL=1 CUMULATIVE"
@REM
@REM Note that we use incremental level 0 to specify full backups.
@REM That is because, although they are identical in content, only
@REM the incremental level 0 backup can have incremental backups of
@REM level > 0 applied to it.
@REM ---------------------------------------------------------------------------
@REM ---------------------------------------------------------------------------
@REM What kind of backup will we perform.
@REM ---------------------------------------------------------------------------
@if "%NB_ORA_FULL%" EQU "1" @set BACKUP_TYPE=INCREMENTAL Level=0
@if "%NB_ORA_INCR%" EQU "1" @set BACKUP_TYPE=INCREMENTAL Level=1
@if "%NB_ORA_CINC%" EQU "1" @set BACKUP_TYPE=INCREMENTAL Level=1 CUMULATIVE
@if NOT DEFINED BACKUP_TYPE @set BACKUP_TYPE=INCREMENTAL Level=0
@REM ---------------------------------------------------------------------------
@REM Call Recovery Manager to initiate the backup. This example does not use a
@REM Recovery Catalog. If you choose to use one, remove the option, nocatalog,
@REM from the rman command line below and add a
@REM 'rcvcat <userid>/<passwd>@<tns alias>' statement.
@REM
@REM NOTE WHEN USING TNS ALIAS: When connecting to a database
@REM using a TNS alias, you must use a send command or a parms operand to
@REM specify environment variables. In other words, when accessing a database
@REM through a listener, the environment variables set at the system level are not
@REM visible when RMAN is running. For more information on the environment
@REM variables, please refer to the NetBackup for Oracle Admin. Guide.
@REM
@REM If you are getting an error that the input line is too long, you will need
@REM to put the RMAN run block in a separate file. Then use the "cmdfile"
@REM option of RMAN. For more information on the "cmdfile" options please
@REM refer to the RMAN documentation.
@REM ---------------------------------------------------------------------------
@REM ---------------------------------------------------------------------------
@REM PROXY
@REM For a PROXY backup, you must use a send command to specify
@REM the NB_ORA_PC_STREAMS environment variable. For example,
@REM echo ALLOCATE CHANNEL ch01 TYPE 'SBT_TAPE';
@REM echo SEND 'NB_ORA_PC_STREAMS=%%NB_ORA_PC_STREAMS%%';
@REM
@REM %BACKUP_TYPE% must also be removed and replaced with the PROXY parameter
@REM in the RMAN section associated with the data files. For example,
@REM echo BACKUP
@REM echo PROXY
@REM echo FORMAT 'bk_u%%u_s%%s_p%%p_t%%t'
@REM echo DATABASE;
@REM .
@REM .
@REM Note that the controlfiles and archivelogs are not backed up using proxy
@REM copy method. Rman will initiate non-proxy copy sessions to backup the
@REM controlfile and archivelogs.
@REM ---------------------------------------------------------------------------
@(
echo RUN {
echo ALLOCATE CHANNEL ch00 TYPE 'SBT_TAPE';
echo ALLOCATE CHANNEL ch01 TYPE 'SBT_TAPE';
echo SEND 'NB_ORA_POLICY=SAPSR3_ORACLE,NB_ORA_CLIENT=XXXXXXXXssm001.DOMAIN.corp,NB_ORA_SERV=bkp103';
echo BACKUP
echo %BACKUP_TYPE%
echo FORMAT 'bk_u%%u_s%%s_p%%p_t%%t'
echo DATABASE;
echo sql 'alter system archive log current';
echo RELEASE CHANNEL ch00;
echo RELEASE CHANNEL ch01;
echo # Backup all archive logs
echo ALLOCATE CHANNEL ch00 TYPE 'SBT_TAPE';
echo SEND 'NB_ORA_POLICY=SAPSR3_ORACLE,NB_ORA_CLIENT=XXXXXXXXssm001.DOMAIN.corp,NB_ORA_SERV=bkp103';
echo BACKUP
echo FILESPERSET 20
echo FORMAT 'arch-s%%s-p%%p'
echo ARCHIVELOG ALL DELETE INPUT;
echo RELEASE CHANNEL ch00;
echo ALLOCATE CHANNEL dev1 TYPE Disk;
echo COPY CURRENT CONTROLFILE TO '%ORACLE_HOME%\fic_ctrl_%ORACLE_SID%.ctl';
echo RELEASE CHANNEL dev1;
echo }
) | %RMAN% target %TARGET_CONNECT_STR% nocatalog msglog '%RMAN_LOG_FILE%' append
@set ERRLEVEL=%ERRORLEVEL%
@REM ---------------------------------------------------------------------------
@REM NetBackup (bphdb) stores the name of a file in an environment variable,
@REM called STATUS_FILE. This file is used by an automatic schedule to
@REM communicate status information with NetBackup's job monitor. It is up to
@REM the script to write a 0 (passed) or 1 (failure) to the status file.
@REM ---------------------------------------------------------------------------
@if %ERRLEVEL% NEQ 0 @goto err
@set LOGMSG=ended successfully
@if "%STATUS_FILE%" EQU "" goto end
@echo 0 > "%STATUS_FILE%"
@goto end
:err
@set LOGMSG=ended in error
@if "%STATUS_FILE%" EQU "" @goto end
@echo 1 > "%STATUS_FILE%"
:end
@REM ---------------------------------------------------------------------------
@REM Log the completion of this script.
@REM ---------------------------------------------------------------------------
@for /F "tokens=1*" %%p in ('date /T') do @set DATE=%%p %%q
@for /F %%p in ('time /T') do @set DATE=%DATE% %%p
@echo # >> %RMAN_LOG_FILE%
@echo %==== %LOGMSG% on %DATE% ==== >> %RMAN_LOG_FILE%
@endlocal
@REM End of Main Program -----------------------------------------------------
Seems to me that it is mismatch between policies, NB_ORA_POLICY=SAPSR3_ORACLE in the script and SAPSSM_ORACLE in the job details. Think a correction of the NB_ORA_POLICY to SAPSSM_ORACLE would solve this
