RMAN command

Hi
RUN {
2>     BACKUP AS BACKUPSET
3>     FORMAT '/u01/db01/backup/%d_%s_%p'
4> DURATION 10:00 MINIMIZE LOAD
5>     (DATABASE);
6>     SQL 'alter system archive log current';
7>}
Can anybody explain me what is meaning of ' DURATION 10:00 MINIMIZE LOAD' from the above script

Hello,
The DURATION clause limit the time for the BACKUP.
You may be carefull when using this clause, the BACKUP could be stopped before being completed:
http://www.oracle-base.com/articles/10g/RMANEnhancements10g.php#managing_backup_duration_and_throttling
So, here the duration of the BACKUP is limited to 10 hours. If you start the BACKUP at 10 PM it should finish before 8 AM to complete, else it will be interrupted and you'll have an error message.
Hope this help.
Best regards,
Jean-Valentin
Edited by: Lubiez Jean-Valentin on Apr 23, 2011 8:12 AM

Similar Messages

Why it automatically recover current redo log in RMAN command window?

Firstly, I restore controlfile and datafiles from a backupset.
Then when I recover database in RMAN command window like below:
RMAN> recover database;
Starting recover at 15-AUG-13
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=156 devtype=DISK
starting media recovery
archive log thread 1 sequence 9 is already on disk as file /u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_9_90sd0slz_.arc
archive log thread 1 sequence 10 is already on disk as file
/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_10_90sd0tsb_.arc
archive log thread 1 sequence 11 is already on disk as file
/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_11_90sd110b_.arc
archive log thread 1 sequence 12 is already on disk as file
/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_12_90sd2ksr_.arc
archive log thread 1 sequence 13 is already on disk as file
/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_13_90sd2mc6_.arc
archive log thread 1 sequence 14 is already on disk as file
/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_14_90sd2qrm_.arc
archive log thread 1 sequence 15 is already on disk as file
/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_15_90sd2s0w_.arc
archive log thread 1 sequence 16 is already on disk as file /u01/app/oracle/oradata/lonion/redo03.log
archive log filename=/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_9_90sd0slz_.arc thread=1 sequence=9
archive log filename=/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_10_90sd0tsb_.arc thread=1 sequence=10
archive log filename=/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_11_90sd110b_.arc thread=1 sequence=11
archive log filename=/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_12_90sd2ksr_.arc thread=1 sequence=12
archive log filename=/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_13_90sd2mc6_.arc thread=1 sequence=13
archive log filename=/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_14_90sd2qrm_.arc thread=1 sequence=14
archive log filename=/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_15_90sd2s0w_.arc thread=1 sequence=15
archive log filename=/u01/app/oracle/oradata/lonion/redo03.log thread=1 sequence=16
media recovery complete, elapsed time: 00:00:04
Finished recover at 15-AUG-13
RMAN>
But, when I recover database in SQL*Plus command window like below:
[oracle@lonion ~]$ uniread sqlplus /nolog
[uniread] Loaded history (2178 lines)
SQL*Plus: Release 10.2.0.1.0 - Production on Thu Aug 15 19:25:38 2013
Copyright (c) 1982, 2005, Oracle. All rights reserved.
SQL> conn /as sysdba
Connected.
SQL>
SQL> recover database;
ORA-00283: recovery session canceled due to errors
ORA-01610: recovery using the BACKUP CONTROLFILE option must be done
SQL> recover database using backup controlfile;
ORA-00279: change 2147842454 generated at 08/15/2013 18:34:28 needed for thread
1
ORA-00289: suggestion :
/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_9_%u_.a
rc
ORA-00280: change 2147842454 for thread 1 is in sequence #9
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
auto
ORA-00279: change 2147842651 generated at 08/15/2013 18:40:25 needed for thread
1
ORA-00289: suggestion :
/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_10_%u_.
arc
ORA-00280: change 2147842651 for thread 1 is in sequence #10
ORA-00278: log file
'/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_9_90sd
0slz_.arc' no longer needed for this recovery
ORA-00279: change 2147842653 generated at 08/15/2013 18:40:26 needed for thread
1
ORA-00289: suggestion :
/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_11_%u_.
arc
ORA-00280: change 2147842653 for thread 1 is in sequence #11
ORA-00278: log file
'/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_10_90s
d0tsb_.arc' no longer needed for this recovery
ORA-00279: change 2147842656 generated at 08/15/2013 18:40:32 needed for thread
1
ORA-00289: suggestion :
/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_12_%u_.
arc
ORA-00280: change 2147842656 for thread 1 is in sequence #12
ORA-00278: log file
'/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_11_90s
d110b_.arc' no longer needed for this recovery
ORA-00279: change 2147842684 generated at 08/15/2013 18:41:21 needed for thread
1
ORA-00289: suggestion :
/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_13_%u_.
arc
ORA-00280: change 2147842684 for thread 1 is in sequence #13
ORA-00278: log file
'/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_12_90s
d2ksr_.arc' no longer needed for this recovery
ORA-00279: change 2147842686 generated at 08/15/2013 18:41:23 needed for thread
1
ORA-00289: suggestion :
/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_14_%u_.
arc
ORA-00280: change 2147842686 for thread 1 is in sequence #14
ORA-00278: log file
'/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_13_90s
d2mc6_.arc' no longer needed for this recovery
ORA-00279: change 2147842689 generated at 08/15/2013 18:41:27 needed for thread
1
ORA-00289: suggestion :
/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_15_%u_.
arc
ORA-00280: change 2147842689 for thread 1 is in sequence #15
ORA-00278: log file
'/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_14_90s
d2qrm_.arc' no longer needed for this recovery
ORA-00279: change 2147842691 generated at 08/15/2013 18:41:28 needed for thread
1
ORA-00289: suggestion :
/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_16_%u_.
arc
ORA-00280: change 2147842691 for thread 1 is in sequence #16
ORA-00278: log file
'/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_15_90s
g0or9_.arc' no longer needed for this recovery
ORA-00279: change 2147842986 generated at 08/15/2013 19:14:29 needed for thread
1
ORA-00289: suggestion :
/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_17_%u_.
arc
ORA-00280: change 2147842986 for thread 1 is in sequence #17
ORA-00278: log file
'/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_16_90s
g0os5_.arc' no longer needed for this recovery
ORA-00308: cannot open archived log
'/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_17_%u_
.arc'
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3
SQL> recover database using backup controlfile;
ORA-00279: change 2147842986 generated at 08/15/2013 19:14:29 needed for thread
1
ORA-00289: suggestion :
/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_17_%u_.
arc
ORA-00280: change 2147842986 for thread 1 is in sequence #17
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
/u01/app/oracle/oradata/lonion/redo01.log ---- Yon see, proceeding this process, it can't automatically apply the current redo log.
Log applied.
Media recovery complete.
SQL>
Question Coming:
Now, my question is that 「Why it automatically recover current redo log in RMAN command window but not in SQL*Plus」?
BTW: Please pay attention to the red font.

