Any rman scripts?

Hi all,
is there any rman scripts that I can download and put to production?
thanks
andrew

Hi,
Sample Script fine.. Sir..
Refer to the following doc's.. you will get any Idea
http://www.idevelopment.info/data/Oracle/DBA_tips/RMAN_9i/RMAN9_12.shtml
http://www.oracle-base.com/articles/10g/RMANEnhancements10g.php
http://www.oracle.com/technology/deploy/availability/htdocs/rman_overview.htm
I am not Angry.. I though you are messing up with Production DB.. That's it.. nothing much.. !!
I am just helping out not the do any thing on your production DB that is my concern.
Do Remember you posted the statement
is there any rman scripts that I can download and put to productionI think you have not specified the any word "SAMPLE" over in first post. Second thing is you specified "on Production"
- Pavan Kumar N
Edited by: Pavan Kumar on Feb 16, 2009 6:46 PM

Similar Messages

Please review the RMAN script and throw any comments which will increase KB

Dear Sirs:
I would be grateful if anyone in this forum checks whether the RMAN strategy taken by me is OK or require any room for improvement. I have not yet
moved into production.
Environment: ORACLE 10G R2 running on RAC, RHEL 4.0 for Intel Itanium. RMAN script runs every night at 10PM from node 1 of 2.
ASM is used and all datafiles, controlfiles, arc, redo in SAN
Process:
<1> Empty folder "PreviousdayBackup
<2> Move backup of yesterday night to "PreviousdayBackup"
<3> Execute RMAN the script provided below.
run {
     backup
          filesperset=15
          incremental level 0
          spfile format '/archive/backup/rman/spfile_%d_%s_%T.bak' tag 'spfile_backup'
          database format '/archive/backup/rman/data_%d_%s_%T.bak' tag 'full_data_backup';
          crosscheck backup;
          sql 'alter system archive log current';
          crosscheck archivelog all;
          backup filesperset 288 format '/archive/backup/rman/cscdb_data_archive_%d_%u' archivelog all delete input;
          delete archivelog all completed before 'sysdate-7';
          delete noprompt expired archivelog all;
          delete noprompt obsolete;
          backup current controlfile format '/archive/backup/rman/%d_data_control_%s_%p_%u' tag 'control_file';
The Tape runs at 3:00AM in the morning and takes all the files from '/archive/backup/rman/'
_*RMAN Configuration*_
CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
CONFIGURE BACKUP OPTIMIZATION OFF;
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/archive/backup/rman/ctrl_%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
CONFIGURE MAXSETSIZE TO UNLIMITED;
CONFIGURE ENCRYPTION FOR DATABASE OFF;
CONFIGURE ENCRYPTION ALGORITHM 'AES128';
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/oracle/product/1020/db_1/database/snapcf_cscdb1.f';
I am also not getting the concepts properly on :
delete archivelog all completed before 'sysdate-7';
delete noprompt expired archivelog all;
delete noprompt obsolete;
Is the delete within the RMAN pieces or within the folder. It would be great if someone can explain me on these
Awaiting for your kind response
Caesar
Edited by: caesar dutta on 10-May-2012 00:10

Hi emre baransel :
Step 1: Delete from folder "previousdaybackup"
Step 2: Move last night backup from "/archive/backup/rman" to "previousdaybackup"
Step 3: Run RMAN and backup is stored at "/archive/backup/rman"
Stpe 4: Data is backed up to DLT cartridge from "/archive/backup/rman"
The folder "/archive/backup/rman" is a separate partition from SAN mounted in the LINUX SYSTEM as ext3
Why did you chose filesperset=15, do you have specific purpose?Well I am looking at existing RMAN in the place and not changing any basic configuration. Frankly speaking I do not have answer to this.
I have changed the RMAN commands as
run {
     backup
          filesperset=15
          incremental level 0
          spfile format 'D:\archive\backup\rman\cscdb1\spfile_%d_%s_%T.bak' tag 'spfile_backup'
          database format 'D:\archive\backup\rman\cscdb1\data_%d_%s_%T.bak' tag 'full_data_backup';
          crosscheck backup;
          sql 'alter system archive log current';
          crosscheck archivelog all;
          backup filesperset 288 format 'D:\archive\backup\rman\cscdb1\cscdb_data_archive_%d_%u' archivelog all not backed up 2 times;
          delete noprompt archivelog all completed before 'sysdate-7';
          delete noprompt expired archivelog all;
          delete noprompt obsolete;
I feel that I will be in a safer side.
Please provide comments. Anything that will increase knowledge base and will educate others too in this forum.
regards,
caesar

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 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 for Unix

We have decided to abandon user managed hot backups and go with RMAN. Could you critizize the following approach and see if we are missing anything? I am making whole database backup and controlfile and archivelogs. I am using RMAN catalog.
In a Unix script setting all of the environment variables and then
connect target ********
connect catalog *********
configure snapshot controlfile to '${ORACLE_HOME}/snapshot_${ORACLE_SID}_${TIMESTAMP}_ctl';
run {
allocate channel c1 type disk;
allocate channel c2 type disk;
allocate channel c3 type disk;
backup database plus archivelogs;
release channel c1;
release channel c2;
p.s. control file autobackup is on
Also, I have these questions:
1. How do I direct the output of this backup to a file?
2. Is there a way to check for errors within this file to see if the backup went ok?
3. Would anyone have a unix shell script example of the above?
4. How do I make sure that catalog is synched with control file and what is on the file system?
5. Is it customary to delete archive logs via RMAN script if, say, my policy is to keep it on the file system for 7 days?
thank you for any input!

Hi,
You didnot mention the db version, assumed it's 10g.
If you planned to schedule this job at os level, you might use crontab (unix). The snapshot controlfile config can set with catalog once, so it's not needed to include in your backup script. Like wise your retention can set as "recovery window of 7 days".
1. How do I direct the output of this backup to a file?
==> inside rman script you might use the following command,
set log to '/home/oracle/rmanbkp.log';
2. Is there a way to check for errors within this file to see if the backup went ok?
==> you might check in the logfile for ORA- and RMAN- errors.
3. Would anyone have a unix shell script example of the above?
I use to schedule this job either by OEM or crontab using rman script file.
4. How do I make sure that catalog is synched with control file and what is on the file system?
RMAN will do auto sync with controlfile.
5. Is it customary to delete archive logs via RMAN script if, say, my policy is to keep it on the file system for 7 days?
Upon successful backup you may delete the archivelogs or you might decide to keep it for 7 days and then delete by applying "delete obsolete" command.
Thanks,
Nirmal

How can RMAN script check if database is down?

Some of our test databases are not always up and running, however when our backup software still calls the RMAN scripts and bombs when it can't connect, producing unwanted errors in the backup software logs.
Is there something simple I can put in the RMAN script that will check if the DB is down and simply exit if it is?

i know RMAN simply errors out, that's the problem.
we don't consider that a "real" error, but our backup software sees any error as legit and reports it to us.
we don't simply want to ignore these error messages, because sometimes they contain an error that IS important to us.

Using scheduler to directly execute rman script stored in recovery catalog

Hi everyone, I usually automate my rman backups using either cron or dbms_scheduler to call my rman scripts stored in a NIX sh file. Everything works fine but does anyone know how/if it's possible to call an rman script stored in the recovery catalog. Lets say I create a script in the catalog:
RMAN> create script showall
comment 'just an example for demonstration'
SHOW ALL;
Can I use dbms_scheduler to call that script directly? If so how and if not then how can I schedule this or any catalog stored script stored in the rman catalog. Searched all over the place but everything seems to point to having to leave Oracle to call either a .sh or .bat file.
Regards,
Dave

Hi Greg, think you are definately on the right track mate. Based on what you put I found this at:
http://www.oracle-base.com/articles/12c/scheduler-enhancements-12cr1.php
It has the entire rman script in the pl/sql block but going to see if I can modify what's on that page and use what you put so instead of executing the entire script it will run something like:
BEGIN
DBMS_SCHEDULER.CREATE_JOB(
job_name => 'RMAN_SHOW_ALL',
job_type => 'EXECUTABLE',
job_action => 'RMAN TARGET / CATALOG rman/password@ your_cat run {execute script showall;}'
END;
Or something similar with times etc for execution if possible as the mechanics are the same. Believe though that using the job_action parameter will be the answer and allow me to automate my daily etc backups at night.
Will let you know once it's done and mark as correct answer.
Dave

Creating pfile in RMAN script

I am trying to create pfile from spfile from RMAN scripts as follows, but ran into issues
run {
2> sql 'create pfile=/tmp/p.ora from spfile';
3> }
sql statement: create pfile=/tmp/p.ora from spfile
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of sql command on default channel at 02/20/2009 11:23:06
RMAN-11003: failure during parse/execution of SQL statement: create pfile=/tmp/p.ora from spfile
ORA-02236: invalid file name
Any other suggestions to get the desired results. I want to create pfile in a different directory rather than defualt dbs directory.

stevencallan wrote:
How would this command look in SQL*Plus?
http://download.oracle.com/docs/cd/B19306_01/server.102/b14200/statements_6008.htm#i2072768
Check your use of quotation marks.NO...read what you said.
What does SQL*Plus have to do with this command. You mentioned quotations marks...what kind of quotation marks..single or double and where should there be ??

Getting the RMAN scripts triggered from OEM ?

RDBMS Version : 11.2.0.3/RHEL 5.4
In our shop, Level 0 , Level 1 scripts are triggered from OEM. I am not an OEM guy :). Is there any way I could retrieve the RMAN scripts used to perform L0 and L1 backups ?

Hi,
Connect to EM.
Go to Availability tab, go to Schedule Backup menu under Manage.
There you can see: Backup Jobs link.
You can remove or edit this jobs.
Mahir M. Quluzade
http://www.mahir-quluzade.com

Edit rman script

Hi guys,
someone can tell me if is possible to edit rman script in Backup Jobs definition of Grid?
I've scheduled some jobs backup and I need to edit script but don't find where i can edit it..
thanks
Andrea

hi,
yes this is possible.
from grid, select the database and then scroll down to the bottom of the page, there you will see a section called Related Lin ks,
one of these is jobs.
select this and you will then get a page which shows any scheduled jobs, completed jobs.
there are also a number of options one of which is 'edit', this will allow you to edit your job.
hope this helps
Alan

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

Create a user who can run only 'rman script'

Dear Friends ,
I have created a 'rmanback; user who only can run the RMAN script only . I have created user like follwoing way :
1)
SQL> CREATE USER rmanback IDENTIFIED BY rmanback;
User created.
SQL> GRANT RECOVERY_CATALOG_OWNER TO rmanback;
Grant succeeded.
SQL> GRANT CONNECT, RESOURCE TO rmanback;
Grant succeeded.
2)
And My rman script is :
rman target rmanback/rmanback@orcl <<!
run
allocate channel t1 type disk;
backup format 'df_%t_%s_%p'
(database);}
3) And I make a situation where sys user cannot enter the database using its password . For this reason i give the follwoing entry in "sqlnet.ora" :
SQLNET.AUTHENTICATION_SERVICES=(NONE)
Now when I run the script then it shows the follwing error :
[oracle@localhost RMAN]$ sh rman.sh.copy
Recovery Manager: Release 10.1.0.3.0 - Production
Copyright (c) 1995, 2004, Oracle. All rights reserved.
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-01031: insufficient privileges
Now plz tell me where is the problem . If I make any mistake then plz inform me .....
Thx
-----

