Can't backup SAP on AIX with Netbackup 6.5.4 on Windows.

[Apitha]

I had follow the document NetBackup for SAp administrator on UNIX

I use method as backup SAP without RMAN.

I had copy sap_online_backup from netbackup to another path and change orasap to oradev.

I already had use link backint from netbackup to backint in SAP.

I had copy initSAP.sap and initSAP.utl from netbackup to $ORACLE_HOME/dbs and then change to initDEV.sap and initDEV.utl

I had change initDEV.sap as:


---------------------------------- START FILE -----------------------------------------------------------------------------------

# @(#)initD22.netb.sap    20.9.6.1    SAP    94/10/25
########################################################################
#                                                                      #
# SAP backup profile for Veritas Netbackup.            #
#bcpyrght
#***************************************************************************
#* $VRTScprght: Copyright 1993 - 2008 Symantec Corporation, All Rights Reserved $ *
#***************************************************************************
#ecpyrght
# The parameter syntax is the same as for init.ora parameters.         #
# Enclose parameter values which consist of more than one symbol in    #
# double quotes.                                                       #
# After any symbol, parameter definition can be continued on the next  #
# line.                                                                #
# A parameter value list should be enclosed in parentheses, the list   #
# items should be delimited by commas.                                 #
# There can be any number of white spaces (blanks, tabs and new lines) #
# between symbols of parameter definition.                             #
#                                                                      #
########################################################################

# backup device type
# [disk | tape | tape_auto | pipe | pipe_auto | util_file | util_vol]
# default: tape
#backup_dev_type = tape
backup_dev_type = util_file

# backup mode [all | <tablespaces_name> | (<tablespace_name_list>)]
# default: all
backup_mode = all
#backup_mode = (PSAPUSER1D,PSAPUSER1I,PSAPCLUI)

# backup type [offline | offline_force | online]
# default: offline
#backup_type = offline
backup_type = online

# backup root directory [<path_name> | (<path_name_list>)]
# default: $ORACLE_HOME/sapbackup
backup_root_dir = /oracle/DEV/sapbackup

# compression flag [yes | no | hardware | only]
# default: no
compress = no

# compress command
# first $-character is replaced with the source file name
# second $-character is replaced with the target file name
# <target_file_name> = <source_file_name>.Z
# for compress command the -c option must be set
# !!! enclose the parameter value in double quotes !!!
# no default
compress_cmd = "compress -c $ > $"

# temporary directory for compression
# default: value of the backup_root_dir parameter
compress_dir = /oracle/DEV/sapreorg

# flags for cpio command
# default: -ovB
cpio_flags = -ovB

# remote shell command (backup_dev_type = pipe)
# !!! enclose the parameter value in double quotes !!!
# !!! do not include pipe character "|" in the parameter value !!!
# !!! do not include dd command in the parameter value !!!
# !!! use copy_in_cmd and copy_out_cmd parameters instead !!!
# no default
# HP-UX:  "remsh hs0001" or "remsh hs0001 -l orac11"
# OSF1:   "rsh ds0011"   or "rsh ds0011 -l orac11"
# AIX:    "remsh is0001" or "remsh is0001 -l orac11"
# SINIX:  "rsh ss0001"   or "rsh ss0001 -l orac11"
# SUN:    "rsh us0001"   or "rsh us0001 -l orac11"
# DGUX:   "rsh gs0001"   or "rsh gs0001 -l orac11"
# NT:     "rsh xs0001"   or "rsh xs0001 -l orac11"
read_fifo_cmd = "rsh us0001"

# remote copy-in command (backup_dev_type = pipe)
# $-character is replaced with current tape address
# !!! use copy_in_cmd to define the dd command for tape reading !!!
# !!! enclose the parameter value in double quotes !!!
# no default
copy_in_cmd = "dd bs=5k if=$"

# remote copy-out command (backup_dev_type = pipe)
# $-character is replaced with current tape address
# !!! use copy_out_cmd to define the dd command for tape writing !!!
# !!! enclose the parameter value in double quotes !!!
# no default
copy_out_cmd = "dd bs=5k of=$"

