RMAN script error in UNIX

I have db10.2.0.3 on SUN Solaris 10.
I have a rman script called backup_aps2
This is the content
#!/usr/bin/csh -fvx
rman target / <<EOF
configure controlfile autobackup on;
run
recover copy of database with tag 'incr_update';
backup incremental level 1 for recover of copy with tag 'incr_update'
database;
EOFI got this error when I ran it:
test% ./backup_aps2
rman target / << EOF
/tmp/shXXXXXX: Permission deniedPlease help!
Thanks a lot!

Not an Oracle problem.
A 'here-document' is automatically turned in a temporary file.
The default directory for temporary files is /tmp.
As per the error message, you apparently didn't read, you have no permission to create files in this directory.
You can change the location of your temporary files for your session by setting the TMP and TMPDIR variables to an appropiate value.
Sybrand Bakker
Senior Oracle DBA

Similar Messages

RMAN Script Error

Hi
I am a DBA working on ORACLE 9i on Tru64 Unix
Recently i changed password for the sys and system users on the Database
We have some scripts running on the Server to conduct various backups
After changing the necessary password on the script RMAN.sh (the script that we use to trigger the backup daily) i noted that the RMAN Backup log is giving 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 privileges
When i run the same script (RMAN.sh) manually it works fine but it gives the above error when it is triggered automatically every night.
Where am i wrong in this.

This things happen sometimes.
After changing the password have changed any thing in your script?
If not then check your script
In your problematic script change all the codes and just take the backup of your spfile or a small tablespace then you will be confirmed that weather it is a problem of your script or not.
If it is a same problem or it is a new error. If the error persist then create a new .sh file of your old scripts. Run the new script and check if the problem comes again or not.
Regards
Asif Kabir

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.

MAXL Script error in UNIX

Hi All,
i have a maxl script to export the level 0 data and also a shell script with command "*essmsh maxlscriptname.mxl*" in it, the version that i am working on is essbase 11.1.2 and the platform is in unix.
I have seen that, for the maxl script to work in version 11 we have to use the command "*startEssmsh.sh*" so that it sets all the variables and then runs the required script.
The problem is, i dont have startEssmsh.sh in my \bin directory and even if i change my shell script to "*startEssmsh.sh maxlscriptname.mxl*" its not working, it says that startEssmsh.sh not found.
Kindly let me know on how to run the mxl script in unix with no startEssmsh.sh file present \bin directory. Are there any manual steps to set up the variables and if yes, what are they.
Thanks,
Amogh

The script you are looking for is:
<MIDDLEWAREHOME>/user_projects/epmsystem1/EssbaseServer/essbaseserver1/bin/startMaxl.sh
In UNIX you will need to use the full path to startMaxl.sh unless you have <MIDDLEWAREHOME>/user_projects/epmsystem1/EssbaseServer/essbaseserver1/bin in your PATH statement.
Regards,
John A. Booth
http://www.metavero.com

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

Rman/PERL scripts errors

