Solved: Backup Oracle 10 + Netbackup 7.5.0.6

lfernandez · ‎10-29-2014

Good morning!

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: 102
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.

Job Detail said me that the specified policy is not of the correct client type(245), but its impossible, because the type its ORACLE and i want to do a ORACLE backup.

THANKS for your work!

----------------------------
----------------------------

The error

----------------------------
----------------------------

The specified policy is not of the correct client type(245)

----------------------------
----------------------------

SCRIPT

----------------------------
----------------------------

@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=G:\oracle\BWP\102

@REM ---------------------------------------------------------------------------
@REM Replace ora81, below, with the Oracle SID.
@REM ---------------------------------------------------------------------------

@set ORACLE_SID=BWP

@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=SAPBWP_ORACLE,NB_ORA_CLIENT=XXXXXXXsbw101.DOMAIN.corp,NB_ORA_SERV=XXXXXXXbkp103';
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=SAPBWP_ORACLE,NB_ORA_CLIENT=XXXXXXXsbw101.DOMAIN.corp,NB_ORA_SERV=XXXXXXXbkp103';
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 -----------------------------------------------------

--------------------------------------
--------------------------------------
LOG
--------------------------------------
--------------------------------------

==== started on Wed 10/29/2014 11:49 ====
Script name: "D:\RMAN\SAPBWP_ORACLE.cmd"
#
RMAN : G:\oracle\BWP\102\bin\rman.exe
NLS_LANG : american
ORACLE_HOME : G:\oracle\BWP\102
ORACLE_SID : BWP
NLS_DATE_FORMAT : YYYY-MM-DD:hh24:mi:ss
RMAN_LOG_FILE : "D:\RMAN\SAPBWP_ORACLE.out"
NB_ORA_SERV : XXXXXXXbkp103
NB_ORA_FULL : 1
NB_ORA_INCR : 0
NB_ORA_CINC : 0
NB_ORA_CLASS : SAPBWP_ORACLE

Recovery Manager: Release 10.2.0.4.0 - Production on Wed Oct 29 11:49:15 2014

connected to target database: BWP (DBID=2517900574)
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=257 devtype=SBT_TAPE
channel ch00: Veritas NetBackup for Oracle - Release 7.5 (20130610)

