FILESPERSET

Hi,
in 8.1.7 how should I use FILESPERSET for RMAN ? How can I put it in :
run {
backup format 'C:\backup\myDB\df_%d_%T_%s_%p' database;
Thank you.

user522961 wrote:
Hi,
in 8.1.7 how should I use FILESPERSET for RMAN ? How can I put it in :
run {
backup format 'C:\backup\myDB\df_%d_%T_%s_%p' database;
Thank you.Refer to documentation
http://download-west.oracle.com/docs/cd/A87860_01/doc/server.817/a76990/rmanconc.htm#449771

Similar Messages

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

Back in time with rman ?

Hi,
I have a rman set of backups from an Oracle database. The database is ok, only the user wants to have that older stand of the data, so I must go back in time.
The rman script to generate the backups is as follows:
rman target sys/manager@EON1 catalog rman/rman@rman << EOF >> $LOG 2>&1
run {
configure retention policy to redundancy 2;
# debug on;
allocate channel d1 type disk;
backup incremental level 0
skip inaccessible filesperset 10 noexclude
format '/u0/oracle/backup/INCR_%s_%p'
database include current controlfile;
release channel d1;
sql 'alter system archive log current';
allocate channel d1 type disk;
backup skip inaccessible filesperset 50
format '/u0/oracle/backup/ARCH_%s_%p'
archivelog all delete all input;
release channel d1;
report obsolete;
delete noprompt obsolete;
allocate channel for maintenance type disk;
crosscheck backup;
release channel;
allocate channel for delete type disk;
delete noprompt expired backup;
release channel;
EOF
My database world is Sybase, a little bit Oracle skills too but no rman.
Can anybody describe me the steps to restore that backup set?
Thanks a lot.
Daniel S

1. shutdown and backup your database (!!!).
2. start in umount mode
3. rman target sys/manager@EON1 catalog rman/rman@rman
4. at the RMAN prompt perform a point in time restore/recover, e.q.:
restore database until time "to_date('19.01.2009 13:00:00','DD.MM.YYYY HH24:MI:SS')";
recover database until time "to_date('19.01.2009 13:00:00','DD.MM.YYYY HH24:MI:SS')";

Error: Sheduled Backup Job Problem

Dear all.
I've been getting a problem with a scheduled backup job through OEM since yesterday which I'm not able to find out why as it was working fine. When I access OEM I can see that I have a problem execution and when I investigate why it says "Unable to perform the backup because the database is closed". But my db is open for sure and I'm able to execute the backup from RMAN command line normally. I shut my db down and started it up again but didn't work. Does anybody know why this is happening?
OS: Oracle Enterprise Linux 5
DB: Oracle Database 10g
Thanks a lot.

**** Job Definition ****
Status: Scheduled
Scheduled: 09-Jun-2009 20:00:00 o'clock GMT-03:00
Repeating: Daily beginning 09-Jun-2009 20:00:00 (because I changed to do tests)
Type: Database Backup
Owner: SYS
Description: Whole Database Backup
Database Connect String: (DESCRIPTION=(ADDRESS_LIST=(ADDR...
Version 10g or higher: YES
Backup Strategy: advanced
Offline Backup: NO
Blackout: NO
Database Name: ORCL
**** Script ****
$rman_script="backup incremental level 0 cumulative device type disk filesperset = 3 tag '%TAG' database;
backup device type disk filesperset = 3 tag '%TAG' archivelog all not backed up;
allocate channel for maintenance type disk;
delete noprompt obsolete device type disk;
release channel;
&br_save_agent_env();
&br_prebackup($l_db_connect_string, $l_is_cold_backup, $l_use_rcvcat, $l_db_10_or_higher, $l_backup_strategy, "TRUE");
my $result = &br_backup();
exit($result);

Error when scheduling backup job in OEM

We have Oracle 11.2 RAC on Redhat Linux. I was creating an customized backup job and get the errorsORA-01476: divisor is equal to zero
ORA-06512: at "SYSMAN.MGMT_JOB_ENGINE", line 7544
ORA-06512: at "SYSMAN.MGMT_JOB_ENGINE", line 7699
ORA-06512: at "SYSMAN.MGMT_JOB_ENGINE", line 8211
ORA-06512: at "SYSMAN.MGMT_JOB_ENGINE", line 8342
ORA-06512: at "SYSMAN.MGMT_JOB_ENGINE", line 8503
ORA-06512: at "SYSMAN.MGMT_JOB_ENGINE", line 8570
ORA-06512: at "SYSMAN.MGMT_JOBS", line 273
ORA-06512: at "SYSMAN.MGMT_JOBS", line 86
ORA-06512: at line 1 The backup command is created by OEM as backup incremental level 0 cumulative device type disk filesperset = 5 tag '%TAG' section size 500 M database;
backup device type disk filesperset = 500 tag '%TAG' section size 500 M archivelog all not backed up;
allocate channel for maintenance type disk;
delete noprompt obsolete device type disk;
release channel; Actually using other ommand also get the same error.
What is wrong? I scheduled backup job before on this server and it worked.

This may be due to that the schedule frequecy is not set. Make sure Frequency Type and Repeat Every boxes get filled properly.

How to find out which archived logs needed to recover a hot backup?

I'm using Oracle 11gR2 (11.2.0.1.0).
I have backed up a database when it is online using the following backup script through RMAN
connect target /
run {
allocate channel d1 type disk;
backup
incremental level=0 cumulative
filesperset 4
format '/san/u01/app/backup/DB_%d_%T_%u_%c.rman'
database
}The backup set contains the backup of datafiles and control file. I have copied all the backup pieces to another server where I will restore/recover the database but I don't know which archived logs are needed in order to restore/recover the database to a consistent state.
I have not deleted any archived log.
How can I find out which archived logs are needed to recover the hot backup to a consistent state? Can this be done by querying V$BACKUP_DATAFILE and V$ARCHIVED_LOG? If yes, which columns should I query?
Thanks for any help.

A few ways :
1a. Get the timestamps when the BACKUP ... DATABASE began and ended.
1b. Review the alert.log of the database that was backed up.
1c. From the alert.log identify the first Archivelog that was generated after the begin of the BACKUP ... DATABASE and the first Archivelog that was generated after the end of the BACKUP .. DATABASE.
1d. These (from 1c) are the minimal Archivelogs that you need to RECOVER with. You can choose to apply additional Archivelogs that were generated at the source database to contininue to "roll-forward"
2a. Do a RESTORE DATABASE alone.
2b. Query V$DATAFILE on the restored database for the lowest CHECKPOINT_CHANGE# and CHECKPOINT_TIME. Also query for the highest CHECKPOINT_CHANGE# and CHECKPOINT_TIME.
2c. Go back to the source database and query V$ARCHIVED_LOG (FIRST_CHANGE#) to identify the first Archivelog that has a higher SCN (FIRST_CHANGE#) than the lowest CHECKPOINT_CHANGE# from 2b above. Also query for the first Archivelog that has a higher SCN (FIRST_CHANGE#) than the highest CHECKPOINT_CHANGE# from 2b above.
2d. These (from 2c) are the minimal Archivelogs that you need to RECOVER with.
(why do you need to query V$ARCHIVED_LOG at the source ? If RESTORE a controlfile backup that was generated after the first Archivelog switch after the end of the BACKUP ... DATABASE, you would be able to query V$ARCHIVED_LOG at the restored database as well. That is why it is important to force an archivelog (log switch) after a BACKUP ... DATABASE and then backup the controlfile after this -- i.e. last. That way, the controlfile that you have restored to the new server has all the information needed).
3. RESTORE DATABASE PREVIEW in RMAN if you have the archivelogs and subsequent controlfile in the backup itself !
Hemant K Chitale

Backup to disk storage, from ASM enabled DB, Solaris 10,11gRel1. RAC

Hi,
I am struggling with completing backup of database within appropriate time. It keeps running for days. I have tried with 07 channels and now trying with 03 channels.
Database is 2 node RAC cluster, each running "Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - 64bit Production" on Solaris 10, SPARC-Enterprise-T5220 with 6 CPU and 32GB RAM. The ASM is running on LUNs taken from IBM XIV.
RMAN> SHOW ALL;
RMAN configuration parameters for database with db_unique_name EPMPRD are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 10 DAYS;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/u998/backups/epmprd/rman_backup/ora_cf%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 3 BACKUP TYPE TO COPY;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 2;
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/u998/backups/oepmprd/rman_backup/%d_%u_%p_%N_fileno:%f.dbf';
CONFIGURE CHANNEL 1 DEVICE TYPE DISK FORMAT '/u998/backups/epmprd/rman_backup/ora_df_%d_%T_%s_%c_%p' CONNECT '*';
CONFIGURE CHANNEL 2 DEVICE TYPE DISK FORMAT '/u998/backups/epmprd/rman_backup/ora_df_%d_%T_%s_%c_%p' CONNECT '*';
CONFIGURE CHANNEL 3 DEVICE TYPE DISK FORMAT '/u998/backups/epmprd/rman_backup/ora_df_%d_%T_%s_%c_%p' CONNECT '*';
CONFIGURE MAXSETSIZE TO 4296 M;
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE COMPRESSION ALGORITHM 'ZLIB';
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
SQL> SELECT filename, status, bytes FROM v$block_change_tracking;
FILENAME STATUS BYTES
+DGA1/epmprd/block_change.dbf ENABLED 22085632
RMAN script running under crontab has:
CONFIGURE CHANNEL 1 DEVICE TYPE DISK FORMAT '$DATA_FILE_DIR/ora_df_%d_%T_%s_%c_%p' connect = '$CONNECT_TARGET1';
CONFIGURE CHANNEL 2 DEVICE TYPE DISK FORMAT '$DATA_FILE_DIR/ora_df_%d_%T_%s_%c_%p' connect = '$CONNECT_TARGET1';
CONFIGURE CHANNEL 3 DEVICE TYPE DISK FORMAT '$DATA_FILE_DIR/ora_df_%d_%T_%s_%c_%p' connect = '$CONNECT_TARGET1';
BACKUP AS COMPRESSED BACKUPSET INCREMENTAL LEVEL 0 DATABASE FILESPERSET 1;
BACKUP ARCHIVELOG ALL not backed up FORMAT '$DATA_FILE_DIR/ora_arch_%d_%s_%T_%c_%p';
DELETE FORCE NOPROMPT ARCHIVELOG UNTIL TIME 'SYSDATE-7' backed up 2 times to disk;
BACKUP SPFILE format '$DATA_FILE_DIR/spfile_%d_%T_%s_%p';
where TARGET1=epmprd1 (instance 1 of RAC i.e. using instance 1 as backup node)
SQL> @tbs_usage.sql
TABLESPACE_NAME SUM_SPACE(M) SUM_BLOCKS USED_SPACE(M) USED_RATE(%) FREE_SPACE(M)
SYSTEM 2000 256000 1074.94 53.75 925.06
CALC 250 32000 5.5 2.2 244.5
FDMCOMMA2D 250 32000 .06 .02 249.94
FDMXCHANGING1I 250 32000 .06 .02 249.94
FDMXCHANGING1D 250 32000 .06 .02 249.94
FDMXCHANGING3I 250 32000 .06 .02 249.94
FDMXCHANGING4D 451.56 57800 421.06 93.25 30.5
USERS 2000 256000 381.37 19.07 1618.63
BIPLUS 250 32000 81.44 32.58 168.56
FDMCOMMAI 250 32000 .06 .02 249.94
FDMXCHANGING2I 250 32000 .06 .02 249.94
UNDOTBS2 4279 547712 18.44 .43 4260.56
EPMA 250 32000 57.81 23.12 192.19
EPMAINT 250 32000 .06 .02 249.94
HFM 50000 6400000 18566.75 37.13 31433.25
HSS 250 32000 25.06 10.02 224.94
FDMSTAT 250 32000 .06 .02 249.94
FDMCOMMAD 250 32000 .06 .02 249.94
FDMCOMMA2I 250 32000 .06 .02 249.94
FDMXCHANGING2D 250 32000 .06 .02 249.94
FDMXCHANGING3D 250 32000 .06 .02 249.94
SYSAUX 2000 256000 1208.37 60.42 791.63
FDMXCHANGING4I 250 32000 .06 .02 249.94
UNDOTBS1 2000 256000 26.56 1.33 1973.44
TEMP 10284 1316352 10284 100 0
25 rows selected.
SQL>select sum(bytes/1024)/1024/1024 from dba_segments;
SUM(BYTES/1024)/1024/1024
40.0876465
Please share what i can do to optimize the backups. Your suggestions are highly appreciated.
regards,
Anjum

Hi,
/998 is SAN mountpoint taken from IBM XIV.
oepmprd@basfisprddatg01$ cat /etc/vfstab | grep -i u998
/dev/md/dsk/d200 /dev/md/rdsk/d200 /u998 ufs 2 yes logging
I have done some testing and following are results.
1.
ASMCMD> cp hfm22.dbf /u998/backups/epmprd/rman_backup
copying +DGA1/epmprd/hfm22.dbf -> /u998/backups/epmprd/rman_backup/hfm22.dbf
oepmprd@basfisprddatg01$ du -sh hfm22.dbf
2.0G hfm22.dbf
Time taken: 29 seconds
================================================
2.
ASMCMD> cp group_5.600.766282841 /u998/backups/epmprd/rman_backup
copying +FRA/epmprd/ONLINELOG/group_5.600.766282841 -> /u998/backups/epmprd/rman_backup/group_5.600.766282841
oepmprd@basfisprddatg01$ du -sh group_5.600.766282841
500M group_5.600.766282841
Time taken: 11 seconds
================================================
3.
ASMCMD> cp temp01.dbf /u998/backups/epmprd/rman_backup
copying +DGA1/epmprd/temp01.dbf -> /u998/backups/epmprd/rman_backup/temp01.dbf
oepmprd@basfisprddatg01$ du -sh temp01.dbf
10.0G temp01.dbf
Time taken: 03 mins, 16 seconds
=================================================
Moreover, i copied a file from /u998 to /tmp and it was quick:
grid@basfisprddatg01$ pwd
/u998/backups/epmprd/rman_backup
grid@basfisprddatg01$ du -sh ora_df_EPMPRD_20111210_7783_1_1
266M ora_df_EPMPRD_20111210_7783_1_1
grid@basfisprddatg01$ cp ora_df_EPMPRD_20111210_7783_1_1 /tmp/
It took 2-3 seconds.
regards,
Anjum
Edited by: Anjum Shehzad on Dec 12, 2011 11:18 AM

How Backup on DISK for Standby when Device "Tape" is alredy configured

hello Dba's
For 3 Weeks I've this issue and I start don't get
usualy this database ws backup on Disk but last month we decided to setup the DLL fro Netbackup on TAPE
and I've configured the RMAN for tape and it works fine.
Now I need to Backup on DISK to create my Standby Database, because the Secondary Server doesn't have the DLL/License for TAPE
So i decided to proceed as a backup on Disk but when I try it alyway gpo into TAPE !!!!!
Any help is welcome.
txs
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 30 DAYS;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backup/export/cf_%F_$ORACLE_SID';
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE 'SBT_TAPE' TO '%F';
CONFIGURE DEVICE TYPE SBT_TAPE PARALLELISM 1; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 1; # default
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 DISK FORMAT '/backup/export/%d_%D%M%T_full_%U';
CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' FORMAT '%d_%D%M%T_full_%U';
CONFIGURE MAXSETSIZE TO UNLIMITED;
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/9.2/dbs/snapcf_SIEB.scf';
RMAN> allocate channel for maintenance device type 'DISK'
2> ;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of allocate command on ORA_MAINT_DISK_1 channel at 06/29/2010 15:14:44
ORA-19554: error allocating device, device type: DISK, device name:
ORA-27001: unsupported device type
Additional information: 1
RMAN> allocate channel for maintenance device type DISK;
allocated channel: ORA_MAINT_DISK_2
channel ORA_MAINT_DISK_2: sid=236 devtype=DISK
RMAN> run
2> 3> sql "Alter System Switch logfile";
4> sql "Alter System Archive Log Current";
5> Backup database plus archivelog format '/backup/%d_%D%M%T_full_%U';
6> sql "Alter System Switch logfile";
7> Backup current controlfile for standby format '/backup/%U_$ORACLE_SID';
8> sql "Alter System Switch logfile";
9> Backup filesperset 10 ArchiveLog all;
10> }
sql statement: Alter System Switch logfile
sql statement: Alter System Archive Log Current
Starting backup at 29-JUN-10
current log archived
allocated channel: ORA_SBT_TAPE_1
channel ORA_SBT_TAPE_1: sid=118 devtype=SBT_TAPE
channel ORA_SBT_TAPE_1: Veritas NetBackup for Oracle - Release 7.0 (2010010419)
channel ORA_SBT_TAPE_1: starting archive log backupset
channel ORA_SBT_TAPE_1: specifying archive log(s) in backup set
input archive log thread=1 sequence=2879 recid=688 stamp=722953267
input archive log thread=1 sequence=2880 recid=689 stamp=722960690
input archive log thread=1 sequence=2881 recid=691 stamp=722963294
input archive log thread=1 sequence=2882 recid=690 stamp=722963293
input archive log thread=1 sequence=2883 recid=692 stamp=722963296
input archive log thread=1 sequence=2884 recid=693 stamp=722963703
input archive log thread=1 sequence=2885 recid=694 stamp=722963703
input archive log thread=1 sequence=2886 recid=695 stamp=722963705
channel ORA_SBT_TAPE_1: starting piece 1 at 29-JUN-10
channel ORA_SBT_TAPE_1: finished piece 1 at 29-JUN-10
piece handle=/backup/SIEB_290620100629_full_qelhf37t_1_1 comment=API Version 2.0,MMS Version 5.0.0.0
channel ORA_SBT_TAPE_1: backup set complete, elapsed time: 00:00:56
Finished backup at 29-JUN-10
Starting backup at 29-JUN-10
using channel ORA_SBT_TAPE_1
channel ORA_SBT_TAPE_1: starting full datafile backupset
channel ORA_SBT_TAPE_1: specifying datafile(s) in backupset
input datafile fno=00020 name=/u01/oradata/SIEB/data/tbs_siebel_data_01.dbf
input datafile fno=00002 name=/u02/oradata/SIEB/system/undotbs02_02.dbf
input datafile fno=00001 name=/u02/oradata/SIEB/system/system01.dbf
input datafile fno=00011 name=/u01/oradata/SIEB/data/tbs_siebview_01.dbf
input datafile fno=00025 name=/u01/oradata/SIEB/data/undotbs02_01.dbf
input datafile fno=00018 name=/u01/oradata/SIEB/data/tbs_siebel_empty.dbf
input datafile fno=00022 name=/u01/oradata/SIEB/data/users_01.dbf
input datafile fno=00019 name=/u01/oradata/SIEB/data/invoice_app_data01.dbf
input datafile fno=00015 name=/u01/oradata/SIEB/data/tbs_dwhview_01.dbf
input datafile fno=00010 name=/u01/oradata/SIEB/data/dm_casebase_docbase_01.dbf
input datafile fno=00014 name=/u01/oradata/SIEB/data/tbs_siebdw_data_01.dbf
input datafile fno=00016 name=/u01/oradata/SIEB/data/tbs_igd_01.dbf
input datafile fno=00017 name=/u01/oradata/SIEB/data/igd_eim_01.dbf
input datafile fno=00013 name=/u01/oradata/SIEB/data/dm_imdoc_docbase_01.dbf
input datafile fno=00023 name=/u01/oradata/SIEB/data/perfstat_01.dbf
input datafile fno=00012 name=/u01/oradata/SIEB/data/dm_imdoc_audit_01.dbf
input datafile fno=00021 name=/u01/oradata/SIEB/data/tools_01.dbf
input datafile fno=00009 name=/u01/oradata/SIEB/data/dm_casebase_audit_01.dbf
channel ORA_SBT_TAPE_1: starting piece 1 at 29-JUN-10
channel ORA_SBT_TAPE_1: finished piece 1 at 29-JUN-10
piece handle=SIEB_290620100629_full_qflhf39l_1_1 comment=API Version 2.0,MMS Version 5.0.0.0
channel ORA_SBT_TAPE_1: backup set complete, elapsed time: 00:12:36
channel ORA_SBT_TAPE_1: starting full datafile backupset
channel ORA_SBT_TAPE_1: specifying datafile(s) in backupset
input datafile fno=00006 name=/u03/oradata/SIEB/index/tbs_siebbig_index01.dbf
input datafile fno=00024 name=/u03/oradata/SIEB/index/tbs_siebel_index_01.dbf
input datafile fno=00004 name=/u03/oradata/SIEB/index/tbs_siebdw_index_01.dbf
input datafile fno=00005 name=/u03/oradata/SIEB/index/tbs_igd_index01.dbf
input datafile fno=00007 name=/u03/oradata/SIEB/index/dm_casebase_index_01.dbf
input datafile fno=00008 name=/u03/oradata/SIEB/index/dm_imdoc_index_01.dbf
input datafile fno=00003 name=/u03/oradata/SIEB/index/tbs_invoice_index01.dbf
channel ORA_SBT_TAPE_1: starting piece 1 at 29-JUN-10
channel ORA_SBT_TAPE_1: finished piece 1 at 29-JUN-10
piece handle=SIEB_290620100629_full_qglhf419_1_1 comment=API Version 2.0,MMS Version 5.0.0.0
channel ORA_SBT_TAPE_1: backup set complete, elapsed time: 00:07:15
Finished backup at 29-JUN-10
Starting backup at 29-JUN-10
current log archived
using channel ORA_SBT_TAPE_1
channel ORA_SBT_TAPE_1: starting archive log backupset
channel ORA_SBT_TAPE_1: specifying archive log(s) in backup set
input archive log thread=1 sequence=2887 recid=696 stamp=722964956
channel ORA_SBT_TAPE_1: starting piece 1 at 29-JUN-10
channel ORA_SBT_TAPE_1: finished piece 1 at 29-JUN-10
piece handle=/backup/SIEB_290620100629_full_qhlhf4es_1_1 comment=API Version 2.0,MMS Version 5.0.0.0
channel ORA_SBT_TAPE_1: backup set complete, elapsed time: 00:00:57
Finished backup at 29-JUN-10
Starting Control File and SPFILE Autobackup at 29-JUN-10
piece handle=c-1097630847-20100629-04 comment=API Version 2.0,MMS Version 5.0.0.0
Finished Control File and SPFILE Autobackup at 29-JUN-10
sql statement: Alter System Switch logfile
Starting backup at 29-JUN-10
using channel ORA_SBT_TAPE_1
channel ORA_SBT_TAPE_1: starting full datafile backupset
channel ORA_SBT_TAPE_1: specifying datafile(s) in backupset
including standby controlfile in backupset
channel ORA_SBT_TAPE_1: starting piece 1 at 29-JUN-10

Thxs for Reply
But When I type Allocate Channel as you suggested I get Error
ORA-19502: write error on file "qslhf5sr_1_1", blockno 1 (blocksize=8192)
RMAN> run
2> {
3> allocate channel c1 type disk;
4> sql "Alter System Switch logfile";
5> sql "Alter System Archive Log Current";
6> Backup database plus archivelog format '/backup/%d_%D%M%T_full_%U';
7> sql "Alter System Switch logfile";
8> Backup current controlfile for standby format '/backup/%U_$ORACLE_SID';
9> sql "Alter System Switch logfile";
10> Backup filesperset 10 ArchiveLog all;
11> }
starting full resync of recovery catalog
full resync complete
released channel: ORA_SBT_TAPE_1
allocated channel: c1
channel c1: sid=12 devtype=DISK
sql statement: Alter System Switch logfile
sql statement: Alter System Archive Log Current
Starting backup at 29-JUN-10
current log archived
skipping archive log file /u03/archive/SIEB/1_2879.dbf; already backed up 1 time(s)
skipping archive log file /u03/archive/SIEB/1_2880.dbf; already backed up 1 time(s)
skipping archive log file /u03/archive/SIEB/1_2881.dbf; already backed up 1 time(s)
skipping archive log file /u03/archive/SIEB/1_2882.dbf; already backed up 1 time(s)
skipping archive log file /u03/archive/SIEB/1_2883.dbf; already backed up 1 time(s)
skipping archive log file /u03/archive/SIEB/1_2884.dbf; already backed up 1 time(s)
skipping archive log file /u03/archive/SIEB/1_2885.dbf; already backed up 1 time(s)
skipping archive log file /u03/archive/SIEB/1_2886.dbf; already backed up 1 time(s)
skipping archive log file /u03/archive/SIEB/1_2887.dbf; already backed up 1 time(s)
skipping archive log file /u03/archive/SIEB/1_2888.dbf; already backed up 1 time(s)
skipping archive log file /u03/archive/SIEB/1_2889.dbf; already backed up 1 time(s)
skipping archive log file /u03/archive/SIEB/1_2890.dbf; already backed up 1 time(s)
skipping archive log file /u03/archive/SIEB/1_2891.dbf; already backed up 1 time(s)
skipping archive log file /u03/archive/SIEB/1_2892.dbf; already backed up 1 time(s)
skipping archive log file /u03/archive/SIEB/1_2893.dbf; already backed up 1 time(s)
channel c1: starting piece 1 at 29-JUN-10
channel c1: finished piece 1 at 29-JUN-10
piece handle=/backup/SIEB_290620100629_full_qrlhf5on_1_1 comment=NONE
channel c1: backup set complete, elapsed time: 00:02:12
Finished backup at 29-JUN-10
Starting backup at 29-JUN-10
channel c1: starting full datafile backupset
channel c1: specifying datafile(s) in backupset
input datafile fno=00020 name=/u01/oradata/SIEB/data/tbs_siebel_data_01.dbf
input datafile fno=00002 name=/u02/oradata/SIEB/system/undotbs02_02.dbf
input datafile fno=00001 name=/u02/oradata/SIEB/system/system01.dbf
input datafile fno=00011 name=/u01/oradata/SIEB/data/tbs_siebview_01.dbf
input datafile fno=00025 name=/u01/oradata/SIEB/data/undotbs02_01.dbf
input datafile fno=00018 name=/u01/oradata/SIEB/data/tbs_siebel_empty.dbf
input datafile fno=00022 name=/u01/oradata/SIEB/data/users_01.dbf
input datafile fno=00019 name=/u01/oradata/SIEB/data/invoice_app_data01.dbf
input datafile fno=00015 name=/u01/oradata/SIEB/data/tbs_dwhview_01.dbf
input datafile fno=00010 name=/u01/oradata/SIEB/data/dm_casebase_docbase_01.dbf
input datafile fno=00014 name=/u01/oradata/SIEB/data/tbs_siebdw_data_01.dbf
input datafile fno=00016 name=/u01/oradata/SIEB/data/tbs_igd_01.dbf
input datafile fno=00017 name=/u01/oradata/SIEB/data/igd_eim_01.dbf
input datafile fno=00013 name=/u01/oradata/SIEB/data/dm_imdoc_docbase_01.dbf
input datafile fno=00023 name=/u01/oradata/SIEB/data/perfstat_01.dbf
input datafile fno=00012 name=/u01/oradata/SIEB/data/dm_imdoc_audit_01.dbf
input datafile fno=00021 name=/u01/oradata/SIEB/data/tools_01.dbf
input datafile fno=00009 name=/u01/oradata/SIEB/data/dm_casebase_audit_01.dbf
channel c1: starting piece 1 at 29-JUN-10
released channel: c1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 06/29/2010 16:00:34
ORA-19502: write error on file "qslhf5sr_1_1", blockno 1 (blocksize=8192)
ORA-27072: skgfdisp: I/O error
Linux-x86_64 Error: 2: No such file or directory
RMAN>

RMAN ERROR ORA-04030 out of process memory allocate 1049100 bytes pga heap

Hello,
I have this problem with a production database 9.2.0.8.
I attach the parameters from production database and repository rman database (9.2.0.8).
PRODUCTION DB SERVER 9.2.0.8
WINDOWS SERVER 2003 R2 SP1
SQL> SHOW PARAMETER SGA
NAME VALUE
lock_sga FALSE
pre_page_sga FALSE
sga_max_size 1888562548
SQL>
SQL> SHOW PARAMETER PGA
NAME VALUE
pga_aggregate_target 335544320
SQL> SHOW PARAMETER POOL
NAME VALUE
java_pool_size 33554432
large_pool_size 134217728
shared_pool_reserved_size 13421772
shared_pool_size 268435456
SQL> SHOW PARAMETER CACHE
NAME VALUE
db_cache_advice ON
db_cache_size 1073741824
REPOSITORY RMAN DB SERVER 9.2.0.8
WINDOWS SERVER 2000 SP4
SQL> SHOW PARAMETER SGA
NAME VALUE
lock_sga FALSE
pre_page_sga FALSE
sga_max_size 1074865628
SQL> SHOW PARAMETER PGA
NAME VALUE
pga_aggregate_target 134217728
SQL> SHOW PARAMETER POOL
NAME VALUE
java_pool_size 33554432
large_pool_size 134217728
shared_pool_reserved_size 6710886
shared_pool_size 134217728
SQL> SHOW PARAMETER CACHE
NAME VALUE
db_cache_size 134217728
SCRIPT RMAN
run {
allocate channel t1 type disk;
allocate channel t2 type disk;
backup skip readonly filesperset = 1 format 'E:\rman\BDWEBEXT\BD_%d_%u_%s_%p.rmn' tag 'Backup Completo BDWEBEXT' database;
release channel t1;
release channel t2;
ERROR
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on t2 channel at 02/09/2008 14:46:58
ORA-04030: out of process memory when trying to allocate 1049100 bytes (pga heap,KSFQ Buffers)
Recovery Manager complete.
Does someone know that it can be?
Thank you

how solve ORA-04030: out of process memory when trying to allocate
Sybrand Bakker
Senior Oracle DBA

How to pass a shell variable to rman scripts

I want to backup datafile to different directory
depending on the current time,and I can do this to
pass a shell variable to rman scripts,and this
variable will used as part of format ,like this:
backup incremental level=0
tag rman_inc0_bck
filesperset 5
format '$(DIR)/rman_fulldb_%u_%s_%p_%d'
(database include current controlfile)
and $(DIR) is shell variable ,but rman will not
recognize this ,how to achieve this?

You could send your script to rman thru a pipe | or <<
echo "backup incremental level=0
tag rman_inc0_bck
filesperset 5
format '$(DIR)/rman_fulldb_%u_%s_%p_%d'
(database include current controlfile);" | rman target /You could also create a "temp script" and then use it from rman with cmdfile
sed "s,XXXDIR,$(DIR)," yourtemplate > /tmp/rmanscript.$$
rman target / cmdfile /tmp/rmanscript.$$
rm /tmp/rmanscript.$$

Error in making backup of current controlfile, rman

Hi All,
i am hitting by a strange error, i tried metalink and google but did't get any satisfactory answer yet, i would like to discuss it here...
we have an ORACLE 9iR2 two nodes RAC on solaris 9 SPARC, with a DR site dataguard 9i server...we also have a separate rman catalog server...initially everything was working fine but with the time the size of databases has been raised...now it has been observed that off n on we get following error when we take RMAN based backup:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03015: error occurred in stored script exec_bkp_full
RMAN-03015: error occurred in stored script caf_db
RMAN-03002: failure of backup command at 01/21/2009 10:28:04
RMAN-06004: ORACLE error from recovery catalog database: ORA-03114: not connected to ORACLE
RMAN-06097: text of failing SQL statement: declare first boolean ; conf# number ; begin if ( :first > 0 ) then fi
RMAN-06099: error occurred in source file: krmk.pc, line: 27998
our backup script is:
printing stored script: backup_db
allocate channel canal01 type disk ;
sql 'alter database backup controlfile to trace';
sql 'alter system archive log current';
backup filesperset 4 format "path-to-directory/db_%U.bkp" ( database );
backup format "path-to-directory/stdby_%U.cf" current controlfile for standby keep forever nologs;
backup format "path-to-directory/arch_%U.bkp" archivelog all;
release channel canal01;
it has been noticed that when we remove "backup format "path-to-directory/stdby_%U.cf" current controlfile for standby keep forever nologs;" from backup script the backup runs without any problem...but when we have added this line, it gives above mentioned error.
PS: the same script runs fine with small size databases...we are getting such problem only with much huge size databases.
TIA

Hi,
Fareedh wrote:
1. But has this resolved your backup error?Yeah, amazingly this time Hot backup worked !
2. Try not to configure it, instead have the statement inside the run script.what is the difference in both types?
>
eg:-
run
allocate channel ch1 type Disk maxpiecesize=2500M;
backup
filesperset 50
format '<Your directory>'
database include current controlfile;
release channel ch1;

Calling RMAN script with DBMS_JOB

Hi,
Maybe someone can help me out. I'm perfecting my skills on 9i in the backup area before I have a need to use them and am taking notes.
What I want to do is to store the backup script in the recovery catalog (which I already did under the name BACKUP) and call that script on a daily basis using DBMS_JOBS.
Here is my script:
RMAN>CREATE SCRIPT 'BACKUP'
{ALLOCATE CHANNEL C1 TYPE DISK;
BACKUP INCREMENTAL LEVEL 0 DATABASE
FILESPERSET 4;
BACKUP ARCHIVELOG ALL;
DELETE ARCHIVELOG UNTILTIME 'SYSDATE-7';}
This script compiled and is stored in rman. I ran it and it worked. I also autoconfigured the parameters to backup the controlfile automatically when the backup or copy is done.
Now my next goal is to get this script to run automatically everyday using DBMS_JOBS and this is where it is not working.
I used the DBMS_JOB.SUBMIT parameters to store the job in this feature but first the procedure 'RUNBACKUP' must compile successfully.
DBMS_JOB.SUBMIT(:1,'RUNBACKUP', SYSDATE,'SYSDATE+1');
This RUNBACKUP is a procedure that has to be called by the DBMS_JOBS PACKAGE. But the procedure is where Im having problems trying to write.
I am assuming that rman is not connected to the target database here. So this is what I think it should look like:
CREATE OR REPLACE PROCEDURE RUNBACKUP
BEGIN
RMAN; --the first thing that
has to be called is rman executable.
CONNECT TARGET AL/AL@BBROWN
--now we have to connect the target db to rman.
CONNECT CATALOG RMAN/RMAN@RCAT;
-- connecting to the recovery catalog.
RUN {EXECUTE SCRIPT 'BACKUP';} --execute the stored backup script
END;
Also, at the end of this procedure I would like to exit rman as the final command.
Any ideas on this would be appreciated and thanks for your help in advance.
Al

You need to create a shell script to execute rman and add that script to cron, something like this:
#!/bin/ksh
# Script name: whole_db_backup.ksh
export PATH=/oracle/app/9i/bin:$PATH
export ORACLE_HOME=/oracle/app/9i
export ORACLE_SID=MDR
rman <<EOF
connect target /
connect catalog rmancat/PASS@RMANCAT
run {execute script whole_db_backup;}
exit
EOF

RMAN script issue ....

Oracle Server - Enterprise Edition - Version: 10.2.0.3
RMAN Catalog : 10.2.0.4
I am using the follwoing script for backup :
4> run
5> {
6>     allocate channel dev1 type disk format 'Z:\Rbackup\DMP\db_t%t_s%s_p%p';
7>     allocate channel dev2 type disk format 'Z:\Rbackup\DMP\db_t%t_s%s_p%p';
8>     backup database FILESPERSET 20 ;
9>     backup archivelog all archivelog until time 'sysdate-1' delete all input ;
10>     release channel dev1 ;
11>     release channel dev2 ;
12> }The issue is with backup archivelog all archivelog until time 'sysdate-1' delete all input ;
This command gives error
ORA-19588: Archived Log Recid Stamp Is No Longer Valid
even after doing crosscheck .
Referred Metalink ID : 1189883.1
which clearly indicates that the statement
backup archivelog all archivelog until time 'sysdate-1' delete all input ;
is wrong by logic and is the reason for the issue .
And suggests to use
backup archivelog until time 'sysdate-1' delete all input ;
or
backup archivelog all delete input ;
which definitely do not serve the purpose .
The logic that needs to be implemented is
I need to backup all archivelogs and delete archivelogs until sysdate-1 .....
How can I do this ? Please help ....
Regards
Renjith Madhavan

Of course. You have asked Oracle to backup files as of 1 day old. Your command is explicitly stating that it is not to backup files newer than 1 day old.
Read and understand "archivelogRecordSpecifier" at
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14194/rcmsynta008.htm#sthref121
UNTIL TIME "Specifies the end date for a sequence of archived redo log files"
It is actually used when doing RECOVER and RESTORE so as to do Point In Time Recovery.
Backups are not done with UNTIL TIME. The only scenario where someone would backup until TIME is when he is writing separate sets of backups deliberately to different backupsets (e.g. one backupset representing 01-Dec will subsequently be copied to another location or to Tape-1, the next backupset representing 02-Dec will be copied to a different location or to Tape-2 etc).
However, when you do a BACKUP DATABASE today, you have to ensure that you BACKUP ARCHIVELOG upto the latest archivelog else, you will NOT be able to use today's database backup for restore and recovery.
Hemant K Chitale
Edited by: Hemant K Chitale on Dec 6, 2010 2:57 PM

RMAN Script is not allocating channels

I have a customer who is running a Solaris Server with Oracle 9i and is trying to backup using an RMAN script to define the channels to back up to through Networker.
The script is as follows:
run {
allocate channel t1 type "sbt_tape";
allocate channel t2 type "sbt_tape";
send 'NSR_ENV=(NSR_SERVER=XXXX,NSR_DATA_VOLUME_POOL=Default)';
sql 'alter system archive log current';
change archivelog all crosscheck;
set command id to 'bkrs';
backup
filesperset 20
archivelog all
delete input;
release channel t1;
release channel t2;
Normally there are 3 channel allocations, but for some reason this does not work. He can only get 1 channel to work at a time which is impacting Backup Performance.
There are no errors logged in the log files which is also odd. The device parallelism is 4 under Networker
The version of Networker is 7.1
Anyone else had any similar issues - I have been scratching my head on this for a while, or if anyone has any ideas on how to troubleshoot this I would appreciate any help
Thanks

I have now found some error information. Please see below.
RMAN-00571: ======================================
RMAN-00569: ===== ERROR MESSAGE STACK FOLLOWS =====
RMAN-00571: =======================================
RMAN-03009: failure of allocate command on t1 channel at 04/08/2004 10:37:02
ORA-19554: error allocating device, device type: SBT_TAPE, device name:
ORA-27211: Failed to load Media Management Library
Any help much appreciated !!!!!

FILESPERSET

Similar Messages

Maybe you are looking for