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

Similar Messages

Users priveleges who is able to edit the RMAN script in OEM

Hi
Can anyone help me, how to find the list of users who has privileges to change/edit the RMAN script in OEM?
Thanks

Hi,
I believe its required DBA privileges as well as OS level login credential to edit the job,
you can Query from dba_role_privs which user having DBA role assign, and find those user having OS level Credential.
HTH

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 in Solaris

Hi,
I am running Following rman script through shell in Solaris 10.2 to validate the database:
oracle@mtcetl # cat rman_validate.sh
#!/bin/bash
ORACLE_HOME=/u01/app/oracle/product/10g
PATH=$ORACLE_HOME/bin:$PATH
ORACLE_SID=mtcedwp
export ORACLE_HOME ORACLE_SID PATH
rman target / <<EOF
CONFIGURE DEVICE TYPE DISK PARALLELISM 8;
ALLOCATE CHANNEL d1 DEVICE TYPE DISK;
ALLOCATE CHANNEL d2 DEVICE TYPE DISK;
ALLOCATE CHANNEL d3 DEVICE TYPE DISK;
ALLOCATE CHANNEL d4 DEVICE TYPE DISK;
ALLOCATE CHANNEL d5 DEVICE TYPE DISK;
ALLOCATE CHANNEL d6 DEVICE TYPE DISK;
ALLOCATE CHANNEL d7 DEVICE TYPE DISK;
ALLOCATE CHANNEL d8 DEVICE TYPE DISK;
BACKUP VALIDATE DATABASE;
RELEASE CHANNEL d1;
RELEASE CHANNEL d2;
RELEASE CHANNEL d3;
RELEASE CHANNEL d4;
RELEASE CHANNEL d5;
RELEASE CHANNEL d6;
RELEASE CHANNEL d7;
RELEASE CHANNEL d8;
EOF
I am executing this script as follows:
oracle@mtcetl # nohup ./rman_validate.sh &
Then I receive following errors in the nohup.out file:
input datafile fno=00125 name=+MTCDATA_GRP/mtcedwp/datafile/atbi_tds.385.702198275
input datafile fno=00081 name=+MTCDATA_GRP/mtcedwp/datafile/atbi_tds.340.695129943
input datafile fno=00090 name=+MTCDATA_GRP/mtcedwp/datafile/atbi_tds.349.695475749
input datafile fno=00120 name=+MTCDATA_GRP/mtcedwp/datafile/atbi_ads.380.700249057
input datafile fno=00142 name=+MTCDATA_GRP/mtcedwp/datafile/atbi_tds.402.707084055
input datafile fno=00131 name=+MTCDATA_GRP/mtcedwp/datafile/atbi_ads.391.704194625
input datafile fno=00093 name=+MTCDATA_GRP/mtcedwp/datafile/atbi_ods1.352.696598449
input datafile fno=00099 name=+MTCDATA_GRP/mtcedwp/datafile/atbi_ods1.358.696598613
input datafile fno=00124 name=+MTCDATA_GRP/mtcedwp/datafile/atbi_ods1.384.700933397
input datafile fno=00070 name=+MTCDATA_GRP/mtcedwp/datafile/atbi_rds.329.676059403
input datafile fno=00111 name=+MTCDATA_GRP/mtcedwp/datafile/atbitdscdrpart.370.697290733
input datafile fno=00002 name=+MTCDATA_GRP/mtcedwp/datafile/undotbs1.261.654101459
input datafile fno=00071 name=+MTCDATA_GRP/mtcedwp/datafile/atbi_ods_sbscrbr_hist_jan07.330.680708683
input datafile fno=00072 name=+MTCDATA_GRP/mtcedwp/datafile/atbi_ods_sbscrbr_hist_jan07.331.680708755
input datafile fno=00008 name=+MTCDATA_GRP/mtcedwp/datafile/atbi_rpstry.268.654113363
input datafile fno=00051 name=+MTCDATA_GRP/mtcedwp/datafile/atbi_dds.310.662492431
input datafile fno=00067 name=+MTCDATA_GRP/mtcedwp/datafile/atbi_rds_tapin.326.667722723
channel ORA_DISK_8: starting compressed full datafile backupset
channel ORA_DISK_8: specifying datafile(s) in backupset
input datafile fno=00004 name=+MTCDATA_GRP/mtcedwp/datafile/users.264.654101503
input datafile fno=00146 name=+MTCDATA_GRP/mtcedwp/datafile/atbi_tds.406.707084307
input datafile fno=00084 name=+MTCDATA_GRP/mtcedwp/datafile/atbi_tds.343.695237005
input datafile fno=00075 name=+MTCDATA_GRP/mtcedwp/datafile/atbi_tds.334.695040959
input datafile fno=00080 name=+MTCDATA_GRP/mtcedwp/datafile/atbi_tds.339.695129765
input datafile fno=00153 name=+MTCDATA_GRP/mtcedwp/datafile/users.413.708271033
input datafile fno=00014 name=+MTCDATA_GRP/mtcedwp/datafile/atbi_ads.274.654113499
input datafile fno=00130 name=+MTCDATA_GRP/mtcedwp/datafile/atbi_ads.390.704194583
input datafile fno=00145 name=+MTCDATA_GRP/mtcedwp/datafile/atbi_tds.405.707084139
input datafile fno=00096 name=+MTCDATA_GRP/mtcedwp/datafile/atbi_ods1.355.696598533
input datafile fno=00149 name=+MTCDATA_GRP/mtcedwp/datafile/atbi_tds.409.707569511
input datafile fno=00106 name=+MTCDATA_GRP/mtcedwp/datafile/undotbs1.366.696693453
input datafile fno=00117 name=+MTCDATA_GRP/mtcedwp/datafile/atbitdscdrpart.377.697290949
input datafile fno=00016 name=+MTCDATA_GRP/mtcedwp/datafile/atbi_olap.276.654113543
input datafile fno=00013 name=+MTCDATA_GRP/mtcedwp/datafile/atbi_dds.273.654113489
input datafile fno=00035 name=+MTCDATA_GRP/mtcedwp/datafile/atbi_ads_indexes.295.654113845
input datafile fno=00064 name=+MTCDATA_GRP/mtcedwp/datafile/atbi_ads_tapout.323.667722723
input datafile fno=00126 name=+MTCDATA_GRP/mtcedwp/datafile/atbi_ads_tapout.386.701419275
input datafile fno=00134 name=+MTCDATA_GRP/mtcedwp/datafile/atbi_ads_tapout.394.704728861
input datafile fno=00055 name=+MTCDATA_GRP/mtcedwp/datafile/atbi_dds.314.662492689
channel ORA_DISK_1: backup set complete, elapsed time: 00:54:31
channel ORA_DISK_3: backup set complete, elapsed time: 01:10:07
channel ORA_DISK_2: backup set complete, elapsed time: 01:11:23
channel ORA_DISK_4: backup set complete, elapsed time: 01:12:08
channel ORA_DISK_6: backup set complete, elapsed time: 01:12:52
channel ORA_DISK_7: backup set complete, elapsed time: 01:12:52
channel ORA_DISK_8: backup set complete, elapsed time: 01:14:27
channel ORA_DISK_5: backup set complete, elapsed time: 01:30:23
Finished backup at 09-APR-10
RMAN>
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "identifier": expecting one of: ";"
RMAN-01008: the bad identifier was: d1
RMAN-01007: at line 1 column 17 file: standard input
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found ";": expecting one of: "allocate, alter, backup, beginline, blockrecover, catalog, change, connect, copy, convert, create, crosscheck, c
onfigure, duplicate, debug, delete, drop, exit, endinline, flashback, host, {, library, list, mount, open, print, quit, recover, register, release, replace, report, ren
ormalize, reset, restore, resync, rman, run, rpctest, set, setlimit, sql, switch, spool, startup, shutdown, send, show, test, transport, upgrade, unregister, validate"
RMAN-01007: at line 1 column 19 file: standard input
RMAN>
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "identifier": expecting one of: ";"
RMAN-01008: the bad identifier was: d2
RMAN-01007: at line 1 column 17 file: standard input
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found ";": expecting one of: "allocate, alter, backup, beginline, blockrecover, catalog, change, connect, copy, convert, create, crosscheck, c
onfigure, duplicate, debug, delete, drop, exit, endinline, flashback, host, {, library, list, mount, open, print, quit, recover, register, release, replace, report, ren
ormalize, reset, restore, resync, rman, run, rpctest, set, setlimit, sql, switch, spool, startup, shutdown, send, show, test, transport, upgrade, unregister, validate"
RMAN-01007: at line 1 column 19 file: standard input
RMAN>
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "identifier": expecting one of: ";"
RMAN-01008: the bad identifier was: d3
RMAN-01007: at line 1 column 17 file: standard input
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found ";": expecting one of: "allocate, alter, backup, beginline, blockrecover, catalog, change, connect, copy, convert, create, crosscheck, c
onfigure, duplicate, debug, delete, drop, exit, endinline, flashback, host, {, library, list, mount, open, print, quit, recover, register, release, replace, report, ren
ormalize, reset, restore, resync, rman, run, rpctest, set, setlimit, sql, switch, spool, startup, shutdown, send, show, test, transport, upgrade, unregister, validate"
RMAN-01007: at line 1 column 19 file: standard input
RMAN>
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "identifier": expecting one of: ";"
RMAN-01008: the bad identifier was: d4
RMAN-01007: at line 1 column 17 file: standard input
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found ";": expecting one of: "allocate, alter, backup, beginline, blockrecover, catalog, change, connect, copy, convert, create, crosscheck, c
onfigure, duplicate, debug, delete, drop, exit, endinline, flashback, host, {, library, list, mount, open, print, quit, recover, register, release, replace, report, ren
ormalize, reset, restore, resync, rman, run, rpctest, set, setlimit, sql, switch, spool, startup, shutdown, send, show, test, transport, upgrade, unregister, validate"
RMAN-01007: at line 1 column 19 file: standard input
RMAN>
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "identifier": expecting one of: ";"
RMAN-01008: the bad identifier was: d5
RMAN-01007: at line 1 column 17 file: standard input
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found ";": expecting one of: "allocate, alter, backup, beginline, blockrecover, catalog, change, connect, copy, convert, create, crosscheck, c
onfigure, duplicate, debug, delete, drop, exit, endinline, flashback, host, {, library, list, mount, open, print, quit, recover, register, release, replace, report, ren
ormalize, reset, restore, resync, rman, run, rpctest, set, setlimit, sql, switch, spool, startup, shutdown, send, show, test, transport, upgrade, unregister, validate"
RMAN-01007: at line 1 column 19 file: standard input
RMAN>
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "identifier": expecting one of: ";"
RMAN-01008: the bad identifier was: d6
RMAN-01007: at line 1 column 17 file: standard input
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found ";": expecting one of: "allocate, alter, backup, beginline, blockrecover, catalog, change, connect, copy, convert, create, crosscheck, c
onfigure, duplicate, debug, delete, drop, exit, endinline, flashback, host, {, library, list, mount, open, print, quit, recover, register, release, replace, report, ren
ormalize, reset, restore, resync, rman, run, rpctest, set, setlimit, sql, switch, spool, startup, shutdown, send, show, test, transport, upgrade, unregister, validate"
RMAN-01007: at line 1 column 19 file: standard input
RMAN>
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "identifier": expecting one of: ";"
RMAN-01008: the bad identifier was: d7
RMAN-01007: at line 1 column 17 file: standard input
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found ";": expecting one of: "allocate, alter, backup, beginline, blockrecover, catalog, change, connect, copy, convert, create, crosscheck, c
onfigure, duplicate, debug, delete, drop, exit, endinline, flashback, host, {, library, list, mount, open, print, quit, recover, register, release, replace, report, ren
ormalize, reset, restore, resync, rman, run, rpctest, set, setlimit, sql, switch, spool, startup, shutdown, send, show, test, transport, upgrade, unregister, validate"
RMAN-01007: at line 1 column 19 file: standard input
RMAN>
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "identifier": expecting one of: ";"
RMAN-01008: the bad identifier was: d8
RMAN-01007: at line 1 column 17 file: standard input
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found ";": expecting one of: "allocate, alter, backup, beginline, blockrecover, catalog, change, connect, copy, convert, create, crosscheck, c
onfigure, duplicate, debug, delete, drop, exit, endinline, flashback, host, {, library, list, mount, open, print, quit, recover, register, release, replace, report, ren
ormalize, reset, restore, resync, rman, run, rpctest, set, setlimit, sql, switch, spool, startup, shutdown, send, show, test, transport, upgrade, unregister, validate"
RMAN-01007: at line 1 column 19 file: standard input
RMAN>
Recovery Manager complete.
regards

Thanks for the help.
The command has finished now and I didn't get a chance to check the ps -ef command.
As you see in my original post, I am using nohup to run the script in the background and its sending its output to nohup.out file. But in the content of nohup.out file, there is no mention of report generated by RMAN regarding how many blocks it found. Output is as follows:
oracle@TEST # more nohup.out
Recovery Manager: Release 10.2.0.3.0 - Production on Sat Apr 10 10:45:28 2010
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: TEST (DBID=978723866)
RMAN> 2> 3> 4> 5> 6> 7> 8> 9> 10> 11> 12> 13> 14> 15> 16> 17> 18> 19> 20> 21>
using target database control file instead of recovery catalog
old RMAN configuration parameters:
CONFIGURE DEVICE TYPE DISK PARALLELISM 8 BACKUP TYPE TO COMPRESSED BACKUPSET;
new RMAN configuration parameters:
CONFIGURE DEVICE TYPE DISK PARALLELISM 8 BACKUP TYPE TO COMPRESSED BACKUPSET;
new RMAN configuration parameters are successfully stored
allocated channel: d1
channel d1: sid=208 devtype=DISK
allocated channel: d2
channel d2: sid=427 devtype=DISK
allocated channel: d3
channel d3: sid=198 devtype=DISK
allocated channel: d4
channel d4: sid=448 devtype=DISK
allocated channel: d5
channel d5: sid=127 devtype=DISK
allocated channel: d6
channel d6: sid=434 devtype=DISK
allocated channel: d7
channel d7: sid=143 devtype=DISK
allocated channel: d8
channel d8: sid=430 devtype=DISK
Starting backup at 10-APR-10
channel d1: starting compressed full datafile backupset
channel d1: specifying datafile(s) in backupset
input datafile fno=00108 name=+TEST_GRP/TEST/datafile/undotbs1.368.696699605
input datafile fno=00040 name=+TEST_GRP/TEST/datafile/TEST_tds.300.656367299
input datafile fno=00085 name=+TEST_GRP/TEST/datafile/TEST_tds.344.695237023
input datafile fno=00076 name=+TEST_GRP/TEST/datafile/TEST_tds.335.695041023
input datafile fno=00046 name=+TEST_GRP/TEST/datafile/TEST_tds.305.662491879
input datafile fno=00039 name=+TEST_GRP/TEST/datafile/TEST_ads.299.654710687
input datafile fno=00048 name=+TEST_GRP/TEST/datafile/TEST_ads.307.662492133
input datafile fno=00049 name=+TEST_GRP/TEST/datafile/TEST_ads.308.662492197
input datafile fno=00107 name=+TEST_GRP/TEST/datafile/undotbs1.367.696699507
input datafile fno=00098 name=+TEST_GRP/TEST/datafile/TEST_ods1.357.696598585
input datafile fno=00150 name=+TEST_GRP/TEST/datafile/TEST_tds.410.707569569
input datafile fno=00155 name=+TEST_GRP/TEST/datafile/TEST_ads.415.709551523
input datafile fno=00113 name=+TEST_GRP/TEST/datafile/TESTtdscdrpart.373.697290733
input datafile fno=00003 name=+TEST_GRP/TEST/datafile/sysaux.262.654101493
input datafile fno=00001 name=+TEST_GRP/TEST/datafile/system.260.654101443
input datafile fno=00010 name=+TEST_GRP/TEST/datafile/TEST_lds.270.654113411
channel d2: starting compressed full datafile backupset
channel d2: specifying datafile(s) in backupset
input datafile fno=00086 name=+TEST_GRP/TEST/datafile/TEST_tds.345.695237043
input datafile fno=00136 name=+TEST_GRP/TEST/datafile/TEST_tds.396.705247353
input datafile fno=00128 name=+TEST_GRP/TEST/datafile/TEST_tds.388.702478685
input datafile fno=00087 name=+TEST_GRP/TEST/datafile/TEST_tds.346.695237103
input datafile fno=00078 name=+TEST_GRP/TEST/datafile/TEST_tds.337.695129727
input datafile fno=00045 name=+TEST_GRP/TEST/datafile/TEST_tds.304.662491639
input datafile fno=00119 name=+TEST_GRP/TEST/datafile/TEST_ads.379.700249037
input datafile fno=00050 name=+TEST_GRP/TEST/datafile/TEST_ads.309.662492253
input datafile fno=00132 name=+TEST_GRP/TEST/datafile/TEST_ads.392.704194655
input datafile fno=00101 name=+TEST_GRP/TEST/datafile/TEST_ods1.360.696598703
input datafile fno=00097 name=+TEST_GRP/TEST/datafile/TEST_ods1.356.696598559
input datafile fno=00127 name=+TEST_GRP/TEST/datafile/TEST_ods1.387.701852257
input datafile fno=00077 name=+TEST_GRP/TEST/datafile/users.336.695041119
input datafile fno=00116 name=+TEST_GRP/TEST/datafile/TESTtdscdrpart.376.697290909
input datafile fno=00006 name=+TEST_GRP/TEST/datafile/owbindex.266.654113339
input datafile fno=00066 name=+TEST_GRP/TEST/datafile/TEST_rds_post_paid_cdr.325.667722723
input datafile fno=00068 name=+TEST_GRP/TEST/datafile/TEST_rds_tapout.327.667722823
input datafile fno=00109 name=+TEST_GRP/TEST/datafile/TEST_tds_user.372.696949827
input datafile fno=00110 name=+TEST_GRP/TEST/datafile/uat_users.371.697117641
input datafile fno=00033 name=+TEST_GRP/TEST/datafile/TEST_tds_indexes.293.654113827
channel d3: starting compressed full datafile backupset
channel d3: specifying datafile(s) in backupset
input datafile fno=00057 name=+TEST_GRP/TEST/datafile/undotbs1.365.696688443
input datafile fno=00140 name=+TEST_GRP/TEST/datafile/TEST_tds.400.707083997
input datafile fno=00083 name=+TEST_GRP/TEST/datafile/TEST_tds.342.695130467
input datafile fno=00074 name=+TEST_GRP/TEST/datafile/TEST_tds.333.695040881
input datafile fno=00079 name=+TEST_GRP/TEST/datafile/TEST_tds.338.695129749
input datafile fno=00152 name=+TEST_GRP/TEST/datafile/users.412.707602603
input datafile fno=00047 name=+TEST_GRP/TEST/datafile/TEST_ads.306.662492079
input datafile fno=00133 name=+TEST_GRP/TEST/datafile/TEST_ads.393.704194691
input datafile fno=00091 name=+TEST_GRP/TEST/datafile/TEST_ods1.350.696598015
input datafile fno=00100 name=+TEST_GRP/TEST/datafile/TEST_ods1.359.696598683
input datafile fno=00105 name=+TEST_GRP/TEST/datafile/TEST_ods1.364.696598825
input datafile fno=00012 name=+TEST_GRP/TEST/datafile/TEST_sds.272.654113455
input datafile fno=00069 name=+TEST_GRP/TEST/datafile/TEST_rds.328.676059355
input datafile fno=00115 name=+TEST_GRP/TEST/datafile/TESTtdscdrpart.375.697290875
input datafile fno=00118 name=+TEST_GRP/TEST/datafile/TEST_sds.378.698406119
input datafile fno=00059 name=+TEST_GRP/TEST/datafile/TEST_tds_post_paid_cdr.318.667722719
input datafile fno=00060 name=+TEST_GRP/TEST/datafile/TEST_ods_post_paid_cdr.319.667722719
input datafile fno=00061 name=+TEST_GRP/TEST/datafile/TEST_ods_tapout.320.667722721
input datafile fno=00062 name=+TEST_GRP/TEST/datafile/TEST_ods_tapin.321.667722721
input datafile fno=00063 name=+TEST_GRP/TEST/datafile/TEST_ads_post_paid_cdr.322.667722721
channel d4: starting compressed full datafile backupset
channel d4: specifying datafile(s) in backupset
input datafile fno=00154 name=+TEST_GRP/TEST/datafile/users.414.708271719
input datafile fno=00135 name=+TEST_GRP/TEST/datafile/TEST_tds.395.705247313
input datafile fno=00042 name=+TEST_GRP/TEST/datafile/TEST_tds.302.656520125
input datafile fno=00073 name=+TEST_GRP/TEST/datafile/TEST_tds.332.695040819
input datafile fno=00082 name=+TEST_GRP/TEST/datafile/TEST_tds.341.695130447
input datafile fno=00147 name=+TEST_GRP/TEST/datafile/TEST_tds.407.707084333
input datafile fno=00122 name=+TEST_GRP/TEST/datafile/TEST_ads.382.700249099
input datafile fno=00144 name=+TEST_GRP/TEST/datafile/TEST_tds.404.707084111
input datafile fno=00038 name=+TEST_GRP/TEST/datafile/TEST_ads.298.654710453
input datafile fno=00102 name=+TEST_GRP/TEST/datafile/TEST_ods1.361.696598723
input datafile fno=00094 name=+TEST_GRP/TEST/datafile/TEST_ods1.353.696598467
input datafile fno=00044 name=+TEST_GRP/TEST/datafile/undotbs1.271.696679255
input datafile fno=00015 name=+TEST_GRP/TEST/datafile/TEST_rds.275.654113509
input datafile fno=00065 name=+TEST_GRP/TEST/datafile/TEST_ads_tapin.324.667722723
input datafile fno=00031 name=+TEST_GRP/TEST/datafile/TEST_rds_dly_act_smry_jan07.291.654113807
input datafile fno=00032 name=+TEST_GRP/TEST/datafile/TEST_rds_dly_act_smry_maxval.292.654113817
input datafile fno=00036 name=+TEST_GRP/TEST/datafile/TEST_rds_indexes.296.654113879
input datafile fno=00037 name=+TEST_GRP/TEST/datafile/dbatemp.297.654113889
input datafile fno=00043 name=+TEST_GRP/TEST/datafile/TEST_ods_sbscrbr_hist.303.656530541
input datafile fno=00058 name=+TEST_GRP/TEST/datafile/TEST_tds_post_paid_src.317.667722667
channel d5: starting compressed full datafile backupset
channel d5: specifying datafile(s) in backupset
input datafile fno=00011 name=+TEST_GRP/TEST/datafile/dba_activity.316.696605947
input datafile fno=00104 name=+TEST_GRP/TEST/datafile/TEST_ods1.363.696598773
input datafile fno=00151 name=+TEST_GRP/TEST/datafile/TEST_ads.411.707569675
input datafile fno=00123 name=+TEST_GRP/TEST/datafile/TEST_ods1.383.700933365
input datafile fno=00056 name=+TEST_GRP/TEST/datafile/TEST_rds.315.662492837
input datafile fno=00112 name=+TEST_GRP/TEST/datafile/TESTtdscdrpart.369.697290733
input datafile fno=00007 name=+TEST_GRP/TEST/datafile/owbuser.267.654113349
input datafile fno=00017 name=+TEST_GRP/TEST/datafile/TEST_olap_audit.277.654113553
input datafile fno=00018 name=+TEST_GRP/TEST/datafile/TEST_ods_cdr.278.654113587
input datafile fno=00019 name=+TEST_GRP/TEST/datafile/TEST_ods_edr.279.654113597
input datafile fno=00020 name=+TEST_GRP/TEST/datafile/TEST_ods_sms.280.654113631
input datafile fno=00021 name=+TEST_GRP/TEST/datafile/TEST_ods_sbscrbr_hist.281.654113639
input datafile fno=00023 name=+TEST_GRP/TEST/datafile/TEST_ods_sbscrbr_hist_maxval.283.654113657
input datafile fno=00024 name=+TEST_GRP/TEST/datafile/TEST_ads_actvty_cube.284.654113691
input datafile fno=00025 name=+TEST_GRP/TEST/datafile/TEST_ads_actvty_cube_jan07.285.654113701
input datafile fno=00026 name=+TEST_GRP/TEST/datafile/TEST_ads_actvty_cube_maxval.286.654113711
input datafile fno=00027 name=+TEST_GRP/TEST/datafile/TEST_ads_subss_status_fact.287.654113719
input datafile fno=00028 name=+TEST_GRP/TEST/datafile/TEST_ads_subs_stts_fct_jan07.288.654113729
input datafile fno=00029 name=+TEST_GRP/TEST/datafile/TEST_ads_subs_stts_fct_maxval.289.654113763
input datafile fno=00030 name=+TEST_GRP/TEST/datafile/TEST_rds_dly_actvty_smry.290.654113773
channel d6: starting compressed full datafile backupset
channel d6: specifying datafile(s) in backupset
input datafile fno=00089 name=+TEST_GRP/TEST/datafile/TEST_tds.348.695475571
input datafile fno=00138 name=+TEST_GRP/TEST/datafile/TEST_tds.398.706176093
input datafile fno=00041 name=+TEST_GRP/TEST/datafile/TEST_tds.301.656463415
input datafile fno=00009 name=+TEST_GRP/TEST/datafile/TEST_tds.269.654113401
input datafile fno=00088 name=+TEST_GRP/TEST/datafile/TEST_tds.347.695475473
input datafile fno=00141 name=+TEST_GRP/TEST/datafile/TEST_tds.401.707084029
input datafile fno=00121 name=+TEST_GRP/TEST/datafile/TEST_ads.381.700249081
input datafile fno=00143 name=+TEST_GRP/TEST/datafile/TEST_tds.403.707084083
input datafile fno=00092 name=+TEST_GRP/TEST/datafile/TEST_ods1.351.696598425
input datafile fno=00095 name=+TEST_GRP/TEST/datafile/TEST_ods1.354.696598497
input datafile fno=00103 name=+TEST_GRP/TEST/datafile/TEST_ods1.362.696598755
input datafile fno=00148 name=+TEST_GRP/TEST/datafile/TEST_tds.408.707569461
input datafile fno=00156 name=+TEST_GRP/TEST/datafile/TEST_rds.257.714381137
input datafile fno=00114 name=+TEST_GRP/TEST/datafile/TESTtdscdrpart.374.697290735
input datafile fno=00034 name=+TEST_GRP/TEST/datafile/TEST_ods_indexes.294.654113835
input datafile fno=00022 name=+TEST_GRP/TEST/datafile/TEST_ods_sbscrbr_hist_jan07.282.654113649
input datafile fno=00053 name=+TEST_GRP/TEST/datafile/TEST_dds.312.662492551
input datafile fno=00052 name=+TEST_GRP/TEST/datafile/TEST_dds.311.662492489
input datafile fno=00054 name=+TEST_GRP/TEST/datafile/TEST_dds.313.662492619
input datafile fno=00005 name=+TEST_GRP/TEST/datafile/owbdata.265.654113297
channel d7: starting compressed full datafile backupset
channel d7: specifying datafile(s) in backupset
input datafile fno=00137 name=+TEST_GRP/TEST/datafile/TEST_tds.397.706176033
input datafile fno=00139 name=+TEST_GRP/TEST/datafile/TEST_tds.399.706176127
input datafile fno=00129 name=+TEST_GRP/TEST/datafile/TEST_tds.389.702542715
input datafile fno=00125 name=+TEST_GRP/TEST/datafile/TEST_tds.385.702198275
input datafile fno=00081 name=+TEST_GRP/TEST/datafile/TEST_tds.340.695129943
input datafile fno=00090 name=+TEST_GRP/TEST/datafile/TEST_tds.349.695475749
input datafile fno=00120 name=+TEST_GRP/TEST/datafile/TEST_ads.380.700249057
input datafile fno=00142 name=+TEST_GRP/TEST/datafile/TEST_tds.402.707084055
input datafile fno=00131 name=+TEST_GRP/TEST/datafile/TEST_ads.391.704194625
input datafile fno=00093 name=+TEST_GRP/TEST/datafile/TEST_ods1.352.696598449
input datafile fno=00099 name=+TEST_GRP/TEST/datafile/TEST_ods1.358.696598613
input datafile fno=00124 name=+TEST_GRP/TEST/datafile/TEST_ods1.384.700933397
input datafile fno=00070 name=+TEST_GRP/TEST/datafile/TEST_rds.329.676059403
input datafile fno=00111 name=+TEST_GRP/TEST/datafile/TESTtdscdrpart.370.697290733
input datafile fno=00002 name=+TEST_GRP/TEST/datafile/undotbs1.261.654101459
input datafile fno=00071 name=+TEST_GRP/TEST/datafile/TEST_ods_sbscrbr_hist_jan07.330.680708683
input datafile fno=00072 name=+TEST_GRP/TEST/datafile/TEST_ods_sbscrbr_hist_jan07.331.680708755
input datafile fno=00008 name=+TEST_GRP/TEST/datafile/TEST_rpstry.268.654113363
input datafile fno=00051 name=+TEST_GRP/TEST/datafile/TEST_dds.310.662492431
input datafile fno=00067 name=+TEST_GRP/TEST/datafile/TEST_rds_tapin.326.667722723
channel d8: starting compressed full datafile backupset
channel d8: specifying datafile(s) in backupset
input datafile fno=00004 name=+TEST_GRP/TEST/datafile/users.264.654101503
input datafile fno=00146 name=+TEST_GRP/TEST/datafile/TEST_tds.406.707084307
input datafile fno=00084 name=+TEST_GRP/TEST/datafile/TEST_tds.343.695237005
input datafile fno=00075 name=+TEST_GRP/TEST/datafile/TEST_tds.334.695040959
input datafile fno=00080 name=+TEST_GRP/TEST/datafile/TEST_tds.339.695129765
input datafile fno=00153 name=+TEST_GRP/TEST/datafile/users.413.708271033
input datafile fno=00014 name=+TEST_GRP/TEST/datafile/TEST_ads.274.654113499
input datafile fno=00130 name=+TEST_GRP/TEST/datafile/TEST_ads.390.704194583
input datafile fno=00145 name=+TEST_GRP/TEST/datafile/TEST_tds.405.707084139
input datafile fno=00096 name=+TEST_GRP/TEST/datafile/TEST_ods1.355.696598533
input datafile fno=00149 name=+TEST_GRP/TEST/datafile/TEST_tds.409.707569511
input datafile fno=00106 name=+TEST_GRP/TEST/datafile/undotbs1.366.696693453
input datafile fno=00117 name=+TEST_GRP/TEST/datafile/TESTtdscdrpart.377.697290949
input datafile fno=00016 name=+TEST_GRP/TEST/datafile/TEST_olap.276.654113543
input datafile fno=00013 name=+TEST_GRP/TEST/datafile/TEST_dds.273.654113489
input datafile fno=00035 name=+TEST_GRP/TEST/datafile/TEST_ads_indexes.295.654113845
input datafile fno=00064 name=+TEST_GRP/TEST/datafile/TEST_ads_tapout.323.667722723
input datafile fno=00126 name=+TEST_GRP/TEST/datafile/TEST_ads_tapout.386.701419275
input datafile fno=00134 name=+TEST_GRP/TEST/datafile/TEST_ads_tapout.394.704728861
input datafile fno=00055 name=+TEST_GRP/TEST/datafile/TEST_dds.314.662492689
channel d1: backup set complete, elapsed time: 00:54:41
channel d3: backup set complete, elapsed time: 01:10:07
channel d2: backup set complete, elapsed time: 01:11:12
channel d4: backup set complete, elapsed time: 01:12:18
channel d6: backup set complete, elapsed time: 01:12:42
channel d7: backup set complete, elapsed time: 01:12:57
channel d8: backup set complete, elapsed time: 01:14:31
channel d5: backup set complete, elapsed time: 01:30:28
Finished backup at 10-APR-10
released channel: d1
released channel: d2
released channel: d3
released channel: d4
released channel: d5
released channel: d6
released channel: d7
released channel: d8
RMAN>
Recovery Manager complete.Edited by: Fahd Mirza on Apr 10, 2010 8:37 PM

RMAN script problem to create logical standby database !

Dear Friends ,
I am using Oracle10g database . I want to create a logical standby database . I create two database :
Primary : orcl
standby : orclsby1
Every steps I followed successfully , but when I am going to create "standby database" from "primary database" using rman then I found the following error :
The script is below which I have to run in Primary (orcl) database :
Script :
run {
allocate channel prmy1 type disk;
allocate channel prmy2 type disk;
allocate channel prmy3 type disk;
allocate channel prmy4 type disk;
allocate auxiliary channel stby type disk;
duplicate target database for standby from active database
spfile
parameter_value_convert 'orcl','orclsby1'
set db_unique_name='orclsby1'
set db_file_name_convert='/orcl/','/orclsby1/'
set log_file_name_convert='/orcl/','/orclsby1/'
set control_files='/u01/app/oracle/oradata/orclsby1.ctl'
set log_archive_max_processes='5'
set fal_client='orclsby1'
set fal_server='orcl'
set standby_file_management='AUTO'
set log_archive_config='dg_config=(orcl,orclsby1)'
set log_archive_dest_1='service=orcl ASYNC
valid_for=(ONLINE_LOGFILE,PRIMARY_ROLE) db_unique_name=orcl'
Problem which I got :
[oracle@localhost DG]$ rman target sys/sys123@orcl auxiliary sys/sys123@orclsby1
Recovery Manager: Release 10.2.0.1.0 - Production on Mon Oct 19 15:58:17 2009
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: ORCL (DBID=1227832857)
connected to auxiliary database: ORCLSBY1 (not mounted)
RMAN> @cr_phys_sby1.txt
RMAN> run {
2> allocate channel prmy1 type disk;
3> allocate channel prmy2 type disk;
4> allocate channel prmy3 type disk;
5> allocate channel prmy4 type disk;
6> allocate auxiliary channel stby type disk;
7> duplicate target database for standby from
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "from": expecting one of: "dorecover, db_file_name_convert, nofilenamecheck, ;"
RMAN-01007: at line 7 column 39 file: cr_phys_sby1.txt
I try to edit the above script using 'nofilenamecheck' 'dorecover' etc. , but cannot resolve the problem . Would u plz help me .... where the problem is .
Both databases are running on Oracle10g platform .
Waiting for ur kind reply .. ...

You need to:
- create a SPFILE manually for standby database
- use the RMAN command: DUPLICATE TARGET DATABASE FOR STANDBY
- remove all SPFILE statements from RMAN script.

Rman script creation

Hi,
How to create a rman script? On the computer with the catalog you give the command "rman", then "connect target" command and then "create script" and I write the script?
Thank you,
Mihaela

Check this out..
<< Command >>
rman rcvcat rman/rman target backup_admin/backup_admin@test cmdfile=Full_Bkup.sql
<< Full_Bkup.sql >>
run {
allocate channel dev1 type disk;
backup
incremental level 0
filesperset 4
format '/u06/orabackup/TEST/rman/Full_Sun_Level0_%t'
tag Full_Arch_Sun
(database);
backup archivelog all delete input;
release channel dev1;
-Sri
Message was edited by:
Srikanth Pulikonda

Scheduler with RMAN script

hi,
i have the following RMAN script:
/*daily.sh*/
run {
allocate channel ch1 device type disk format '/rman/%d_%T_%p_%U' maxpiecesize 1G;
backup
incremental level 1 cumulative
database
plus archivelog delete input;
backup current controlfile;
backup spfile;
release channel ch1;
and also have the following scheduler script:
BEGIN
DBMS_SCHEDULER.CREATE_JOB(
job_name=>'BDOFFICE.INC_BACKUP',
job_type => 'EXECUTABLE',
job_action =>'/office/u01/daily.sh',
start_date=>'28-NOV-06 02.18.00 PM',
repeat_interval=>'TRUNC(SYSDATE+1)+14/24',
/* after 1 days at 1:00 PM */
comments => 'daily backup');
END;
how can i integrate these so that scheduler run the script automatically.
plz give me the steps with example.
thanks
Message was edited by:
bijitesh

You can use the dbconsole to schedule your backup script. It is quite easy and you can have it show you the sql used to create the job.

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

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

Help needed with rman script

Hi guys,
I need you help in creating rman scripts.
my plan is the following:
- at night i would like to make a backup of the database, archivelogs, control file and spfile. then delete the archivelogs on disk.
- during the day i would like to make every hour, a backup level 1, archivelogs and crontrol file.
my questions are:
for the night backup is the following script ok?
run {
set command id to 'xxx';
allocate channel t1 type 'SBT_TAPE';
allocate channel t2 type 'SBT_TAPE';
BACKUP INCREMENTAL LEVEL 0 DATABASE;
sql 'ALTER SYSTEM ARCHIVE LOG CURRENT';
change archivelog all;
backup archivelog all delete input;
backup current controlfile;
BACKUP SPFILE;
release channel t1;
release channel t2;
and for the daily backup (run on every hour) what do you think about this? is it ok?
run {
set command id to 'xxx';
allocate channel t1 type 'SBT_TAPE';
allocate channel t2 type 'SBT_TAPE';
BACKUP INCREMENTAL LEVEL 1 CUMULATIVE DATABASE;
sql 'ALTER SYSTEM ARCHIVE LOG CURRENT';
backup archivelog all not backed up 1 times;
backup current controlfile;
release channel t1;
release channel t2;
please help.
Message was edited.

Hi Alanm,
Right now the DB is generating many archives, that doesn't mean that we cant adapt the script in the future if less archives are generated.
By saying "You don't have to make the archive log script an incremental 1 backup" you mean that, since we are already making a backup at night to the archives, theres no need to make them also during the incremental 1?
and for the rest, do you thing the script is ok?

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

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

How do I edit this script (newbie)

Editing a script
I found a script that creates a reminder event based upon the birthdays of my contacts in Address Book. It looks forward one week at a time.
I'm not familiar with creating scripts. How would I edit this to do the following (if possible)
1- I set up a contact list in Address Book for only those people whose birthdays I want to be reminded of. Is it possible to have this script only look through this contact list, not every contact.
2- Can it also be set up to delete the previously set events (so that the only events that appear are the ones for the ensuing week)
3- Can it be set up to remind me of anniversaries also? How would I edit it? (I tried to find and replace the term birthday with anniversary, but all it did was notify me of forthcoming week's birthdays but called them anniversaries)
Thanks!
===============
birthdayAlert.scpt
User set variables
set numberDaysNotice to 1 -- how many days before the birthday to alert you, 0 is that day
set timeOfNotification to 5 -- the hour you want the notification
set selectedCalender to "Birthday Reminders" -- the calender in iCal you want to add the events to
Setup
set birthdayPeople to {}
set birthdayDates to {}
Get the current date & next week
set today to current date
set nextWeek to today + (60 * 60 * 24 * 7)
Loop through everyone in the Address Book
tell application "Address Book"
set peopleArray to the name of every person
repeat with i from 1 to count of peopleArray
set thisPerson to person i
set thisBirthday to birth date of thisPerson
Check if they've got a birthday entered on their card
if thisBirthday is not equal to (missing value) then
set year of thisBirthday to year of (current date) -- otherwise it uses their birth year
See if it's in the next week
if (thisBirthday is greater than today) and (thisBirthday is less than nextWeek) then
set thisBirthday_day to day of thisBirthday
set thisBirthday_month to month of thisBirthday
Add them to our list
set birthdayPeople to birthdayPeople & name of thisPerson
set birthdayDates to birthdayDates & birth date of thisPerson
end if
end if
end repeat
end tell
If we have birthday's go into iCal and add the alerts
if (count of birthdayPeople) is greater than 0 and ((count of birthdayPeople) is equal to (count of birthdayDates)) then
tell application "iCal"
tell calendar selectedCalender
repeat with i from 1 to count of birthdayPeople
set thisDate to item i of birthdayDates
set year of thisDate to year of today
set time of thisDate to (60 * 60) * timeOfNotification
set day of thisDate to (day of thisDate) - numberDaysNotice
set thisEvent to make new event at end with properties {description:"", summary:(item i of birthdayPeople) & "'s Birthday", location:"", start date:thisDate, end date:thisDate + 15 * minutes}
tell thisEvent
make new display alarm at end with properties {trigger interval:0}
end tell
end repeat
end tell
end tell
end if

1- I set up a contact list in Address Book for only those people whose birthdays I want to be reminded of. Is it possible to have this script only look through this contact list, not every contact.
Sure - if you created a specific group of the people you want to track then just change the line:
set peopleArray to the name of every person
to:
set peopleArray to the name of every person of group "Birthdays"
(or whatever group name you used). You see, as written your script just grabs everyone's name as opposed to just the names of people in the specific group.
2- Can it also be set up to delete the previously set events (so that the only events that appear are the ones for the ensuing week)
Yes, but that's a little trickier since you need some way to denote which events are birthday events vs. other events from last week. If you're using a specific calendar for this then you could just delete existing events in that calendar, or you could implement a minor change to the way you create events - use the description to identify this is one of your auto-created birthday alarms:
set thisEvent to make new event at end with properties {description:"birthday", summary:(item i of birthdayPeople) & "'s Birthday", location:"", start date:thisDate, end date:thisDate + 15 * minutes}
So now the events will have a specific description, so it's easy to start your new script off with a line that deletes existing 'birthday" events, via:
tell application "iCal"
delete every event of calendar selectedCalendar whose description = "birthday"
end tell
(you can nix the '... whose description = "birthday"' element if you just want to delete all existing events in the calendar).
3- Can it be set up to remind me of anniversaries also? How would I edit it? (I tried to find and replace the term birthday with anniversary, but all it did was notify me of forthcoming week's birthdays but called them anniversaries)
Sure, that's because you specifically ask Address Book for birthdays:
set thisBirthday to birth date of thisPerson
To track anniversaries you need to ask Address Book for different data. This one's a little tricker since anniversaries are tracked via the custom date element, so you'd need something like:
set anniversaryList to {}
tell application "Address Book"
repeat with eachPerson in (get every person) -- add 'of group "anniversaries' if you use a specific group
repeat with eachDate in eachPerson's custom dates
if label of eachDate = "anniversary" then
-- this person has an Anniversary set, so add your code here to check if eachDate is in the next week if it is:
copy eachPerson to end of anniversaryList
end if
end repeat
end repeat
end tell
At the end of this you'll have a list of people whose anniversary is upcoming and you can duplicate your iCal code to add anniversary events in addition to birthdays.

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.

Edit rman script

Similar Messages

Maybe you are looking for