It also seems not work.
SQL> recover automatic database using backup controlfile;
ORA-00279: change 2148632889 generated at 09/26/2013 12:45:22 needed for thread
1
ORA-00289: suggestion :
/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_09_26/o1_mf_1_48_%u_.
arc
ORA-00280: change 2148632889 for thread 1 is in sequence #48
ORA-00278: log file
'/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_09_26/o1_mf_1_48_%u_
.arc' no longer needed for this recovery
ORA-00308: cannot open archived log
'/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_09_26/o1_mf_1_48_%u_
.arc'
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
auto
ORA-00308: cannot open archived log
'/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_09_26/o1_mf_1_48_%u_
.arc'
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3
ORA-00308: cannot open archived log
'/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_09_26/o1_mf_1_48_%u_
.arc'
ORA-27037: unable to obtain file status
Linux Error: 2: No such file
or directory
Additional information: 3
SQL>
It must specify the redo log.
SQL> recover database using backup controlfile;
ORA-00279: change 2148632889 generated at 09/26/2013 12:45:22 needed for thread
1
ORA-00289: suggestion :
/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_09_26/o1_mf_1_48_%u_.
arc
ORA-00280: change 2148632889 for thread 1 is in sequence #48
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
/u01/app/oracle/oradata/lonion/redo02.log
Log applied.
Media recovery complete.
SQL>