I am trying to automate the backups and disk maintenence on a test machine using a "Host Command" in the 10g EM environment. If I run the script from the command on the target host the scripts completes successfully.
This is the script:
ORACLE_HOME=/u01/app/oracle/product/9.2.0
export ORACLE_HOME
ORACLE_SID=coeusdba.
export ORACLE_SID
rman <<EOF
connect target sys<password>@coeusdba;
connect catalog <user>/<password>@recv;
replace script coeusdba_full_bkp {
allocate channel Channel1 type disk format '/u03/orabkp/coeusdba/b_%u_%p_%c';
backup
( database include current controlfile );
backup ( archivelog all delete input );
run { execute script coeusdba_full_bkp;}
EOF
/u01/app/oracle/product/9.2.0/dbs/scripts/coeusdba_new.sh
exit
When I execute the same script from a 10g EM "Host Command" job the script fails at the PERL command step with the following output:
Recovery Manager: Release 9.2.0.7.0 - Production
Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
RMAN>
RMAN>
connected to target database: COEUSDBA (DBID=1916078485)
RMAN>
RMAN>
connected to recovery catalog database
RMAN> 2> 3> 4> 5> 6> 7> 8>
replaced script coeusdba_full_bkp
RMAN>
RMAN>
executing script: coeusdba_full_bkp
allocated channel: Channel1
channel Channel1: sid=10 devtype=DISK
Starting backup at NOV-01-2005 10:32:32
channel Channel1: starting full datafile backupset
channel Channel1: specifying datafile(s) in backupset
including current controlfile in backupset
input datafile fno=00006 name=/u02/oradata/coeusdba/users01.dbf
input datafile fno=00002 name=/u03/oradata/coeusdba/undotbs01.dbf
input datafile fno=00004 name=/u03/oradata/coeusdba/index01.dbf
input datafile fno=00005 name=/u03/oradata/coeusdba/tools01.dbf
input datafile fno=00007 name=/u03/oradata/coeusdba/xdb01.dbf
input datafile fno=00001 name=/u02/oradata/coeusdba/system01.dbf
input datafile fno=00003 name=/u02/oradata/coeusdba/drsys01.dbf
channel Channel1: starting piece 1 at NOV-01-2005 10:32:33
channel Channel1: finished piece 1 at NOV-01-2005 10:33:28
piece handle=/u03/orabkp/coeusdba/b_3rh2l4q1_1_1 comment=NONE
channel Channel1: backup set complete, elapsed time: 00:00:55
Finished backup at NOV-01-2005 10:33:28
Starting backup at NOV-01-2005 10:33:29
current log archived
channel Channel1: starting archive log backupset
channel Channel1: specifying archive log(s) in backup set
input archive log thread=1 sequence=49 recid=200 stamp=573215609
channel Channel1: starting piece 1 at NOV-01-2005 10:33:32
channel Channel1: finished piece 1 at NOV-01-2005 10:33:33
piece handle=/u03/orabkp/coeusdba/b_3sh2l4rr_1_1 comment=NONE
channel Channel1: backup set complete, elapsed time: 00:00:02
channel Channel1: deleting archive log(s)
archive log filename=/u04/arch/coeusdba/1_49.dbf recid=200 stamp=573215609
Finished backup at NOV-01-2005 10:33:35
Starting Control File and SPFILE Autobackup at NOV-01-2005 10:33:35
piece handle=/u04/orabkp/coeusdba/ctl_file_bkps/c-1916078485-20051101-00 comment=NONE
Finished Control File and SPFILE Autobackup at NOV-01-2005 10:33:38
released channel: Channel1
RMAN>
RMAN>
Recovery Manager complete.
syntax error at /u01/app/oracle/product/9.2.0/EM10g_1/perl/lib/5.6.1/warnings.pm line 306, near "{^"
syntax error at /u01/app/oracle/product/9.2.0/EM10g_1/perl/lib/5.6.1/warnings.pm line 311, near "{^"
BEGIN failed--compilation aborted at /u01/app/oracle/product/9.2.0/EM10g_1/perl/lib/5.6.1/English.pm line 38.
BEGIN failed--compilation aborted at /u01/app/oracle/product/9.2.0/dbs/scripts/rmanc.pl line 20
Is anyone having this problem in 10g and if so , can you provide me with some insight with respect to resolution?

The .sh script calls a perl script that parses the output of the report obsolete command in rman and deletes the obsolete datasets from disk. This shell completes from the command line with no errors. Here is the .sh and the perl script. Like I said the odd thing is that this shell executes successfully from the command line. Thanks for your interest in looking at this.
cat coeusdba_new.sh
/u01/app/oracle/product/9.2.0/dbs/scripts/rmanc.pl target sys/<password>@coeusdba catalog rmantest/<password>@recv redundancy 2
rmanc.$ cat rmanc.pl
#!/usr/bin/perl -w
# NAME
# rmanc.pl - delete obsolete backups and copies
# DESCRIPTION
# This perl script automates deletion of obsolete datafilecopies and
# backup pieces. It uses perl strin manipulation to process the output of the RMAN
# "report obsolete" command and creates rm commands to delete the files
# NOTES
# Some customization is necessary.
# Adapted from Oracle 8i rman1.sh Unix shell script.
# benmalek 03/08/2003 - Modified to delete backup sets and datafilecopies only
# Does not touch backup records.
use strict;
#use English;
#$ENV{ORACLE_OWNER}='oracle';
#$ENV{ORACLE_HOME}='/disk01/app/oracle/product/9.2.0';
$ENV{NLS_DATE_FORMAT}='DD-MON-YYYY:HH24:MI:SS';
&PrintEnv;
sub Usage {
my ($arg1, @arg2) = @_;
my $base_name = `basename $0`;
chop($base_name);
CASE: {
if (!defined($arg1)) {last CASE; }
if ($arg1 =~ /\S/) {print ("\nUnknown argument or incorrect value for: $arg1\n\n"); last CASE; }
my $example1 = 'rmanc.pl target sys/orclpass@orcl catalog rman/rmanpass@rec redundancy 5';
my $example2 = 'rmanc.pl target sys/orclpass@orcl nocatalog redundancy 5';
my $usage_txt =
" Usage: $base_name [option] ...
option: [target CNCTSTR] [catalog CNCTSTR | nocatalog] [params 'PARMS'] [redundancy NUMBER]
Option Description
target CNCTSTR Connect to the target db using CNCTSTR.
catalog CNCTSTR Connect to catalog db using CNCTSTR.
nocatalog Don't use a recovery catalog.
parms 'PARMS' Use PARMS string for SBT_TAPE maintenance channel.
You can use single or double quotes depending on
your needs. In the rman script, single-quotes
will be used.
redundancy NUMBER Set redundancy of backups to NUMBER.
The catalog or nocatalog option must be specified. All others are optional
The target option must also be specified
Examples:
$example1
$example2 ";
print ("$usage_txt \n");
die "Exiting subroutine 'Usage'.\n";
# Initialize default connect string variables:
my $target=""; # force user to supply target option
my $catalog=""; # force user to supply catalog option;
my $parms="";
my $redun=""; # force user to supply redundancy option;
# process target and catalog arguments
my $args = @ARGV;
while ( $args > 0 ) {
ARGS: {
if (($ARGV[0] eq "target") && defined($ARGV[1]))
{$target="$ARGV[0] $ARGV[1]"; shift(@ARGV); last ARGS;}
if (($ARGV[0] eq "catalog" || $ARGV[0] eq "rcvcat") && defined($ARGV[1]))
{ $catalog="$ARGV[0] $ARGV[1]"; shift(@ARGV); last ARGS;}
if ($ARGV[0] eq "nocatalog") { $catalog="$ARGV[0]"; last ARGS;}
if (($ARGV[0] eq "parms") && defined($ARGV[1])) { $parms = "$ARGV[0] $ARGV[1]"; shift(@ARGV); last ARGS;}
if (($ARGV[0] eq "redundancy") && defined($ARGV[1]) && !($ARGV[1] =~ /\D/))
{$redun=$ARGV[1]; shift(@ARGV); last ARGS;}
&Usage($ARGV[0]);
shift(@ARGV);
$args= @ARGV;
if ((!defined($catalog) || $catalog eq "") || (!defined($target) || $target eq "") || (!defined($redun) || $redun eq "" )) {&Usage;}
#print (" target=$target \n catalog=$catalog \n parms=$parms \n redundancy=$redun\n");
# Get a list of obsolete disk files to delete:
my @rman_out=`rman $target $catalog << EOF
report obsolete redundancy=$redun device type disk;
exit;
EOF`;
# debug
print ("############################################\n");
print ("Output of REPORT OBSOLETE REDUNDANCY=$redun\n");
print @rman_out;
print ("############################################\n");
#my $command = `rman $target $catalog << EOF
# report obsolete redundancy=$redun device type disk;
# exit;
# EOF"
#open (RMAN, "$command |" );
#my @rman_out=<RMAN>;
# Extract the names of the obsolete files to delete
my $line;
my @files;
my @dates;
my @pieces;
foreach $line (@rman_out) {
if (($line =~ /Backup Piece/) && ($line =~ /\S/)) {
my @fields=split (/\s+/, $line);
my $nelem=@fields;
push(@pieces, $fields[$nelem-3]);
push(@dates, $fields[$nelem-2]);
push(@files, $fields[$nelem-1]);
# Verify files exists
my $i=0;
foreach $line (@files) {
if (-e $line) {
print ("Deleting backup piece or file copy: $pieces[$i] $dates[$i] $line\n");
system("rm $line");
} else {
# print ("file $line does not exist. \n");
$i = $i + 1;
sub PrintEnv{
my $var;
foreach $var (sort keys %ENV) {
print "$var: \"$ENV{$var}\".\n"
pl

RMAN-03015: error occurred in stored script Memory Script

getting this error during
target db is 10202 & aux is 10204 ?
duplicate target database to dcxt;
RMAN> connect TARGET SYS/spurs_04@capq;
PL/SQL package SYS.DBMS_BACKUP_RESTORE version 10.02.00.03 in TARGET database is not current
PL/SQL package SYS.DBMS_RCVMAN version 10.02.00.03 in TARGET database is not current
connected to target database: CAPQ (DBID=2420849281)
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00601: fatal error in recovery manager
RMAN-03004: fatal error during execution of command
RMAN-10039: error encountered while polling for RPC completion on channel clone_default
RMAN-10006: error running SQL statement: select action from gv$session where sid=:1 and serial#=:2 and inst_id=:3
RMAN-10002: ORACLE error: ORA-03114: not connected to ORACLE
RMAN-10041: Could not re-create polling channel context following failure.
RMAN-10024: error setting up for rpc polling
RMAN-10005: error opening cursor
RMAN-10002: ORACLE error: ORA-03114: not connected to ORACLE
RMAN-03002: failure of Duplicate Db command at 05/21/2010 15:32:29
RMAN-03015: error occurred in stored script Memory Script
RMAN-06136: ORACLE error from auxiliary database: ORA-01092: ORACLE instance terminated. Disconnection forced
ORA-00704: bootstrap process failure
ORA-39700: database must be opened with UPGRADE option
oracle:tuldcorpadb01:dcxt$
Edited by: DBA2008 on May 21, 2010 3:37 PM

never mind, i resolved this by switching duplicate db to 10203....and adjusting log_arch_dest .....

RMAN Backup Script Error

Hi ,
I am getting the following error when i am executing manbackup shell script.
Message file RMAN<lang>.msb not found
Verify that ORACLE_HOME is set properly
RMAN Script
DATE=`date +%Y%m%d.%H%M`
#su - oracle
#<<EOF
export ORACLE_HOME=/home/app/oracle/product/10.2.0/db_1
echo $ORACLE_HOME
export PATH=$PATH:$ORACLE_HOME/bin
#export PATH=$ORACLE_HOME/bin:$PATH
export ORACLE_SID=ACILOC
echo $ORACLE_SID
rman cmdfile=/oraclebkp/rmanbackupscripts/rmanlevel0bkp.bck log=/oraclebkp/rmanbackupscripts/rmanACILOClev0$DATE.log
export ORACLE_SID=ACIDC
echo $ORACLE_SID
rman cmdfile=/oraclebkp/rmanbackupscripts/rmanlevel0bkp.bck log=/oraclebkp/rmanbackupscripts/rmanACIDClev0$DATE.log
#EOF
level0bkp.bck
connect target `/'
run
backup incremental level 0 database;
but I am able to take RMAN backups by connecting as RMAN TARGET /
Thanks in advance
Priya

connect target `/'Dont give / in quotations just connect as
connect target /
backup incremental level 0 database;
}Thanks
Close the threads as answered if helpful/correct.
user11342455
Handle: user11342455
Status Level: Newbie
Registered: Feb 18, 2010
Total Posts: 22
Total Questions: 10 (8 unresolved)
Edited by: CKPT on Jan 5, 2011 12:17 PM

RMAN script gives error when scheduled

Hi,
I have this rman script....
run {
allocate channel 'dev_0' type 'sbt_tape'
parms 'ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=TPRD,OB2BARLIST=test TPRD)';
backup incremental level <incr_level>
format 'test TPRD<TPRD_%s:%t:%p>.dbf'
database;
backup
format 'test TPRD<TPRD_%s:%t:%p>.dbf'
archivelog all;
backup
format 'test TPRD<TPRD_%s:%t:%p>.dbf'
current controlfile;
When this script is executed to run at the present moment, it gives no problems. However, when this script is scheduled and when executed at the scheduled time, it gives the following error:
RMAN> CONNECT TARGET *
2> run {
3> allocate channel 'dev_0' type 'sbt_tape'
4> parms 'ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=TPRD,OB2BARLIST=test TPRD,OB2BARHOSTNAME=+server.com+)';
5> backup incremental level
6> format
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "format": expecting one of: "equal, integer"
RMAN-01007: at line 6 column 1 file: C:/ob2.cmdfile.12274.c1e9.rman
[Major] From: ob2rman@+server.com+ "TPRD" Time: 2-11-2009 13:35:16
The database reported error while performing requested operation.
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "format": expecting one of: "equal, integer"
RMAN-01007: at line 6 column 1 file: C:/ob2.cmdfile.12274.c1e9.rman
[Major] From: ob2rman@+server.com+ "TPRD" Time: 2-11-2009 13:35:16
Oracle Recovery Manager completed with errors.
Does anyone know what the problem is and why it only gives the error when it is scheduled and not otherwise?
Thanks in advance.

Hi user629987,
The error comes from the following line
backup incremental level <incr_level>(found "format": expecting one of: "equal, integer"
see link:
http://download.oracle.com/docs/cd/B10501_01/server.920/a96565/rcmsynta9.htm#78484)
Can you replace it with
backup incremental level 0and retry?
Might be you have to adjust your format string to avoid <, > and : characters.
Regards,
Tycho

RMAN-06010: error while looking up datafile: 82

Iam building dataguard - Physical Standby database by using the RMAN duplicate command and we are not using the recovery catalog but control file.
Iam getting the following error while running the duplicate command.
set newname for datafile 82 to
"/dflx02/flx/o01flx3rbs/rbs02_02.O01FLX3";
RMAN-06010: error while looking up datafile: 82
Actually we dropped the datafile(tablespace) before taken the backup but it is giving error though we are using the latest control file.
I do not see this file is available in the database as we dropped it successfully.
Could some one let me know what could be the problem and how to resolve it.
Your early response is greatly appreciated.
Note:
backup script -- It went successfully.
# Script to be used to backup the production in preparation of creating a DataGuard instance
YYYY=`date +"%Y"`
mmdd=`date +"%m%d"`
hh=`date +"%H"`
mm=`date +"%M"`
ss=`date +"%S"`
hhmmss=${hh}${mm}${ss}
dt=${YYYY}${mmdd}_${hhmmss}
echo "Starting backup on O01FLX3"
$ORACLE_HOME/bin/rman nocatalog <<EOF >> /dflx02/flx/oracle/log/full_backup_run_$dt.log
connect target /
configure device type disk clear;
configure channel device type disk maxpiecesize 4G;
configure device type disk backup type to compressed backupset parallelism 8;
run{
change archivelog all validate;
backup current controlfile for standby format '/tmp/stby_snapcf_O01FLX3.f';
backup database format '/dflx02/flx/o01flx3dump/rman/O01FLX3_%s_%p_%T_%t.bak';
sql 'alter system archive log current';
backup archivelog all format '/dflx02/flx/o01flx3dump/rman/O01FLX3_%s_%p_%T_%t.arc';
EXIT
EOF
duplicate Script:
#!/bin/ksh
# Script to create standby database for production.
YYYY=`date +"%Y"`
mmdd=`date +"%m%d"`
hh=`date +"%H"`
mm=`date +"%M"`
ss=`date +"%S"`
hhmmss=${hh}${mm}${ss}
dt=${YYYY}${mmdd}_${hhmmss}
echo "Starting dataguard instance on O01FLX3DR"
$ORACLE_HOME/bin/rman nocatalog <<EOF >> /dflx02/flx/oracle/log/cr_stdby_O01FLX3$dt.log
connect target /
connect auxiliary sys/xxxxxx@O01FLX3DR
configure channel device type disk maxpiecesize 4G;
configure device type disk backup type to compressed backupset parallelism 8;
run {
set until time "to_date('20080217:19:00', 'YYYYMMDD:HH24:MI')";
duplicate target database for standby dorecover nofilenamecheck;
exit;
EOF
set newname for datafile 82 to
"/dflx02/flx/o01flx3rbs/rbs02_02.O01FLX3";

Thank you for your reply. Actually Iam not renaming the datafile but building the
dataguard instance and some how control file is looking for old datafile that was deleted.
Actually both primary and dataguard instances are running on 10.2.0.3 . Oracle control file is listing the datafile 82 as old deleted file, while building the dataguard.
---- This file was deleted long time back but still oracle control file is looking for this file while building the dataguard. Iam using the latest control file.
set newname for datafile 82 to
"/dflx02/flx/o01flx3rbs/rbs02_02.O01FLX3"
When I listed the datafile 82, it is showing the correct datafile.
RMAN> list backup of datafile 82;
List of Backup Sets
===================
BS Key Type LV Size Device Type Elapsed Time Completion Time
50234 Incr 2 26.93M DISK 00:04:03 18-FEB-08
BP Key: 101470 Status: AVAILABLE Compressed: YES Tag: DATABASE_BACKUP
Piece Name: /dflx02/flx/o01flx3dump/rman/O01FLX3_51757_1_20080218_647031779.bak
List of Datafiles in backup set 50234
File LV Type Ckp SCN Ckp Time Name
82 2 Incr 7953177017970 18-FEB-08 /dflx02/flx/o01flx3ndx15/flx_ndx3_18.O01FLX3
BS Key Type LV Size Device Type Elapsed Time Completion Time
50334 Incr 2 27.76M DISK 00:04:16 19-FEB-08
BP Key: 101587 Status: AVAILABLE Compressed: YES Tag: DATABASE_BACKUP
Piece Name: /dflx02/flx/o01flx3dump/rman/O01FLX3_51857_1_20080219_647119328.bak
List of Datafiles in backup set 50334
File LV Type Ckp SCN Ckp Time Name
82 2 Incr 7953257549488 19-FEB-08 /dflx02/flx/o01flx3ndx15/flx_ndx3_18.O01FLX3
So Iam thinking that there should be a problem in control file and let me know how to resolve it.
Please let me know if you have any questions.
Thanks for your help.
Suresh.D

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 duplicate errors

Hi:
I was doing a 11g database clone on linux using rman duplicate. After runing 40min, it stopped and got the following errors. All the file permission are the same 777, one third of files have been copied.
ORA-27041: unable to open file
Linux-x86_64 Error: 13: Permission denied
Additional information: 9
failover to previous backup
released channel: aux1
released channel: aux2
released channel: aux3
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 05/30/2012 08:28:07
RMAN-05501: aborting duplication of target database
RMAN-03015: error occurred in stored script Memory Script
RMAN-20506: no backup of archived log found
RMAN-06053: unable to perform media recovery because of missing log
RMAN-06025: no backup of archived log for thread 1 with sequence 12312 and starting SCN of 23167256063 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 12311 and starting SCN of 23167250994 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 12310 and starting SCN of 23167245674 found to restore
Thanks and regards.

Files from source database:
-rwxrwSrwx 1 root root 48653824 May 29 20:57 db_t784587134_s1208_p1
-rwxrwSrwx 1 root root 48594944 May 29 20:57 db_t784587149_s1209_p1
-rwxrwSrwx 1 root root 7761920 May 29 20:57 db_t784587150_s1210_p1
-rwxrwSrwx 1 root root 4062945280 May 29 21:23 db_t784587170_s1211_p1
-rwxrwSrwx 1 root root 1124147200 May 29 21:07 db_t784587170_s1212_p1
-rwxrwSrwx 1 root root 2049015808 May 29 21:16 db_t784587725_s1213_p1
-rwxrwSrwx 1 root root 4012630016 May 29 21:36 db_t784588310_s1214_p1
-rwxrwSrwx 1 root root 4620419072 May 29 21:43 db_t784588726_s1215_p1
-rwxrwSrwx 1 root root 3724255232 May 29 21:52 db_t784589461_s1216_p1
-rwxrwSrwx 1 root root 1818624 May 29 21:43 db_t784589896_s1217_p1
-rwxrwSrwx 1 root root 2071040 May 29 21:52 db_t784590427_s1218_p1
There are about 30 dbf files on source database, 10 dbf files on target database now.

RMAN Clone Errors

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

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

RMAN 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 error in UNIX

Similar Messages

Maybe you are looking for