# rewind command (operating system dependent)
# $-character is replaced with current tape address
# !!! enclose the parameter value in double quotes !!!
# no default
# HP-UX:  "mt -t $ rew"
# OSF1:   "mt -f $ rew"
# AIX:    "tctl -f $ rewind"
# SINIX:  "mt -f $ rew"
# SUN:    "mt -f $ rew"
# DGUX:   "mt -f $ rewind"
# NT:     "mt -f $ rewind"
rewind = "mt -f $ rew"

# rewind set offline command (operating system dependent)
# $-character is replaced with current tape address
# !!! enclose the parameter value in double quotes !!!
# default: value of the rewind parameter
# HP-UX:  "mt -t $ offl"
# OSF1:   "mt -f $ offline"
# AIX:    "tctl -f $ offline"
# SINIX:  "mt -f $ offline"
# SUN:    "mt -f $ offline"
# DGUX:   "mt -f $ offline"
# NT:     "mt -f $ offline"
rewind_offline = "mt -f $ offline"

# tape size in KB = K or in MB = M (tape device dependent)
# !!! do not put spaces between the number and 'K' or 'M' !!!
# default: 1200M
# recommended values for tape devices without hardware compression:
# 60 m   4 mm  DAT tape:    1200M
# 90 m   4 mm  DAT tape:    1800M
# 120 m  4 mm  DAT tape:    2400M
# 112 m  8 mm  Video tape:  2000M
# recommended values for tape devices with hardware compression:
# 60 m   4 mm  DAT tape:    1000M
# 90 m   4 mm  DAT tape:    1600M
# 120 m  4 mm  DAT tape:    2200M
# 112 m  8 mm  Video tape:  1800M
# HP-UX:  1200M
# OSF1:   1200M
# AIX:    2000M
# SINIX:  2000M
# SUN:    1200M
# DGUX:   1200M
# NT:     1200M
tape_size = 800G

# address of tape device without rewind [<dev_addr> | (<dev_addr_list>)]
# no default
# HP-UX:  /dev/rmt/0mn
# OSF1:   /dev/nrmt0h
# AIX:    /dev/rmt0.1
# SINIX:  /dev/ios0/rstape005n
# SUN:    /dev/rmt/0mn
# DGUX:   /dev/rmt/0n
# NT:     \\.\tape0
#tape_address = /dev/rmt/3mn

# address of tape device with rewind [<dev_addr> | (<dev_addr_list>)]
# no default
# HP-UX:  /dev/rmt/0m
# OSF1:   /dev/rmt0h
# AIX:    /dev/rmt0
# SINIX:  /dev/ios0/rstape005
# SUN:    /dev/rmt/0m
# DGUX:   /dev/rmt/0
# NT:     /dev/mt0
#tape_address_rew = /dev/rmt/3m

# tape volumes for brarchive
# [<volume_name> | (<volume_name_list>) | SCRATCH]
# no default
#volume_archive = (859AFV)

# tape volumes for brbackup
# [<volume_name> | (<volume_name_list>) | SCRATCH]
# no default
#volume_backup = (Daily-Monday)

# expiration period in days for tape volumes
# default: 30
expir_period = 30

# recommended use count of tape volumes
# default: 100
tape_use_count = 100

# backup utility parameter file
# default: no parameter file
# util_par_file = ?/dbs/init@.utl
util_par_file = /oracle/DEV/102_64/dbs/initDEV.utl

---------------------------- END FILE --------------------------------------------------------------

and edit initDEV.utl as :


-------------------------- START FILE --------------------------------------------------------------