allocated channel: ch01
channel ch01: sid=248 devtype=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-29:11:49:18
channel ch00: starting incremental level 0 datafile backupset
channel ch00: specifying datafile(s) in backupset
channel ch01: starting incremental level 0 datafile backupset
channel ch01: specifying datafile(s) in backupset
input datafile fno=00019 name=M:\ORACLE\BWP\SAPDATA4\BWP_11\BWP.DATA11
input datafile fno=00025 name=N:\ORACLE\BWP\SAPDATA4\BWP_16\BWP.DATA16
input datafile fno=00045 name=M:\ORACLE\BWP\SAPDATA4\BWP_31\BWP.DATA31
input datafile fno=00047 name=N:\ORACLE\BWP\SAPDATA4\BWP_33\BWP.DATA33
input datafile fno=00049 name=K:\ORACLE\BWP\SAPDATA4\BWP_35\BWP.DATA35
input datafile fno=00070 name=N:\ORACLE\BWP\SAPDATA4\BWP_54\BWP.DATA54
input datafile fno=00093 name=N:\ORACLE\BWP\SAPDATA4\BWP_73\BWP.DATA73
input datafile fno=00095 name=N:\ORACLE\BWP\SAPDATA4\BWP_75\BWP.DATA75
input datafile fno=00022 name=K:\ORACLE\BWP\SAPDATA4\BWP_13\BWP.DATA13
input datafile fno=00024 name=M:\ORACLE\BWP\SAPDATA4\BWP_15\BWP.DATA15
input datafile fno=00028 name=L:\ORACLE\BWP\SAPDATA4\BWP_18\BWP.DATA18
input datafile fno=00030 name=N:\ORACLE\BWP\SAPDATA4\BWP_20\BWP.DATA20
input datafile fno=00032 name=L:\ORACLE\BWP\SAPDATA4\BWP_22\BWP.DATA22
input datafile fno=00034 name=N:\ORACLE\BWP\SAPDATA4\BWP_24\BWP.DATA24
input datafile fno=00036 name=L:\ORACLE\BWP\SAPDATA4\BWP_26\BWP.DATA26
input datafile fno=00038 name=N:\ORACLE\BWP\SAPDATA4\BWP_28\BWP.DATA28
input datafile fno=00002 name=K:\ORACLE\BWP\SAPDATA2\UNDO_1\UNDO.DATA1
input datafile fno=00004 name=L:\ORACLE\BWP\SAPDATA4\BWP_2\BWP.DATA2
input datafile fno=00057 name=L:\ORACLE\BWP\SAPDATA2\UNDO_2\UNDO.DATA2
input datafile fno=00081 name=L:\ORACLE\BWP\SAPDATA2\UNDO_4\UNDO.DATA4
input datafile fno=00090 name=M:\ORACLE\BWP\SAPDATA4\BWP_71\BWP.DATA71
input datafile fno=00051 name=L:\ORACLE\BWP\SAPDATA4\BWP_36\BWP.DATA36
input datafile fno=00053 name=N:\ORACLE\BWP\SAPDATA4\BWP_38\BWP.DATA38
input datafile fno=00055 name=L:\ORACLE\BWP\SAPDATA4\BWP_40\BWP.DATA40
input datafile fno=00058 name=N:\ORACLE\BWP\SAPDATA4\BWP_42\BWP.DATA42
input datafile fno=00061 name=M:\ORACLE\BWP\SAPDATA4\BWP_45\BWP.DATA45
input datafile fno=00063 name=K:\ORACLE\BWP\SAPDATA4\BWP_47\BWP.DATA47
input datafile fno=00065 name=M:\ORACLE\BWP\SAPDATA4\BWP_49\BWP.DATA49
input datafile fno=00067 name=K:\ORACLE\BWP\SAPDATA4\BWP_51\BWP.DATA51
input datafile fno=00069 name=M:\ORACLE\BWP\SAPDATA4\BWP_53\BWP.DATA53
input datafile fno=00072 name=L:\ORACLE\BWP\SAPDATA4\BWP_56\BWP.DATA56
input datafile fno=00074 name=N:\ORACLE\BWP\SAPDATA4\BWP_58\BWP.DATA58
input datafile fno=00076 name=M:\ORACLE\BWP\SAPDATA4\BWP_60\BWP.DATA60
input datafile fno=00083 name=N:\ORACLE\BWP\SAPDATA2\UNDO_5\UNDO.DATA5
input datafile fno=00085 name=N:\ORACLE\BWP\SAPDATA4\BWP_66\BWP.DATA66
input datafile fno=00087 name=N:\ORACLE\BWP\SAPDATA4\BWP_68\BWP.DATA68
input datafile fno=00092 name=K:\ORACLE\BWP\SAPDATA1\SYSAUX_2\SYSAUX.DATA2
input datafile fno=00078 name=L:\ORACLE\BWP\SAPDATA4\BWP_62\BWP.DATA62
input datafile fno=00088 name=N:\ORACLE\BWP\SAPDATA4\BWP_69\BWP.DATA69
input datafile fno=00016 name=N:\ORACLE\BWP\SAPDATA4\BWP_8\BWP.DATA8
input datafile fno=00007 name=L:\ORACLE\BWP\SAPDATA4\BWP640_2\BWP640.DATA2
input datafile fno=00012 name=N:\ORACLE\BWP\SAPDATA4\BWP_4\BWP.DATA4
input datafile fno=00014 name=L:\ORACLE\BWP\SAPDATA4\BWP_6\BWP.DATA6
input datafile fno=00017 name=K:\ORACLE\BWP\SAPDATA4\BWP_9\BWP.DATA9
input datafile fno=00021 name=K:\ORACLE\BWP\SAPDATA4\BWP640_5\BWP640.DATA5
input datafile fno=00039 name=N:\ORACLE\BWP\SAPDATA1\SYSTEM_3\SYSTEM.DATA3
input datafile fno=00011 name=K:\ORACLE\BWP\SAPDATA4\BWPDB_1\BWPDB.DATA1
input datafile fno=00010 name=M:\ORACLE\BWP\SAPDATA4\BWPUSR_1\BWPUSR.DATA1
input datafile fno=00042 name=K:\ORACLE\BWP\SAPDATA4\BWPUSR_2\BWPUSR.DATA2
input datafile fno=00043 name=L:\ORACLE\BWP\SAPDATA4\BWPUSR_3\BWPUSR.DATA3
channel ch01: starting piece 1 at 2014-10-29:11:49:20
including current SPFILE in backupset
including current control file in backupset
input datafile fno=00020 name=N:\ORACLE\BWP\SAPDATA4\BWP_12\BWP.DATA12
input datafile fno=00040 name=K:\ORACLE\BWP\SAPDATA4\BWP_29\BWP.DATA29
input datafile fno=00046 name=N:\ORACLE\BWP\SAPDATA4\BWP_32\BWP.DATA32
input datafile fno=00048 name=K:\ORACLE\BWP\SAPDATA4\BWP_34\BWP.DATA34
input datafile fno=00060 name=L:\ORACLE\BWP\SAPDATA4\BWP_44\BWP.DATA44
input datafile fno=00091 name=L:\ORACLE\BWP\SAPDATA4\BWP_72\BWP.DATA72
input datafile fno=00094 name=N:\ORACLE\BWP\SAPDATA4\BWP_74\BWP.DATA74
input datafile fno=00096 name=N:\ORACLE\BWP\SAPDATA4\BWP_76\BWP.DATA76
input datafile fno=00023 name=L:\ORACLE\BWP\SAPDATA4\BWP_14\BWP.DATA14
input datafile fno=00027 name=K:\ORACLE\BWP\SAPDATA4\BWP_17\BWP.DATA17
input datafile fno=00029 name=M:\ORACLE\BWP\SAPDATA4\BWP_19\BWP.DATA19
input datafile fno=00031 name=K:\ORACLE\BWP\SAPDATA4\BWP_21\BWP.DATA21
input datafile fno=00033 name=M:\ORACLE\BWP\SAPDATA4\BWP_23\BWP.DATA23
input datafile fno=00035 name=K:\ORACLE\BWP\SAPDATA4\BWP_25\BWP.DATA25
input datafile fno=00037 name=M:\ORACLE\BWP\SAPDATA4\BWP_27\BWP.DATA27
input datafile fno=00041 name=L:\ORACLE\BWP\SAPDATA4\BWP_30\BWP.DATA30
input datafile fno=00003 name=K:\ORACLE\BWP\SAPDATA4\BWP_1\BWP.DATA1
input datafile fno=00005 name=M:\ORACLE\BWP\SAPDATA4\BWP_3\BWP.DATA3
input datafile fno=00080 name=M:\ORACLE\BWP\SAPDATA2\UNDO_3\UNDO.DATA3
input datafile fno=00044 name=N:\ORACLE\BWP\SAPDATA1\SYSAUX_1\SYSAUX.DATA1
input datafile fno=00097 name=M:\ORACLE\BWP\SAPDATA4\BWP_77\BWP.DATA77
input datafile fno=00052 name=M:\ORACLE\BWP\SAPDATA4\BWP_37\BWP.DATA37
input datafile fno=00054 name=K:\ORACLE\BWP\SAPDATA4\BWP_39\BWP.DATA39
input datafile fno=00056 name=M:\ORACLE\BWP\SAPDATA4\BWP_41\BWP.DATA41
input datafile fno=00059 name=K:\ORACLE\BWP\SAPDATA4\BWP_43\BWP.DATA43
input datafile fno=00062 name=N:\ORACLE\BWP\SAPDATA4\BWP_46\BWP.DATA46
input datafile fno=00064 name=L:\ORACLE\BWP\SAPDATA4\BWP_48\BWP.DATA48
input datafile fno=00066 name=N:\ORACLE\BWP\SAPDATA4\BWP_50\BWP.DATA50
input datafile fno=00068 name=L:\ORACLE\BWP\SAPDATA4\BWP_52\BWP.DATA52
input datafile fno=00071 name=K:\ORACLE\BWP\SAPDATA4\BWP_55\BWP.DATA55
input datafile fno=00073 name=M:\ORACLE\BWP\SAPDATA4\BWP_57\BWP.DATA57
input datafile fno=00075 name=M:\ORACLE\BWP\SAPDATA4\BWP_59\BWP.DATA59
input datafile fno=00082 name=L:\ORACLE\BWP\SAPDATA4\BWP_64\BWP.DATA64
input datafile fno=00084 name=M:\ORACLE\BWP\SAPDATA4\BWP_65\BWP.DATA65
input datafile fno=00086 name=N:\ORACLE\BWP\SAPDATA4\BWP_67\BWP.DATA67
input datafile fno=00089 name=N:\ORACLE\BWP\SAPDATA4\BWP_70\BWP.DATA70
input datafile fno=00077 name=M:\ORACLE\BWP\SAPDATA4\BWP_61\BWP.DATA61
input datafile fno=00079 name=L:\ORACLE\BWP\SAPDATA4\BWP_63\BWP.DATA63
input datafile fno=00099 name=L:\ORACLE\BWP\SAPDATA4\BWP640_7\BWP640.DATA7
input datafile fno=00006 name=K:\ORACLE\BWP\SAPDATA4\BWP640_1\BWP640.DATA1
input datafile fno=00008 name=M:\ORACLE\BWP\SAPDATA4\BWP640_3\BWP640.DATA3
input datafile fno=00013 name=K:\ORACLE\BWP\SAPDATA4\BWP_5\BWP.DATA5
input datafile fno=00015 name=M:\ORACLE\BWP\SAPDATA4\BWP_7\BWP.DATA7
input datafile fno=00018 name=L:\ORACLE\BWP\SAPDATA4\BWP_10\BWP.DATA10
input datafile fno=00050 name=L:\ORACLE\BWP\SAPDATA4\BWP640_6\BWP640.DATA6
input datafile fno=00098 name=N:\ORACLE\BWP\SAPDATA1\SYSTEM_4\SYSTEM.DATA4
input datafile fno=00009 name=N:\ORACLE\BWP\SAPDATA4\BWP640_4\BWP640.DATA4
input datafile fno=00001 name=N:\ORACLE\BWP\SAPDATA1\SYSTEM_1\SYSTEM.DATA1
input datafile fno=00026 name=N:\ORACLE\BWP\SAPDATA1\SYSTEM_2\SYSTEM.DATA2
channel ch00: starting piece 1 at 2014-10-29:11:49:22
RMAN-03009: failure of backup command on ch01 channel at 10/29/2014 11:49:25
ORA-19506: failed to create sequential file, name="bk_u6qpm93lv_s16602_p1_t862228159", 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 policy is not of the correct client type
channel ch01 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 ch00 channel at 10/29/2014 11:49:28
ORA-19506: failed to create sequential file, name="bk_u6ppm93lv_s16601_p1_t862228159", 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 policy is not of the correct client type

