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

Similar Messages

  • How to pass a parameter into RMAN script

    Hello,
    I have the following rman script :
    run {
    CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
    CONFIGURE CONTROLFILE AUTOBACKUP OFF;
    CONFIGURE DEVICE TYPE DISK PARALLELISM 2;
    CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT 'c:\oracle\RmanORCL102\ora_df%t_s%s_s%p';
    This script called configure.rman is launch by a .bat script with the following command:
    rman target 'sys/[email protected] as sysdba' @c:\oracle\RmanORCL102\configure.rman
    How can I pass a parameter into rman script, I want to pass an additional directory like this:
    rman target 'sys/[email protected] as sysdba' @c:\oracle\RmanORCL102\configure.rman v_dir_name
    And use it in rman script:
    CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT 'c:\oracle\RmanORCL102\$v_dir_name\ora_df%t_s%s_s%p';
    Is it a way to do this?
    Regards,
    Elodie

    One option would be to create a file called backup.bat with the following:
    echo run {
    echo CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
    echo CONFIGURE CONTROLFILE AUTOBACKUP OFF;
    echo CONFIGURE DEVICE TYPE DISK PARALLELISM 2;
    echo CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT 'c:\oracle\RmanORCL102\%1\ora_df%t_s%s_s%p';
    echo } ) | rman target sys/[email protected] then call the script as:
    c:\> backup.bat backup_directory_name

  • What's wrong with this RMAN script?

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

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

  • RMAN Script in Solaris

    Hi,
    I am running Following rman script through shell in Solaris 10.2 to validate the database:
    [email protected] # 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:
    [email protected] # 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:
    [email protected] # 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 for Unix

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

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

  • RMAN scripts & variables/parameters

    Hi
    We are using RMAN with TSM. There are a number of 9i and 8i databases. I tried to set the environment up to with as few scripts as possible to cover the variety of databases. I provide various variables/parameters to handle the differences between the various databases.
    In the 9i environment I "CONFIGURE" as much as possible to avoid setting changes in the actual backup script. That gives me a fairly clean generic backup script which also avoids manual channel allocations ie :
    run
    backup incremental level=0
    not backed up since time='SYSDATE-(8/24)'
    check logical
    filesperset=4
    format='/LVL0_%d_%T_%U'
    (database include current controlfile)
    plus archivelog format '/ARC_%d_%T_%U' delete all input;
    However due to the lack of "CONFIGURE" in 8i I cannot configure automatic channels. Therefor my script has to change to :
    run
    allocate channel ch01 type 'sbt_tape' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin/tdpo_${ORACLE_SID}.opt)';
    allocate channel ch02 type 'sbt_tape' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin/tdpo_${ORACLE_SID}.opt)';
    allocate channel ch03 type 'sbt_tape' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin/tdpo_${ORACLE_SID}.opt)';
    allocate channel ch04 type 'sbt_tape' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin/tdpo_${ORACLE_SID}.opt)';
    backup incremental level=0
    check logical
    filesperset=4
    format='/LVL0_%d_%T_%U'
    (database include current controlfile)
    (archivelog all format '/ARC_%d_%T_%U' delete input);
    release channel ch01;
    release channel ch02;
    release channel ch03;
    release channel ch04;
    I have multiple database instances on the same server & would like to have a single generic script with a variable/parameter to change the "tdpo.opt" file for each instance. The alternate is to have a complete set of scripts for each DB instance with everything hard coded.
    The question is : Can I pass variables/parameters to a RMAN script? If yes, how do I go about it?
    Maybe there are other ideas out there to do this. The key to me in this whole execise is to reduce maintenance & increase flexibility.
    Your responses will be appreciated
    CM

    I was hoping to get away from building part of the backup script ie the channel allocation in the RMAN statement.Don't know how you expect to do this when it's required for 8i databases ?
    Well since you are looking to accommodate 8i & 9i database and you need to manually allocate channels for the 8i databases, then you could configure your script to include an IF..THEN block that will run one set of RUN commands if the database name that is passed in is in a certain list and run the other RUN block if it isn't. You could maintain two "here document" blocks, one for 8i and one for 9i. Therefore, all of the commands can reside in one generic script.
    For example, you could configure your single, generic script as:
    # add your logic checking here to see if a 9i database sid
    # was passed in as a parameter.  If so run the following code
    rman target / log=${sid}bkp_log append << !1
    run
    backup incremental level=0
    not backed up since time='SYSDATE-(8/24)'
    check logical
    filesperset=4
    format='/LVL0_%d_%T_%U'
    (database include current controlfile)
    plus archivelog format '/ARC_%d_%T_%U' delete all input;
    !1
    # if not run the following (ie. 8i databases)
    rman target / log=${sid}bkp_log append << !2
    run
    allocate channel ch01 type 'sbt_tape' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin/tdpo_${ORACLE_SID}.opt)';
    allocate channel ch02 type 'sbt_tape' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin/tdpo_${ORACLE_SID}.opt)';
    allocate channel ch03 type 'sbt_tape' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin/tdpo_${ORACLE_SID}.opt)';
    allocate channel ch04 type 'sbt_tape' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin/tdpo_${ORACLE_SID}.opt)';
    backup incremental level=0
    check logical
    filesperset=4
    format='/LVL0_%d_%T_%U'
    (database include current controlfile)
    (archivelog all format '/ARC_%d_%T_%U' delete input);
    release channel ch01;
    release channel ch02;
    release channel ch03;
    release channel ch04;
    !2then you could call this generic script with the appropriate command line parameters.
    Hope I'm following your explanation/requirement.

  • RMAN script error in UNIX

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

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

  • Rman script clarification

    Hi gurus,
    Im new to rman and im configuring it from EM.
    My strategy is disk-based. I don't backup with rman on tape. Im sending it on tape from another program.
    The generated script is:
    [BEGIN SCRIPT]
    $rman_script="backup device type disk tag '%TAG' database;
    backup device type disk tag '%TAG' archivelog all not backed up;
    allocate channel for maintenance type 'SBT_TAPE';
    delete noprompt obsolete device type disk;
    release channel;
    &br_save_agent_env();
    &br_prebackup($l_db_connect_string, $l_is_cold_backup, $l_use_rcvcat, $l_db_10_or_higher, $l_backup_strategy, "TRUE");
    my $result = &br_backup();
    exit($result);
    [END SCRIPT]
    The backup appears failed because it seems its trying to backup on tape too. As saw on metalink, I sent a command that is supposed to clear the tape channel.
    Here is the error message:
    [MESSAGE START]
    RMAN> allocate channel for maintenance type 'SBT_TAPE';
    released channel: ORA_DISK_1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03009: failure of allocate command on ORA_MAINT_SBT_TAPE_1 channel at 10/09/2007 02:49:27
    ORA-19554: error allocating device, device type: SBT_TAPE, device name:
    ORA-27211: Failed to load Media Management Library
    Additional information: 22
    [MESSAGE END]
    It still appears failed.
    Can I remove the line
    allocate channel for maintenance type 'SBT_TAPE';
    Thanks, your help is greatly appreciated

    I think you definitely need to delete that line if
    you are not using tape.
    can you also paste the output of
    RMAN> show all;
    enricoHi,
    thanks for replying. Here is the result for the "show all" command:
    using target database control file instead of recovery catalog
    RMAN configuration parameters are:
    CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
    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 '/u18/oracle/BACKUPPRODUCTION/%F';
    CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO BACKUPSET PARALLELISM 1;
    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 '/u18/oracle/HOTBACKUP/%U';
    CONFIGURE MAXSETSIZE TO UNLIMITED; # default
    CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
    CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
    CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/appora/oracle/product/10.2.0/db_1/dbs/snapcf_giga10g.f'; # default
    I also executed this morning
    RMAN> CONFIGURE DEVICE TYPE 'SBT_TAPE' CLEAR;
    RMAN> CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' clear;
    I already tried CONFIGURE DEVICE TYPE 'SBT_TAPE' CLEAR; but not the second line, I'll see tonight if it's ok now.
    ...and I forgot to mention I'm running a 10gR2 database on Redhat AS 4
    Thanks and have a nice day,
    JF

  • RMAN Scripts for 9i RAC

    We have just recently started to use Oracle 9i RAC on Red Hat linux 2.1. And we are going to use RMAN for backing up the archived logs.
    Currently we have 2 node cluster and the archived logs of respective nodes are on their respective local hard disk. e.g for node1 logs are archived on /arch1 and for node2 on /arch2 individually.
    Can I have some sample RMAN scripts for backing and restoring the logs of this individual nodes.?
    An early guidance is highly appreciated.
    Thanks

    you can use the same scripts as you where running before you upgraded to RAC. The main difference is that to distribute the load you can allocate channels from other nodes. A simple backup could be done as follows:
    #rman
    #connect target /
    #connect catalog rman/[email protected]
    #run{
    #allocate channel ch1 type sbt_tape;
    #allocate channel ch2 type sbt_tape;
    #configure channel 1 device type 'SBT_TAPE' connect = 'node 1'
    #configure channel 2 device type 'SBT_TAPE connect = 'node 2'
    #backup database;
    that will work (he says) but thats the main difference, remember oracle only recommend you allocate the same number of channels as you have devices (EG if you have 2 tape drives you can allocate 2 channels to maximize effiantcy)...
    hope this helps a bit,
    Marky Mark...

  • Oracle Online Backup through EMC Networker - RMAN Script

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

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

  • Rman script in windows

    hi .
    I dont know how can i write RMAN script in windowse,
    please help me.

    Create a script, say backup.cmd : the following backs up the controlfile, entire DB, all archivelogs and deletes backed up archivelogs :
    run { allocate channel d1 type disk;
          configure controlfile autobackup on;
          backup database plus archivelog delete input;
    }then, at OS prompt
    C:\> set ORACLE_SID=<your SID>
    C:\> rman target /
    RMAN> @backup.cmd

  • Understanding order of commands in RMAN script

    I just started working at a new job and the prior DBA had already left before I got there. I'm looking at his RMAN script to backup the 11gR2 single instance database and I can't understand what is the need for two "crosscheck backup" commands? Wouldn't it be prudent to also have a "crosscheck backup of archivelog all" command as well? Also, what is the point of having the "restore database preview" command in the daily backup script?
    run
    crosscheck backup;
    recover copy of database with tag 'ORA$OEM_LVL1_ILANDB_PRIM' until time 'SYSDATE-1';
    backup incremental level 1 for recover of copy with tag 'ORA$OEM_LVL1_ILANDB_PRIM' database plus archivelog delete all input;
    delete noprompt obsolete;
    restore database preview;
    crosscheck backup;
    }

    Here is how RMAN is currently configured. How do you suggest I clean this up?
    RMAN> show all;
    using target database control file instead of recovery catalog
    RMAN configuration parameters for database with db_unique_name ORCL are:
    CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
    CONFIGURE BACKUP OPTIMIZATION ON;
    CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/u02/app/oracle/fast_recovery_area/ORCL/fullbackup/full_bkp_${DD}/%F';
    CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 4;
    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 '/u02/app/oracle/fast_recovery_area/ILANDB/fullbackup/full_bkp_%d_DB_%u_%s_%p';
    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 EXCLUDE FOR TABLESPACE 'WEBTASK_DATA';
    CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/11.2.0/db_1/dbs/snapcf_ORCL.f'; # default

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

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

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

  • RMAN backup of 8i target db using 9i rman scripts

    Hello,
    I have set up a server for Monitoring and Backup using OEM and RMAN, and I have installed Oracle 9.2.0.6 RMAN catalog, to store the backup scripts and the backup information
    I have registred and taken backup of Oracle 9i databases, and it works okay. Now I want to register Oracle 8.1.7.4 databases and take backup of 8i target databases using the scripts and configuration setting that I created for 9i databases
    Can I use the 9i scripts and "configure" command to backup 8i databases?
    I had checked the compatability matrix on metalink (docid: 73431.1) and it suggested using same version of rman executable (.. wrt target database). Is it so?
    I assumed that 9i RMAN is backward compatible and so this can be used to backup the 8i databases... sames commands and not just the 9i catalog. I get RMAN-6429 when I try to connect to 8i database from the backup server.
    Please let me know if I can use Oracle 9i RMAN command and features to backup Oracle 8.1.7.4 databases?
    Regards
    Sudhanshu

    Update on this thread (...the feedback I got from metalink)
    No, you cannot use the 9i rman executable and features to backup a 8.1.x Database. The rman executable must match the Target Database when Target is 8.1.x.
    New features in 9i are not backward compatible.
    Thanks

  • 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