# $Header: initSAP.utl,v 1.8 2006/08/31 13:26:01 $
#
#********************************************************************************
# $Copyright: Copyright 1993 - 2008 Symantec Corporation, All Rights Reserved $ *
#********************************************************************************
#
# backint parameters
#
# switch_list: is required and is used as a control file to communicate with
# BACKINT and BRBACKUP for online backups.  A switch list file is created
# every time BRBACKUP wants to backup a file or when it wants to indicate that
# a backup is finished.  The switch_list parameter must be set to a file path
# that is located in: $ORACLE_HOME/sapbackup/.switch.lis.
#
switch_list /oracle/DEV/sapbackup/.switch.lis
#
#
# switch_sem: is required and is used as a control file which is used between
# BACKINT and BRBACKUP to communicate.  After the switch list file has been
# created and closed, BACKINT creates the switch semaphore file and waits until
# it is deleted by BRBACKUP.  The switch_sem parameter must be set to a file
# path that is located in: $ORACLE_HOME/sapbackup/.switch.sem.
#
switch_sem /oracle/DEV/sapbackup/.switch.sem
#
#
# switch_log: is required and is used as a control file which is used between
# BACKINT and BRBACKUP to communicate.  After the switch semaphore file has
# been deleted, BACKINT opens and reads the switch log file to determine if
# the process is successful.  The switch log file is created by BRBACKUP.  The
# switch_log parameter must be set to a file path that is located in:
# $ORACLE_HOME/sapbackup/.switch_log.
#
switch_log /oracle/DEV/sapbackup/.switch.log
#
#
# backint_dir: is an optional parameter and must be set to a directory that is
# public.  BACKINT uses this directory for work space and to store files called
# backint.times, which keeps track of backup information.
#
backint_dir /usr/openv/netbackup/logs/backint
#
#
# server: is an optional parameter and is the machine name of the NetBackup
# Master server.   The NetBackup Master server is the name of the machine that
# provides most of the administration and control for Netbackup operations and
# contains the NetBackup database.  If BACKINT finds a $SAP_SERVER environment
# variable, the server parameter's value will be overriden by the value of
# $SAP_SERVER. Also, if the server parameter is not specified and there is
# no environment variable then the currently configured server for
# the NetBackup Client will be used.
#
server SFSITSV04
#
#
# client: is an optional parameter and must be set to a machine name that has
# the NetBackup client software, an Oracle database, and a SAP environment. 
# In some cases the server and client machine will be the same machine.  If
# BACKINT finds a $SAP_CLIENT environment variable, the client parameter value
# will be overriden by the assigned environment variable.  If the client parameter
# is not specified and there is no environment variable then the currently
# configured NetBackup Client will be used. If BACKINT could not get the currently
# configured NetBackup Client also, then it uses the value returned by
# the gethostname() library function.
#
client sfsdev
#
#
# drives: is an optional parameter and should be set to the number of
# simultaneous tape drives to kickoff backup. Set NetBackup Server to support
# multiple simultaneous client backups and the number of storage units/tape
# drives for this backup policy.  Based on the number of drives specified
# BACKINT will simultaneously run the same number of backup jobs.
# So for example, if the drives parameter is set to 5, then 5 backup jobs will
# run at the same time.
# The drives parameter should be set to the following rule:
#
# drives = Number of storage units per policy  X  MPX number
#
# The drives parameter value should not exceed the Set Maxium Jobs per Client
# global attribute.  If BACKINT finds a $SAP_DRIVES environment variable, the
# drive parameter value will be overriden by the value of the $SAP_DRIVES
# variable.  If the drive parameter is not specified and there is no
# environment variable, default value of one will be used.
#
#drives 1
drives 1
#
# policy: is an optionl parameter and should be set to the name of a SAP policy
# type that has been defined in Netbackup.  The SAP policy must have a schedule
# type of Application Backup defined in order for BACKINT to work.  If BACKINT finds
# a $SAP_POLICY environment variable, the policy parameter value will be
# overriden by the value of the $SAP_POLICY variable.  If the policy parameter
# is not specified and there is no environment variable, then BACKINT will
# exit with an error.
#
#policy sap_backup
policy sap_backup
#
# schedule: Is optional and must be set to the name of type  Application Backup
# schedule that is associates with a SAP policy type.  The schedule can
# define aspects of the backup such as how long Netbackup retains images,
# maximum MPX per drive, storage unit, and volume pool.  If BACKINT finds a
# $SAP_SCHED environment variable, the schedule parameter value will be
# overriden by the value of the $SAP_SCHED environment variable.  If the
# schedule parameter is not specified and there is no environment variable,
# then, NetBackup uses the first schedule of type Application Backup
# that it finds. It is higly recommended to set schedule parameter in *.utl file.
#
schedule Default-Application-Backup
#
#
# policy2: is optional and is the name of a policy to be used for the
# secondary SAP backup.  The secondary backup is performed for each SAP
# database backup on files that are needed to track SAP backup information.
# This option would be used to save the backup information on a different
# media.  If policy2 is not specified, then the policy parameter value is used.
#
#policy2 sap_sec_backup
#
#
# schedule2: is optional and is the name of a Application Backup schedule to be
# used for the secondary SAP  backup.  The secondary backup is performed for
# each SAP database backup on files that are needed to track SAP backup
# information.  This option would be used to save the backup information on a
# different media.  If schedule2 is not specified, then the schedule parameter
# value is used.
#
#schedule2 userbkps
#
#
# sort_backup_type: [size | custom | device | drive ]
# This parameter is optional and is used to specify four different backup
# sort option.  If sort_backup_type is not specified it will default to
# the size option.
#
#sort_backup_type size
#
# sort_restore_type: [image | custom | drive ]
# This parameter is optional and is used to specify three different restore
# sort option.  If sort_restore_type is not specified it will default to   
# the image option. This option is only applicable for pre 6.0 releases.
#
#sort_restore_type image
#
#
# custom_sort_file: is optional and is used in conjunction with the
# sort_backup_type and sort_restore_type parameter.  If the custom option is
# specified on either the sort_backup_type or sort_restore_type parameter,
# then the custom_sort_file parameter needs to be set to a valid file.  The
# value for this parameter must be a full path name to a custom sort file and
# must have public permissions. 
#
#custom_sort_file /oracle/SAP/sapscripts/custom_sort_file
#
#
# master_time_offset:  is an option parameter used to restore old backups
# if there was a time difference between the master and client machines. 
# This option should only be used for restoring 3.0 or older backup or if a
# backint restore can't find a specified backup.  The master_time_offset is
# specified in minutes.  The value will be subtracted from the start time and
# added to the end time for a restore or inquire.   
#
#master_time_offset 2
#
#
#sleep: is optional and is used to specify a sleep time to monitor the
# bpbackup or bprestore logs.  The default is 5 seconds.  When BACKINT is
# called a number of bpbackup/bprestore commands can be running at the
# sametime.  BACKINT monitors each command and display the information to the
# -o parameter.  In some cases bpbackup/bprestore information is not displayed
# because of the monitoring cycle.  Therefore this option is used mainly for
# debug reasons. This option is only applicable for pre 6.0 releases.
#
#sleep 5
#
#
# policy_log: is optional and is the name of a policy to be used for
# backing up a second copy of an archive log.  If this option is specified
# then two backups will be performed on the same archive log.  The first
# backup will go to the "policy" name option and the second backup will go
# to the "policy_log" name option.
#
#policy_log sap_archive_logs
#
#
# sched_log: is optional and is the name of a schedule to create a second
# backing up of an archive log.  If this option is specified then two backups
# will be performed on the same archive log.  The first backup will go to the
# "schedule" option and the second backup will be go to the "sched_log" and
# option.  The "sched_log" name must be a valid schedule name under the
# "policy_log" name option, otherwise it must be a valid schedule name under
# the "policy" name option.
#
#sched_log Default-Application-Backup
#
#
# retry_backup: is an optional parameter and should be set to the number of
# retries for a failed backup.  If this option is specified BACKINT will
# retry a failed backup job.  The number of retries is determine by the
# value on the retry_backup parameter.
#
retry_backup 1
#
#
# fail_backup: is optional and is used to stop the backup process immediately
# when an error occurs.  The standard behavior of BACKINT is to continue
# processing even in the event of an error and then report what files failed
# and what files were successful.  If this parameter is specified then BACKINT
# will stop process on the first error and report failures for all the
# files that were not backed up.
#
#fail_backup
#
#
# media_notify_script: is optional and is used to call a script when a
# "Waiting mount" is displayed in a bpbackup/bprestore log.  The value for this
# option must be the full path name to a script.  The script should also have
# the right file permissions and should be tested before implementation.  If
# the message is encountered and this optional is specified, then the
# following commands will be executed from BACKINT:
#   MEDIA_ID=A001;export MEDIA_ID
#   NETBACKUP_SERVER=saturn;export NETBACKUP_SERVER
#   /oracle/SAP/sapscripts/sap_media_notify
# This option is only applicable for pre 6.0 releases.
#
#media_notify_script /oracle/SAP/sapscripts/sap_media_notify
#
#
# restore_filter: is optional and is used to resolve linked file paths on a
# restore.  This parameter should be commented out and should be used only on
# rare occasions.  The following are the cases were this parameter is needed:
#   1) Oracle table spaces use file paths
#   2) The directory paths to the Oracle table spaces are linked paths
#   3) The linked directory paths don't exist at restore time
# The value for this parameter must be a fully qualified file path name to a
# script, which has the right permissions and has been tested before being
# implemented.  The script must have an input and output parameter and be able
# to modify the contents of a text file which contains file paths.  The script
# is responsible for converting linked directory paths into absolute directory
# paths. See /usr/openv/netbackup/ext/db_ext/sap/scripts/restore_filter for
# an example.  
#
#restore_filter /oracle/SAP/sapscripts/restore_filter.sh
#
#
# bplist_filter: is optional and is used to resolve linked file passes on an
# inquire.  This parameter should be commented out and should be used only on
# rare occasions.  Like the restore_filter_script parameter this is needed
# for the following cases:
#   1) Oracle table spaces use file paths
#   2) The directory paths to the Oracle table spaces are linked paths
#   3) The linked directory paths don't exist at restore time
# The value for this option must be a fully qualified path name to a script,
# which has the right file permission and has been tested before being
# implemented.  The script must have an input and output parameter and be able
# to modify the contents of a text file, which contains file paths.  The script
# is responsible for converting absolute directory paths into linked directory
# paths.  This is just the opposite of the restore filter script. See
# /usr/openv/netbackup/ext/db_ext/sap/scripts/bplist_filter for an example.
#
#bplist_filter /oracle/SAP/sapscripts/restore_filter.sh
#
#
# check_directory_flag: is optional and is used to allow directory and
# subdirectory backups.  The parameter value can be either set to a 1 for true
# or 0 for false. The SAP Tools only allows file backups, not directories or
# subdirectories.  The SAP Tools requires BACKINT to report an error if a
# directory being backed up.  This option provides the ability to override
# this design and gives the SAP Tools the ability to backup directories and
# subdirectories.   The default is not to allow directory and subdirectory
# backups. This option is only applicable for pre 6.0 releases.
#
#check_directory_flag 1
#
#
# second_secondary_archive: is optional, and it can have value of 0 or 1.
# If value is one, then 2 copies of secondary backup will be made. This
# parameter will have an effect only if policy_log and/or schedule_log are
# specified. The first backup will go to the "policy"  name option and the
# second backup will go to the "policy_log" name option. Furthermore, it
# will serve brarchive but it will have no effect on brbackup.
#
#second_secondary_archive 0
#
# backup_stream_buffersize: is optional. This parameter can be used to
# specify the value of buffer size in case of stream backup. Data is
# received through stream (pipe) in case of SAPDB. When passing this
# data to netbackup, the buffer size specified by this value will be used.
#
#backup_stream_buffersize 65535
#
# restore_stream_buffersize: is optional. This parameter can be used to
# specify the value of buffer size in case of stream restore. Data is
# received from netbackup and passed to SAPDB through stream (pipe) in case
# of restore. When receiving data from netbackup and copying it to pipe,
# the buffer size specified by this value will be used.
#
#restore_stream_buffersize 65535
#
#inquire_query_period: In case of #NULL based inquire query, SAP agent will
#restrict the catalog search to six months by default.  This parameter can be
#used to specify the query period (in months). For example if user wants to
#restrict the result of #NULL inquire query search to last 10 months then this
#parameter should be set to 10.
#
#inquire_query_period 10
#

