RMAN SBT_TAPE

hello,
as far as i learn that sbt_tape configuration needs a media manager
i explore that some of them is netbackup, tivoli
now, i think they are not open source .
can any 1 tell me which media manager is open source ? i wanna do practice on sbt_tape
Thanks in advance
Reg

P. Forstmann wrote:
As far as I know there is no open source media manager for RMAN.
You can try to simulate a tape device using disk with:
allocate channel c1 device type sbt parms 'SBT_LIBRARY=oracle.disksbt, ENV=(BACKUP_DIR=<local directory>)';
Thanks , ENV= environment parameter right? and we need to configure library also , i guess 'SBT_LIBRARY=oracle.disksbt' is the one ? ( btw what does oracle.disksbt means?)
Edited by: 990608 on Feb 27, 2013 1:48 PM
Edited by: 990608 on Feb 27, 2013 1:52 PM

Similar Messages

RMAN SBT_TAPE error

When I am trying to delete the obsolete backups I get this error .
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of allocate command on ch1 channel at 11/08/2007 15:21:08
ORA-19554: error allocating device, device type: SBT_TAPE, device name:
ORA-27211: Failed to load Media Management Library
need help !
Thanks,

Hi,
Looks like you had done the "TAPE" backup earlier and trying to delete obsolete backup from the "TAPE".
Then, you need to allocate "SBT_TAPE" channel for deleting obsolete backup as like you did for the tape backup.
Right now, default rman uses disk type channels.
HTH.
- Nirmal

Can you help me? I meet errors when I do incomplete recovery with RMAN

