Re: TSM for ERP - RMAN backup apparently succeeds, BRBACKUP gives up
BR0522E 112 of 108 files / save sets processed by RMAN
Haha! The reason it backed up 4 MORE files than it had to was the fact that
RMAN retried and successfully backed up the 4 files that failed. BR*Tools must
be using a ~= test, I guess.
Thanks for the suggestion. We'll probably open a ticket with SAP if we can
duplicate the problem with the latest BR*Tools.
Steve
STEPHEN STACKWICK | Senior Consultant | 301.518.6352 (m) |
stephen.stackw...@icfi.com | icfi.com
ICF INTERNATIONAL | 7125 Thomas Edison Dr, Suite 100, Columbia, Md 21046 |
443-573-0524, 443-718-4900 (o)
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On
Behalf Of Del Hoobler
Sent: Tuesday, July 22, 2014 06:31
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] TSM for ERP - RMAN backup apparently succeeds,
BRBACKUP gives up
Response appended on behalf of Thomas Prause
BRBACKUP thinks that RMAN has not saved all objects:
BR0522E 112 of 108 files / save sets processed by RMAN
If you disagree you may open an incident at SAP. BRBACKUP belongs to SAP
BR*Tools and is not part of TSM for ERP.
(All messages prefixed with BR are from BR*Tools.
TSM for ERP messages have BKI.)
If you have only a single drive you could limit the number of RMAN channels
to one. Set 'rman_channels=1'
in /oracle/ECP/112_64/dbs/initECP.sap
Regards,
Thomas
From: Stackwick, Stephen stephen.stackw...@icfi.com
To: ADSM-L@vm.marist.edu
Date: 07/15/2014 03:05 PM
Subject: TSM for ERP - RMAN backup apparently succeeds, BRBACKUP
gives
up
Sent by: ADSM: Dist Stor Manager ADSM-L@vm.marist.edu
Using RMAN to backup a 10.2 Oracle SAP database with TSM for ERP 6.
3. It seems when TSM preempts a drive, it kills the corresponding RMAN
channel. Sounds reasonable, but apparently RMAN continues with the
remaining channel(s) to finish the backup, obviously taking a little
longer. But the TSM for ERP program BRBACKUP, doesn't seem able to
deal with that and falls over:
First, RMAN:
RMAN-03009: failure of backup command on sbt_1 channel at 07/14/2014
22:19:05
ORA-27192: skgfcls: sbtclose2 returned error - failed to close file
ORA-19511: Error received from media manager layer, error text:
BKI9309E: Operation terminated due to an explicit abort request.
ORA-19502: write error on file ECP_beohkssf.27102_1, block number
13010401 (block size=8192)
ORA-27030: skgfwrt: sbtwrite2 returned error
ORA-19511: Error received from media manager layer, error text:
BKI5008E: Tivoli Storage Manager Error.
channel sbt_1 disabled, job failed on it will be run on another
channel channel sbt_2: finished piece 1 at 14-JUL-14
:
:
Finished backup at 15-JUL-14
released channel: sbt_1
released channel: sbt_2
RMAN-00571:
==
=
RMAN-00569: === ERROR MESSAGE STACK FOLLOWS
===
RMAN-00571:
==
=
RMAN-03002: failure of release command at 07/15/2014 04:04:46
RMAN-06012: channel: sbt_1 not allocated
RMAN
List of Backup Sets
===
RMAN proceeds to list all the backupsets and, indeed, they are all
there and backed up. But, apparently, because of the RMAN-03002
error, BRBACKUP concludes there was a failure and ends the backup,
reporting failure:
Recovery Manager complete.
BR0280I BRBACKUP time stamp: 2014-07-15 04.04.55 BR0279E Return code
from 'SHELL=/bin/sh /oracle/ECP/112_64/bin/rman
nocatalog': 1
BR0522E 112 of 108 files / save sets processed by RMAN BR0536E RMAN
call for database instance ECP failed BR0200I BR_TRACE: location
BrRmanCall-56, commands for RMAN in: /
oracle/ECP/sapbackup/.beohkssf.cmd
@/oracle/ECP/sapbackup/..beohkssf..cmd
host '/usr/sap/ECP/SYS/exe/run/brtools -f delete /oracle/ECP/
sapbackup/..beohkssf..cmd'; run { allocate channel sbt_1 device type
'SBT_TAPE'
parms 'ENV=(XINT_PROFILE=/oracle/ECP/112_64/dbs/
initECP.utl,PROLE_PORT=57323,BR_CALLER=BRBACKUP,BR_BACKUP=FULL,B
R_REQUEST=NEW,BR_RUN=beohkssf.fnr)';
allocate channel sbt_2 device type 'SBT_TAPE'
parms 'ENV=(XINT_PROFILE=/oracle/ECP/112_64/dbs/
initECP.utl,PROLE_PORT=57323,BR_CALLER=BRBACKUP,BR_BACKUP=FULL,B
R_REQUEST=NEW,BR_RUN=beohkssf.fnr)';
backup incremental level 0 tag beohkssf format 'ECP_beohkssf.%s_%p'
filesperset 4
database;
release channel sbt_1;
release channel sbt_2; }
list backup of database tag beohkssf;
exit;
BR0280I BRBACKUP time stamp: 2014-07-15 04.04.55 BR0506E Full database
backup (level 0) using RMAN failed
BR0056I End of database backup: beohkssf.fnr 2014-07-15 04.04.55
BR0280I BRBACKUP time stamp: 2014-07-15 04.04.57 BR0054I BRBACKUP
terminated with errors
Doesn't seem right to me. Is there a workaround (I know, I know, have
enough tape drives), or is this PMR territory?
Steve Stackwick
STEPHEN STACKWICK | Senior
Re: TSM for ERP - RMAN backup apparently succeeds, BRBACKUP gives up
Response appended on behalf of Thomas Prause
BRBACKUP thinks that RMAN has not saved all objects:
BR0522E 112 of 108 files / save sets processed by RMAN
If you disagree you may open an incident at SAP. BRBACKUP
belongs to SAP BR*Tools and is not part of TSM for ERP.
(All messages prefixed with BR are from BR*Tools.
TSM for ERP messages have BKI.)
If you have only a single drive you could limit the number
of RMAN channels to one. Set 'rman_channels=1'
in /oracle/ECP/112_64/dbs/initECP.sap
Regards,
Thomas
From: Stackwick, Stephen stephen.stackw...@icfi.com
To: ADSM-L@vm.marist.edu
Date: 07/15/2014 03:05 PM
Subject: TSM for ERP - RMAN backup apparently succeeds, BRBACKUP gives
up
Sent by: ADSM: Dist Stor Manager ADSM-L@vm.marist.edu
Using RMAN to backup a 10.2 Oracle SAP database with TSM for ERP 6.
3. It seems when TSM preempts a drive, it kills the corresponding
RMAN channel. Sounds reasonable, but apparently RMAN continues with
the remaining channel(s) to finish the backup, obviously taking a
little longer. But the TSM for ERP program BRBACKUP, doesn't seem
able to deal with that and falls over:
First, RMAN:
RMAN-03009: failure of backup command on sbt_1 channel at 07/14/2014
22:19:05
ORA-27192: skgfcls: sbtclose2 returned error - failed to close file
ORA-19511: Error received from media manager layer, error text:
BKI9309E: Operation terminated due to an explicit abort request.
ORA-19502: write error on file ECP_beohkssf.27102_1, block number
13010401 (block size=8192)
ORA-27030: skgfwrt: sbtwrite2 returned error
ORA-19511: Error received from media manager layer, error text:
BKI5008E: Tivoli Storage Manager Error.
channel sbt_1 disabled, job failed on it will be run on another channel
channel sbt_2: finished piece 1 at 14-JUL-14
:
:
Finished backup at 15-JUL-14
released channel: sbt_1
released channel: sbt_2
RMAN-00571: ===
RMAN-00569: === ERROR MESSAGE STACK FOLLOWS ===
RMAN-00571: ===
RMAN-03002: failure of release command at 07/15/2014 04:04:46
RMAN-06012: channel: sbt_1 not allocated
RMAN
List of Backup Sets
===
RMAN proceeds to list all the backupsets and, indeed, they are all
there and backed up. But, apparently, because of the RMAN-03002
error, BRBACKUP concludes there was a failure and ends the backup,
reporting failure:
Recovery Manager complete.
BR0280I BRBACKUP time stamp: 2014-07-15 04.04.55
BR0279E Return code from 'SHELL=/bin/sh /oracle/ECP/112_64/bin/rman
nocatalog': 1
BR0522E 112 of 108 files / save sets processed by RMAN
BR0536E RMAN call for database instance ECP failed
BR0200I BR_TRACE: location BrRmanCall-56, commands for RMAN in: /
oracle/ECP/sapbackup/.beohkssf.cmd
@/oracle/ECP/sapbackup/..beohkssf..cmd
host '/usr/sap/ECP/SYS/exe/run/brtools -f delete /oracle/ECP/
sapbackup/..beohkssf..cmd';
run { allocate channel sbt_1 device type 'SBT_TAPE'
parms 'ENV=(XINT_PROFILE=/oracle/ECP/112_64/dbs/
initECP.utl,PROLE_PORT=57323,BR_CALLER=BRBACKUP,BR_BACKUP=FULL,BR_REQUEST=NEW,BR_RUN=beohkssf.fnr)';
allocate channel sbt_2 device type 'SBT_TAPE'
parms 'ENV=(XINT_PROFILE=/oracle/ECP/112_64/dbs/
initECP.utl,PROLE_PORT=57323,BR_CALLER=BRBACKUP,BR_BACKUP=FULL,BR_REQUEST=NEW,BR_RUN=beohkssf.fnr)';
backup incremental level 0 tag beohkssf format 'ECP_beohkssf.%s_%p'
filesperset 4
database;
release channel sbt_1;
release channel sbt_2; }
list backup of database tag beohkssf;
exit;
BR0280I BRBACKUP time stamp: 2014-07-15 04.04.55
BR0506E Full database backup (level 0) using RMAN failed
BR0056I End of database backup: beohkssf.fnr 2014-07-15 04.04.55
BR0280I BRBACKUP time stamp: 2014-07-15 04.04.57
BR0054I BRBACKUP terminated with errors
Doesn't seem right to me. Is there a workaround (I know, I know,
have enough tape drives), or is this PMR territory?
Steve Stackwick
STEPHEN STACKWICK | Senior Consultant | 301.518.6352 (m) |
stephen.stackw...@icfi.commailto:sstackw...@icfi.com | icfi.com
http://www.icfi.com/
ICF INTERNATIONAL | 7125 Thomas Edison Dr, Suite 100, Columbia, Md
21046 | 443-573-0524, 443-718-4900 (o)
TSM for ERP - RMAN backup apparently succeeds, BRBACKUP gives up
Using RMAN to backup a 10.2 Oracle SAP database with TSM for ERP 6.3. It seems
when TSM preempts a drive, it kills the corresponding RMAN channel. Sounds
reasonable, but apparently RMAN continues with the remaining channel(s) to
finish the backup, obviously taking a little longer. But the TSM for ERP
program BRBACKUP, doesn't seem able to deal with that and falls over:
First, RMAN:
RMAN-03009: failure of backup command on sbt_1 channel at 07/14/2014 22:19:05
ORA-27192: skgfcls: sbtclose2 returned error - failed to close file
ORA-19511: Error received from media manager layer, error text:
BKI9309E: Operation terminated due to an explicit abort request.
ORA-19502: write error on file ECP_beohkssf.27102_1, block number 13010401
(block size=8192)
ORA-27030: skgfwrt: sbtwrite2 returned error
ORA-19511: Error received from media manager layer, error text:
BKI5008E: Tivoli Storage Manager Error.
channel sbt_1 disabled, job failed on it will be run on another channel
channel sbt_2: finished piece 1 at 14-JUL-14
:
:
Finished backup at 15-JUL-14
released channel: sbt_1
released channel: sbt_2
RMAN-00571: ===
RMAN-00569: === ERROR MESSAGE STACK FOLLOWS ===
RMAN-00571: ===
RMAN-03002: failure of release command at 07/15/2014 04:04:46
RMAN-06012: channel: sbt_1 not allocated
RMAN
List of Backup Sets
===
RMAN proceeds to list all the backupsets and, indeed, they are all there and
backed up. But, apparently, because of the RMAN-03002 error, BRBACKUP
concludes there was a failure and ends the backup, reporting failure:
Recovery Manager complete.
BR0280I BRBACKUP time stamp: 2014-07-15 04.04.55
BR0279E Return code from 'SHELL=/bin/sh /oracle/ECP/112_64/bin/rman nocatalog':
1
BR0522E 112 of 108 files / save sets processed by RMAN
BR0536E RMAN call for database instance ECP failed
BR0200I BR_TRACE: location BrRmanCall-56, commands for RMAN in:
/oracle/ECP/sapbackup/.beohkssf.cmd
@/oracle/ECP/sapbackup/..beohkssf..cmd
host '/usr/sap/ECP/SYS/exe/run/brtools -f delete
/oracle/ECP/sapbackup/..beohkssf..cmd';
run { allocate channel sbt_1 device type 'SBT_TAPE'
parms
'ENV=(XINT_PROFILE=/oracle/ECP/112_64/dbs/initECP.utl,PROLE_PORT=57323,BR_CALLER=BRBACKUP,BR_BACKUP=FULL,BR_REQUEST=NEW,BR_RUN=beohkssf.fnr)';
allocate channel sbt_2 device type 'SBT_TAPE'
parms
'ENV=(XINT_PROFILE=/oracle/ECP/112_64/dbs/initECP.utl,PROLE_PORT=57323,BR_CALLER=BRBACKUP,BR_BACKUP=FULL,BR_REQUEST=NEW,BR_RUN=beohkssf.fnr)';
backup incremental level 0 tag beohkssf format 'ECP_beohkssf.%s_%p' filesperset
4
database;
release channel sbt_1;
release channel sbt_2; }
list backup of database tag beohkssf;
exit;
BR0280I BRBACKUP time stamp: 2014-07-15 04.04.55
BR0506E Full database backup (level 0) using RMAN failed
BR0056I End of database backup: beohkssf.fnr 2014-07-15 04.04.55
BR0280I BRBACKUP time stamp: 2014-07-15 04.04.57
BR0054I BRBACKUP terminated with errors
Doesn't seem right to me. Is there a workaround (I know, I know, have enough
tape drives), or is this PMR territory?
Steve Stackwick
STEPHEN STACKWICK | Senior Consultant | 301.518.6352 (m) |
stephen.stackw...@icfi.commailto:sstackw...@icfi.com |
icfi.comhttp://www.icfi.com/
ICF INTERNATIONAL | 7125 Thomas Edison Dr, Suite 100, Columbia, Md 21046 |
443-573-0524, 443-718-4900 (o)