--------------------------- END FILE ---------------------------------------------------------------------

my sap_online_backup:

----------------------------- START FILE ----------------------------------------------------------------

#!/bin/sh

#bcpyrght
#***************************************************************************
#* $VRTScprght: Copyright 1993 - 2008 Symantec Corporation, All Rights Reserved $ *
#***************************************************************************
#ecpyrght

#
#NOTE:IF your SAP user (in this script oradev) runs in C shell, environmental
#variables can not be exported. In that case, you should modify this script to
#work in your environment. For example:
#   SAP_SERVER=$SAP_SERVER; export SAP_SERVER; (Correct for Bourne and Korn shells)
#   can change into
#   setenv SAP_SERVER $SAP_SERVER; (Correct for C shell)
#

#
#This environment variable are created by Netbackup (bphdb)
#

echo "SAP_SCHEDULED = $SAP_SCHEDULED"
echo "SAP_USER_INITIATED = $SAP_USER_INITIATED"
echo "SAP_SERVER = $SAP_SERVER"
echo "SAP_POLICY = $SAP_POLICY"
echo "SAP_SCHED = $SAP_SCHED"
echo "SAP_SNC_SCHED = $SAP_SNC_SCHED"

RETURN_STATUS=0

# SAP_ENV - Holds environmental variables.
SAP_ENV=""