In recover step, There are following errors:
RMAN-11001: Oracle Error: ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '/d/db/oradata/db01/system01.dbf'
question:
1. Should I restore archive log files generated on July 16th back to orignal archive directory in order to avoid to recover failure?
2. Or Should I add the command "sql 'alter system archive log current'" in the backup script in order to avoid to recover failure?
The following is the detail information:
The database is ok when I try to do incomplete recovery database that was fully backed up on July,16th,2004. The database is oracle 8.1.7 and is in the archive mode:
The following is the backup script:
run {
allocate channel 'dev_0' type 'sbt_tape'
parms 'ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=db01,OB2BARLIST=ora8i_online)';
backup incremental level 0 filesperset 1
format 'ora8i_online<db01_%s:%t:%p>.dbf'
database
include current controlfile
archivelog all delete input;
I use it to do a full backup on July 16th,17th successfully.
And I use the following scripts to do incomplete recovery:
run {
allocate channel 'dev_0' type 'sbt_tape'
parms 'ENV=(OB2BARTYPE=ORACLE8,OB2APPNAME=db01)';
sql "alter database mount";
set until time ='17.07.2004';
restore database;
recover database;
sql "alter database open resetlogs";
sql "alter database open";
There script is successful in restore step. But there are some errors in recover step. The detail information is showing in following log:
RMAN-03022: compiling command: allocate
RMAN-03023: executing command: allocate
RMAN-08030: allocated channel: dev_0
RMAN-08500: channel dev_0: sid=13 devtype=SBT_TAPE
RMAN-08526: channel dev_0: HP OpenView OmniBack II A.04.10/176
RMAN-03022: compiling command: sql
RMAN-06162: sql statement: alter database mount
RMAN-03023: executing command: sql
RMAN-03022: compiling command: set
RMAN-03022: compiling command: restore
RMAN-03022: compiling command: IRESTORE
RMAN-03023: executing command: IRESTORE
RMAN-08016: channel dev_0: starting datafile backupset restore
RMAN-08502: set_count=2056 set_stamp=531622798 creation_time=16.07.2004
RMAN-08089: channel dev_0: specifying datafile(s) to restore from backup set
RMAN-08016: channel dev_0: starting datafile backupset restore
RMAN-08502: set_count=2180 set_stamp=531623409 creation_time=16.07.2004
RMAN-08089: channel dev_0: specifying datafile(s) to restore from backup set
RMAN-08523: restoring datafile 00001 to /d/db/oradata/db01/system01.dbf
RMAN-08023: channel dev_0: restored backup piece 1
RMAN-08511: piece handle=netace_ora8i_online<db01_2180:531623409:1>.dbf tag=null params=NULL
RMAN-08024: channel dev_0: restore complete
RMAN-08023: channel dev_0: restored backup piece 1
RMAN-08511: piece handle=netace_ora8i_online<db01_2212:531623994:1>.dbf tag=null params=NULL
RMAN-08024: channel dev_0: restore complete
RMAN-03022: compiling command: recover
RMAN-03022: compiling command: recover(1)
RMAN-03022: compiling command: recover(2)
RMAN-03022: compiling command: recover(3)
RMAN-03023: executing command: recover(3)
RMAN-08054: starting media recovery
RMAN-03022: compiling command: recover(4)
RMAN-03026: error recovery releasing channel resources
RMAN-11001: Oracle Error: ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '/d/db/oradata/db01/system01.dbf'
RMAN-08031: released channel: dev_1
RMAN-08031: released channel: dev_2
RMAN-08031: released channel: dev_0
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure during compilation of command
RMAN-03013: command type: recover
RMAN-03002: failure during compilation of command
RMAN-03013: command type: recover(4)
RMAN-06003: ORACLE error from target database: ORA-01220: file based sort illegal before database is open
ORA-06512: at "SYS.X$DBMS_RCVMAN", line 7220
ORA-06512: at "SYS.X$DBMS_RCVMAN", line 5053
ORA-06512: at line 1
I repeat my questions:
1. Should I restore archive log files generated on July 16th back to original archive directory in order to avoid to recover failure?
2. Or Should I add the command "sql 'alter system archive log current'" in the backup script in order to avoid to recover failure?
Can you help me ? Thank you.

which o.s u are using i can't help you as i never worked on ver 8i,i can tell you incomplete recovery on oracle 9i on win 2000 server.
thanks : alok kumar

Can you help me? I meet some errors when I do incomplete recovery with RMAN

In recover step, There are following errors:
RMAN-11001: Oracle Error: ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '/d/db/oradata/db01/system01.dbf'
question:
1. Should I restore archive log files generated on July 16th back to orignal archive directory in order to avoid to recover failure?
2. Or Should I add the command "sql 'alter system archive log current'" in the backup script in order to avoid to recover failure?
The following is the detail information:
The database is ok when I try to do incomplete recovery database that was fully backed up on July,16th,2004. The database is oracle 8.1.7 and is in the archive mode:
The following is the backup script:
run {
allocate channel 'dev_0' type 'sbt_tape'
parms 'ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=db01,OB2BARLIST=ora8i_online)';
backup incremental level 0 filesperset 1
format 'ora8i_online<db01_%s:%t:%p>.dbf'
database
include current controlfile
archivelog all delete input;
I use it to do a full backup on July 16th,17th successfully.
And I use the following scripts to do incomplete recovery:
run {
allocate channel 'dev_0' type 'sbt_tape'
parms 'ENV=(OB2BARTYPE=ORACLE8,OB2APPNAME=db01)';
sql "alter database mount";
set until time ='17.07.2004';
restore database;
recover database;
sql "alter database open resetlogs";
sql "alter database open";
There script is successful in restore step. But there are some errors in recover step. The detail information is showing in following log:
RMAN-03022: compiling command: allocate
RMAN-03023: executing command: allocate
RMAN-08030: allocated channel: dev_0
RMAN-08500: channel dev_0: sid=13 devtype=SBT_TAPE
RMAN-08526: channel dev_0: HP OpenView OmniBack II A.04.10/176
RMAN-03022: compiling command: sql
RMAN-06162: sql statement: alter database mount
RMAN-03023: executing command: sql
RMAN-03022: compiling command: set
RMAN-03022: compiling command: restore
RMAN-03022: compiling command: IRESTORE
RMAN-03023: executing command: IRESTORE
RMAN-08016: channel dev_0: starting datafile backupset restore
RMAN-08502: set_count=2056 set_stamp=531622798 creation_time=16.07.2004
RMAN-08089: channel dev_0: specifying datafile(s) to restore from backup set
RMAN-08016: channel dev_0: starting datafile backupset restore
RMAN-08502: set_count=2180 set_stamp=531623409 creation_time=16.07.2004
RMAN-08089: channel dev_0: specifying datafile(s) to restore from backup set
RMAN-08523: restoring datafile 00001 to /d/db/oradata/db01/system01.dbf
RMAN-08023: channel dev_0: restored backup piece 1
RMAN-08511: piece handle=netace_ora8i_online<db01_2180:531623409:1>.dbf tag=null params=NULL
RMAN-08024: channel dev_0: restore complete
RMAN-08023: channel dev_0: restored backup piece 1
RMAN-08511: piece handle=netace_ora8i_online<db01_2212:531623994:1>.dbf tag=null params=NULL
RMAN-08024: channel dev_0: restore complete
RMAN-03022: compiling command: recover
RMAN-03022: compiling command: recover(1)
RMAN-03022: compiling command: recover(2)
RMAN-03022: compiling command: recover(3)
RMAN-03023: executing command: recover(3)
RMAN-08054: starting media recovery
RMAN-03022: compiling command: recover(4)
RMAN-03026: error recovery releasing channel resources
RMAN-11001: Oracle Error: ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '/d/db/oradata/db01/system01.dbf'
RMAN-08031: released channel: dev_1
RMAN-08031: released channel: dev_2
RMAN-08031: released channel: dev_0
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure during compilation of command
RMAN-03013: command type: recover
RMAN-03002: failure during compilation of command
RMAN-03013: command type: recover(4)
RMAN-06003: ORACLE error from target database: ORA-01220: file based sort illegal before database is open
ORA-06512: at "SYS.X$DBMS_RCVMAN", line 7220
ORA-06512: at "SYS.X$DBMS_RCVMAN", line 5053
ORA-06512: at line 1
I repeat my questions:
1. Should I restore archive log files generated on July 16th back to original archive directory in order to avoid to recover failure?
2. Or Should I add the command "sql 'alter system archive log current'" in the backup script in order to avoid to recover failure?
Can you help me ? Thank you.

You are correct. In RMAN8i, you should add the "alter system archive log current; command before you backup the archive logs.
You are running into the case where Oracle needs additional redo to make the database consistent that was located in the current online log at the time of the backup.
If you set UNTIL TIME to an earlier time does the recover work?
In Oracle9i, if you issue the command, "backup database plus archive logs", RMAN will automatically archive the current online log before performing the archive log backups.
Thanks, Tammy

If I need a full rman restore which backups will it use?

Hello,
I have a database 11.1.0.7 with 8TB. Block change tracking is enabled.
At the weekend I take level 0 backup and during the week level 1 cumulative.
For some weeks the level 0 backup is failing, so I only have level 1 cumulative backups taken every week day with a 4 weeks old level 0 backup.
If I need a full rman restore which backups will it use? Will it be the last level 0 backup with the last level 1 cumulative?
I ask this because grid crontrol tells me that the recent level 1 backups input size is smaller than last week level 1 backups and in between I dont have any level 0 sucessfull backups. Shouldn't the input size of level 1 cumulative increase until the next level 0 backup ?
The grid reports:
Backup Name Status Start Time Time Taken Type Output Devices Input Size Output Size Output Rate (Per Sec)
rman_df_lv1c COMPLETED 25/Jul/2011 21H00m WEST 02:33:29 DB INCR SBT_TAPE *1.32T* 289.02G 32.14M
rman_df_lv0 FAILED 23/Jul/2011 02H01m WEST DB INCR SBT_TAPE 8.78T 8.06T
rman_df_lv1c COMPLETED 21/Jul/2011 21H00m WEST 04:39:38 DB INCR SBT_TAPE *3.46T* 550.82G 33.62M
rman_df_lv1c COMPLETED 20/Jul/2011 21H00m WEST 04:47:36 DB INCR SBT_TAPE *3.37T* 524.36G 31.12M
rman_df_lv1c COMPLETED 19/Jul/2011 21H00m WEST 04:06:09 DB INCR SBT_TAPE *3.15T* 490.75G 34.03M
rman_df_lv1c COMPLETED 18/Jul/2011 21H00m WEST 03:40:24 DB INCR SBT_TAPE *2.49T* 410.88G 31.82M
rman_df_lv0 FAILED 16/Jul/2011 22H16m WEST DB INCR SBT_TAPE 6.27T 5.69T
rman_df_lv1c FAILED 14/Jul/2011 21H00m WEST 06:13:40 DB INCR SBT_TAPE 4.38T 714.30G 32.62M
rman_df_lv1c FAILED 13/Jul/2011 21H01m WEST 04:40:45 DB INCR SBT_TAPE 3.25T 542.98G 33.01M
rman_df_lv1c COMPLETED 12/Jul/2011 21H00m WEST 07:15:54 DB INCR SBT_TAPE 4.74T 847.93G 33.20M
rman_df_lv1c COMPLETED 11/Jul/2011 21H00m WEST 07:26:40 DB INCR SBT_TAPE 3.78T 766.40G 29.28M
rman_df_lv0 FAILED 9/Jul/2011 02H32m WEST 04:30:44 DB INCR SBT_TAPE 749.89G 716.02G 45.14M
rman_df_lv1c FAILED 7/Jul/2011 21H01m WEST 04:49:24 DB INCR SBT_TAPE 2.16T 515.90G 30.42M
rman_df_lv1c FAILED 6/Jul/2011 21H00m WEST 01:26:06 DB INCR SBT_TAPE 745.83G 165.48G 32.80M
rman_df_lv1c FAILED 5/Jul/2011 21H01m WEST 00:05:48 DB INCR SBT_TAPE 58.56G 7.56G 22.24M
rman_df_lv1c FAILED 4/Jul/2011 21H00m WEST 01:55:03 DB INCR SBT_TAPE 422.40G 79.55G 11.80M
rman_df_lv0 FAILED 3/Jul/2011 16H32m WEST 30:22:04 DB INCR SBT_TAPE 4.53T 4.21T 40.40M

>
If I need a full rman restore which backups will it use? Will it be the last level 0 backup with the last level 1 cumulative?
From http://download.oracle.com/docs/cd/B28359_01/backup.111/b28270/rcmvalid.htm
Validating Backups Before Restoring Them
You can run RESTORE ... VALIDATE to test whether RMAN can restore a specific file or set of files from a backup. RMAN chooses which backups to use.
The database must be mounted or open for this command. You do not have to take datafiles offline when validating the restore of datafiles, because validation of backups of the datafiles only reads the backups and does not affect the production datafiles.
When validating files on disk or tape, RMAN reads all blocks in the backup piece or image copy. RMAN also validates offsite backups. The validation is identical to a real restore operation except that RMAN does not write output files.
You can monitor what RESTORE VALIDATE does.
Make precautions, so you do not damage the production DB!!!
Iordan Iotzov
http://iiotzov.wordpress.com/

Restore from OSB. RMAN-06024: no backup or copy of the control file found

I backed up controlfile for standby on production server to OSB media:
-bash-3.00$ rman target / catalog rman/rman@emgc
Recovery Manager: Release 10.2.0.5.0 - Production on Tue Jan 25 15:15:33 2011
Copyright (c) 1982, 2007, Oracle. All rights reserved.
connected to target database: EMGC (DBID=1838014073)
connected to recovery catalog database
RMAN>
RMAN> CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 2 BACKUP TYPE TO COMPRESSED BACKUPSET;
RUN
ALLOCATE CHANNEL ch1 DEVICE TYPE 'SBT_TAPE';
BACKUP CURRENT CONTROLFILE FOR STANDBY tag 'stb_ctl';
RELEASE CHANNEL ch1;
CONFIGURE DEVICE TYPE 'SBT_TAPE' CLEAR;
new RMAN configuration parameters:
CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 2 BACKUP TYPE TO COMPRESSED BACKUPSET;
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN> 2> 3> 4> 5> 6>
allocated channel: ch1
channel ch1: sid=1085 devtype=SBT_TAPE
channel ch1: Oracle Secure Backup
Starting backup at 25-JAN-11
channel ch1: starting compressed full datafile backupset
channel ch1: specifying datafile(s) in backupset
including standby control file in backupset
channel ch1: starting piece 1 at 25-JAN-11
channel ch1: finished piece 1 at 25-JAN-11
piece handle=1em30ngu_1_1 tag=STB_CTL comment=API Version 2.0,MMS Version 10.3.0.2
channel ch1: backup set complete, elapsed time: 00:00:27
Finished backup at 25-JAN-11
released channel: ch1
RMAN> list backup of controlfile;
old RMAN configuration parameters:
CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 2 BACKUP TYPE TO COMPRESSED BACKUPSET;
RMAN configuration parameters are successfully reset to default value
starting full resync of recovery catalog
full resync complete
List of Backup Sets
===================
BS Key Type LV Size Device Type Elapsed Time Completion Time
1479 Full 512.00K SBT_TAPE 00:00:18 25-JAN-11
BP Key: 1480 Status: AVAILABLE Compressed: YES Tag: STB_CTL
Handle: 1em30ngu_1_1 Media: mf_rman-000003
Standby Control File Included: Ckp SCN: 33567224 Ckp time: 25-JAN-11
RMAN>
On standby server I try to restore this control file but there is some trouble with restore... By the way I can delete that backup piece...
-bash-3.00$ rman target / catalog rman/rman@emgc
Recovery Manager: Release 10.2.0.5.0 - Production on Tue Jan 25 15:34:32 2011
Copyright (c) 1982, 2007, Oracle. All rights reserved.
connected to target database: emgc (not mounted)
connected to recovery catalog database
RMAN> set DBID=1838014073;
executing command: SET DBID
database name is "EMGC" and DBID is 1838014073
RMAN> RUN
ALLOCATE CHANNEL ch1 DEVICE TYPE 'SBT_TAPE';
crosscheck backup of controlfile;
2> 3> 4> 5>
allocated channel: ch1
channel ch1: sid=1093 devtype=SBT_TAPE
channel ch1: Oracle Secure Backup
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=1em30ngu_1_1 recid=40 stamp=741367328
Crosschecked 1 objects
released channel: ch1
RMAN> list backup of controlfile;
List of Backup Sets
===================
BS Key Type LV Size Device Type Elapsed Time Completion Time
1479 Full 512.00K SBT_TAPE 00:00:18 25-JAN-11
BP Key: 1480 Status: AVAILABLE Compressed: YES Tag: STB_CTL
Handle: 1em30ngu_1_1 Media: mf_rman-000003
Standby Control File Included: Ckp SCN: 33567224 Ckp time: 25-JAN-11
RMAN> RUN
ALLOCATE CHANNEL ch1 DEVICE TYPE 'SBT_TAPE';
RESTORE CONTROLFILE FROM TAG 'STB_CTL';
2> 3> 4> 5>
allocated channel: ch1
channel ch1: sid=1093 devtype=SBT_TAPE
channel ch1: Oracle Secure Backup
Starting restore at 25-JAN-11
released channel: ch1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 01/25/2011 15:35:20
RMAN-06026: some targets not found - aborting restore
RMAN-06024: no backup or copy of the control file found to restore
RMAN> RUN
ALLOCATE CHANNEL ch1 DEVICE TYPE 'SBT_TAPE';
delete noprompt backup of controlfile;
2> 3> 4> 5>
allocated channel: ch1
channel ch1: sid=1093 devtype=SBT_TAPE
channel ch1: Oracle Secure Backup
List of Backup Pieces
BP Key BS Key Pc# Cp# Status Device Type Piece Name
1480 1479 1 1 AVAILABLE SBT_TAPE 1em30ngu_1_1
deleted backup piece
backup piece handle=1em30ngu_1_1 recid=40 stamp=741367328
Deleted 1 objects
released channel: ch1
RMAN>

You cannot specify a tag for a standby control file.
read here
http://download.oracle.com/docs/cd/B10501_01/server.920/a96566/rcmstand.htm#1002594
Edited by: Adigozalov Gurban on Jan 25, 2011 2:14 PM

Restore to a different node with RMAN and EMC Networker

Please, really need help :)
I took hotbackup using RMAN catalog which went to tape. Here is the script for that:
connect target sys/****@PROD;*
connect rcvcat rman/***@catalog;*
*run {*
allocate channel t1 type 'SBT_TAPE';
send 'NSR_ENV=(NSR_SERVER="**",NSR_DATA_VOLUME_POOL=Oracle)';*
*backup database plus archivelog;*
*release channel t1;*
My settings include control file autobackup as follows:
*RMAN> show all;*
*RMAN configuration parameters are:*
*CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 10 DAYS;*
*CONFIGURE BACKUP OPTIMIZATION OFF; # default*
*CONFIGURE DEFAULT DEVICE TYPE TO DISK;*
*CONFIGURE CONTROLFILE AUTOBACKUP ON;*
*CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE 'SBT_TAPE' TO '/NMO_%F/';*
*CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default*
*CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default*
*CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default*
*CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default*
*CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/data/backups/PROD/ora_df%t_s%s_s%p';*
*CONFIGURE MAXSETSIZE TO UNLIMITED; # default*
*CONFIGURE ENCRYPTION FOR DATABASE OFF; # default*
*CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default*
*CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default*
*CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/data/backups/PROD/hotbkp/snapcf_PROD.f';*
I am trying to restore this backup that is on tape (EMC Networker) to a different node. I can do this outside of Networker without any problems. However, when I try to get the backup from tape I have this issue:
1. initPROD.ora is created and modified accordingly on a new server
2. Export sid, startup nomount on new server
export ORACLE_SID=PROD (on this new server)
*rman target /*
*startup nomount*
3. I then run the following and get this error:
*RMAN> run {*
*2> allocate channel t1 type 'SBT_TAPE'*
*3> send 'NSR_ENV=(NSR_SERVER="***",NSR_CLIENT="********")';*
*4> restore controlfile from autobackup;*
*5> sql 'alter database mount';*
*6> sql 'alter database rename file "/data/dbf/PROD/redo01.log" to "/data/scratch/dbf/PROD/redo01.log"';*
*7> sql 'alter database rename file "/data/dbf/PROD/redo02.log to "/data/scratch/dbf/PROD/redo02.log"';*
*8> sql 'alter database rename file "/data/dbf/PROD/redo03.log to "/data/scratch/dbf/PROD/redo03.log"';*
*9> set until sequence 22; (I get this from archive logs)*
*10> set newname for datafile 1 to '/data/scratch/dbf/PROD/system01.dbf';*
*11> set newname for datafile 2 to '/data/scratch/dbf/PROD/undotbs01.dbf';*
*12> set newname for datafile 3 to '/data/scratch/dbf/PROD/sysaux01.dbf';*
*13> set newname for datafile 4 to '/data/scratch/dbf/PROD/users01.dbf';*
*14> restore database;*
*15> switch datafile all;*
*16> recover database;*
*17> alter database open resetlogs;*
*18> }*
*allocated channel: t1*
*channel t1: sid=149 devtype=SBT_TAPE*
*channel t1: NMO v4.5.0.0*
*Starting restore at 27-FEB-09*
*released channel: t1*
*RMAN-00571: ===========================================================*
*RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============*
*RMAN-00571: ===========================================================*
*RMAN-03002: failure of restore command at 02/27/2009 22:10:43*
*RMAN-06495: must explicitly specify DBID with SET DBID command*
I cannot seem to pass this error. This error indicates that the db has to be either mounted or DBID set before the restore of teh controlfile. Mounting db before the restore of the controlfile does not work. Setting db id 1) does not make sense because if the primary db is down then I cannot get it, right? My primary is up now, so I was able to get db id, but setting it made the restore hang with the following:
*RMAN> run {*
*connect target*
*set dbid=466048808*
*2> allocate channel t1 type 'SBT_TAPE'*
*3> send 'NSR_ENV=(NSR_SERVER="***",NSR_CLIENT="********")';*
*4> restore controlfile from autobackup;*
*5> sql 'alter database mount';*
*6> sql 'alter database rename file "/data/dbf/PROD/redo01.log" to "/data/scratch/dbf/PROD/redo01.log"';*
*7> sql 'alter database rename file "/data/dbf/PROD/redo02.log to "/data/scratch/dbf/PROD/redo02.log"';*
*8> sql 'alter database rename file "/data/dbf/PROD/redo03.log to "/data/scratch/dbf/PROD/redo03.log"';*
*9> set until sequence 22; (I get this from archive logs)*
*10> set newname for datafile 1 to '/data/scratch/dbf/PROD/system01.dbf';*
*11> set newname for datafile 2 to '/data/scratch/dbf/PROD/undotbs01.dbf';*
*12> set newname for datafile 3 to '/data/scratch/dbf/PROD/sysaux01.dbf';*
*13> set newname for datafile 4 to '/data/scratch/dbf/PROD/users01.dbf';*
*14> restore database;*
*15> switch datafile all;*
*16> recover database;*
*17> alter database open resetlogs;*
*18> }*
*connected to target database: PROD (not mounted)*
*executing command: SET DBID*
*using target database control file instead of recovery catalog*
*allocated channel: t1*
*channel t1: sid=152 devtype=SBT_TAPE*
*channel t1: NMO v4.5.0.0*
*Starting restore at 27-FEB-09*
*channel t1: looking for autobackup on day: 20090227*
*channel t1: looking for autobackup on day: 20090226*
*channel t1: looking for autobackup on day: 20090225*
It looks like it cannot find the autbackup of controlfile? But when I list backup while connected to the target db and rman catalog, I see that autobackup is included in every hot backup that we do:
*BS Key Type LV Size Device Type Elapsed Time Completion Time*
*4639 Full 7.00M SBT_TAPE 00:00:04 27-FEB-09*
*BP Key: 4641 Status: AVAILABLE Compressed: NO Tag: TAG20090227T150141*
*Handle: /NMO_c-466048808-20090227-01/ Media:*
*Control File Included: Ckp SCN: 23352682865 Ckp time: 27-FEB-09*
*SPFILE Included: Modification time: 26-FEB-09*
I am stuck What I am doing wrong? Thank you!
Edited by: rysalka on Feb 28, 2009 8:35 AM

Do a list command to see if the controlfile backup is on tape.
RMAN> list backup of controlfile;
I suggest you to read the manual of EMC Networker or call EMC on how to restore the database to another node. I am using Veritas Netbackup, it may be similar to EMC Networke for your reference. There are a few things that need to be followed when you restore database to another node:
1) set DB_ID, which you have done
2) set NB_CLIENT (in your case NSR_CLIENT) to the primary node from where backup was taken
3) configure the backup server to allow redirect restore between the two nodes.
Hope this helps.

10g Physical Standby to be used for Backup through RMAN

Dear All,
I have 10g Database Primary and Standby Server which is operating in Maximum Performance Mode. I want to use Standby Database for performing Weekly Full and Daily Incremental Backups through RMAN. Kindly inform me is it possible, if yes how should I configure it. I will also be using Compression and Encryption while performing backups.
Best Regards,
Asif

Yes, that is possible.
Because the standby databases are in mount mode, they can be accessed through the SYS account .
I use the following RMAN script for the same purpose. Please note that we have configure the flashback area, so we are not letting RMAN delete the archive files:
run {
sql 'alter system archive log current';
sql 'alter system archive log current';
allocate channel ch1 type 'sbt_tape' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
backup
incremental level 0
tag full_bk_db_webshop
format 'df_%d_t%t_s%s_p%p'
(database include current controlfile);
backup archivelog all;
This script is for a FULL backup ( level 0 ). You could also use the "backup full" command
You can easily change the level of the Backup for incremental purposes.
Starting RMAN - if configured correctly - is the same as with an open database
export ORACLE_SID=<STDBYSID>
rman target / rcvcat <rman/rman>@<catalogsid>
the user for, and the catalogsid are merely examples
Edited by: fjfranken on Mar 24, 2009 4:07 AM

RMAN-06004:ORACLE error from recovery catalog ... ORA-00904: : invalid ...

Good Morning All,
One of our RMAN backups is failing with the following error message. Any suggestions would be greatly appreciated.
==================================================================================================
Starting backup at 12/30/2008 22:03:47
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 12/30/2008 22:03:47
RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
RMAN>
RMAN> ##BACKUP ARCHIVELOG ALL FORMAT '%d_bkp_al_%t_Set%s_Piece%p' delete input;
2>
3> # DELETE ARCHIVELOG UNTIL TIME 'SYSDATE-7';
4>
5> # check if database can be restored
6> # RESTORE DATABASE VALIDATE;
7>
8> # check if controlfile can be restored
9> ##RESTORE CONTROLFILE to '/backups/admin/custpr/custpr_bkp_cntlfile.ctl' VALIDATE;
10>
11> # check if archivelogs for the past two weeks can be restored
12> # RESTORE ARCHIVELOG FROM TIME 'SYSDATE-7' VALIDATE;
13>
14> # - Verify all backups on backup media are intact
15> # CROSSCHECK BACKUP OF DATABASE;
16>
17> # - Display a list of files that need to be backed up based on the retention
18> # policy. For this case study, files that don't have at least 1 backups
19> # will be reported.
20> REPORT NEED BACKUP;
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 7 days
Report of files whose recovery needs more than 7 days of archived logs
File Days Name
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of report command at 12/30/2008 22:03:48
RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
RMAN>
RMAN> # - delete un-necessary backups. This command deletes backups based on the
2> # retention policy.
3> ######### commented out DELETE OBSOLETE - TSM not configured to delete on 68
4> #########DELETE OBSOLETE;
5>
6> # - get complete list of existing backups
7> LIST BACKUP;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of list command at 12/30/2008 22:03:49
RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
RMAN>
RMAN> #-end of file-
2> **end-of-file**
RMAN>
Edited by: ORA_UMAIR on Dec 31, 2008 7:51 AM

This Oracle Database is 9.2.0.6.0. Here is the complete log file. The RMAN script that I am using ran successfully many times before.
====================================================================================================
Recovery Manager: Release 9.2.0.6.0 - 64bit Production
Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
RMAN>
connected to recovery catalog database
RMAN>
connected to target database: CUSTPR (DBID=525071053)
RMAN>
RMAN> #########################################################################
2> # LEVEL 0 BACKUP #
3> #########################################################################
4>
5> # Configure backups to be written to disk.
6> CONFIGURE DEFAULT DEVICE TYPE TO DISK;
old RMAN configuration parameters:
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
new RMAN configuration parameters:
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Set the retention policy to a recovery window of 7 days. This ensures that
2> # RMAN retains all backups needed to recover the database to any point in time
3> # in the last 7 days. You can use the DELETE OBSOLETE command to delete
4> # backups that are no longer required by the retention policy. To exclude a
5> # backup from consideration by the policy, you can use KEEP option with the
6> # BACKUP command.
7> CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
old RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
new RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Configure RMAN to use two disk channels for backup, restore, recovery, and
2> # maintenance operations.
3> CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
old RMAN configuration parameters:
CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
new RMAN configuration parameters:
CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Configure RMAN to write disk backups to the /backup directory.
2> # The format specifier %t is replaced with a 4-byte timestamp, %s with the
3> # backup set number, and %p with the backup piece number.
4> CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p';
old RMAN configuration parameters:
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p';
new RMAN configuration parameters:
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p';
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Configure RMAN to back up the control file after each backup.
2> CONFIGURE CONTROLFILE AUTOBACKUP ON;
old RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP ON;
new RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP ON;
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Configure RMAN to write controlfile autobackups to the /backup directory.
2> CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backups/admin/custpr/%d_bkp_cf%F';
old RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backups/admin/custpr/%d_bkp_cf%F';
new RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backups/admin/custpr/%d_bkp_cf%F';
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Enable the backup optimization feature introduced in 9i to make sure that
2> # RMAN won't backup an archivelog or datafile if there already exists a backup
3> # of that file. The FORCE option can be used to override optimization on a
4> # specific BACKUP command.
5> CONFIGURE BACKUP OPTIMIZATION ON;
old RMAN configuration parameters:
CONFIGURE BACKUP OPTIMIZATION ON;
new RMAN configuration parameters:
CONFIGURE BACKUP OPTIMIZATION ON;
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Use the SHOW ALL command to see the current configuration settings.
2> SHOW ALL ;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE 'SBT_TAPE' TO '%d_bkp_cf%F';
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backups/admin/custpr/%d_bkp_cf%F';
CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 1;
CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' FORMAT '%d_bkp_df%t_Set%s_Piece%p';
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p';
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/orahome2/custprdb/9.2.0/dbs/snapcf_custpr.f'; # default
RMAN>
RMAN> # The following commands are run each day to start the backup cycle.
2> # The steps are:
3> # - Take an incremental level 0 backup of the database. A level 0 backup is
4> # a complete backup of the entire file which can be used as the basis
5> # for a subsequent incremental backup.
6> # - Backup all archivelogs that have not already been backed up.
7> # - Delete on-disk archivelogs older than seven days.
8>
9> BACKUP INCREMENTAL LEVEL 0 FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p'
10> DATABASE maxsetsize 33G
11> PLUS ARCHIVELOG FORMAT '/backups/admin/custpr/%d_bkp_al%t_Set%s_Piece%p'
12> delete all input;
Starting backup at 12/30/2008 22:01:40
current log archived
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=11 devtype=DISK
channel ORA_DISK_1: starting archive log backupset
channel ORA_DISK_1: specifying archive log(s) in backup set
input archive log thread=1 sequence=8008 recid=7910 stamp=674638862
input archive log thread=1 sequence=8009 recid=7911 stamp=674671207
input archive log thread=1 sequence=8010 recid=7912 stamp=674697380
input archive log thread=1 sequence=8011 recid=7913 stamp=674780433
input archive log thread=1 sequence=8012 recid=7914 stamp=674784211
input archive log thread=1 sequence=8013 recid=7915 stamp=674863288
input archive log thread=1 sequence=8014 recid=7916 stamp=674863300
channel ORA_DISK_1: starting piece 1 at 12/30/2008 22:01:41
channel ORA_DISK_1: finished piece 1 at 12/30/2008 22:03:47
piece handle=/backups/admin/custpr/CUSTPR_bkp_al674863300_Set3083_Piece1 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:02:07
channel ORA_DISK_1: deleting archive log(s)
archive log filename=/custpr/arch/arch_custpr_8008.log recid=7910 stamp=674638862
archive log filename=/custpr/arch/arch_custpr_8009.log recid=7911 stamp=674671207
archive log filename=/custpr/arch/arch_custpr_8010.log recid=7912 stamp=674697380
archive log filename=/custpr/arch/arch_custpr_8011.log recid=7913 stamp=674780433
archive log filename=/custpr/arch/arch_custpr_8012.log recid=7914 stamp=674784211
archive log filename=/custpr/arch/arch_custpr_8013.log recid=7915 stamp=674863288
archive log filename=/custpr/arch/arch_custpr_8014.log recid=7916 stamp=674863300
Finished backup at 12/30/2008 22:03:47
Starting backup at 12/30/2008 22:03:47
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 12/30/2008 22:03:47
RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
RMAN>
RMAN> ##BACKUP ARCHIVELOG ALL FORMAT '%d_bkp_al_%t_Set%s_Piece%p' delete input;
2>
3> # DELETE ARCHIVELOG UNTIL TIME 'SYSDATE-7';
4>
5> # check if database can be restored
6> # RESTORE DATABASE VALIDATE;
7>
8> # check if controlfile can be restored
9> ##RESTORE CONTROLFILE to '/backups/admin/custpr/custpr_bkp_cntlfile.ctl' VALIDATE;
10>
11> # check if archivelogs for the past two weeks can be restored
12> # RESTORE ARCHIVELOG FROM TIME 'SYSDATE-7' VALIDATE;
13>
14> # - Verify all backups on backup media are intact
15> # CROSSCHECK BACKUP OF DATABASE;
16>
17> # - Display a list of files that need to be backed up based on the retention
18> # policy. For this case study, files that don't have at least 1 backups
19> # will be reported.
20> REPORT NEED BACKUP;
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 7 days
Report of files whose recovery needs more than 7 days of archived logs
File Days Name
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of report command at 12/30/2008 22:03:48
RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
RMAN>
RMAN> # - delete un-necessary backups. This command deletes backups based on the
2> # retention policy.
3> ######### commented out DELETE OBSOLETE - TSM not configured to delete on 68
4> #########DELETE OBSOLETE;
5>
6> # - get complete list of existing backups
7> LIST BACKUP;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of list command at 12/30/2008 22:03:49
RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
RMAN>
RMAN> #-end of file-
2> **end-of-file**
RMAN>
Recovery Manager complete.

RMAN (DP6.0) backup failure on Oracle10g

Hello,
I am using DP6.0 with Oracle10g environment for backup.
While I was able to successfully able to allocate the channels I am getting the below error message stack when the backup script is executed.
Thanks
RMAN> CONNECT TARGET *
2> run {
3> allocate channel 'dev_0' type 'sbt_tape'
4> parms 'ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=<SID>,OB2BARLIST=<SID>BAZAORACLE,OB2BARHOSTNAME=server.xx.yy)';
5> backup incremental level 0
6> format '<SID>BAZAORACLE<<SID>_%s:%t:%p>.dbf'
7> database;
8> sql 'alter system archive log current';
9> backup
10> format '<SID>BAZAORACLE<<SID>_%s:%t:%p>.dbf'
11> archivelog all;
12> delete archivelog until time 'sysdate-1';
13> backup
14> format '<SID>BAZAORACLE<<SID>_%s:%t:%p>.dbf'
15> current controlfile;
16> }
17> EXIT
connected to target database: <SID> (DBID=3497973964)
using target database control file instead of recovery catalog
allocated channel: dev_0
channel dev_0: sid=134 devtype=SBT_TAPE
channel dev_0: Data Protector A.06.00/DPWIN_00268
released channel: dev_0
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on dev_0 channel at 06/21/2007 12:00:20
ORA-19506: failed to create sequential file, name="<SID>_BAZA_ORACLE<<SID>_7:625838365:1>.dbf", parms=""
ORA-27028: skgfqcre: sbtbackup returned error
ORA-19511: Error received from media manager layer, error text:
Vendor specific error: OB2_StartObjectBackup() failed ERR(8010)
Recovery Manager complete.
[Major] From: [email protected] "<SID>" Time: 21.6.2007 12:00:20
     The database reported error while performing requested operation.
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on dev_0 channel at 06/21/2007 12:00:20
ORA-19506: failed to create sequential file, name="<SID>_BAZA_ORACLE<<SID>_7:625838365:1>.dbf", parms=""
ORA-27028: skgfqcre: sbtbackup returned error
ORA-19511: Error received from media manager layer, error text:
Vendor specific error: OB2_StartObjectBackup() failed ERR(8010)
Recovery Manager complete.
[Major] From: [email protected] "<SID>" Time: 21.6.2007 12:00:20
     Oracle Recovery Manager completed with errors.
[Major] From: [email protected] "<SID>" Time: 21.6.2007 12:00:20
     Backup of target database failed
*************************************************************************************

I changed the tapes and backup drive but problem is standing. Now the message is:
released channel: dev_0
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on dev_0 channel at 07/04/2007 09:11:48
ORA-19506: failed to create sequential file, name="<SID>_BAZA_ORACLE<<SID>_15:627037853:1>.dbf", parms=""
ORA-27028: skgfqcre: sbtbackup returned error
ORA-19511: Error received from media manager layer, error text:
Vendor specific error: OB2_StartObjectBackup() failed ERR(8010)
Recovery Manager complete.
[Major] From: [email protected] "<SID>" Time: 4.7.2007 9:11:49
[Critical] From: [email protected] "LTO2-1_server" Time: 4.7.2007 9:12:01
IPC Cannot Allocate Shared Memory Segment
     The database reported error while performing requested operation.
[Normal] From: [email protected] "LTO2-1_server" Time: 4.7.2007 9:12:07
     scsi5:0:1:0C
     Medium header verification completed, 0 errors found
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on dev_0 channel at 07/04/2007 09:11:48
ORA-19506: failed to create sequential file, name="<SID>_BAZA_ORACLE<<SID>_15:627037853:1>.dbf", parms=""
ORA-27028: skgfqcre: sbtbackup returned error
ORA-19511: Error received from media manager layer, error text:
Vendor specific error: OB2_StartObjectBackup() failed ERR(8010)
Recovery Manager complete.
[Major] From: [email protected] "<SID>" Time: 4.7.2007 9:11:49
     Oracle Recovery Manager completed with errors.
[Major] From: [email protected] "<SID>" Time: 4.7.2007 9:11:49
     Backup of target database failed.
Please help me.... I don't have backup 20 days...

How to restore a database from host A to host B by using RMAN

Hi there
I wanted to restore 1 database from machine A to machine B with the differente files systemes. I did these steps below, but I have a problem when I restore the controlfile from machine A to machine B.
1-copy the controlfile from machine A to machine B by using OS utility.
2-startup nomount the database on machine B.
3-connect target and catalog RMAN.
4-I have to restore the controlfile from last full backup of the machine A to machine B (see the procedure RMAN).
I have the error messages like:
RMAN> connect target /
RMAN-06006: connected to target database: dbtest (not mounted)
RMAN> connect catalog rman/rman@rcattest
RMAN-06008: connected to recovery catalog database
RMAN> run {
2> allocate channel c1 type 'sbt_tape' ;
3> restore controlfile ;
4> }
RMAN-03022: compiling command: allocate
RMAN-03023: executing command: allocate
RMAN-08030: allocated channel: c1
RMAN-08500: channel c1: sid=10 devtype=SBT_TAPE
RMAN-08526: channel c1: VERITAS NetBackup for Oracle8 - Release 3.2GA
RMAN-03022: compiling command: restore
RMAN-03022: compiling command: IRESTORE
RMAN-03023: executing command: IRESTORE
RMAN-08016: channel c1: starting datafile backupset restore
RMAN-08502: set_count=177 set_stamp=419449530 creation_time=19-JAN-01
RMAN-08021: channel c1: restoring controlfile
RMAN-08505: output filename=/db/oracle/dbtest/dbtestcontrol01.ctl
RMAN-03026: error recovery releasing channel resources
RMAN-08031: released channel: c1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure during compilation of command
RMAN-03013: command type: restore
RMAN-03007: retryable error occurred during execution of command: IRESTORE
RMAN-07004: unhandled exception during command execution on channel c1
RMAN-10035: exception raised in RPC: ORA-19507: failed to retrieve sequential file, handle="5hcg0ilq_1_1", parms=""
ORA-27029: skgfrtrv: sbtrestore returned error
ORA-19511: sbtrestore: Backup file not found.
RMAN-10031: ORA-19624 occurred during call to DBMS_BACKUP_RESTORE.RESTOREBACKUPPIE
null

Hi there
I'm also trying to restore a full RMAN backup to our DR site using Netbackup as MML
My scenario is:
We have one tape library at our PROD data center and another one at our DR site both using Netbackup as Storage manager
I performed a full RMAN backup on 4 DLT tapes with recovery catalog at our PROD datacenter, then I removed the 4 tapes and place it in our tape lib at DR site
I tried to import the tapes using bpimport from Netbackup which has been successful up to now
But when I tried to restore controlfile from RMAN, I get the following error:
connected to target database: prod (not mounted)
connected to recovery catalog database
RMAN> run {
2> allocate channel c1 type 'SBT_TAPE';
3> allocate channel c2 type 'SBT_TAPE';
4> allocate channel c3 type 'SBT_TAPE';
5> allocate channel c4 type 'SBT_TAPE';
6> set until time '16-AUG-2005 15:00:00';
7> restore controlfile;
8> }
allocated channel: c1
channel c1: sid=13 devtype=SBT_TAPE
channel c1: VERITAS NetBackup for Oracle - Release 5.0GA (2003103005)
allocated channel: c2
channel c2: sid=12 devtype=SBT_TAPE
channel c2: VERITAS NetBackup for Oracle - Release 5.0GA (2003103005)
allocated channel: c3
channel c3: sid=11 devtype=SBT_TAPE
channel c3: VERITAS NetBackup for Oracle - Release 5.0GA (2003103005)
allocated channel: c4
channel c4: sid=9 devtype=SBT_TAPE
channel c4: VERITAS NetBackup for Oracle - Release 5.0GA (2003103005)
executing command: SET until clause
Starting restore at 18-AUG-2005:10:28:23
channel c1: starting datafile backupset restore
channel c1: restoring controlfile
output filename=/oracle9i/dba/dbs/control01_drprod.ctl
released channel: c1
released channel: c2
released channel: c3
released channel: c4
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 08/18/2005 10:28:25
ORA-19507: failed to retrieve sequential file, handle="df_t566491965_s8860_p1", parms=""
ORA-27029: skgfrtrv: sbtrestore returned error
ORA-19511: Error received from media manager layer, error text:
Failed to process backup file <df_t566491965_s8860_p1>
Anyone mastering this, please help !!
thks
BL

Using variables in RMAN - Unix Shell script

I am new to Oracle and would appreciate advise on my requirement below.
Environment:
Oracle DB Version 11.2.0.3.0
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production with 2 nodes RAC.
Requirement :
Daily at morning 5:00, Flashback the database to the yesterday restore point.
It has to be scheduled to be done automatically. Now it being performed manually.
Psuedo code:
1. Shutdown the RAC database
2. Bring up the RAC database with mount mode
3. Flashback the database to yesterday restore point
4. Create new restore point to be used on next day
5. Bring up other instance of the RAC database.
#!/bin/ksh
# Shutdown databases and bring up one instance in NOMOUNT mode.
# Set Oracle 11gR2 Enviornment variables
. ora11gr2setup
# Check the status of the database
echo srvctl status database -d TestDB
srvctl status database -d TestDB
# Stop the RAC database
echo srvctl stop database -d TestDB
srvctl stop database -d TestDB
# Start one instance of the database with mount mode
echo srvctl start instance -d TestDB -i TestDB1 -o mount
srvctl start instance -d TestDB -i TestDB1 -o mount
# Set database contect
. setdb TestDB
start_dt=`date +%Y%m%d_%H%M`
job=`basename $0 ".sh"`
rman >> ${job}_${start_dt}.log 2>&1 <<eof
set echo on;
#connect catalog rman/rman@recovery_catalog_database
connect catalog rman/rman123@rmandb
connect target / ; #(instance name, not database name)
run {
allocate CHANNEL dev_2 TYPE 'SBT_TAPE' format '%U' PARMS 'SBT_LIBRARY=/opt/omni/lib/libob2oracle8_64bit.so,ENV=(OB2BARTYPE=Oracle8)';
allocate CHANNEL dev_3 TYPE 'SBT_TAPE' format '%U' PARMS 'SBT_LIBRARY=/opt/omni/lib/libob2oracle8_64bit.so,ENV=(OB2BARTYPE=Oracle8)';
allocate CHANNEL dev_4 TYPE 'SBT_TAPE' format '%U' PARMS 'SBT_LIBRARY=/opt/omni/lib/libob2oracle8_64bit.so,ENV=(OB2BARTYPE=Oracle8)';
flashback database to restore point BEFORE_TEST_20130416_5AM;
sql "alter database open resetlogs";
release channel dev_2;
release channel dev_3;
release channel dev_4;
# create new restore point, which will be used on next day
sql "create restore point BEFORE_TEST_20130417_5AM";
show all;
exit
eof
echo srvctl status database -d TestDB
srvctl status database -d TestDB
echo srvctl start instance -d TestDB -i TestDB2 -o mount
srvctl start instance -d TestDB -i TestDB2 -o mount
echo srvctl status database -d TestDB
srvctl status database -d TestDB
eofQuestions:
1. How can i get the laterst restore point for the database and pass it on the RMAN FLASHBACK command?
2. How can I create new restore point with todays date suffixed with lable like BEFORE_TEST_20130417_5AM, with in RMAN ?

Hi,
Why You are allocating the RMAN Channel..
You can restore the database from restore point from Sql prompt
startup mount
flashback database to restore point <res_name>;
alter database open resetlogs;what is the use of Previous restore point.. so you can drop the restore point after the restore and create new one.
Pass the $tag in the restore point.. and assign $tag=date
HTH
Edited by: DK2010 on Apr 18, 2013 3:26 AM

RMAN cold backup taking more time than usual

Hi everybody.. please help me resolving below issue..
I have configured the RMAN in one of the production database with separate catalogue database six months earlier. I have sceduled weekly cold backup through RMAN on sunday 6pm. Normally it used to take one hour to complete the cold backup and database goes down soon as the job starts.
But since from then every week the time taken to just initiate the database shutdown continuosly increasing and recently when i checked it is taking 1 hour to initiate the database shutdown. Once the initiation starts it hardly take 1 to 3 min to shutdown.
Database is up and running during that one Hour. I was in the assumption that RMAN takes some time to execute its internal packages.
Please help
Regards,
Arun Kumar

Hi John and Tychos,
Thank you very much for your valuable inputs.
Yesterday there was cold backup and i have monitored the CPU usage. But there was no load on the CPU at that time and CPU usage was 0%
I have tried connecting to RMAN manually and it connects within a second. And also noticed in prstat -a that rman connects as soon as the job starts.
So i think that its taking time at the deleting obsolete backups.
But I have observerd following observation.
Before executing the delete obsolete command as mentioned before
RMAN> REPORT OBSOLETE RECOVERY WINDOW OF 35 DAYS DEVICE TYPE 'SBT_TAPE';
Report of obsolete backups and copies
Type Key Completion Time Filename/Handle
Backup Set 83409 25-JUL-09
Backup Piece 83587 25-JUL-09 arc_SID_20090725_557_1
Backup Set 83410 25-JUL-09
Backup Piece 83588 25-JUL-09 arc_SID_20090725_558_1
Backup Set 83411 25-JUL-09
Backup Piece 83589 25-JUL-09 arc_SID_20090725_559_1
After executing the delete obsolete command
RMAN> REPORT OBSOLETE RECOVERY WINDOW OF 35 DAYS DEVICE TYPE 'SBT_TAPE';
Report of obsolete backups and copies
Type Key Completion Time Filename/Handle
Backup Set 83409 25-JUL-09
Backup Piece 83587 25-JUL-09 arc_SID_20090725_557_1
Backup Set 83410 25-JUL-09
Backup Piece 83588 25-JUL-09 arc_SID_20090725_558_1
Backup Set 83411 25-JUL-09
Backup Piece 83589 25-JUL-09 arc_SID_20090725_559_1
Please advice me on the following.
1. Why its not deleting the obsolete BACKUP SETS?
2. Is it normal that RMAN takes this much deleting obsolete backup sets? How can i minimize the time taking for deleting obsolete files.
Thanks and Regards,
Arun Kumar

RMAN Delete Obsolete job fails due to Error Allocating Device

Experts, I need help, please.
This is 10.2.0.1 on Windows
RMAN> DELETE NOPROMPT OBSOLETE;
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 3 days
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=130 devtype=DISK
released channel: ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of delete command at 05/15/2012 14:10:17
ORA-19554: error allocating device, device type: SBT_TAPE, device name:
ORA-27211: Failed to load Media Management Library
I ran RMAN> configure device type 'SBT_TAPE' clear;
but I still get the same error.
I backup to Disk, not tape
Notice the reference to SBT_TAPE:
RMAN configuration parameters are:
CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO BACKUPSET PARALLELISM 1;
CONFIGURE DEVICE TYPE SBT_TAPE PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
What do I need to do to be able to run DELETE OBSOLETE; ?
Thanks, John

as anand mention ,you've to reset this parameter to default value.
and clear cmd with configure will remove it from configuration parameter
see below
RMAN> show all;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP OFF; # default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE SBT_TAPE TO '%F'; # default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
*CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 1 BACKUP TYPE TO BACKUPSET;*
CONFIGURE DEVICE TYPE DISK PARALLELISM 2 BACKUP TYPE TO BACKUPSET;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/10/db/dbs/snapcf_GG1.f'; # default
RMAN> delete obsolete;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of delete command at 05/16/2012 12:04:34
ORA-19554: error allocating device, device type: SBT_TAPE, device name:
ORA-27211: Failed to load Media Management Library
Additional information: 2
RMAN> CONFIGURE DEVICE TYPE 'SBT_TAPE' clear;
old RMAN configuration parameters:
CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 1 BACKUP TYPE TO BACKUPSET;
RMAN configuration parameters are successfully reset to default value
RMAN> show all;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP OFF; # default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 2 BACKUP TYPE TO BACKUPSET;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/10/db/dbs/snapcf_GG1.f'; # default
RMAN> delete obsolete;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 1
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=1591 instance=GG1 devtype=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: sid=1627 instance=GG1 devtype=DISK
no obsolete backups found

RMAN Clone Errors

Hello,
We use Commvault for our backup software. I can successfully clone one application's PROD instance on server1 to TEST on server2.
However, for another application, attempting the same process of cloning the app's PROD instance on server1 to TEST on server2, I'm getting RMAN errors.
The prod database is ISLP and test database is ISLT. I've set the parameters:
o alter system set db_file_name_convert = '/u02/oradata/ISLP', '/u02/oradata/ISLT'
o alter system set log_file_name_convert= '/u01/oradata/ISLP', '/data/oracle/ISLT'
Again the destination is on a second server.
The error message I receive is:
Oracle instance shut down
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 05/09/2013 12:48:55
RMAN-05501: aborting duplication of target database
RMAN-05001: auxiliary file name /u02/oradata/ISLP/redo_ISLP_2b.log conflicts with a file used by the target database
RMAN-05001: auxiliary file name /u02/oradata/ISLP/redo_ISLP_1b.log conflicts with a file used by the target database
RMAN>
Recovery Manager complete.
I don't understand why RMAN keeps trying to create new redo log files in a directory that is not specified by the log_file_name_convert parameter. I also don't understand why this exact same process works for cloning one applications database but not this application. I would appreciate any help. Thank you. Here is the RMAN script being executed by Commvault.
Rman Script:
[run {
set newname for datafile '/u02/oradata/ISLP/infosilem_ISLP_01.dbf' to '/u02/oradata/ISLT/infosilem_ISLP_01.dbf';
set newname for datafile '/u02/oradata/ISLP/sysaux_ISLP_01.dbf' to '/u02/oradata/ISLT/sysaux_ISLP_01.dbf';
set newname for datafile '/u02/oradata/ISLP/system_ISLP_01.dbf' to '/u02/oradata/ISLT/system_ISLP_01.dbf';
set newname for datafile '/u02/oradata/ISLP/tools_ISLP_01.dbf' to '/u02/oradata/ISLT/tools_ISLP_01.dbf';
set newname for datafile '/u02/oradata/ISLP/undo_ISLP_01.dbf' to '/u02/oradata/ISLT/undo_ISLP_01.dbf';
set newname for datafile '/u02/oradata/ISLP/users_ISLP_01.dbf' to '/u02/oradata/ISLT/users_ISLP_01.dbf';
allocate auxiliary channel ch1 type 'sbt_tape'
PARMS="SBT_LIBRARY=/opt/galaxy/Base64/libobk.so,BLKSIZE=262144,ENV=(CV_mmsApiVsn=2,CV_channelPar=ch1,ThreadCommandLine= RESTORE -jm 142 -a 2:0 -cl 137 -ins 150 -at 22 -j 700481 -jt 700481:3:1 -bal 0 -rcp 0 -ms 1 -p 2 -cn s-dbint -vm Instance001)"
TRACE 0;
set until time = "TO_DATE('05/08/2013 09:00:00','MM/DD/YYYY HH24:MI:SS')" ;
duplicate target database to 'ISLT'
exit;
]

You haven't defined a log_file_name_convert for /u02/oradata/ISLP/
Possibly, the database has multiplexed redo log files, one member each in /u01/oradata/ISLP and one member each in /u02/oradata/ISLP.
Hemant K Chitale

RMAN SBT_TAPE

Similar Messages

Maybe you are looking for