SYSOPER is a privilege that is not enough for recovery manager. Talking about SYSOPER privileges to perform a backup/recover operation from a sqlplus prompt, SYSOPER can perform backup operations, but when recovery is required, the only kind of recover it can perform is a complete recover, if the user requires any kind of incomplete recover it won't be possible since SYSOPER cannot issue neither of until time|change|cancel|controlfile operations, which require the user to connect with the SYSDBA role.
If you attempt to connect to the database by means of recovery manager with an account with SYSOPER role, you will get the following error:
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-01031: insufficient privilegesFor the OP, there is no way to create some sort of operator accout, since this will have to connect as SYSDBA to perform all operations required by recovery manager, you will absolutely have to rethink your security strategy, and as I previously posted, you should use OS authentication and protect access to the host server.
~ Madrid
http://hrivera99.blogspot.com/

How to store the value into variable and access it in RMAN script

I want to create a variable and dynamically assign a numeric value to it (may get the value may be from SQL )and access the value in RMAN script.
Thanks...Raj

Raj,
We have been getting this type of request and it is not possible via RMAN to do that.
BUT--You could write a sql/plus script to query your variable and produce the RMAN script with the new value.
Just a suggestion.
Tammy

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.

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.

Any rman scripts?

Similar Messages

Maybe you are looking for