#
# If SAP_SERVER exists then export it to make it available to backint.
#
if [ -n "$SAP_SERVER" ]
then
#    SAP_ENV="$SAP_ENV SAP_SERVER=$SAP_SERVER; export SAP_SERVER;"
#if Oracle DBA acount(oradev user) uses C Shell,comment the above line and uncomment the next line
    SAP_ENV="$SAP_ENV setenv SAP_SERVER $SAP_SERVER;"
fi

#
# If SAP_POLICY exists then export it to make it available to backint.
#
if [ -n "$SAP_POLICY" ]
then
#    SAP_ENV="$SAP_ENV SAP_POLICY=$SAP_POLICY; export SAP_POLICY;"
#if Oracle DBA account(oradev user) uses C Shell, comment the above line and uncomment the next line
    SAP_ENV="$SAP_ENV setenv SAP_POLICY $SAP_POLICY;"
fi

#
# If SAP_SCHED exists then export it to make it available to backint.
#
if [ -n "$SAP_SCHED" ]
then
#        SAP_ENV="$SAP_ENV SAP_SCHED=$SAP_SCHED; export SAP_SCHED;"
#if Oracle DBA account(oradev user) uses C Shell, comment the above line and uncomment the next line
       SAP_ENV="$SAP_ENV setenv SAP_SCHED $SAP_SCHED;"
