FRA backup in RMAN script

Hello members, hope you are having a good day.
Is it a good idea to back up FRA to tape in the same script as RMAN backup of database to FRA? This will backup RMAN to FRA and then backup FRA to tape. If not, I will create a separate script that will back up the FRA to tape. Thanks for all suggestions. I will greatly appreciate any scripts from you that I can reference. Thank you.
run {
delete noprompt obsolete;
crosscheck backup;
crosscheck archivelog all;
delete noprompt expired backup;
delete noprompt expired archivelog all;
backup as compressed backupset database plus archivelog;
backup flash recovery area;
exit

As Daniel says, it depends on the size of your backup.
Consider your Retention policy and how many full database backups you keep on-disk (in the FRA).
For example, if you have 7 days backups on disk, do you need all 7 backups to go to tape every day -- you will end up with 6 tape copies of each days backup). If your backups are small and you have the capacity and bandwidth, that would be good.

Similar Messages

RMAN script doesnt exit shell after backup

Hi,
I've the following script on AIX 6.1, Oracle 11.2.0.1.0:
export ORACLE_HOME=/oracle/medprod/product/11.2.0/dbhome_1
export ORACLE_SID=MEDPROD
export PATH=$ORACLE_HOME/bin:$PATH
export LOG_DIR=/home/medinous/backup/logs
export LOG_FILE=$LOG_DIR/medprod_daily_backup_`date +%d%m%Y%X`.log
rman target / catalog rman/rman@rman log=$LOG_FILE <<EOF
execute script medinous_daily;
exit;
EXIT;
EOF
and:
printing stored script: medinous_daily
+{+
allocate channel t1 type 'sbt_tape' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
allocate channel t2 type 'sbt_tape' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
allocate channel t3 type 'sbt_tape' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
backup format 'medinous_dailybackup_%d_%s_%t' database;
backup format 'medinous_dailyarchbackup_%d_%s_%t' archivelog all not backed up 1 times;
crosscheck backup;
delete noprompt obsolete;
delete noprompt expired backup;
delete noprompt expired archivelog all;
release channel t1;
release channel t2;
release channel t3;
+}+
For some reason, the rman script, scheduled via crontab doesn't exit after successful backup, the process just remain alive, even though there's an explicit exit command at the end.
Any idea?
dula

No, the script actully executes successfully. The problem is that after executing, the process does'nt die, it doesnt exit rman:
channel t1: finished piece 1 at 28-DEC-10
piece handle=prodarchbackup_PROD_666_738921153 tag=TAG20101228T075233 comment=API Version 2.0,MMS Version 5.5.2.0
channel t1: backup set complete, elapsed time: 00:00:03
channel t2: finished piece 1 at 28-DEC-10
piece handle=prodarchbackup_PROD_667_738921153 tag=TAG20101228T075233 comment=API Version 2.0,MMS Version 5.5.2.0
channel t2: backup set complete, elapsed time: 00:00:03
channel t3: finished piece 1 at 28-DEC-10
piece handle=prodarchbackup_PROD_668_738921153 tag=TAG20101228T075233 comment=API Version 2.0,MMS Version 5.5.2.0
channel t3: backup set complete, elapsed time: 00:00:03
Finished backup at 28-DEC-10
Starting Control File and SPFILE Autobackup at 28-DEC-10
piece handle=c-148294895-20101228-00 comment=API Version 2.0,MMS Version 5.5.2.0
Finished Control File and SPFILE Autobackup at 28-DEC-10
released channel: t1
released channel: t2
released channel: t3
*<< I expect the rman shell script to exit at this point and 'die' >>>>*

RMAN script for hot backup (looking for code critic) code attached.