Using environment variables in RMAN command line

I'm running Oracle 11gR2 and working in a Solaris 10 environment.
I am trying to run the rman command by connecting to the target, auxiliary, and catalog by catting out the contents of password files where I have my connect strings stored for each database. Also in there I am trying to use environment variables to reference each database.
rman target "`cat ${HOME}/password_dir/prod_connect.txt`@${PROD_DB}" auxiliary "`cat ${HOME}/password_dir/stage_connect.txt`@`${STAGE_DB}`" catalog "`cat ${HOME}/password_dir/rman_catalog_connect.txt`@${RMAN_CATALOG_DB}"
The end result I need is:
rman target "username/password@db" auxiliary "username/password@db" catalog "username/password@db"
Is this possible?

Levi,
Good idea on the variables. I set up a variable with my connect string including the TNS reference (i.e. user/password@XXX)
So when I run this:
rman auxiliary ${AUXILIARY}
I get this:
Recovery Manager: Release 11.2.0.2.0 - Production on Wed Jun 13 10:19:44 2012
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-04006: error from auxiliary database: ORA-01031: insufficient privileges
But if I try to run it without the TNS entry it works. The only issue with that is I need the TNS reference to connect to the database I'm cloning from. Any idea what's going on here?
Also, the same applies to the TARGET, but oddly enough not the CATALOG. It will connect to my rman catalog using the TNS just fine. The only difference is with the catalog I'm logging in as my rman catalog user. With the TARGET and AUXILIARY I'm logging in as the system user.
Edited by: Nevin on Jun 13, 2012 8:25 AM

RMAN command in Oracle VSS Writer for incremental/differential restore