fi

#
# If SAP_SNC_SCHED exists then export it to make it available to backint.
#
if [ -n "$SAP_SNC_SCHED" ]
then
#        SAP_ENV="$SAP_ENV SAP_SNC_SCHED=$SAP_SNC_SCHED; export SAP_SNC_SCHED;"
#if Oracle DBA account(oradev user) uses C Shell, comment the above line and uncomment the next line
       SAP_ENV="$SAP_ENV setenv SAP_SNC_SCHED $SAP_SNC_SCHED;"
fi

#
# Full online backup with dynamic BEGIN/END BACKUP switch
#

CMD_LINE="$SAP_ENV brbackup -c -d util_file_online -t online -m all"

# 
# The username on the "su" command needs to be replaced with the correct user
# name.
#
echo "Execute $CMD_LINE"
su - oradev -c "$CMD_LINE"

RETURN_STATUS=$?

#
# save and delete archive logs
#


if [ $RETURN_STATUS -eq 0 ]
then

    timeStamp=`date '+%m%d%y%H%M%S'` ;
    br_out_file="/tmp/brarchive_out.${timeStamp}" ;
    CMD_LINE="$SAP_ENV brarchive -c -d util_file -sd > $br_out_file"

#
# The username on the "su" command needs to be replaced with the correct user
# name.
#
    echo "Execute $CMD_LINE"
    su - oradev -c "$CMD_LINE"

    RETURN_STATUS=$?


# If there were no redo logs to backup, brarchive will return 1. But if 1 is
# returned to bphdb, job will appear as failed in the activity monitor. To
# prevent Netbackup failure, check return code from brarchive. If the return code
# is 1, check for message code BR0013W in the output of brarchive. If this message
# is present, then there were no redo logs present to backup and its not a failure.
# So in that case return 0 to bphdb.

        if [ $RETURN_STATUS = 1 ]; then
                su - oradev -c "grep 'BR0*13W' $br_out_file > /dev/null"
                if [ $? = 0 ]; then
                        RETURN_STATUS=0
                fi
        fi
    su - oradev -c "cat $br_out_file;rm $br_out_file"
fi
exit $RETURN_STATUS

--------------------------- END FILE -------------------------------------------------------------------





******************************************************************************************************************************
****************************************** MY PROBLEM ********************************************************************
******************************************************************************************************************************

I had create policy for backup as sap_backup and use default schedule as application backup

when I test perform backup by use brtools, I found error as:

....................................................