Maybe you are looking for

  • How many fonts are free prvoide from Adobe?

    Dear Sir/Miss:   I want to know how many fonts users can free download the fonts? Cause someone tell me, if you install Adobe reader, you can use their fonts for free !? and your system also will install these fonts?

  • Jaxb with weblogic -- java.lang.NoClassDefFoundError: javax/xml/bind/MarshallableRootElement

    I am trying to use jaxb with Weblogic 6.1. I kept both the jaxb jar file in weblogic classpath in setEnv script. I am getting the following error, when I am trying to use jaxb java.lang.NoClassDefFoundError: javax/xml/bind/MarshallableRootElement I t

  • I am losing my mind because everything I try never works!!!

    My iPod repeatedly shows an apple sign and a sad iPod face. I tried EVERY POSSIBLE THING I can think of but it didn't work. I tried: resetting, disk mode, restoring, different computer, updating iTunes,charging on wall charger or whatever it's called

  • Restoring Game Cener

    Hi, My son has an 8GB 4thGen Touch and manged to reset it last night.  Luckily I back everything up and was able to restore it to how he had it set up, with one exception.  I can't get Game Center to allow him to log back in with his AppleID.  If we

  • Cs5 opens fine with 2 monitors but not with one? (Macintosh)

    Hi, I use a macbook pro with an external apple display. When I open a file in CS5 and the second monitor is plugged in, everything opens perfectly. The tabs are in the 2nd monitor and the image opens in that same monitor. However, when the monitor is