RMAN>

Recovery Manager complete.
#

lfernandez · ‎11-03-2014

Thanks for all.

I resolved the problem, we upgrade the version of the database 10 to 11.

Change in the Environments Variables:

ORACLE_SID = empty to BWP (name of the DB)

ORACLE_HOME = G:\oracle\BWP\102 to G:\oracle\BWP\11102

and the backup works fine.

Thanks for your replies!

View solution in original post

lfernandez · ‎10-29-2014

Policy Name: SAPBWP_ORACLE
Options: 0x0
template: FALSE
audit_reason: ?
Names: (none)
Policy Type: Oracle (4)
Active: yes
Effective date: 09/30/2014 12:06:49
Block Incremental: no
Mult. Data Stream: no
Perform Snapshot Backup: no
Snapshot Method: (none)
Snapshot Method Arguments: (none)
Perform Offhost Backup: no
Backup Copy: 0
Use Data Mover: no
Data Mover Type: 2
Use Alternate Client: no
Alternate Client Name: (none)
Use Virtual Machine: 0
Hyper-V Server Name: (none)
Enable Instant Recovery: no
Policy Priority: 0
Max Jobs/Policy: Unlimited
Disaster Recovery: 0
Collect BMR Info: no
Keyword: (none specified)
Data Classification: -
Residence is Storage Lifecycle Policy: no
Client Encrypt: no
Checkpoint: no
Residence: stu_disk_XXXXXXXbkp103
Volume Pool: NetBackup
Server Group: *ANY*
Granular Restore Info: no
Exchange Source attributes: no
Exchange DAG Preferred Server: (none defined)
Application Discovery: no
Discovery Lifetime: 28800 seconds
ASC Application and attributes: (none defined)
Generation: 17
Ignore Client Direct: no
Enable Metadata Indexing: no
Index server name: NULL
Use Accelerator: no
Client/HW/OS/Pri/DMI: XXXXXXXsbw101.DOMAIN.corp Windows-x64 Windows2003 0 0 0 0 ?
Include: D:\RMAN\SAPBWP_ORACLE.cmd
Schedule: Default-Application-Backup
Type: UBAK Obak (2)
Frequency: 7 day(s) (604800 seconds)
Maximum MPX: 1
Synthetic: 0
Checksum Change Detection: 0
PFI Recovery: 0
Retention Level: 3 (1 month)
u-wind/o/d: 0 0
Incr Type: DELTA (0)
Alt Read Host: (none defined)
Max Frag Size: 0 MB
Number Copies: 1
Fail on Error: 0
Residence: (specific storage unit not required)
Volume Pool: (same as policy volume pool)
Server Group: (same as specified for policy)
Residence is Storage Lifecycle Policy: 0
Schedule indexing: 0
Daily Windows:
Day Open Close W-Open W-Close
Sunday 000:00:00 024:00:00 000:00:00 024:00:00
Monday 000:00:00 024:00:00 024:00:00 048:00:00
Tuesday 000:00:00 024:00:00 048:00:00 072:00:00
Wednesday 000:00:00 024:00:00 072:00:00 096:00:00
Thursday 000:00:00 024:00:00 096:00:00 120:00:00
Friday 000:00:00 024:00:00 120:00:00 144:00:00
Saturday 000:00:00 024:00:00 144:00:00 168:00:00
Schedule: SEMANAL
Type: FULL SObk (0)
Frequency: 7 day(s) (604800 seconds)
Maximum MPX: 1
Synthetic: 0
Checksum Change Detection: 0
PFI Recovery: 0
Retention Level: 1 (2 weeks)
u-wind/o/d: 0 0
Incr Type: DELTA (0)
Alt Read Host: (none defined)
Max Frag Size: 0 MB
Number Copies: 1
Fail on Error: 0
Residence: (specific storage unit not required)
Volume Pool: (same as policy volume pool)
Server Group: (same as specified for policy)
Residence is Storage Lifecycle Policy: 0
Schedule indexing: 0
Daily Windows:
Day Open Close W-Open W-Close
Sunday 000:00:00 000:00:00
Monday 000:00:00 000:00:00
Tuesday 000:00:00 000:00:00
Wednesday 000:00:00 000:00:00
Thursday 000:00:00 000:00:00
Friday 000:00:00 000:00:00
Saturday 000:00:00 018:30:00 144:00:00 162:30:00
Schedule: DIARIO
Type: CINC (4)
Frequency: 1 day(s) (86400 seconds)
Maximum MPX: 1
Synthetic: 0
Checksum Change Detection: 0
PFI Recovery: 0
Retention Level: 1 (2 weeks)
u-wind/o/d: 0 0
Incr Type: DELTA (0)
Alt Read Host: (none defined)
Max Frag Size: 0 MB
Number Copies: 1
Fail on Error: 0
Residence: (specific storage unit not required)
Volume Pool: (same as policy volume pool)
Server Group: (same as specified for policy)
Residence is Storage Lifecycle Policy: 0
Schedule indexing: 0
Daily Windows:
Day Open Close W-Open W-Close
Sunday 000:00:00 010:00:00 000:00:00 010:00:00
Monday 000:00:00 010:00:00 024:00:00 034:00:00
Tuesday 000:00:00 010:00:00 048:00:00 058:00:00
Wednesday 000:00:00 010:00:00 072:00:00 082:00:00
Thursday 000:00:00 010:00:00 096:00:00 106:00:00
Friday 000:00:00 010:00:00 120:00:00 130:00:00
Saturday 000:00:00 000:00:00

