RMAN backup error using DB13

[Former Member]

we are getting below error message while tried to take backup from DB13 calendar but it is working fine unix level orasid and sidadm.

BR0280I BRARCHIVE time stamp: 2014-02-25 08.08.10
BR0202I Saving /oracle/SID/oraarch/SIDarch1_8912_793122936.dbf ...
BR0278E Command output of 'SHELL=/bin/sh /oracle/SID/112_64/bin/rman nocatalog':

Recovery Manager: Release 11.2.0.3.0 - Production on Tue Feb 25 08:08:07 2014

Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.

RMAN>
RMAN> connect target *
connected to target database: SID (DBID=1683077722)
using target database control file instead of recovery catalog

RMAN> **end-of-file**

RMAN>
host command complete

RMAN> 2> 3> 4>
allocated channel: sbt_1
channel sbt_1: SID=123 device type=SBT_TAPE
channel sbt_1: Data Protection for SAP(R)

Starting backup at 25-FEB-14
channel sbt_1: starting archived log backup set
channel sbt_1: specifying archived log(s) in backup set
input archived log thread=1 sequence=8912 RECID=8776 STAMP=840434379
channel sbt_1: starting piece 1 at 25-FEB-14
released channel: sbt_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on sbt_1 channel at 02/25/2014 08:08:11
ORA-19506: failed to create sequential file, name="SID_aenhauna.38_1", parms=""
ORA-27028: skgfqcre: sbtbackup returned error
ORA-19511: Error received from media manager layer, error text:
   BKI7051E: The environment variable XINT_PROFILE is not set. It must be set and contain the fully qualified path to the *.utl file to be used.

RMAN>
specification does not match any backup in the repository

RMAN>

Recovery Manager complete.
BR0280I BRARCHIVE time stamp: 2014-02-25 08.08.12

[Former Member · Accepted solution]

Dhavan Arumugam wrote:

we are getting below error message while tried to take backup from DB13 calendar but it is working fine unix level orasid and sidadm.

What commands at unix level were executed? Please attach output of env command for both users. And check rman_parms value in init<SID>.sap profile.

[Former Member · Accepted solution]

I had set XINT_profile file in both orasid and sidadm

XINT_PROFILE=/oracle/SID/112_64/dbs/initISID.utl

i could see below profile was set in init<SID>.sap

# rman_parms = "BLKSIZE=65536 ENV=(BACKUP_SERVER=HOSTNAME)"

using below command i take rman archive log backup in orasid and sidadm but not run in db13

brarchive -p initSID.sap -copy_delete_save -d rman_util -r initSID.utl -k no -l E -U

[Former Member · Accepted solution]

In DB13 calendar am getting below command

brarchive -jid LOG__20140225113711 -u / -c force -p initSID.sap -cds

but we are using manually below command

brarchive -p initSID.sap -copy_delete_save -d rman_util -r initSID.utl -k no -l E -U

i don't know why it is not picking the above command in db13 calendar and have two option in db13 calendar

1.redo log backup

2 prepare for RMAN backup.

what option required to select ...please advice

[Former Member · Accepted solution]

Please check official documentation for Data Protection solution you are using. You need to add/set backup_dev_type and rman_parms in init<SID>.sap as follows:

backup_dev_type = rman_util

rman_parms="ENV=(XINT_PROFILE=<ORACLE_HOME>/dbs/init<SID>.utl,PROLE_PORT=<portnumber>,&BR_INFO)"

[Former Member · Accepted solution]

Thanks a lot roman ,it working fine.

i am doing new rman setup in my environmental.please advice if need any change  the below setup,

# additional parameters for RMAN

# rman_channels and rman_filesperset are only used when rman_util,

# rman_disk or rman_stage

# rman_channels defines the number of parallel sbt channel allocations

# rman_filesperset = 0 means:

# one file per save set - for non-incremental backups

# all files in one save set - for incremental backups

# the others have the same meaning as for native RMAN

# rman_channels = 1

# rman_filesperset = 0

# rman_maxpiecesize = 0   # in KB - former name rman_kbytes

# rman_rate = 0           # in KB - former name rman_readrate

# rman_maxopenfiles = 0

# rman_maxsetsize = 0     # in KB - former name rman_setsize

# additional parameters for RMAN version 8.1

# the parameters have the same meaning as for native RMAN

# rman_diskratio = 0

# rman_pool = 0

# rman_copies = 0 | 1 | 2 | 3 | 4 # former name rman_duplex

# rman_proxy = no | yes | only

# special parameters for an external backup library, example:

rman_parms="ENV=(XINT_PROFILE=/oracle/sid/112_64/dbs/initsid.utl,PROLE_PORT=57323,&BR_INFO)"

# rman_parms = "BLKSIZE=65536 ENV=(BACKUP_SERVER=HOSTNAME)"

# rman_send = "'<command>'"

# rman_send = ("channel sbt_1 '<command1>' parms='<parameters1>'",

#              "channel sbt_2 '<command2>' parms='<parameters2>'")

# rman_compress = no | yes

# rman_maxcorrupt = (<dbf_name>|<dbf_id>:<corr_cnt>, ...)

[former_member188883]

Hi Dhavan,

BKI7051E: The environment variable XINT_PROFILE is not set. It must be set and contain the fully qualified path to the *.utl file to be used.

Explanation

The way DP for SAP works is specified in a profile. When called, DP for SAP looks for the environment variable XINT_PROFILE which must contain the fully qualified path to the profile.

User response

Check the environment for XINT_PROFILE of the user who started DP for SAP.

Hope this helps.

Regards,

Deepak Kori