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

Similar Messages

  • RMAN Script is not allocating channels

    I have a customer who is running a Solaris Server with Oracle 9i and is trying to backup using an RMAN script to define the channels to back up to through Networker.
    The script is as follows:
    run {
    allocate channel t1 type "sbt_tape";
    allocate channel t2 type "sbt_tape";
    send 'NSR_ENV=(NSR_SERVER=XXXX,NSR_DATA_VOLUME_POOL=Default)';
    sql 'alter system archive log current';
    change archivelog all crosscheck;
    set command id to 'bkrs';
    backup
    filesperset 20
    archivelog all
    delete input;
    release channel t1;
    release channel t2;
    Normally there are 3 channel allocations, but for some reason this does not work. He can only get 1 channel to work at a time which is impacting Backup Performance.
    There are no errors logged in the log files which is also odd. The device parallelism is 4 under Networker
    The version of Networker is 7.1
    Anyone else had any similar issues - I have been scratching my head on this for a while, or if anyone has any ideas on how to troubleshoot this I would appreciate any help
    Thanks

    I have now found some error information. Please see below.
    RMAN-00571: ======================================
    RMAN-00569: ===== ERROR MESSAGE STACK FOLLOWS =====
    RMAN-00571: =======================================
    RMAN-03009: failure of allocate command on t1 channel at 04/08/2004 10:37:02
    ORA-19554: error allocating device, device type: SBT_TAPE, device name:
    ORA-27211: Failed to load Media Management Library
    Any help much appreciated !!!!!

  • RMAN script 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

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

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

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

  • Can I call an external program from my rman script

    Hi
    Is it possible to do an external call to a bat-file in a rman script?
    My script looks like this (it's pretty much generated from EM):
    $rman_script="backup device type disk tag '%TAG' database;
    sql 'alter system archive log current';
    backup device type disk tag '%TAG' archivelog all not backed up delete all input;
    allocate channel for maintenance type disk;
    delete noprompt obsolete device type disk;
    release channel;
    Can i somehow make an external call before at the end?
    Regards
    Klaus Mogensen

    You can use the HOST command.

  • RMAN script errors out for some DB's

    I have a single RMAN script that uses env variables to execute RMAN for two databases. It runs fine. I cloned the two DB's (changed DBID's), all four are on the same host. Now I try to use same script for all four. I receive an error when trying to run against the cloned databases. Here is script:
    spool log to full.log append;
    connect catalog rman/xxxxxx@iasrman
    connect target /
    run {
    sql 'ALTER SYSTEM SWITCH LOGFILE';
    backup incremental level 0 database diskratio=0 plus archivelog delete input;
    And here is error, it stops same place everytime, input appreciated.
    Recovery Manager: Release 9.2.0.5.0 - 64bit Production
    RMAN>
    connected to recovery catalog database
    RMAN>
    connected to target database: PRSMQ02 (DBID=944525168)
    RMAN> 2> 3> 4>
    sql statement: ALTER SYSTEM SWITCH LOGFILE
    Starting backup at 30-MAY-07
    current log archived
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=20 devtype=DISK
    allocated channel: ORA_DISK_2
    channel ORA_DISK_2: sid=19 devtype=DISK
    allocated channel: ORA_DISK_3
    channel ORA_DISK_3: sid=18 devtype=DISK
    allocated channel: ORA_DISK_4
    channel ORA_DISK_4: sid=17 devtype=DISK
    allocated channel: ORA_DISK_5
    channel ORA_DISK_5: sid=11 devtype=DISK
    channel ORA_DISK_1: starting archive log backupset
    channel ORA_DISK_1: specifying archive log(s) in backup set
    input archive log thread=1 sequence=25 recid=25 stamp=623931644
    channel ORA_DISK_1: starting piece 1 at 30-MAY-07
    channel ORA_DISK_2: starting archive log backupset
    channel ORA_DISK_2: specifying archive log(s) in backup set
    input archive log thread=1 sequence=26 recid=26 stamp=623931644
    channel ORA_DISK_2: starting piece 1 at 30-MAY-07
    channel ORA_DISK_1: finished piece 1 at 30-MAY-07
    piece handle=/iasrman/q02/prsmq02/prsmq02_df623931649_s59_s1 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:02
    channel ORA_DISK_1: deleting archive log(s)
    archive log filename=/q02/archive/prism/log_prsmq02_25.arc recid=25 stamp=623931644
    channel ORA_DISK_2: finished piece 1 at 30-MAY-07
    piece handle=/iasrman/q02/prsmq02/prsmq02_df623931649_s60_s1 comment=NONE
    channel ORA_DISK_2: backup set complete, elapsed time: 00:00:02
    channel ORA_DISK_2: deleting archive log(s)
    archive log filename=/q02/archive/prism/log_prsmq02_26.arc recid=26 stamp=623931644
    Finished backup at 30-MAY-07
    Starting backup at 30-MAY-07
    using channel ORA_DISK_1
    using channel ORA_DISK_2
    using channel ORA_DISK_3
    using channel ORA_DISK_4
    using channel ORA_DISK_5
    channel ORA_DISK_1: starting incremental level 0 datafile backupset
    channel ORA_DISK_1: specifying datafile(s) in backupset
    input datafile fno=00009 name=/q02/oradata01/prsmdata/Data_13.dbf
    input datafile fno=00016 name=/q02/oradata01/prsmdata/Data_20.dbf
    input datafile fno=00025 name=/q02/oradata01/prsmdata/Data_04.dbf
    input datafile fno=00005 name=/q02/oraindx01/prsmdata/Index_11.dbf
    input datafile fno=00020 name=/q02/oradata01/prsmdata/Tools02.dbf
    input datafile fno=00022 name=/q02/oraindx01/prsmdata/index_12.dbf
    channel ORA_DISK_1: starting piece 1 at 30-MAY-07
    channel ORA_DISK_2: starting incremental level 0 datafile backupset
    channel ORA_DISK_2: specifying datafile(s) in backupset
    input datafile fno=00010 name=/q02/oradata01/prsmdata/Data_14.dbf
    input datafile fno=00015 name=/q02/oradata01/prsmdata/Data_19.dbf
    input datafile fno=00024 name=/q02/oradata01/prsmdata/Data_03.dbf
    input datafile fno=00003 name=/q02/oratmp01/prsmdata/rbs01.dbf
    input datafile fno=00001 name=/q02/orasys01/prsmdata/system01.dbf
    input datafile fno=00012 name=/q02/orasys01/prsmdata/system02.dbf
    channel ORA_DISK_2: starting piece 1 at 30-MAY-07
    channel ORA_DISK_3: starting incremental level 0 datafile backupset
    channel ORA_DISK_3: specifying datafile(s) in backupset
    input datafile fno=00008 name=/q02/oradata01/prsmdata/Data_12.dbf
    input datafile fno=00014 name=/q02/oradata01/prsmdata/Data_18.dbf
    input datafile fno=00023 name=/q02/oradata01/prsmdata/Data_02.dbf
    input datafile fno=00028 name=/q02/oradata01/prsmdata/Data06.dbf
    input datafile fno=00019 name=/q02/oratmp01/prsmdata/rbs02.dbf
    input datafile fno=00021 name=/q02/orasys01/prsmdata/DRSYS.dbf
    channel ORA_DISK_3: starting piece 1 at 30-MAY-07
    channel ORA_DISK_4: starting incremental level 0 datafile backupset
    channel ORA_DISK_4: specifying datafile(s) in backupset
    input datafile fno=00007 name=/q02/oradata01/prsmdata/Data_11.dbf
    input datafile fno=00013 name=/q02/oradata01/prsmdata/Data_17.dbf
    input datafile fno=00018 name=/q02/oradata01/prsmdata/Data_01.dbf
    input datafile fno=00006 name=/q02/oradata01/prsmdata/Tools01.dbf
    input datafile fno=00002 name=/q02/oradata01/prsmdata/Users01.dbf
    input datafile fno=00026 name=/q02/oradata01/prsmdata/Data05.dbf
    channel ORA_DISK_4: starting piece 1 at 30-MAY-07
    channel ORA_DISK_5: starting incremental level 0 datafile backupset
    channel ORA_DISK_5: specifying datafile(s) in backupset
    input datafile fno=00004 name=/q02/oradata01/prsmdata/Data_15.dbf
    input datafile fno=00011 name=/q02/oradata01/prsmdata/Data_16.dbf
    input datafile fno=00017 name=/q02/oradata01/prsmdata/Data_22.dbf
    input datafile fno=00027 name=/q02/oradata01/prsmdata/Data_05.dbf
    channel ORA_DISK_5: starting piece 1 at 30-MAY-07
    channel ORA_DISK_1: finished piece 1 at 30-MAY-07
    piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s61_s1 comment=NONE
    channel ORA_DISK_1: starting piece 2 at 30-MAY-07
    channel ORA_DISK_2: finished piece 1 at 30-MAY-07
    piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s62_s1 comment=NONE
    channel ORA_DISK_2: starting piece 2 at 30-MAY-07
    channel ORA_DISK_3: finished piece 1 at 30-MAY-07
    piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s63_s1 comment=NONE
    channel ORA_DISK_3: starting piece 2 at 30-MAY-07
    channel ORA_DISK_4: finished piece 1 at 30-MAY-07
    piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s64_s1 comment=NONE
    channel ORA_DISK_4: starting piece 2 at 30-MAY-07
    channel ORA_DISK_5: finished piece 1 at 30-MAY-07
    piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s65_s1 comment=NONE
    channel ORA_DISK_5: starting piece 2 at 30-MAY-07
    channel ORA_DISK_2: finished piece 2 at 30-MAY-07
    piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s62_s2 comment=NONE
    channel ORA_DISK_2: starting piece 3 at 30-MAY-07
    channel ORA_DISK_1: finished piece 2 at 30-MAY-07
    piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s61_s2 comment=NONE
    channel ORA_DISK_1: starting piece 3 at 30-MAY-07
    channel ORA_DISK_4: finished piece 2 at 30-MAY-07
    piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s64_s2 comment=NONE
    channel ORA_DISK_4: starting piece 3 at 30-MAY-07
    channel ORA_DISK_5: finished piece 2 at 30-MAY-07
    piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s65_s2 comment=NONE
    channel ORA_DISK_5: starting piece 3 at 30-MAY-07
    channel ORA_DISK_3: finished piece 2 at 30-MAY-07
    piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s63_s2 comment=NONE
    channel ORA_DISK_3: starting piece 3 at 30-MAY-07
    channel ORA_DISK_2: finished piece 3 at 30-MAY-07
    piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s62_s3 comment=NONE
    channel ORA_DISK_2: starting piece 4 at 30-MAY-07
    channel ORA_DISK_4: finished piece 3 at 30-MAY-07
    piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s64_s3 comment=NONE
    channel ORA_DISK_4: starting piece 4 at 30-MAY-07
    channel ORA_DISK_1: finished piece 3 at 30-MAY-07
    piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s61_s3 comment=NONE
    channel ORA_DISK_1: starting piece 4 at 30-MAY-07
    channel ORA_DISK_2: finished piece 4 at 30-MAY-07
    piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s62_s4 comment=NONE
    channel ORA_DISK_2: backup set complete, elapsed time: 00:53:23
    channel ORA_DISK_5: finished piece 3 at 30-MAY-07
    piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s65_s3 comment=NONE
    channel ORA_DISK_5: starting piece 4 at 30-MAY-07
    channel ORA_DISK_3: finished piece 3 at 30-MAY-07
    piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s63_s3 comment=NONE
    channel ORA_DISK_3: starting piece 4 at 30-MAY-07
    channel ORA_DISK_4: finished piece 4 at 30-MAY-07
    piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s64_s4 comment=NONE
    channel ORA_DISK_4: starting piece 5 at 30-MAY-07
    channel ORA_DISK_1: finished piece 4 at 30-MAY-07
    piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s61_s4 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:59:04
    channel ORA_DISK_3: finished piece 4 at 30-MAY-07
    piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s63_s4 comment=NONE
    channel ORA_DISK_3: backup set complete, elapsed time: 01:00:10
    channel ORA_DISK_5: finished piece 4 at 30-MAY-07
    piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s65_s4 comment=NONE
    channel ORA_DISK_5: backup set complete, elapsed time: 01:00:25
    channel ORA_DISK_4: finished piece 5 at 30-MAY-07
    piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s64_s5 comment=NONE
    channel ORA_DISK_4: backup set complete, elapsed time: 01:01:40
    Finished backup at 30-MAY-07
    Starting backup at 30-MAY-07
    current log archived
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of backup command at 05/30/2007 11:22:38
    RMAN-06004: ORACLE error from recovery catalog database: ORA-03114: not connected to ORACLE

    connect target /You need to inform the connection string to target database.
    Can to be explicitly or with 'export sid' in your script.

  • How to pass a shell variable to rman scripts

    I want to backup datafile to different directory
    depending on the current time,and I can do this to
    pass a shell variable to rman scripts,and this
    variable will used as part of format ,like this:
    backup incremental level=0
    tag rman_inc0_bck
    filesperset 5
    format '$(DIR)/rman_fulldb_%u_%s_%p_%d'
    (database include current controlfile)
    and $(DIR) is shell variable ,but rman will not
    recognize this ,how to achieve this?

    You could send your script to rman thru a pipe | or <<
    echo "backup incremental level=0
    tag rman_inc0_bck
    filesperset 5
    format '$(DIR)/rman_fulldb_%u_%s_%p_%d'
    (database include current controlfile);" | rman target /You could also create a "temp script" and then use it from rman with cmdfile
    sed "s,XXXDIR,$(DIR)," yourtemplate > /tmp/rmanscript.$$
    rman target / cmdfile /tmp/rmanscript.$$
    rm /tmp/rmanscript.$$

  • Schedule rman script in Windows 2003

    Oracle 10.2. I wrote a rman script and tried to schedule auto run in Windows 2003 server. I got this errors:
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00554: initialization of internal recovery manager package failed
    RMAN-04005: error from target database:
    ORA-12560: TNS:protocol adapter error
    The batch file name: rman_backup.bat
    content: rman target / cmdfile rman_backup.rcv log rman_backup.log
    Here is how I set it up:
    go to Control Panel>Scheduled Tasks>Add Scheduled Task, find rman_backup.bat, choose the run time and finish it. When asking for user name and password, I supply the user which is in oracle dba group.
    But when it run, it just produced the above error and won't run.
    Please advise
    S.
    in SQLnet.log
    fatal NI connect error 12560, connecting to:
    (DESCRIPTION=(ADDRESS=(PROTOCOL=BEQ)(PROGRAM=oracle)(ARGV0=oracleORCL)(ARGS='(DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq)))'))(CONNECT_DATA=(SID=ORCL)(CID=(PROGRAM=D:\oracle\product\10.2.0\db_1\bin\rman.exe)(HOST=W3TY5Z203)(USER=WELC))))
    VERSION INFORMATION:
         TNS for 32-bit Windows: Version 10.2.0.4.0 - Production
         Oracle Bequeath NT Protocol Adapter for 32-bit Windows: Version 10.2.0.4.0 - Production
    Time: 30-MAR-2010 11:27:00
    Tracing not turned on.
    Tns error struct:
    ns main err code: 12560
    TNS-12560: TNS:protocol adapter error
    ns secondary err code: 0
    nt main err code: 530
    TNS-00530: Protocol adapter error
    nt secondary err code: 2
    nt OS err code: 0

    here is example of script we are using to backup database from windows scheduler:
    set oracle_home=d:\oracle\ora920
    set path=d:\perl\bin;d:\oracle\ora920\bin;c:\winnt;c:\WINDOWS\system32;
    set PERL5LIB=''
    set NLS_LANG=AMERICAN_AMERICA.WE8MSWIN1252
    set TNS_ADMIN=d:\oracle\ora920\network\admin
    d:
    cd \scripts
    set oracle_sid=car
    rman target sys/car_$z3br4 catalog rman/oemrp_pwd@oemrp @rman_level0_car.rman > rman_level0_car.log
    perl email_log.pl "RMAN Level 0 Log" d:\scripts\rman_level0_car.log CARthis script backing up 9i database. 10g and 11g database we backing up via EM grid control.
    You can change this script to backup 10g or 11g databses as well.

  • What's wrong with this RMAN script?

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

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

  • RMAN 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 doesnt exit shell after backup

    Hi,
    I've the following script on AIX 6.1, Oracle 11.2.0.1.0:
    export ORACLE_HOME=/oracle/medprod/product/11.2.0/dbhome_1
    export ORACLE_SID=MEDPROD
    export PATH=$ORACLE_HOME/bin:$PATH
    export LOG_DIR=/home/medinous/backup/logs
    export LOG_FILE=$LOG_DIR/medprod_daily_backup_`date +%d%m%Y%X`.log
    rman target / catalog rman/rman@rman log=$LOG_FILE <<EOF
    execute script medinous_daily;
    exit;
    EXIT;
    EOF
    and:
    printing stored script: medinous_daily
    +{+
    allocate channel t1 type 'sbt_tape' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
    allocate channel t2 type 'sbt_tape' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
    allocate channel t3 type 'sbt_tape' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
    backup format 'medinous_dailybackup_%d_%s_%t'  database;
    backup  format 'medinous_dailyarchbackup_%d_%s_%t' archivelog all not backed up 1 times;
    crosscheck backup;
    delete noprompt obsolete;
    delete noprompt expired backup;
    delete noprompt expired archivelog all;
    release channel t1;
    release channel t2;
    release channel t3;
    +}+
    For some reason, the rman script, scheduled via crontab doesn't exit after successful backup, the process just remain alive, even though there's an explicit exit command at the end.
    Any idea?
    dula

    No, the script actully executes successfully. The problem is that after executing, the process does'nt die, it doesnt exit rman:
    channel t1: finished piece 1 at 28-DEC-10
    piece handle=prodarchbackup_PROD_666_738921153 tag=TAG20101228T075233 comment=API Version 2.0,MMS Version 5.5.2.0
    channel t1: backup set complete, elapsed time: 00:00:03
    channel t2: finished piece 1 at 28-DEC-10
    piece handle=prodarchbackup_PROD_667_738921153 tag=TAG20101228T075233 comment=API Version 2.0,MMS Version 5.5.2.0
    channel t2: backup set complete, elapsed time: 00:00:03
    channel t3: finished piece 1 at 28-DEC-10
    piece handle=prodarchbackup_PROD_668_738921153 tag=TAG20101228T075233 comment=API Version 2.0,MMS Version 5.5.2.0
    channel t3: backup set complete, elapsed time: 00:00:03
    Finished backup at 28-DEC-10
    Starting Control File and SPFILE Autobackup at 28-DEC-10
    piece handle=c-148294895-20101228-00 comment=API Version 2.0,MMS Version 5.5.2.0
    Finished Control File and SPFILE Autobackup at 28-DEC-10
    released channel: t1
    released channel: t2
    released channel: t3
    *<< I expect the rman shell script to exit at this point and 'die' >>>>*

  • RMAN script failed while creating Data Guard 11g

    Hi Friends,
    I am creating Physical Standby (11g) using RMAN (ACTIVE) on windows using the doc : Step by Step Guide on Creating Physical Standby Using RMAN DUPLICATE...FROM ACTIVE DATABASE [ID 1075908.1]
    The folder structure on Primary DB and on Physical Standby is totally different.
    while executing RMAN script i got errors for lot of locations and i specified the proper location in RMAN script itself (ex set diagnostic_dest = 'c:\app\' , set db_recovery_file_dest='C:\app\flash_recovery_area')
    Location of control files on Primary DB:
    D:\oradata\MESSTG\CONTROL01.CTL
    D:\oradata\flash_recovery\messtg\MESSTG\CONTROL02.CTL
    Location of control files (planned) on Physical Standby DB:
    C:\app\oradata\MESSTDBY\CONTROL01.CTL
    C:\app\flash_recovery_area\MESSTDBY\CONTROL02.CTL
    How to specify control file location of Physical standby in set control_files?
    Also i have 2 control files on Primary DB so do i need to specify both the control files , if so how?
    I tried different combination in RMAN script but all are failed:
    set control_files='D:\oradata\MESSTG\CONTROL01.CTL','C:\app\oradata\MESSTDBY\CONTROL01.CTL'
    RMAN Error is :
    while using set control_files=: C:\app\oradata\MESSTDBY\CONTROL01.CTL
    contents of Memory Script:
    backup as copy current controlfile for standby auxiliary format 'D:\ORADATA\MESSTG\CONTROL01.CTL';
    restore clone controlfile to 'C:\APP\ORADATA\MESSTDBY\CONTROL01.CTL' from
    'D:\ORADATA\MESSTG\CONTROL01.CTL';
    executing Memory Script
    Starting backup at 16-APR-13
    channel prmy1: starting datafile copy
    copying standby control file
    released channel: prmy1
    released channel: prmy2
    released channel: prmy3
    released channel: prmy4
    released channel: stby
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 04/16/2013 14:18:41
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-03009: failure of backup command on prmy1 channel at 04/16/2013 14:18:41
    ORA-17628: Oracle error 19505 returned by remote Oracle server
    RMAN>
    Error 2)
    while using set control_files='D:\oradata\MESSTG\CONTROL01.CTL','C:\app\oradata\MESSTDBY\CONTROL01.CTL'
    contents of Memory Script:
    backup as copy current controlfile for standby auxiliary format 'D:\ORADATA\MESSTG\CONTROL01.CTL';
    executing Memory Script
    Starting backup at 16-APR-13
    channel prmy1: starting datafile copy
    copying standby control file
    released channel: prmy1
    released channel: prmy2
    released channel: prmy3
    released channel: prmy4
    released channel: stby
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 04/16/2013 13:22:33
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-03009: failure of backup command on prmy1 channel at 04/16/2013 13:22:33
    ORA-17628: Oracle error 19505 returned by remote Oracle server
    RMAN>
    Regards,
    DB

    Hi,
    Can you paste here you rman script ?
    I think following script can help you.
    duplicate target database for standby
    from  active database
    spfile
      set "control_files"="d:\oradata\<standbydbuniquename>\CONTROL01.CTL"
      set "db_name"="<DBNAME>"
      set "db_unique_name"="<STANBYD DBA UNIQUENAME>"
      set "db_file_name_convert"="C:\app\oracle\oradata\<dbname>","d:\oradata\<standbydbuniquename>"
      set "log_file_name_convert"="C:\app\oracle\oradata\<dbname>","d:\oradata\<standbydbuniquename>"
      set "db_recovery_file_dest"="D:\fast_recovery_area"
    nofilenamecheck;C:\app\oracle\oradata\<dbname> - it is primary database dafiles location
    D:\oradata\<standbydbuniquename> - it is standby database datafile location.
    Don't forget creation of diagnostinc dests.
    Regards
    Mahir M. Quluzade

  • RMAN script for hot backup (looking for code critic) code attached.

    Hello Guru's,
    I have been having soem trouble running a successful hot full rman backup nightly.
    We max our CPU load whenever our RMAN takes too long and conflicts with a Legato tape backup. I have a development server that I attempted to get a consistent backup time duration that is rock solid as to not conflict with the Legato backup time.
    I just found out about duration with RMAN scripts here is my code:
    #!/bin/bash
    #rman backup script for daily hot whole database backup
    at -f /hd1/rman_scripts/rman_backup 0600 tomorrow
    rman target/
    run {
    allocate channel d1 device type disk format '/path/%U';
    backup duration 1:00 partial minimize load database filesperset 1;
    backup as BACKUPSET tag '%TAG' database;
    backup as BACKUPSET tag '%TAG' archivelog all delete all input;
    delete noprompt obsolete;
    release channel d1;
    exit
    It completes the backup, but does not use the 1 hour allocated- it only uses 15 minutes on average and creates many files instead of normally three backup files.
    Here is the results from querying the v$rman_status table for operation,status,start_time:
    RMAN,FAILED, 17-OCT-06 0600
    BACKUP,FAILED,17-OCT-06 0600
    RMAN,FAILED,17-OCT-06 0606
    BACKUP,COMPLETED,17-OCT-06 0606
    BACKUP,COMPLETED,17-OCT-06 0606
    BACKUP,FAILED,17-OCT-06 0615
    RMAN,COMPLETED,17-OCT-06 1513
    REPORT,COMPLETED,17-OCT-06 1513
    DELETE,COMPLETED,17-OCT-06 1513
    However, the timestamps of the backupset files it creates is:
    06:15 and not 1513?????????????
    RMAN appears to have only taken 15 minutes to create the files, why do I have a completed timestamp from v$rman_status of 1513???
    Please advise and comment, I am just learning RMAN.

    Try to remove the DURATION option in your script.
    Here more details about that part.
    http://download-east.oracle.com/docs/cd/B19306_01/backup.102/b14194/rcmsynta009.htm#i1010261
    Bye, Aron

  • RMAN script for Unix

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

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

  • How can RMAN script check if database is down?

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

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

Maybe you are looking for