C:\Program Files\Veritas\NetBackup\bin\admincmd>

Marianne · ‎10-30-2014

Try to use a SAP policy instead.

See NetBackup for SAP Administrator's Guide for instruction on how to use RMAN with SAP.

Look for this topic: Using NetBackup for SAP on Oracle databases with RMAN

To verify compatibility, see
NetBackup 7 Application/Database Agent (CL): http://www.symantec.com/docs/TECH126904

Handy NetBackup Links

jim_dalton · ‎10-31-2014

Yes its a SAP instance you are backing up, that is running Oracle, so you need the SAP agent, license etc etc. You will need to read the manual, its not plug and play, but works a treat.

Jim

lfernandez · ‎11-03-2014

Thanks for all.

I resolved the problem, we upgrade the version of the database 10 to 11.

Change in the Environments Variables:

ORACLE_SID = empty to BWP (name of the DB)

ORACLE_HOME = G:\oracle\BWP\102 to G:\oracle\BWP\11102

and the backup works fine.

Thanks for your replies!

jim_dalton · ‎11-03-2014

I would make 100% sure this is the correct way to backup your data which does appear to be sap db. I'm not saying it doesnt work I'm saying be certain its totally recoverable.

This does present an interesting thought: if one can backup SAP correctly using the Oracle agent, then why would we buy the SAP agent when the Oracle one is as I recall rather more attractively priced?

VOX

Backup Oracle 10 + Netbackup 7.5.0.6