Hello
Working on application to support incermental/differential backup via VSS ( Oracle VSS Writer )
Accoding to documentation about [Performing Database Backup and Recovery with VSS |http://docs.oracle.com/cd/E11882_01/win.112/e10845/vss.htm]
Oracle VSS Writer does not perform default recovery of Archived redo log or flash recovery component. (This component is defined to contain only log or incremental files)
Nevertheless, the requestor application can invoke required RMAN commands.
What RMAN command is needed to be performed for incermental logs recovery? (This command is set in VssBackupComponents::SetRestoreOptions call and will be performed on PostRertore Phase by Writer)
I have tried RESTORE ARCHIVELOG ALL but did not succeeded .
Thanks

Let we describe my oracle VSS backup/restore proccess in details
Succeeded with full backup/restore only, but failed to to implement differential one.
Oracle VSS Writer support only three components for explicit selection for backup: Oracle Database and it sub-component: Flash Recovery Area/ArchivedLogs.
For full backup stage I explicitly select these components
Why not only Oracle database as ancestor of Flash Recovery Area/ArchivedLogs?
As oracle vss writer uses time stamp mechanism for incremental and differential backups,
I select all these components for full backup stage (to get previous timestamps for Flash Recovery Area/ArchivedLogs on differential backup phase. With explicit selection these components its timestamps will be added to backup component document. )
On diferential backup phase I select Flash Recovery Area/ArchivedLogs only using previous backup stamp(SetPreviousBackupStamp call), loaded from previous backup component document.
Restore perform sequentially:
1. Restore data from full backup phase (select all these three components for Restore), but do SetAdditionalRestore(true) for OracleDatabase component to avoid bringing Oracle database only after full restore phase
2. Restore data from differential phase (select Flash Recovery Area/ArchivedLogs for Restore only( even can't select Database as there is no record in backup component document about it on differential phase backup) and call SetAdditionalRestore(false) for these components
As Oracle Writer does not perform default recovery of this component. Nevertheless, the requester application can run required RMAN commands(via setRestoreOptions VSS call). I tried as RECOVER DATABASE as RESTORE ARCHIVELOG ALL commands , but failed to restore database.
If I restore full backup phase(without differential) only and call SetAdditionalRestore(false) for Oracle Database component, Oracle VSS writer restores data successfully and mount database.
How to restore differential part?

How to hide RMAN command line args from "ps -ef" command?

Hi there
This is not RMAN question per say but it is related to my RMAN script. Part of this RMAN script is below:
rman target / catalog ${RMANID}/${RMANPW}@${RMANSID} log=${TMPFILE} << EOF
While the script is running, if I issue "ps -ef | grep rman" command (from my own user id or as 'oracle' user), I see following:
oracle 32522 32492 36 15:32 pts/1
00:00:01 rman target / catalog rman/rman2013@rmancat log=/tmp/oratmp32492
Is there a way to hide the values of the variables (Id, Pwd, SID) from the "ps -ef" command?
If not, any other an alternates?
Best regards

How to Hide RMAN Passwords when Connecting to a Target Database (Doc ID 183377.1)
How To Hide Usernames And Passwords In RMAN Logfile (Doc ID 246192.1)

Rman command to validate the backupsets are recoverable

Hi,
I'm using 9iR2 rman/controlfile to do the fullbackup. The DB is in archivelog mode. And my fullbackup includes both DB and archivelog file with input delete. What is/are the rman command that I can use to make sure the full backupset are OK in case I need to do recovery? I got no result from following 2 commands. Is it enough? Thanks.
report unrecoverable;
report need backup;

Check the RETENTION POLICY. According to the retention policy RMAN will maintain the backup copy.
REPORT OBSOLETE command will list you which are the backup set we can delete it.
DELETE OBSOLETE
Deletes the backups and copies that are obsolete (that is, "not needed") under the configured retention policy. Alternatively, use REDUNDANCY and RECOVERY WINDOW parameters to specify criteria.

Delete all AVAILABLE valid RMAN backup by RMAN command

Hi
We are taking RMAN full backup on disk every day. But right now we don’t have enough space on RMAN backup mount point. So we want to delete all AVAILABLE valid RMAN backup by RMAN command.
Please guide to delete all AVAILABLE valid RMAN backup by RMAN command.
-Thanks
Edited by: Fazlul Kabir Mahfuz on May 13, 2013 11:06 AM

You can do it by manually delete the backups and archivelogs from OS location. Then use below commands
RMAN>crosscheck backup;
It will give status as EXPIRED for backups which are valid but not available at OS level.
RMAN>delete expired backup;
Delete all the backups whose status are EXPIRED from database level.
Similarly for archivelogs
RMAN>crosscheck archivelog all;
RMAN>delete expired archivelog all;

Restore controlfile without RMAN Command

Hii..!! RMAN Experts ..
I have a RMAN Backup of my production database , Accidentally controlfile, datafiles, and redolog filies are lost .
Important thing is : I want to Restore Controlfile Without RMAN Commands ...
Is this possible,? If Yes How ??
Please get me out of this Doubt., & provide me detail steps
Will be very much thankful to you...

937382 wrote:
Hii..!! RMAN Experts ..
I have a RMAN Backup of my production database , Accidentally controlfile, datafiles, and redolog filies are lost .
Important thing is : I want to Restore Controlfile Without RMAN Commands ...
Is this possible,? If Yes How ??
Please get me out of this Doubt., & provide me detail steps
Will be very much thankful to you...In an emergency situation, you can try using the SNAPSHOT CONTROLFILE.
Oracle is very clear on this point and says that this file should not be used for any purpose, but breaking this rule, we can have success and bring a consistent controlfile.
The snapshot control file is a copy of a database control file created in an operating system-specific location by RMAN. RMAN creates the snapshot control file so that it has a consistent version of a control file to use when either resynchronizing the recovery catalog or backing up the control file.
The Default Location of SNAPSHOT CONTROLFILE is $ORACLE_HOME/dbs/snapcf_<DB_NAME>.f
If we recently used RMAN most recent controlfile will be my SNAPSHOT CONTROLFILE.
See this example:
SQL> create pfile='/home/oracle/spfile.txt' from spfile;
SQL> !
oracle@aix:/home/oracle> cp /u01/app/oracle/product/11.2.0/dbhome_11203/dbs/snapcf_dbtst.f /home/oracle/control.ora
oracle@aix:/home/oracle> vi spfile.txt
"spfile.txt" 27 lines, 957 characters
*.control_files='/home/oracle/control.ora' ## Change this line
SQL> startup mount pfile ='/home/oracle/spfile.txt'
ORACLE instance started.
Total System Global Area 768294912 bytes
Fixed Size                  2225448 bytes
Variable Size             293604056 bytes
Database Buffers          465567744 bytes
Redo Buffers                6897664 bytes
Database mounted.
SQL> alter database open;
alter database open
ERROR at line 1:
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
### We can open reseting log if you have all datafiles restored.
### Or you can use RMAN command to restore your database from Controlfile Catalog.
### Also you can generate a command to create a new controlfile
SQL> alter database backup controlfile to trace;Regards,
Levi Pereira

How to pass parameter to RMAN command?

Hi,
When i am execute delete.sh file. the following error coming. it expecting to pass parameter YES or NO.
How I can pass parameter to RMAN command in shell scripts.
[oracle@dbNode1 rman]$ sh delete.sh
Executing Command : Backup as copy to file system
Recovery Manager: Release 10.2.0.3.0 - Production on Mon Apr 20 12:13:18 2009
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: HERMESQA (DBID=3819666523)
connected to recovery catalog database
RMAN> 2> 3>
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=135 devtype=DISK
List of Backup Pieces
BP Key BS Key Pc# Cp# Status Device Type Piece Name
98 96 1 1 AVAILABLE DISK /u01/app/oracle/flash_recovery_area/HERMESQA/backupset/2009_03_17/o1_mf_ncnnf_TAG20090317T180639_4vz6bqkl_.bkp
Do you really want to delete the above objects (enter YES or NO)?
Error occurred getting response - assuming NO response
thanks
settu gopal

Use
DELETE NOPROMPT - then no questions will be asked.

Taking tablespace offline through RMAN command line

I am taking a Oracle 9i Backup and Recovery class. One of the hands-on assignments is to simulate a lost datafile. The instructions say to shut down the database through RMAN, delete the INDX01.dbf datafile through my operating system, mount the database, take the INDX tablespace offline, open the database, recover the INDX01.dbf datafile, and then place the INDX tablespace online again.
My problem is that when I issue the command (in RMAN) to take the INDX tablespace offline (remember, database is mounted), I get an error saying the database is not open. The command I am issuing through RMAN is this: >sql 'ALTER TABLESPACE INDX OFFLINE IMMEDIATE'; I can't get any further because of the error message that my database is not open. Is my instruction book wrong in that I can't take the tablespace offline if the database is in a mounted state? Does the database have to be open to do this?

4. Mount the database and take the tablespace corresponding to Indx01.dbf data file offline.There could be a misunderstanding about the command to be used. ALTER TABLESPACE command needs an open DB to work, but you can use
RMAN> sql 'alter database datafile <file name or file number> offline drop';
that will work with DB in mount state. See this example :
RMAN> startup mount
connected to target database (not started)
Oracle instance started
database mounted
Total System Global Area     130023424 bytes
Fixed Size                     1218100 bytes
Variable Size                104860108 bytes
Database Buffers              20971520 bytes
Redo Buffers                   2973696 bytes
RMAN> sql 'alter tablespace test offline immediate';
sql statement: alter tablespace test offline immediate
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of sql command on default channel at 05/21/2006 18:51:06
RMAN-11003: failure during parse/execution of SQL statement: alter tablespace test offline immediate
ORA-01109: database not open
RMAN> sql 'alter database datafile 5 offline drop';
sql statement: alter database datafile 5 offline drop
RMAN> alter database open;
database opened
RMAN> restore datafile 5;
Starting restore at 21-MAY-06
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=145 devtype=DISK
channel ORA_DISK_1: starting datafile backupset restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
restoring datafile 00005 to
channel ORA_DISK_1: restore complete, elapsed time: 00:00:08
Finished restore at 21-MAY-06
RMAN> recover datafile 5;
Starting recover at 21-MAY-06
using channel ORA_DISK_1
starting media recovery
media recovery complete, elapsed time: 00:00:01
Finished recover at 21-MAY-06
RMAN> sql 'alter database datafile 5 online';
sql statement: alter database datafile 5 online
RMAN>

RMAN COMMANDS

Hi hussein,
I got these RMAN backup commands from someone's scripts (previous dba).
rman1.exe
========
#!/bin/sh
export ORACLE_SID=PROD
export ORACLE_HOME=/u02/oracle/PROD/db/tech_st/10.2.0
export PATH=$PATH:$ORACLE_HOME/bin
rman target / @/u05/RMAN/backup.cmd log=/u05/RMAN/backup.log
backup.cmd
=========
run {
     CONFIGURE CONTROLFILE AUTOBACKUP ON;
     CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/u05/RMAN/%F';
     backup format '/u05/RMAN/%d_LVL0_%T_%u_s%s_p%p' database;
     delete obsolete;
     }I think this is for RMAN 10g.
Will this script good for 9i and 11g?
What else is lacking in this script ? specifically in the "configure backup pamaters"?
Thanks a lot,
Ms Inday G

Here is my RMAN script:
DB0DB_RMAN_BKP.sh
#!/bin/ksh
# Name: DW0DB_RMAN_BKP.ksh
# Purpose : Full database RMAN backup of DW0DB Database
# Author : xxxxxxxxxxxxxxxxxxxx(its you)
# Created : SEP 02 2009
#Set the Environment
#Define Variables for the script
SCRIPT_TOP=<full path to scripts dir>
LOGDIR=<full path to log dir>
BKPDIR=<full path to backup dir>
LOGFILE=<logfilename>
# list the backups
echo ''
echo "List the existing backups in Backup directory" >> $LOGFILE
ls -ltr $BKPDIR >>$LOGFILE
# Now run the RMAN backup
echo ''
echo "Starting full backup of $ORACLE_SID at $RUNDATE " >> $LOGFILE
$RMAN target / no catalog @/home/oracle/DBA/JOBS/FULL_DW0DB_DISK_BKP.rman >> $LOGFILE
# Show size of the backup directory area after backup
echo ''
echo "Available space in Backup directory after backup" >> $LOGFILE
df -h $BKPDIR >> $LOGFILE
# list the backups there
echo ''
echo "List the backups in Backup directory" >> $LOGFILE
ls -ltr $BKPDIR >>$LOGFILE
## send an email
mail -s "RMAN backup completed" <mailid> < /fullpathtologfile/filename.log
##### end of script###############################################
cat FULL_DW0DB_DISK_BKP.rman
run {
allocate channel c1 type disk;
allocate channel c2 type disk;
backup database
tag DW0DB_FULLBKP
format '/bkp/RMAN/DW0DB_BKP/DW0DB_set%s_piece%p_%T_%U'
filesperset 10;
CROSSCHECK BACKUP OF DATABASE;
sql 'alter system switch logfile';
sql 'alter system switch logfile';
sql 'alter system switch logfile';
crosscheck archivelog all;
backup archivelog all
tag DW0DB_ARCHBKP
format '/bkp/RMAN/DW0DB_BKP/ARCH_DW0DB_set%s_piece%p_%T_%U'
filesperset 20;
backup
format '/bkp/RMAN/DW0DB_BKP/DW0DB_ctl_%U'
current controlfile;
release channel c1;
release channel c2;
cat DB0DB_RMAN_ARCH_BKP.sh
#!/bin/ksh
# Name: DW0DB_RMAN_ARCH_BKP.ksh
# Purpose : Archivelog backup of DW0DB Database
# Author : its you
# Created : SEP 02 2009
#Set the Environment
#Define Variables for the script
SCRIPT_TOP=<full path to scripts dir>
LOGDIR=<full path to log dir>
BKPDIR=<full path to backup dir>
LOGFILE=<logfilename>
# list the backups
echo ''
echo "List the existing backups in Backup directory" >> $LOGFILE
ls -ltr $BKPDIR >>$LOGFILE
# Now run the RMAN backup
echo ''
echo "Starting archivelog backup of $ORACLE_SID at $RUNDATE " >> $LOGFILE
$RMAN target / no catalog @/home/oracle/DBA/JOBS/DW0DB_RMAN_ARCH.rman >> $LOGFILE
# Show size of the backup directory area after backup
echo ''
echo "Available space in Backup directory after backup" >> $LOGFILE
df -h $BKPDIR >> $LOGFILE
# list the backups there
echo ''
echo "List the backups in Backup directory" >> $LOGFILE
ls -ltr $BKPDIR >>$LOGFILE
## send an email
mail -s "RMAN backup completed" <mailid> < /fullpathtologfile/filename.log
##### end of script###############################################
cat DW0DB_RMAN_ARCH.rman
run {
allocate channel c1 type disk;
allocate channel c2 type disk;
sql 'alter system switch logfile';
sql 'alter system switch logfile';
sql 'alter system switch logfile';
crosscheck archivelog all;
backup archivelog all
tag DW0DB_FULLBKP
format '/bkp/RMAN/DW0DB_BKP/ARCH_DW0DB_set%s_piece%p_%T_%U'
filesperset 20;
release channel c1;
release channel c2;
}

RMAN command issue

this following command works fine in RMAN
RMAN> run{
2> set until time "to_date('27-NOV-2013 11:05:00,'DD-MON-YYYY HH24:MI:SS')";
3> }
executing command: SET until clause
but the following command fails :
RMAN> run{
2> set until time "to_date('27-NOV-2013 11:05:00,'DD-MON-YYYY HH24:MI:SS')";
3> restore database;
4> }
executing command: SET until clause
Starting restore at 27-nov-2013 13:53:47
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 11/27/2013 13:53:47
ORA-01756: quoted string not properly terminated
can someone tell me why ?
thanks

another single quote is needed like below
set until time "to_date('27-NOV-2013 11:05:00','DD-MON-YYYY HH24:MI:SS')";

Rman command fails with "RMAN-00554: initialization of internal RMAN"

Hi
I am at cross roads with no direction. 2 things and most like cause for the issue is same
1)rman target rman1/rman1@ppmqa
Recovery Manager: Release 11.2.0.1.0 - Production on Thu Dec 16 10:34:46 2010
Copyright (c) 1982, 2009, Oracle and/or its affiliates. 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
2) sqlnet userid/passwd@db1 "/as sysdba" works some times and fails with insufficient privileges" some times
ppmqa1 10:24 AM sqrac202a:/oracle/base/diag/tnslsnr/sqrac202a/listener/trace > sqlplus rman1/rman1@ppmqa1 "as sysdba"
SQL*Plus: Release 11.2.0.1.0 Production on Thu Dec 16 10:24:55 2010
Copyright (c) 1982, 2009, Oracle. All rights reserved.
ERROR:
ORA-01031: insufficient privileges
ppmqa1 10:24 AM sqrac202a:/oracle/base/diag/tnslsnr/sqrac202a/listener/trace > sqlplus rman1/rman1@ppmqa1 "as sysdba"
SQL*Plus: Release 11.2.0.1.0 Production on Thu Dec 16 10:24:57 2010
Copyright (c) 1982, 2009, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,
Data Mining and Real Application Testing options
SQL>
Information on environment and let me know if you need or know any more details... thanks in advance.
CRS Version 11201 and so DB
current parameters:
SQL> show parameter remote
NAME TYPE VALUE
remote_dependencies_mode string TIMESTAMP
remote_listener string sqrac202-scan.frxntnyc.frx2.co
m:1521
remote_login_passwordfile string EXCLUSIVE
remote_os_authent boolean FALSE
remote_os_roles boolean FALSE
result_cache_remote_expiration integer 0
SQL> select * from v$pwfile_users
USERNAME SYSDB SYSOP SYSAS
SYS TRUE TRUE FALSE
RMAN1 TRUE TRUE FALSE
sqlnet.ora from GRID Home
NAMES.DIRECTORY_PATH= (TNSNAMES, EZCONNECT)
ADR_BASE = /oracle/base
#################################

I found solution just now, this is very simple i was not aware this but this is how it working
Hope this helps
I granted sysdba from node A but not from node B, thinking that if you grant any privilege at instance level that is applicable to db level but that is not the case with sysdba privs
so i need to grant it from both nodes A and B.
here is the output
test case
initially no entry for instance 2
1) select * from gv$pwfile_users;
INST_ID USERNAME SYSDB SYSOP SYSAS
2 SYS TRUE TRUE FALSE
1 SYS TRUE TRUE FALSE
1 RMAN1 TRUE TRUE FALSE
2) grant sysdba to rman1 -- this I did at NODE B or instance 2
3) SQL> select * from gv$pwfile_users;
INST_ID USERNAME SYSDB SYSOP SYSAS
2 SYS TRUE TRUE FALSE
2 RMAN1 TRUE FALSE FALSE
1 SYS TRUE TRUE FALSE
1 RMAN1 TRUE TRUE FALSE
4) I am able to connect remotely
C:\Documents and Settings\kthoka> sqlplus rman1/rman1@ppmqa "as sysdba"
SQL*Plus: Release 10.2.0.3.0 - Production on Thu Dec 16 13:59:20 2010
Copyright (c) 1982, 2006, Oracle. All Rights Reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, Real Application Clusters, Automatic Storage Management
OLAP,
Data Mining and Real Application Testing options
SQL> select instance_name from v$instance;
INSTANCE_NAME
ppmqa2
5) rman also working fine
ppmqa 03:00 PM sqrac202a:/oracle/NSQ/112_64/dbs > rman target rman1/rman1@ppmqa
Recovery Manager: Release 11.2.0.1.0 - Production on Thu Dec 16 15:00:32 2010
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: PPMQA (DBID=774170541)
RMAN> exit
Recovery Manager complete.

