Creating pfile in RMAN script
I am trying to create pfile from spfile from RMAN scripts as follows, but ran into issues
run {
2> sql 'create pfile=/tmp/p.ora from spfile';
3> }
sql statement: create pfile=/tmp/p.ora from spfile
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of sql command on default channel at 02/20/2009 11:23:06
RMAN-11003: failure during parse/execution of SQL statement: create pfile=/tmp/p.ora from spfile
ORA-02236: invalid file name
Any other suggestions to get the desired results. I want to create pfile in a different directory rather than defualt dbs directory.
stevencallan wrote:
How would this command look in SQL*Plus?
http://download.oracle.com/docs/cd/B19306_01/server.102/b14200/statements_6008.htm#i2072768
Check your use of quotation marks.NO...read what you said.
What does SQL*Plus have to do with this command. You mentioned quotations marks...what kind of quotation marks..single or double and where should there be ??
Similar Messages
-
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,
DBHi,
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 problem to create logical standby database !
Dear Friends ,
I am using Oracle10g database . I want to create a logical standby database . I create two database :
Primary : orcl
standby : orclsby1
Every steps I followed successfully , but when I am going to create "standby database" from "primary database" using rman then I found the following error :
The script is below which I have to run in Primary (orcl) database :
Script :
run {
allocate channel prmy1 type disk;
allocate channel prmy2 type disk;
allocate channel prmy3 type disk;
allocate channel prmy4 type disk;
allocate auxiliary channel stby type disk;
duplicate target database for standby from active database
spfile
parameter_value_convert 'orcl','orclsby1'
set db_unique_name='orclsby1'
set db_file_name_convert='/orcl/','/orclsby1/'
set log_file_name_convert='/orcl/','/orclsby1/'
set control_files='/u01/app/oracle/oradata/orclsby1.ctl'
set log_archive_max_processes='5'
set fal_client='orclsby1'
set fal_server='orcl'
set standby_file_management='AUTO'
set log_archive_config='dg_config=(orcl,orclsby1)'
set log_archive_dest_1='service=orcl ASYNC
valid_for=(ONLINE_LOGFILE,PRIMARY_ROLE) db_unique_name=orcl'
Problem which I got :
[oracle@localhost DG]$ rman target sys/sys123@orcl auxiliary sys/sys123@orclsby1
Recovery Manager: Release 10.2.0.1.0 - Production on Mon Oct 19 15:58:17 2009
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: ORCL (DBID=1227832857)
connected to auxiliary database: ORCLSBY1 (not mounted)
RMAN> @cr_phys_sby1.txt
RMAN> run {
2> allocate channel prmy1 type disk;
3> allocate channel prmy2 type disk;
4> allocate channel prmy3 type disk;
5> allocate channel prmy4 type disk;
6> allocate auxiliary channel stby type disk;
7> duplicate target database for standby from
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "from": expecting one of: "dorecover, db_file_name_convert, nofilenamecheck, ;"
RMAN-01007: at line 7 column 39 file: cr_phys_sby1.txt
I try to edit the above script using 'nofilenamecheck' 'dorecover' etc. , but cannot resolve the problem . Would u plz help me .... where the problem is .
Both databases are running on Oracle10g platform .
Waiting for ur kind reply .. ...You need to:
- create a SPFILE manually for standby database
- use the RMAN command: DUPLICATE TARGET DATABASE FOR STANDBY
- remove all SPFILE statements from RMAN script. -
Create a user who can run only 'rman script'
Dear Friends ,
I have created a 'rmanback; user who only can run the RMAN script only . I have created user like follwoing way :
1)
SQL> CREATE USER rmanback IDENTIFIED BY rmanback;
User created.
SQL> GRANT RECOVERY_CATALOG_OWNER TO rmanback;
Grant succeeded.
SQL> GRANT CONNECT, RESOURCE TO rmanback;
Grant succeeded.
2)
And My rman script is :
rman target rmanback/rmanback@orcl <<!
run
allocate channel t1 type disk;
backup format 'df_%t_%s_%p'
(database);}
3) And I make a situation where sys user cannot enter the database using its password . For this reason i give the follwoing entry in "sqlnet.ora" :
SQLNET.AUTHENTICATION_SERVICES=(NONE)
Now when I run the script then it shows the follwing error :
[oracle@localhost RMAN]$ sh rman.sh.copy
Recovery Manager: Release 10.1.0.3.0 - Production
Copyright (c) 1995, 2004, Oracle. All rights reserved.
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-04005: error from target database:
ORA-01031: insufficient privileges
Now plz tell me where is the problem . If I make any mistake then plz inform me .....
Thx
-----SYSOPER is a privilege that is not enough for recovery manager. Talking about SYSOPER privileges to perform a backup/recover operation from a sqlplus prompt, SYSOPER can perform backup operations, but when recovery is required, the only kind of recover it can perform is a complete recover, if the user requires any kind of incomplete recover it won't be possible since SYSOPER cannot issue neither of until time|change|cancel|controlfile operations, which require the user to connect with the SYSDBA role.
If you attempt to connect to the database by means of recovery manager with an account with SYSOPER role, you will get the following error:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS===============
RMAN-00571: ===========================================================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-04005: error from target database:
ORA-01031: insufficient privilegesFor the OP, there is no way to create some sort of operator accout, since this will have to connect as SYSDBA to perform all operations required by recovery manager, you will absolutely have to rethink your security strategy, and as I previously posted, you should use OS authentication and protect access to the host server.
~ Madrid
http://hrivera99.blogspot.com/ -
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...RajRaj,
We have been getting this type of request and it is not possible via RMAN to do that.
BUT--You could write a sql/plus script to query your variable and produce the RMAN script with the new value.
Just a suggestion.
Tammy -
How 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.$$ -
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 AMDear 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 -
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.
regardsThanks for the help.
The command has finished now and I didn't get a chance to check the ps -ef command.
As you see in my original post, I am using nohup to run the script in the background and its sending its output to nohup.out file. But in the content of nohup.out file, there is no mention of report generated by RMAN regarding how many blocks it found. Output is as follows:
oracle@TEST # more nohup.out
Recovery Manager: Release 10.2.0.3.0 - Production on Sat Apr 10 10:45:28 2010
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: TEST (DBID=978723866)
RMAN> 2> 3> 4> 5> 6> 7> 8> 9> 10> 11> 12> 13> 14> 15> 16> 17> 18> 19> 20> 21>
using target database control file instead of recovery catalog
old RMAN configuration parameters:
CONFIGURE DEVICE TYPE DISK PARALLELISM 8 BACKUP TYPE TO COMPRESSED BACKUPSET;
new RMAN configuration parameters:
CONFIGURE DEVICE TYPE DISK PARALLELISM 8 BACKUP TYPE TO COMPRESSED BACKUPSET;
new RMAN configuration parameters are successfully stored
allocated channel: d1
channel d1: sid=208 devtype=DISK
allocated channel: d2
channel d2: sid=427 devtype=DISK
allocated channel: d3
channel d3: sid=198 devtype=DISK
allocated channel: d4
channel d4: sid=448 devtype=DISK
allocated channel: d5
channel d5: sid=127 devtype=DISK
allocated channel: d6
channel d6: sid=434 devtype=DISK
allocated channel: d7
channel d7: sid=143 devtype=DISK
allocated channel: d8
channel d8: sid=430 devtype=DISK
Starting backup at 10-APR-10
channel d1: starting compressed full datafile backupset
channel d1: specifying datafile(s) in backupset
input datafile fno=00108 name=+TEST_GRP/TEST/datafile/undotbs1.368.696699605
input datafile fno=00040 name=+TEST_GRP/TEST/datafile/TEST_tds.300.656367299
input datafile fno=00085 name=+TEST_GRP/TEST/datafile/TEST_tds.344.695237023
input datafile fno=00076 name=+TEST_GRP/TEST/datafile/TEST_tds.335.695041023
input datafile fno=00046 name=+TEST_GRP/TEST/datafile/TEST_tds.305.662491879
input datafile fno=00039 name=+TEST_GRP/TEST/datafile/TEST_ads.299.654710687
input datafile fno=00048 name=+TEST_GRP/TEST/datafile/TEST_ads.307.662492133
input datafile fno=00049 name=+TEST_GRP/TEST/datafile/TEST_ads.308.662492197
input datafile fno=00107 name=+TEST_GRP/TEST/datafile/undotbs1.367.696699507
input datafile fno=00098 name=+TEST_GRP/TEST/datafile/TEST_ods1.357.696598585
input datafile fno=00150 name=+TEST_GRP/TEST/datafile/TEST_tds.410.707569569
input datafile fno=00155 name=+TEST_GRP/TEST/datafile/TEST_ads.415.709551523
input datafile fno=00113 name=+TEST_GRP/TEST/datafile/TESTtdscdrpart.373.697290733
input datafile fno=00003 name=+TEST_GRP/TEST/datafile/sysaux.262.654101493
input datafile fno=00001 name=+TEST_GRP/TEST/datafile/system.260.654101443
input datafile fno=00010 name=+TEST_GRP/TEST/datafile/TEST_lds.270.654113411
channel d2: starting compressed full datafile backupset
channel d2: specifying datafile(s) in backupset
input datafile fno=00086 name=+TEST_GRP/TEST/datafile/TEST_tds.345.695237043
input datafile fno=00136 name=+TEST_GRP/TEST/datafile/TEST_tds.396.705247353
input datafile fno=00128 name=+TEST_GRP/TEST/datafile/TEST_tds.388.702478685
input datafile fno=00087 name=+TEST_GRP/TEST/datafile/TEST_tds.346.695237103
input datafile fno=00078 name=+TEST_GRP/TEST/datafile/TEST_tds.337.695129727
input datafile fno=00045 name=+TEST_GRP/TEST/datafile/TEST_tds.304.662491639
input datafile fno=00119 name=+TEST_GRP/TEST/datafile/TEST_ads.379.700249037
input datafile fno=00050 name=+TEST_GRP/TEST/datafile/TEST_ads.309.662492253
input datafile fno=00132 name=+TEST_GRP/TEST/datafile/TEST_ads.392.704194655
input datafile fno=00101 name=+TEST_GRP/TEST/datafile/TEST_ods1.360.696598703
input datafile fno=00097 name=+TEST_GRP/TEST/datafile/TEST_ods1.356.696598559
input datafile fno=00127 name=+TEST_GRP/TEST/datafile/TEST_ods1.387.701852257
input datafile fno=00077 name=+TEST_GRP/TEST/datafile/users.336.695041119
input datafile fno=00116 name=+TEST_GRP/TEST/datafile/TESTtdscdrpart.376.697290909
input datafile fno=00006 name=+TEST_GRP/TEST/datafile/owbindex.266.654113339
input datafile fno=00066 name=+TEST_GRP/TEST/datafile/TEST_rds_post_paid_cdr.325.667722723
input datafile fno=00068 name=+TEST_GRP/TEST/datafile/TEST_rds_tapout.327.667722823
input datafile fno=00109 name=+TEST_GRP/TEST/datafile/TEST_tds_user.372.696949827
input datafile fno=00110 name=+TEST_GRP/TEST/datafile/uat_users.371.697117641
input datafile fno=00033 name=+TEST_GRP/TEST/datafile/TEST_tds_indexes.293.654113827
channel d3: starting compressed full datafile backupset
channel d3: specifying datafile(s) in backupset
input datafile fno=00057 name=+TEST_GRP/TEST/datafile/undotbs1.365.696688443
input datafile fno=00140 name=+TEST_GRP/TEST/datafile/TEST_tds.400.707083997
input datafile fno=00083 name=+TEST_GRP/TEST/datafile/TEST_tds.342.695130467
input datafile fno=00074 name=+TEST_GRP/TEST/datafile/TEST_tds.333.695040881
input datafile fno=00079 name=+TEST_GRP/TEST/datafile/TEST_tds.338.695129749
input datafile fno=00152 name=+TEST_GRP/TEST/datafile/users.412.707602603
input datafile fno=00047 name=+TEST_GRP/TEST/datafile/TEST_ads.306.662492079
input datafile fno=00133 name=+TEST_GRP/TEST/datafile/TEST_ads.393.704194691
input datafile fno=00091 name=+TEST_GRP/TEST/datafile/TEST_ods1.350.696598015
input datafile fno=00100 name=+TEST_GRP/TEST/datafile/TEST_ods1.359.696598683
input datafile fno=00105 name=+TEST_GRP/TEST/datafile/TEST_ods1.364.696598825
input datafile fno=00012 name=+TEST_GRP/TEST/datafile/TEST_sds.272.654113455
input datafile fno=00069 name=+TEST_GRP/TEST/datafile/TEST_rds.328.676059355
input datafile fno=00115 name=+TEST_GRP/TEST/datafile/TESTtdscdrpart.375.697290875
input datafile fno=00118 name=+TEST_GRP/TEST/datafile/TEST_sds.378.698406119
input datafile fno=00059 name=+TEST_GRP/TEST/datafile/TEST_tds_post_paid_cdr.318.667722719
input datafile fno=00060 name=+TEST_GRP/TEST/datafile/TEST_ods_post_paid_cdr.319.667722719
input datafile fno=00061 name=+TEST_GRP/TEST/datafile/TEST_ods_tapout.320.667722721
input datafile fno=00062 name=+TEST_GRP/TEST/datafile/TEST_ods_tapin.321.667722721
input datafile fno=00063 name=+TEST_GRP/TEST/datafile/TEST_ads_post_paid_cdr.322.667722721
channel d4: starting compressed full datafile backupset
channel d4: specifying datafile(s) in backupset
input datafile fno=00154 name=+TEST_GRP/TEST/datafile/users.414.708271719
input datafile fno=00135 name=+TEST_GRP/TEST/datafile/TEST_tds.395.705247313
input datafile fno=00042 name=+TEST_GRP/TEST/datafile/TEST_tds.302.656520125
input datafile fno=00073 name=+TEST_GRP/TEST/datafile/TEST_tds.332.695040819
input datafile fno=00082 name=+TEST_GRP/TEST/datafile/TEST_tds.341.695130447
input datafile fno=00147 name=+TEST_GRP/TEST/datafile/TEST_tds.407.707084333
input datafile fno=00122 name=+TEST_GRP/TEST/datafile/TEST_ads.382.700249099
input datafile fno=00144 name=+TEST_GRP/TEST/datafile/TEST_tds.404.707084111
input datafile fno=00038 name=+TEST_GRP/TEST/datafile/TEST_ads.298.654710453
input datafile fno=00102 name=+TEST_GRP/TEST/datafile/TEST_ods1.361.696598723
input datafile fno=00094 name=+TEST_GRP/TEST/datafile/TEST_ods1.353.696598467
input datafile fno=00044 name=+TEST_GRP/TEST/datafile/undotbs1.271.696679255
input datafile fno=00015 name=+TEST_GRP/TEST/datafile/TEST_rds.275.654113509
input datafile fno=00065 name=+TEST_GRP/TEST/datafile/TEST_ads_tapin.324.667722723
input datafile fno=00031 name=+TEST_GRP/TEST/datafile/TEST_rds_dly_act_smry_jan07.291.654113807
input datafile fno=00032 name=+TEST_GRP/TEST/datafile/TEST_rds_dly_act_smry_maxval.292.654113817
input datafile fno=00036 name=+TEST_GRP/TEST/datafile/TEST_rds_indexes.296.654113879
input datafile fno=00037 name=+TEST_GRP/TEST/datafile/dbatemp.297.654113889
input datafile fno=00043 name=+TEST_GRP/TEST/datafile/TEST_ods_sbscrbr_hist.303.656530541
input datafile fno=00058 name=+TEST_GRP/TEST/datafile/TEST_tds_post_paid_src.317.667722667
channel d5: starting compressed full datafile backupset
channel d5: specifying datafile(s) in backupset
input datafile fno=00011 name=+TEST_GRP/TEST/datafile/dba_activity.316.696605947
input datafile fno=00104 name=+TEST_GRP/TEST/datafile/TEST_ods1.363.696598773
input datafile fno=00151 name=+TEST_GRP/TEST/datafile/TEST_ads.411.707569675
input datafile fno=00123 name=+TEST_GRP/TEST/datafile/TEST_ods1.383.700933365
input datafile fno=00056 name=+TEST_GRP/TEST/datafile/TEST_rds.315.662492837
input datafile fno=00112 name=+TEST_GRP/TEST/datafile/TESTtdscdrpart.369.697290733
input datafile fno=00007 name=+TEST_GRP/TEST/datafile/owbuser.267.654113349
input datafile fno=00017 name=+TEST_GRP/TEST/datafile/TEST_olap_audit.277.654113553
input datafile fno=00018 name=+TEST_GRP/TEST/datafile/TEST_ods_cdr.278.654113587
input datafile fno=00019 name=+TEST_GRP/TEST/datafile/TEST_ods_edr.279.654113597
input datafile fno=00020 name=+TEST_GRP/TEST/datafile/TEST_ods_sms.280.654113631
input datafile fno=00021 name=+TEST_GRP/TEST/datafile/TEST_ods_sbscrbr_hist.281.654113639
input datafile fno=00023 name=+TEST_GRP/TEST/datafile/TEST_ods_sbscrbr_hist_maxval.283.654113657
input datafile fno=00024 name=+TEST_GRP/TEST/datafile/TEST_ads_actvty_cube.284.654113691
input datafile fno=00025 name=+TEST_GRP/TEST/datafile/TEST_ads_actvty_cube_jan07.285.654113701
input datafile fno=00026 name=+TEST_GRP/TEST/datafile/TEST_ads_actvty_cube_maxval.286.654113711
input datafile fno=00027 name=+TEST_GRP/TEST/datafile/TEST_ads_subss_status_fact.287.654113719
input datafile fno=00028 name=+TEST_GRP/TEST/datafile/TEST_ads_subs_stts_fct_jan07.288.654113729
input datafile fno=00029 name=+TEST_GRP/TEST/datafile/TEST_ads_subs_stts_fct_maxval.289.654113763
input datafile fno=00030 name=+TEST_GRP/TEST/datafile/TEST_rds_dly_actvty_smry.290.654113773
channel d6: starting compressed full datafile backupset
channel d6: specifying datafile(s) in backupset
input datafile fno=00089 name=+TEST_GRP/TEST/datafile/TEST_tds.348.695475571
input datafile fno=00138 name=+TEST_GRP/TEST/datafile/TEST_tds.398.706176093
input datafile fno=00041 name=+TEST_GRP/TEST/datafile/TEST_tds.301.656463415
input datafile fno=00009 name=+TEST_GRP/TEST/datafile/TEST_tds.269.654113401
input datafile fno=00088 name=+TEST_GRP/TEST/datafile/TEST_tds.347.695475473
input datafile fno=00141 name=+TEST_GRP/TEST/datafile/TEST_tds.401.707084029
input datafile fno=00121 name=+TEST_GRP/TEST/datafile/TEST_ads.381.700249081
input datafile fno=00143 name=+TEST_GRP/TEST/datafile/TEST_tds.403.707084083
input datafile fno=00092 name=+TEST_GRP/TEST/datafile/TEST_ods1.351.696598425
input datafile fno=00095 name=+TEST_GRP/TEST/datafile/TEST_ods1.354.696598497
input datafile fno=00103 name=+TEST_GRP/TEST/datafile/TEST_ods1.362.696598755
input datafile fno=00148 name=+TEST_GRP/TEST/datafile/TEST_tds.408.707569461
input datafile fno=00156 name=+TEST_GRP/TEST/datafile/TEST_rds.257.714381137
input datafile fno=00114 name=+TEST_GRP/TEST/datafile/TESTtdscdrpart.374.697290735
input datafile fno=00034 name=+TEST_GRP/TEST/datafile/TEST_ods_indexes.294.654113835
input datafile fno=00022 name=+TEST_GRP/TEST/datafile/TEST_ods_sbscrbr_hist_jan07.282.654113649
input datafile fno=00053 name=+TEST_GRP/TEST/datafile/TEST_dds.312.662492551
input datafile fno=00052 name=+TEST_GRP/TEST/datafile/TEST_dds.311.662492489
input datafile fno=00054 name=+TEST_GRP/TEST/datafile/TEST_dds.313.662492619
input datafile fno=00005 name=+TEST_GRP/TEST/datafile/owbdata.265.654113297
channel d7: starting compressed full datafile backupset
channel d7: specifying datafile(s) in backupset
input datafile fno=00137 name=+TEST_GRP/TEST/datafile/TEST_tds.397.706176033
input datafile fno=00139 name=+TEST_GRP/TEST/datafile/TEST_tds.399.706176127
input datafile fno=00129 name=+TEST_GRP/TEST/datafile/TEST_tds.389.702542715
input datafile fno=00125 name=+TEST_GRP/TEST/datafile/TEST_tds.385.702198275
input datafile fno=00081 name=+TEST_GRP/TEST/datafile/TEST_tds.340.695129943
input datafile fno=00090 name=+TEST_GRP/TEST/datafile/TEST_tds.349.695475749
input datafile fno=00120 name=+TEST_GRP/TEST/datafile/TEST_ads.380.700249057
input datafile fno=00142 name=+TEST_GRP/TEST/datafile/TEST_tds.402.707084055
input datafile fno=00131 name=+TEST_GRP/TEST/datafile/TEST_ads.391.704194625
input datafile fno=00093 name=+TEST_GRP/TEST/datafile/TEST_ods1.352.696598449
input datafile fno=00099 name=+TEST_GRP/TEST/datafile/TEST_ods1.358.696598613
input datafile fno=00124 name=+TEST_GRP/TEST/datafile/TEST_ods1.384.700933397
input datafile fno=00070 name=+TEST_GRP/TEST/datafile/TEST_rds.329.676059403
input datafile fno=00111 name=+TEST_GRP/TEST/datafile/TESTtdscdrpart.370.697290733
input datafile fno=00002 name=+TEST_GRP/TEST/datafile/undotbs1.261.654101459
input datafile fno=00071 name=+TEST_GRP/TEST/datafile/TEST_ods_sbscrbr_hist_jan07.330.680708683
input datafile fno=00072 name=+TEST_GRP/TEST/datafile/TEST_ods_sbscrbr_hist_jan07.331.680708755
input datafile fno=00008 name=+TEST_GRP/TEST/datafile/TEST_rpstry.268.654113363
input datafile fno=00051 name=+TEST_GRP/TEST/datafile/TEST_dds.310.662492431
input datafile fno=00067 name=+TEST_GRP/TEST/datafile/TEST_rds_tapin.326.667722723
channel d8: starting compressed full datafile backupset
channel d8: specifying datafile(s) in backupset
input datafile fno=00004 name=+TEST_GRP/TEST/datafile/users.264.654101503
input datafile fno=00146 name=+TEST_GRP/TEST/datafile/TEST_tds.406.707084307
input datafile fno=00084 name=+TEST_GRP/TEST/datafile/TEST_tds.343.695237005
input datafile fno=00075 name=+TEST_GRP/TEST/datafile/TEST_tds.334.695040959
input datafile fno=00080 name=+TEST_GRP/TEST/datafile/TEST_tds.339.695129765
input datafile fno=00153 name=+TEST_GRP/TEST/datafile/users.413.708271033
input datafile fno=00014 name=+TEST_GRP/TEST/datafile/TEST_ads.274.654113499
input datafile fno=00130 name=+TEST_GRP/TEST/datafile/TEST_ads.390.704194583
input datafile fno=00145 name=+TEST_GRP/TEST/datafile/TEST_tds.405.707084139
input datafile fno=00096 name=+TEST_GRP/TEST/datafile/TEST_ods1.355.696598533
input datafile fno=00149 name=+TEST_GRP/TEST/datafile/TEST_tds.409.707569511
input datafile fno=00106 name=+TEST_GRP/TEST/datafile/undotbs1.366.696693453
input datafile fno=00117 name=+TEST_GRP/TEST/datafile/TESTtdscdrpart.377.697290949
input datafile fno=00016 name=+TEST_GRP/TEST/datafile/TEST_olap.276.654113543
input datafile fno=00013 name=+TEST_GRP/TEST/datafile/TEST_dds.273.654113489
input datafile fno=00035 name=+TEST_GRP/TEST/datafile/TEST_ads_indexes.295.654113845
input datafile fno=00064 name=+TEST_GRP/TEST/datafile/TEST_ads_tapout.323.667722723
input datafile fno=00126 name=+TEST_GRP/TEST/datafile/TEST_ads_tapout.386.701419275
input datafile fno=00134 name=+TEST_GRP/TEST/datafile/TEST_ads_tapout.394.704728861
input datafile fno=00055 name=+TEST_GRP/TEST/datafile/TEST_dds.314.662492689
channel d1: backup set complete, elapsed time: 00:54:41
channel d3: backup set complete, elapsed time: 01:10:07
channel d2: backup set complete, elapsed time: 01:11:12
channel d4: backup set complete, elapsed time: 01:12:18
channel d6: backup set complete, elapsed time: 01:12:42
channel d7: backup set complete, elapsed time: 01:12:57
channel d8: backup set complete, elapsed time: 01:14:31
channel d5: backup set complete, elapsed time: 01:30:28
Finished backup at 10-APR-10
released channel: d1
released channel: d2
released channel: d3
released channel: d4
released channel: d5
released channel: d6
released channel: d7
released channel: d8
RMAN>
Recovery Manager complete.Edited by: Fahd Mirza on Apr 10, 2010 8:37 PM -
RMAN script 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 -
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/sys12@ORCL102 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/sys12@ORCL102 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,
ElodieOne 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/sys12@orcl102and then call the script as:
c:\> backup.bat backup_directory_name -
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 -
Hi,
How to create a rman script? On the computer with the catalog you give the command "rman", then "connect target" command and then "create script" and I write the script?
Thank you,
MihaelaCheck this out..
<< Command >>
rman rcvcat rman/rman target backup_admin/backup_admin@test cmdfile=Full_Bkup.sql
<< Full_Bkup.sql >>
run {
allocate channel dev1 type disk;
backup
incremental level 0
filesperset 4
format '/u06/orabackup/TEST/rman/Full_Sun_Level0_%t'
tag Full_Arch_Sun
(database);
backup archivelog all delete input;
release channel dev1;
-Sri
Message was edited by:
Srikanth Pulikonda -
Using scheduler to directly execute rman script stored in recovery catalog
Hi everyone, I usually automate my rman backups using either cron or dbms_scheduler to call my rman scripts stored in a NIX sh file. Everything works fine but does anyone know how/if it's possible to call an rman script stored in the recovery catalog. Lets say I create a script in the catalog:
RMAN> create script showall
comment 'just an example for demonstration'
SHOW ALL;
Can I use dbms_scheduler to call that script directly? If so how and if not then how can I schedule this or any catalog stored script stored in the rman catalog. Searched all over the place but everything seems to point to having to leave Oracle to call either a .sh or .bat file.
Regards,
DaveHi Greg, think you are definately on the right track mate. Based on what you put I found this at:
http://www.oracle-base.com/articles/12c/scheduler-enhancements-12cr1.php
It has the entire rman script in the pl/sql block but going to see if I can modify what's on that page and use what you put so instead of executing the entire script it will run something like:
BEGIN
DBMS_SCHEDULER.CREATE_JOB(
job_name => 'RMAN_SHOW_ALL',
job_type => 'EXECUTABLE',
job_action => 'RMAN TARGET / CATALOG rman/password@ your_cat run {execute script showall;}'
END;
Or something similar with times etc for execution if possible as the mechanics are the same. Believe though that using the job_action parameter will be the answer and allow me to automate my daily etc backups at night.
Will let you know once it's done and mark as correct answer.
Dave -
Can rman script be encrypted to protect the source?
Hi,
As a solution provider, is it possible to encrypt rman script be encrypted to protect the source?
thanks
andrewI think the best you can do is to use Oracle Encryption Wallet to store credentials for connecting to databases or use Password Encryption to create RMAN Encrypted Backups.
http://docs.oracle.com/cd/B19306_01/backup.102/b14191/rcmbackp.htm
http://docs.oracle.com/cd/B19306_01/network.102/b14266/cnctslsh.htm#i1006413 -
hi,
i have the following RMAN script:
/*daily.sh*/
run {
allocate channel ch1 device type disk format '/rman/%d_%T_%p_%U' maxpiecesize 1G;
backup
incremental level 1 cumulative
database
plus archivelog delete input;
backup current controlfile;
backup spfile;
release channel ch1;
and also have the following scheduler script:
BEGIN
DBMS_SCHEDULER.CREATE_JOB(
job_name=>'BDOFFICE.INC_BACKUP',
job_type => 'EXECUTABLE',
job_action =>'/office/u01/daily.sh',
start_date=>'28-NOV-06 02.18.00 PM',
repeat_interval=>'TRUNC(SYSDATE+1)+14/24',
/* after 1 days at 1:00 PM */
comments => 'daily backup');
END;
how can i integrate these so that scheduler run the script automatically.
plz give me the steps with example.
thanks
Message was edited by:
bijiteshYou can use the dbconsole to schedule your backup script. It is quite easy and you can have it show you the sql used to create the job.
Maybe you are looking for
-
# Question I am using Firefox 3.6.13 and have installed Windows Media Player 1.0.0.8 for Firefox. However, if I attempt to open a file with a .wmv extension it appears to function properly, except, that I cannot "play" the file. What am I doing wrong
-
Connection failover and transaction failover
Connection failover and transaction failover I need to know more about a behavior in a RAC cluster. When a node goes down that is executing one of my transaction through JDBC , does the connection and transaction failover to a new node without me nee
-
How can I see more than one text line?
Can anyone help me?? I know to write more than one line in a HstaticText with the following code label = new HStaticText("This is some text. It's a fairly long " + "\npiece of text that should show \nword wrapping on
-
How do you clear the "Used supplies in use" message
I had a Laserjet 1525nw printer replaced under warranty. The service folks re-installed my original cartridges but now I get the Used Supplies in Use message and I cannot ge the information on how much supply is left in each cartridge. How do I cle
-
How to create an apple id without using credit card
how to create an apple id without using credit card.. i have recently purchased apple iphone 3gs bt unable to get apps because of giving credit card info which i dnt hav.. so plz tel me some way to process..