18:39:57.507 [1298440] <1> :  Backup of </oracle/DEV/sapdata/sapdata1/sysaux_1/s
ysaux.data1> is failed due to <Error 1 : Server Status:  the requested operation
 was partially successful>.
18:39:57.507 [1298440] <1> :  Backup of </oracle/DEV/sapdata/sapdata1/system_1/s
ystem.data1> is failed due to <Error 1 : Server Status:  the requested operation
 was partially successful>.
18:39:57.507 [1298440] <1> :  Backup of </oracle/DEV/sapbackup/cntrlDEV.dbf> is
failed due to <Error 1 : Server Status:  the requested operation was partially s
uccessful>.
BR0233E Backup utility has reported an error while saving file /oracle/DEV/sapda
ta/sapdata2/sr3_1/sr3.data1
BR0233E Backup utility has reported an error while saving file /oracle/DEV/sapda
ta/sapdata2/sr3_10/sr3.data10
BR0233E Backup utility has reported an error while saving file /oracle/DEV/sapda
ta/sapdata2/sr3_11/sr3.data11
BR0233E Backup utility has reported an error while saving file /oracle/DEV/sapda
ta/sapdata2/sr3_12/sr3.data12
BR0233E Backup utility has reported an error while saving file /oracle/DEV/sapda
ta/sapdata2/sr3_13/sr3.data13
BR0233E Backup utility has reported an error while saving file /oracle/DEV/sapda
ta/sapdata2/sr3_14/sr3.data14
BR0233E Backup utility has reported an error while saving file /oracle/DEV/sapda
ta/sapdata2/sr3_15/sr3.data15

.....................................................................................................................................................

[1298440] Error detected while reporting backup ids.
********************************************************************************

BR0280I BRBACKUP time stamp: 2009-09-07 18.39.57
BR0279E Return code from '/usr/sap/DEV/SYS/exe/run/backint -u DEV -f backup -i /
oracle/DEV/sapbackup/.bebklxpk.lst -t file -p /oracle/DEV/102_64/dbs/initDEV.utl
': 2

BR0232E 0 of 35 files saved by backup utility
BR0280I BRBACKUP time stamp: 2009-09-07 18.39.57
BR0231E Backup utility call failed

BR0280I BRBACKUP time stamp: 2009-09-07 18.39.59
BR0317I 'Alter database end backup' successful

BR0056I End of database backup: bebklxpk.anf 2009-09-07 18.39.57
BR0280I BRBACKUP time stamp: 2009-09-07 18.39.59
BR0054I BRBACKUP terminated with errors

###############################################################################

BR0292I Execution of BRBACKUP finished with return code 5

BR0668I Warnings or errors occurred - you can continue to ignore them or go back
 to repeat the last action

BR0280I BRTOOLS time stamp: 2009-09-07 18.39.59
BR0670I Enter 'c[ont]' to continue, 'b[ack]' to go back, 's[top]' to abort:

..............................................................

******************************************************************************************************************************
******************************************************************************************************************************

it 's partial error, but it have same error code.


Any idea to solve my problem, please help.

[Nicolai]

I am not sure this is you're problem, I am missing the complete .anf output. But I suspect SAP can verify the backup.  BRtool verifies a backup by doing a bplist for each SAP .dbf  file

Try to create a local bp.conf file in /oracle/SID/bp.conf with contend :

SERVER = {master server name}
CLIENT = {client name}

And make sure the oraSID and group dba can read it. Also make sure you don't mix FQDN vs. Non-FQDN on the SAP server and Netbackup policy.

[Apitha]

It's can send data to netbackup server and backup as patial file only 10MB. It's still had error as can't backup open file.

How can I resolve this, please help.

[quebek · Accepted solution]

Check how your filesystems with datafiles are mounted. Per my knowledge any oracle data must be mounted with -cio option on JFS files system under AIX.
please also post the backint logs - if this is not the CIO option cause, maybe this log can show us another issue.

[Marianne]

If JFS2 filesystem change FILESYSTEMIO_OPTIONS parameter to ASYNC.
Have a look at this:
http://www-01.ibm.com/support/docview.wss?rs=667&context=SSZHVN&dc=DB520&uid=swg21244385&loc=en_US&cs=UTF-8&lang=en&rss=ct667tivoli

[Apitha]

Oh with CIO option, it's can solve this problem. thanks you everybody.