Difference between BACKUP RMAN commands

Hi Friends
Are there any difference between these 02 commands?
I mean, if I type "backup as compressed backupset database;" it will show me on v$rman_backup_job_details the input_type DB FULL.
If I type "backup as compressed backupset incremental level 0 database;" it shows me DB INC.
My doubt is:
Proceeding with "backup as compressed backupset database" makes a level 0 backup to be used with "backup as compressed backupset incremental level 1 database;" ????
Or I must proceed with the command incremental level 0 to use it with future level1 operations?
I'm running 11.2.0.3.0 on Windows Server
Tks

KeenOnOracle wrote:
Hi Friends
Are there any difference between these 02 commands?
I mean, if I type "backup as compressed backupset database;" it will show me on v$rman_backup_job_details the input_type DB FULL.
If I type "backup as compressed backupset incremental level 0 database;" it shows me DB INC.
My doubt is:
Proceeding with "backup as compressed backupset database" makes a level 0 backup to be used with "backup as compressed backupset incremental level 1 database;" ????
Or I must proceed with the command incremental level 0 to use it with future level1 operations?
A level 0 incremental backup, which is the base for subsequent incremental backups, copies all blocks containing data, backing the datafile up into a backup set just as a full backup would. The only difference between a level 0 incremental backup and a full backup is that a full backup is never included in an incremental strategy.

A possible bug in RMAN CATALOG command in 10g on Linux (SLES9 SP3)

Hi,
I ran into this issue while using RMAN command "CATALOG DATAFILECOPY <filename> TAG <tagname>". In this instance, RMAN is actually trying to write 8K data at block 1. Since a copy is being cataloged, it doen't make any sense to modify it. Please note that this modification doesn't happen without TAG option. This behavious doesn't seem to be present on Oracle 9 on Solaris 8. For more details, please check the following thread:
help with RMAN CATALOG command
Thanks,
Raghu.

Hi Steve,
Unfortunately this is a bug, bug 3612370 in fact. I've published the bug so that it can be tracked via metalink if you have a support contract.
The bug is as you suspected with JDev's parse of the modules. We don't have a workaround at the moment but I'll post here again if we make any progress.
Thanks for reporting this,
Geoff
JDev Test Team

RMAN command

Similar Messages

Maybe you are looking for