Hello Guru's,
I have been having soem trouble running a successful hot full rman backup nightly.
We max our CPU load whenever our RMAN takes too long and conflicts with a Legato tape backup. I have a development server that I attempted to get a consistent backup time duration that is rock solid as to not conflict with the Legato backup time.
I just found out about duration with RMAN scripts here is my code:
#!/bin/bash
#rman backup script for daily hot whole database backup
at -f /hd1/rman_scripts/rman_backup 0600 tomorrow
rman target/
run {
allocate channel d1 device type disk format '/path/%U';
backup duration 1:00 partial minimize load database filesperset 1;
backup as BACKUPSET tag '%TAG' database;
backup as BACKUPSET tag '%TAG' archivelog all delete all input;
delete noprompt obsolete;
release channel d1;
exit
It completes the backup, but does not use the 1 hour allocated- it only uses 15 minutes on average and creates many files instead of normally three backup files.
Here is the results from querying the v$rman_status table for operation,status,start_time:
RMAN,FAILED, 17-OCT-06 0600
BACKUP,FAILED,17-OCT-06 0600
RMAN,FAILED,17-OCT-06 0606
BACKUP,COMPLETED,17-OCT-06 0606
BACKUP,COMPLETED,17-OCT-06 0606
BACKUP,FAILED,17-OCT-06 0615
RMAN,COMPLETED,17-OCT-06 1513
REPORT,COMPLETED,17-OCT-06 1513
DELETE,COMPLETED,17-OCT-06 1513
However, the timestamps of the backupset files it creates is:
06:15 and not 1513?????????????
RMAN appears to have only taken 15 minutes to create the files, why do I have a completed timestamp from v$rman_status of 1513???
Please advise and comment, I am just learning RMAN.

Try to remove the DURATION option in your script.
Here more details about that part.
http://download-east.oracle.com/docs/cd/B19306_01/backup.102/b14194/rcmsynta009.htm#i1010261
Bye, Aron

Oracle Online Backup through EMC Networker - RMAN Script

Hi,
For taking online oracle backup through EMC Networker, we configure the RMAN script to connect to the target database, create the media channels, backup format etc. The password for the sys or rman user entered in the RMAN script is in clear-text format.
Due to security reasons, I don't want the passwords to be entered in the RMAN script. Is there any option for configuring RMAN script without mentioning the username/password to connect to the target database ?
Thanks & Regards,
Shreejesh.

When you have to connect remotely to RMAN, you cannot hide the password, you can only define very restricted access for the script itself. Remote OS authentication will not work, because the target db user needs SYSDBA privilege, which cannot be granted to an externally identified user.
Werner

RMAN script for RAC Hot Backup

Anyone who want to share an RMAN script to Hot Backup a 9i RAC Database.

Try to remove the DURATION option in your script.
Here more details about that part.
http://download-east.oracle.com/docs/cd/B19306_01/backup.102/b14194/rcmsynta009.htm#i1010261
Bye, Aron

RMAN Script

Hi all,
I'm a complete novice at Oracle and scripting, so please go easy. I've tried searching for the answer to this, but to completely honest I probably wouldn't recognise the answer if it was staring me in the face.
Here's the dilemma:
I've recently taken on some oracle servers from a user who has moved on. I know nothing about Oracle, and to be honest until something goes wrong (touch wood) the only real maintainance I'm involved in is clearing the archivelogs.
I've played around with batch files, but to no avail. The commands we currently run each week in the cmd window are:
RMAN
connect target system/manager@database
delete archivelog until time 'sysdate-2';
Y
exit
And that's it. It's a bit of a tedious task as we have around 30 databases, and their must be an easier way of doing this with scheduled scripts.
Any guidance for dummies would be hugely appreciated.

C:\backup.bat
rman target=/ @cmdrman.txtInclude a catalog= entry if a recovery catalog is used. Run manually or schedule
Scheduled Tasks Wizard (Start > Programs > Accessories > System Tools > Scheduled Tasks)
C:\cmdrman.txt
RUN {
ALLOCATE CHANNEL ch1 TYPE
DISK FORMAT 'C:\oracle\backup\STANDBY11%d_DB_%u_%s_%p';
BACKUP DATABASE PLUS ARCHIVELOG;
RELEASE CHANNEL ch1;
EXIT;You probably want to add delete archivelog until time 'sysdate-2'; and something to delete your backups too.
Another example (with FRA in place)
run { allocate channel d1 type disk;
backup full as compressed backupset
database plus archivelog;}
crosscheck backup;
delete noprompt ARCHIVELOG UNTIL TIME 'SYSDATE-11';
DELETE noprompt BACKUP COMPLETED BEFORE 'SYSDATE-2' DEVICE TYPE DISK;
exitEdited by: mseberg on Dec 22, 2010 11:42 AM
Simple quick start guide
http://oreilly.com/catalog/9780596002336

Can I call an external program from my rman script

Hi
Is it possible to do an external call to a bat-file in a rman script?
My script looks like this (it's pretty much generated from EM):
$rman_script="backup device type disk tag '%TAG' database;
sql 'alter system archive log current';
backup device type disk tag '%TAG' archivelog all not backed up delete all input;
allocate channel for maintenance type disk;
delete noprompt obsolete device type disk;
release channel;
Can i somehow make an external call before at the end?
Regards
Klaus Mogensen

You can use the HOST command.

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 script errors out for some DB's

I have a single RMAN script that uses env variables to execute RMAN for two databases. It runs fine. I cloned the two DB's (changed DBID's), all four are on the same host. Now I try to use same script for all four. I receive an error when trying to run against the cloned databases. Here is script:
spool log to full.log append;
connect catalog rman/xxxxxx@iasrman
connect target /
run {
sql 'ALTER SYSTEM SWITCH LOGFILE';
backup incremental level 0 database diskratio=0 plus archivelog delete input;
And here is error, it stops same place everytime, input appreciated.
Recovery Manager: Release 9.2.0.5.0 - 64bit Production
RMAN>
connected to recovery catalog database
RMAN>
connected to target database: PRSMQ02 (DBID=944525168)
RMAN> 2> 3> 4>
sql statement: ALTER SYSTEM SWITCH LOGFILE
Starting backup at 30-MAY-07
current log archived
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=20 devtype=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: sid=19 devtype=DISK
allocated channel: ORA_DISK_3
channel ORA_DISK_3: sid=18 devtype=DISK
allocated channel: ORA_DISK_4
channel ORA_DISK_4: sid=17 devtype=DISK
allocated channel: ORA_DISK_5
channel ORA_DISK_5: 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=25 recid=25 stamp=623931644
channel ORA_DISK_1: starting piece 1 at 30-MAY-07
channel ORA_DISK_2: starting archive log backupset
channel ORA_DISK_2: specifying archive log(s) in backup set
input archive log thread=1 sequence=26 recid=26 stamp=623931644
channel ORA_DISK_2: starting piece 1 at 30-MAY-07
channel ORA_DISK_1: finished piece 1 at 30-MAY-07
piece handle=/iasrman/q02/prsmq02/prsmq02_df623931649_s59_s1 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:02
channel ORA_DISK_1: deleting archive log(s)
archive log filename=/q02/archive/prism/log_prsmq02_25.arc recid=25 stamp=623931644
channel ORA_DISK_2: finished piece 1 at 30-MAY-07
piece handle=/iasrman/q02/prsmq02/prsmq02_df623931649_s60_s1 comment=NONE
channel ORA_DISK_2: backup set complete, elapsed time: 00:00:02
channel ORA_DISK_2: deleting archive log(s)
archive log filename=/q02/archive/prism/log_prsmq02_26.arc recid=26 stamp=623931644
Finished backup at 30-MAY-07
Starting backup at 30-MAY-07
using channel ORA_DISK_1
using channel ORA_DISK_2
using channel ORA_DISK_3
using channel ORA_DISK_4
using channel ORA_DISK_5
channel ORA_DISK_1: starting incremental level 0 datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00009 name=/q02/oradata01/prsmdata/Data_13.dbf
input datafile fno=00016 name=/q02/oradata01/prsmdata/Data_20.dbf
input datafile fno=00025 name=/q02/oradata01/prsmdata/Data_04.dbf
input datafile fno=00005 name=/q02/oraindx01/prsmdata/Index_11.dbf
input datafile fno=00020 name=/q02/oradata01/prsmdata/Tools02.dbf
input datafile fno=00022 name=/q02/oraindx01/prsmdata/index_12.dbf
channel ORA_DISK_1: starting piece 1 at 30-MAY-07
channel ORA_DISK_2: starting incremental level 0 datafile backupset
channel ORA_DISK_2: specifying datafile(s) in backupset
input datafile fno=00010 name=/q02/oradata01/prsmdata/Data_14.dbf
input datafile fno=00015 name=/q02/oradata01/prsmdata/Data_19.dbf
input datafile fno=00024 name=/q02/oradata01/prsmdata/Data_03.dbf
input datafile fno=00003 name=/q02/oratmp01/prsmdata/rbs01.dbf
input datafile fno=00001 name=/q02/orasys01/prsmdata/system01.dbf
input datafile fno=00012 name=/q02/orasys01/prsmdata/system02.dbf
channel ORA_DISK_2: starting piece 1 at 30-MAY-07
channel ORA_DISK_3: starting incremental level 0 datafile backupset
channel ORA_DISK_3: specifying datafile(s) in backupset
input datafile fno=00008 name=/q02/oradata01/prsmdata/Data_12.dbf
input datafile fno=00014 name=/q02/oradata01/prsmdata/Data_18.dbf
input datafile fno=00023 name=/q02/oradata01/prsmdata/Data_02.dbf
input datafile fno=00028 name=/q02/oradata01/prsmdata/Data06.dbf
input datafile fno=00019 name=/q02/oratmp01/prsmdata/rbs02.dbf
input datafile fno=00021 name=/q02/orasys01/prsmdata/DRSYS.dbf
channel ORA_DISK_3: starting piece 1 at 30-MAY-07
channel ORA_DISK_4: starting incremental level 0 datafile backupset
channel ORA_DISK_4: specifying datafile(s) in backupset
input datafile fno=00007 name=/q02/oradata01/prsmdata/Data_11.dbf
input datafile fno=00013 name=/q02/oradata01/prsmdata/Data_17.dbf
input datafile fno=00018 name=/q02/oradata01/prsmdata/Data_01.dbf
input datafile fno=00006 name=/q02/oradata01/prsmdata/Tools01.dbf
input datafile fno=00002 name=/q02/oradata01/prsmdata/Users01.dbf
input datafile fno=00026 name=/q02/oradata01/prsmdata/Data05.dbf
channel ORA_DISK_4: starting piece 1 at 30-MAY-07
channel ORA_DISK_5: starting incremental level 0 datafile backupset
channel ORA_DISK_5: specifying datafile(s) in backupset
input datafile fno=00004 name=/q02/oradata01/prsmdata/Data_15.dbf
input datafile fno=00011 name=/q02/oradata01/prsmdata/Data_16.dbf
input datafile fno=00017 name=/q02/oradata01/prsmdata/Data_22.dbf
input datafile fno=00027 name=/q02/oradata01/prsmdata/Data_05.dbf
channel ORA_DISK_5: starting piece 1 at 30-MAY-07
channel ORA_DISK_1: finished piece 1 at 30-MAY-07
piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s61_s1 comment=NONE
channel ORA_DISK_1: starting piece 2 at 30-MAY-07
channel ORA_DISK_2: finished piece 1 at 30-MAY-07
piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s62_s1 comment=NONE
channel ORA_DISK_2: starting piece 2 at 30-MAY-07
channel ORA_DISK_3: finished piece 1 at 30-MAY-07
piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s63_s1 comment=NONE
channel ORA_DISK_3: starting piece 2 at 30-MAY-07
channel ORA_DISK_4: finished piece 1 at 30-MAY-07
piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s64_s1 comment=NONE
channel ORA_DISK_4: starting piece 2 at 30-MAY-07
channel ORA_DISK_5: finished piece 1 at 30-MAY-07
piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s65_s1 comment=NONE
channel ORA_DISK_5: starting piece 2 at 30-MAY-07
channel ORA_DISK_2: finished piece 2 at 30-MAY-07
piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s62_s2 comment=NONE
channel ORA_DISK_2: starting piece 3 at 30-MAY-07
channel ORA_DISK_1: finished piece 2 at 30-MAY-07
piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s61_s2 comment=NONE
channel ORA_DISK_1: starting piece 3 at 30-MAY-07
channel ORA_DISK_4: finished piece 2 at 30-MAY-07
piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s64_s2 comment=NONE
channel ORA_DISK_4: starting piece 3 at 30-MAY-07
channel ORA_DISK_5: finished piece 2 at 30-MAY-07
piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s65_s2 comment=NONE
channel ORA_DISK_5: starting piece 3 at 30-MAY-07
channel ORA_DISK_3: finished piece 2 at 30-MAY-07
piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s63_s2 comment=NONE
channel ORA_DISK_3: starting piece 3 at 30-MAY-07
channel ORA_DISK_2: finished piece 3 at 30-MAY-07
piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s62_s3 comment=NONE
channel ORA_DISK_2: starting piece 4 at 30-MAY-07
channel ORA_DISK_4: finished piece 3 at 30-MAY-07
piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s64_s3 comment=NONE
channel ORA_DISK_4: starting piece 4 at 30-MAY-07
channel ORA_DISK_1: finished piece 3 at 30-MAY-07
piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s61_s3 comment=NONE
channel ORA_DISK_1: starting piece 4 at 30-MAY-07
channel ORA_DISK_2: finished piece 4 at 30-MAY-07
piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s62_s4 comment=NONE
channel ORA_DISK_2: backup set complete, elapsed time: 00:53:23
channel ORA_DISK_5: finished piece 3 at 30-MAY-07
piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s65_s3 comment=NONE
channel ORA_DISK_5: starting piece 4 at 30-MAY-07
channel ORA_DISK_3: finished piece 3 at 30-MAY-07
piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s63_s3 comment=NONE
channel ORA_DISK_3: starting piece 4 at 30-MAY-07
channel ORA_DISK_4: finished piece 4 at 30-MAY-07
piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s64_s4 comment=NONE
channel ORA_DISK_4: starting piece 5 at 30-MAY-07
channel ORA_DISK_1: finished piece 4 at 30-MAY-07
piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s61_s4 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:59:04
channel ORA_DISK_3: finished piece 4 at 30-MAY-07
piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s63_s4 comment=NONE
channel ORA_DISK_3: backup set complete, elapsed time: 01:00:10
channel ORA_DISK_5: finished piece 4 at 30-MAY-07
piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s65_s4 comment=NONE
channel ORA_DISK_5: backup set complete, elapsed time: 01:00:25
channel ORA_DISK_4: finished piece 5 at 30-MAY-07
piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s64_s5 comment=NONE
channel ORA_DISK_4: backup set complete, elapsed time: 01:01:40
Finished backup at 30-MAY-07
Starting backup at 30-MAY-07
current log archived
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 05/30/2007 11:22:38
RMAN-06004: ORACLE error from recovery catalog database: ORA-03114: not connected to ORACLE

connect target /You need to inform the connection string to target database.
Can to be explicitly or with 'export sid' in your script.

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.$$

Schedule rman script in Windows 2003

Oracle 10.2. I wrote a rman script and tried to schedule auto run in Windows 2003 server. I got this errors:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-04005: error from target database:
ORA-12560: TNS:protocol adapter error
The batch file name: rman_backup.bat
content: rman target / cmdfile rman_backup.rcv log rman_backup.log
Here is how I set it up:
go to Control Panel>Scheduled Tasks>Add Scheduled Task, find rman_backup.bat, choose the run time and finish it. When asking for user name and password, I supply the user which is in oracle dba group.
But when it run, it just produced the above error and won't run.
Please advise
S.
in SQLnet.log
fatal NI connect error 12560, connecting to:
(DESCRIPTION=(ADDRESS=(PROTOCOL=BEQ)(PROGRAM=oracle)(ARGV0=oracleORCL)(ARGS='(DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq)))'))(CONNECT_DATA=(SID=ORCL)(CID=(PROGRAM=D:\oracle\product\10.2.0\db_1\bin\rman.exe)(HOST=W3TY5Z203)(USER=WELC))))
VERSION INFORMATION:
TNS for 32-bit Windows: Version 10.2.0.4.0 - Production
Oracle Bequeath NT Protocol Adapter for 32-bit Windows: Version 10.2.0.4.0 - Production
Time: 30-MAR-2010 11:27:00
Tracing not turned on.
Tns error struct:
ns main err code: 12560
TNS-12560: TNS:protocol adapter error
ns secondary err code: 0
nt main err code: 530
TNS-00530: Protocol adapter error
nt secondary err code: 2
nt OS err code: 0

here is example of script we are using to backup database from windows scheduler:
set oracle_home=d:\oracle\ora920
set path=d:\perl\bin;d:\oracle\ora920\bin;c:\winnt;c:\WINDOWS\system32;
set PERL5LIB=''
set NLS_LANG=AMERICAN_AMERICA.WE8MSWIN1252
set TNS_ADMIN=d:\oracle\ora920\network\admin
d:
cd \scripts
set oracle_sid=car
rman target sys/car_$z3br4 catalog rman/oemrp_pwd@oemrp @rman_level0_car.rman > rman_level0_car.log
perl email_log.pl "RMAN Level 0 Log" d:\scripts\rman_level0_car.log CARthis script backing up 9i database. 10g and 11g database we backing up via EM grid control.
You can change this script to backup 10g or 11g databses as well.

What's wrong with this RMAN script?

Hi,
I have a rman script to back up the 8i database like the following:
#!/bin/ksh
if [ $# != 1 ]; then
echo "Usage: $0 ORACLE_SID"
exit
fi
ORACLE_SID=$1; export ORACLE_SID
RMAN_LOC=/u1/rman_backup
export ORACLE_HOME=/u2/oracle/8.1.7
export PATH=$ORACLE_HOME/bin:$PATH
echo "connect target /" > rman_backup.rcv
echo "" >> rman_backup.rcv
echo "configure controlfile autobackup on;" >> rman_backup.rcv
echo "" >> rman_backup.rcv
echo "configure controlfile autobackup format for device type disk to '${RMAN_LOC}/%F';" >
rman_backup.rcvecho "" >> rman_backup.rcv
echo "run {" >> rman_backup.rcv
echo "allocate channel t1 type disk;" >> rman_backup.rcv
echo "backup database format '${RMAN_LOC}/db_${ORACLE_SID}_%u';" >> rman_backup.rcv
echo "}" >> rman_backup.rcv
rman cmdfile rman_backup.rcv
When I run it, I got the following error:
RMAN> connect target /
2>
3> configure controlfile
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01005: syntax error: found "controlfile": expecting one of: "compatible"
RMAN-01007: at line 3 column 11 file: rman_backup.rcv
BTW, the same script is working fine with 9i db.
Could someone help me?
Thanks in advance,
Helen

Hello,
there is no controlfile autobackup in 8i RMAN. You must copy controlfile on your own, e.g. SQL 'ALTER DATABASE BACKUP CONTROLFILE TO file_name' or use eqiv. rman command - please check documentation.
Kind Regards, Piotr
DBA OCP.

RMAN Script & RMAN Configuration

Dear All,
This is the first time i am using RMAN. i just wanted to execute the following RMAN script for a testing purpose, for this what are the RMAN configuration i must have to do before executing this script below:
RMAN> run {
shutdown immediate;
startup mount;
backup database;
alter database open;
}This is my current setup of RMAN
RMAN> show all;
RMAN configuration parameters for database with db_unique_name DP are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
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 'E:\RMAN\';
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'E:\APP\10004\PRODUCT\11.2.0\DBHOME_1\DATABASE\SNCFDP.ORA'; # defaultKindly advice me and give me a very clear study for this above parameters
Regards
HAMEED
Once i execute that script i got this following error :
+RMAN> run {+
+2> shutdown immediate;+
+3> startup mount;+
+4> backup database;+
+5> alter database open;+
+6> };+
database closed
database dismounted
Oracle instance shut down
connected to target database (not started)
Oracle instance started
database mounted
Total System Global Area     770019328 bytes
Fixed Size                     1374780 bytes
Variable Size                301991364 bytes
Database Buffers             461373440 bytes
Redo Buffers                   5279744 bytes
Starting backup at 18-MAY-11
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=134 device type=DISK
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00006 name=E:\APP\10004\ORADATA\DP\HAMEED01.DBF
input datafile file number=00007 name=E:\APP\10004\ORADATA\DP\ABDUL01.DBF
input datafile file number=00008 name=E:\APP\10004\ORADATA\DP\TEST01.DBF
input datafile file number=00001 name=E:\APP\10004\ORADATA\DP\SYSTEM01.DBF
input datafile file number=00002 name=E:\APP\10004\ORADATA\DP\SYSAUX01.DBF
input datafile file number=00005 name=E:\APP\10004\ORADATA\DP\EXAMPLE01.DBF
input datafile file number=00003 name=E:\APP\10004\ORADATA\DP\UNDOTBS01.DBF
input datafile file number=00004 name=E:\APP\10004\ORADATA\DP\USERS01.DBF
channel ORA_DISK_1: starting piece 1 at 18-MAY-11
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 05/18/2011 17:22:30
ORA-19504: failed to create file "E:\RMAN\"
ORA-27038: created file already exists
OSD-04010: <create> option specified, file already exists
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
Edited by: Hameed on May 18, 2011 4:59 AM

Dear Chinar, can you please varify this below ,, is it correct,, after given your setup i ran this script,,,
Kindly advice me
Regards
HAMEED
RMAN> run
2> {
3> backup current controlfile;
4> }
Starting backup at 18-MAY-11
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=143 device type=DISK
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
including current control file in backup set
channel ORA_DISK_1: starting piece 1 at 18-MAY-11
channel ORA_DISK_1: finished piece 1 at 18-MAY-11
piece handle=E:\RMAN\FULL_06MCLH66_1_1.BK tag=TAG20110518T180910 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
Finished backup at 18-MAY-11
Starting Control File Autobackup at 18-MAY-11
piece handle=E:\RMAN\CFC-796596855-20110518-00 comment=NONE
Finished Control File Autobackup at 18-MAY-11Edited by: Hameed on May 18, 2011 5:55 AM

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 !!!!!

RMAN script failed while creating Data Guard 11g

Hi Friends,
I am creating Physical Standby (11g) using RMAN (ACTIVE) on windows using the doc : Step by Step Guide on Creating Physical Standby Using RMAN DUPLICATE...FROM ACTIVE DATABASE [ID 1075908.1]
The folder structure on Primary DB and on Physical Standby is totally different.
while executing RMAN script i got errors for lot of locations and i specified the proper location in RMAN script itself (ex set diagnostic_dest = 'c:\app\' , set db_recovery_file_dest='C:\app\flash_recovery_area')
Location of control files on Primary DB:
D:\oradata\MESSTG\CONTROL01.CTL
D:\oradata\flash_recovery\messtg\MESSTG\CONTROL02.CTL
Location of control files (planned) on Physical Standby DB:
C:\app\oradata\MESSTDBY\CONTROL01.CTL
C:\app\flash_recovery_area\MESSTDBY\CONTROL02.CTL
How to specify control file location of Physical standby in set control_files?
Also i have 2 control files on Primary DB so do i need to specify both the control files , if so how?
I tried different combination in RMAN script but all are failed:
set control_files='D:\oradata\MESSTG\CONTROL01.CTL','C:\app\oradata\MESSTDBY\CONTROL01.CTL'
RMAN Error is :
while using set control_files=: C:\app\oradata\MESSTDBY\CONTROL01.CTL
contents of Memory Script:
backup as copy current controlfile for standby auxiliary format 'D:\ORADATA\MESSTG\CONTROL01.CTL';
restore clone controlfile to 'C:\APP\ORADATA\MESSTDBY\CONTROL01.CTL' from
'D:\ORADATA\MESSTG\CONTROL01.CTL';
executing Memory Script
Starting backup at 16-APR-13
channel prmy1: starting datafile copy
copying standby control file
released channel: prmy1
released channel: prmy2
released channel: prmy3
released channel: prmy4
released channel: stby
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 04/16/2013 14:18:41
RMAN-03015: error occurred in stored script Memory Script
RMAN-03009: failure of backup command on prmy1 channel at 04/16/2013 14:18:41
ORA-17628: Oracle error 19505 returned by remote Oracle server
RMAN>
Error 2)
while using set control_files='D:\oradata\MESSTG\CONTROL01.CTL','C:\app\oradata\MESSTDBY\CONTROL01.CTL'
contents of Memory Script:
backup as copy current controlfile for standby auxiliary format 'D:\ORADATA\MESSTG\CONTROL01.CTL';
executing Memory Script
Starting backup at 16-APR-13
channel prmy1: starting datafile copy
copying standby control file
released channel: prmy1
released channel: prmy2
released channel: prmy3
released channel: prmy4
released channel: stby
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 04/16/2013 13:22:33
RMAN-03015: error occurred in stored script Memory Script
RMAN-03009: failure of backup command on prmy1 channel at 04/16/2013 13:22:33
ORA-17628: Oracle error 19505 returned by remote Oracle server
RMAN>
Regards,
DB

Hi,
Can you paste here you rman script ?
I think following script can help you.
duplicate target database for standby
from active database
spfile
set "control_files"="d:\oradata\<standbydbuniquename>\CONTROL01.CTL"
set "db_name"="<DBNAME>"
set "db_unique_name"="<STANBYD DBA UNIQUENAME>"
set "db_file_name_convert"="C:\app\oracle\oradata\<dbname>","d:\oradata\<standbydbuniquename>"
set "log_file_name_convert"="C:\app\oracle\oradata\<dbname>","d:\oradata\<standbydbuniquename>"
set "db_recovery_file_dest"="D:\fast_recovery_area"
nofilenamecheck;C:\app\oracle\oradata\<dbname> - it is primary database dafiles location
D:\oradata\<standbydbuniquename> - it is standby database datafile location.
Don't forget creation of diagnostinc dests.
Regards
Mahir M. Quluzade

FRA backup in RMAN script

Similar Messages

Maybe you are looking for