RMAN log

My oracle 10.1 database is running on Win2003 server and I want to send the RMAN output in a log file during the backup.
Any help?
Regards

2 possible solutions in: Re: How to resend the RMAN output to a text file

Similar Messages

How can i bring Hour,Minute, second info in RMAN log ?

DB version: 11.2.0.3
Platform : Oracle Enterprise Linux 6.2
Below is an excerpt from RMAN backup log file.
As shown with the arrows below, the RMAN backup log doesn't have Hour, Minute and Second information. It just has the date 14-OCT-13
input archived log thread=1 sequence=10946 RECID=21079 STAMP=828801629
input archived log thread=2 sequence=10137 RECID=21081 STAMP=828801794
input archived log thread=1 sequence=10947 RECID=21080 STAMP=828801731
channel ch01: starting piece 1 at 14-OCT-13 --------------------------------------------> We need Time here like 17:28:43
channel ch00: finished piece 1 at 14-OCT-13
piece handle=al_9306_1_828819222 tag=TAG20131014T190816 comment=API Version 2.0,MMS Version 5.0.0.0
channel ch00: backup set complete, elapsed time: 00:14:55
channel ch00: deleting archived log(s)
<snipped>
How can I implement the equivalent of below statement for RMAN logging ?
alter session set nls_date_format='DD-MM-YYYY HH24:MI:SS';

HI,
Very interesting question. I think there is no difference. I did the test. There is no difference in terms of performance. But I'm always on the way RMAN Strategist
$ export NLS_DATE_FORMAT=’DD-MON-YY HH24:MI:SS’
$ echo $NLS_DATE_FORMAT
DD-MON-YY HH24:MI:SS
$
$ rman target / nocatalog
Recovery Manager: Release 10.2.0.5.0 – Production on Thu Jun 9 14:47:05 2011
Copyright (c) 1982, 2007, Oracle. All rights reserved
connected to target database: ANARTEST (DBID=1459801106)
using target database control file instead of recovery catalog
RMAN> list backup of database completed between ‘sysdate-2′ and ‘sysdate’;
List of Backup Sets
===================
BS Key Type LV Size       Device Type Elapsed Time Completion Time
1103    Full    591.40M    DISK        00:04:38     08-JUN-11 01:04:43
        BP Key: 1103   Status: AVAILABLE Compressed: YES Tag: TAG20110608T010004
        Piece Name: /oracle/rman/dbbak/Daily_bak_1459801106_2mmeb0ol_1_1.bak
List of Datafiles in backup set 1103
File LV Type Ckp SCN    Ckp Time           Name
1       Full 33971595   08-JUN-11 01:00:05 /dba/data/system01.dbf
2       Full 33971595   08-JUN-11 01:00:05 /dba/data/undotbs01.dbf
3       Full 33971595   08-JUN-11 01:00:05 /dba/data/sysaux01.dbf
4       Full 33971595   08-JUN-11 01:00:05 /dba/data/users01.dbf
5       Full 33971595   08-JUN-11 01:00:05 /dba/data/data_ts01.dbf
6       Full 33971595   08-JUN-11 01:00:05 /dba/data/index_ts01.dbf
BS Key Type LV Size       Device Type Elapsed Time Completion Time
1123    Full    593.09M    DISK        00:04:10     09-JUN-11 01:04:15
        BP Key: 1123   Status: AVAILABLE Compressed: YES Tag: TAG20110609T010005
        Piece Name: /oracle/rman/dbbak/Daily_bak_1459801106_3amedl4l_1_1.bak
List of Datafiles in backup set 1123
File LV Type Ckp SCN    Ckp Time           Name
1       Full 36502391   09-JUN-11 01:00:05 /dba/data/system01.dbf
2       Full 36502391   09-JUN-11 01:00:05 /dba/data/undotbs01.dbf
3       Full 36502391   09-JUN-11 01:00:05 /dba/data/sysaux01.dbf
4       Full 36502391   09-JUN-11 01:00:05 /dba/data/users01.dbf
5       Full 36502391   09-JUN-11 01:00:05 /dba/data/data_ts01.dbf
6       Full 36502391   09-JUN-11 01:00:05 /dba/data/index_ts01.dbf
RMAN>
Thank you

Generating rman log file

hi
How can I generate Rman log file? Oracle xe on windows
My rman backup script is like:
run{
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;
delete noprompt obsolete device type disk;
}

In addition to what Paul mentioned, you can also consider the LOG option from the command line.

RMAN Log file

Hi Folks,
I am using the below mentioned script through windows task scheduler to backup database by RMAN.
RUN
{backup database format '\\200.200.200.132\backup\oracledb%s%t' include current controlfile;
SQL 'ALTER SYSTEM ARCHIVE LOG CURRENT';}
THE PROBLEM IS;
Everytime my backup is unsuccessful & i am unable to know the cause.
Please let me know if its possible to create a Log File....
Thanks in advance...

You can use >> rman.log in your rman command
example
rman target / @rman_script.scr >>rman.log
First try from command prompt after you satisfy you schedule it.

How to check RMAN log

Dear all ,
I am perform cold backup using RMAN .It execute successfully but i want know which are those view and table having last backup time ,path and other(Including cold and Hot Backup) .
Thanks And Regards
Shaikh Abdul Moyed

Hemant K Chitale wrote:
Query v$rman_backup_job_details
A COLD Backup in RMAN needs the database to be MOUNTed. This allows Oracle to read the controlfile for the list of datafiles and also update the controlfile with details of the backup that has been executed.
v$backup_datafile lists the backups by datafile.
(A Backup Job would be "BACKUP DATABASE" which appears as 1 record in V$rman_backup_job_details but one row for each datafile in v$backup_datafile).
The views can be query in SQL.
Alternatively, in RMAN, you can use the "LIST BACKUP" command as well.
Hemant K Chitale
http://hemantoracledba.blogspot.com
Dear sir ,
It is great opportunity talk with you I reads your many blogs .
But when i execute list backup in rman it shows no list but when i execute following commands it show nothing
'no rows selected'
SELECT FROM v$rman_backup_job_details;*
and
SELECT FROM v$backup_datafile;*
Database = RMAN
USER= SYS@RMAN
and also
USER = RMAN@RMAN
Edited by: abdul moyed on Jan 16, 2011 11:16 PM
Edited by: abdul moyed on Jan 16, 2011 11:20 PM

RMAN-05001 - RMAN-03002 | Duplicating Database fails | Redo-Logs

Sorry guys,
first of all...my english is the worsteds you´ve ever seen...
I got some kind of problem using rman duplicating a DB called cs2t into cs2b.
Starting Duplicate Db at 17.05.2006 07:54:10
released channel: t1
released channel: t2
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 05/17/2006 07:54:10
RMAN-05501: aborting duplication of target database
RMAN-05001: auxiliary filename /oracle/orasys/cs2t/redo05.log conflicts with a file used by the target database
RMAN-05001: auxiliary filename /oracle/orasys/cs2t/redo04.log conflicts with a file used by the target database
RMAN-05001: auxiliary filename /oracle/orasys/cs2t/redo03.log conflicts with a file used by the target database
RMAN-05001: auxiliary filename /oracle/orasys/cs2t/redo02.log conflicts with a file used by the target database
RMAN-05001: auxiliary filename /oracle/orasys/cs2t/redo01.log conflicts with a file used by the target database
Recovery Manager complete.
Therefore I found on metalink some informations about using UNTIL TIME.
I´ve tryed it....but now...there are some other erros on my rman.log
executing command: SET until clause
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of set command at 05/17/2006 08:22:14
ORA-01830: date format picture ends before converting entire input string
Recovery Manager complete.
and now: no ideas anymore...i´ve googled for it about 3hours...nothing found....may anybody help me - please?
P.S. I hope you´ll understand anything i´ve wrote into this message ;-)

hi,
you have to use db_file_name_convert and db_log-filename_convert parameter in the auxiliary database parameter file and use nofilenamecheck parameter with the duplicate command.
This is also recommended that you create new redo og files for auxiliary databse just like --
RMAN> run{
2> allocate auxiliary channel c1 device type disk;
3> duplicate target database to prod1 pfile='c:\oracle\ora92\database\initprod1.ora'
4> logfile 'c:\oracle\oradata\prod1\redo01.log' size 50m,
5> 'c:\oracle\oradata\prod1\redo02.log' size 50m,
6> 'c:\oracle\oradata\prod1\redo03.log' size 50m ;}
i hope it solve your problem..
Navneet

How do I setup RMAN not to delete archive log files on the source database so GoldenGate can process DDL/DML changes?

I want to setup RMAN not to delete any archive log files that will be used by GoldenGate.   Once GoldenGate is completed with the archive log file, the archive log file can be backup and deleted by RMAN.   It's my understanding that I can issue the following command "REGISTER EXTRACT <ext_name>, LOGRETENTION" to enable to functionally.   Is this the only thing I need to do to execute to enable this functionally?

Hello,
Yes this is the rigth way using clasic capture.
Using the command : REGISTER EXTRACT Extract_name LOGRETENTION.
Create a Oracle Streams Group Capture (Artificial) that prevent RMAN archive deletion if these are pending to process for Golden Gate capture process.
You can see this integration doing a SELECT * FROM DBA_CAPTURE; after execute the register command.
Then, when RMAN try to delete a archive file pending to process for GG this warning appear AT RMAN logs:
Error:     RMAN 8317 (RMAN-08317 RMAN-8317)
Text:     WARNING: archived log not deleted, needed for standby or upstream capture process.
Then , this is a good manageability feature. I think is a 11.1 GG new feature.
Tip. To avoid RMAN backup multiples times a archive pending to process, there is a option called BACKUP archivelog not backed 1 times.
If you remove a Capture process that is registered with the database you need to use this comand to remove the streams capture group:
unREGISTER EXTRACT extract_name LOGRETENTION;
Then if you query dba_capture, the artificial Streams group is deleted.
I hope help.
Regards
Arturo

Alert log message and RMAN

Hi ,
following is the message from Alert log file and trace files.
This error encountered during RMAN backup but the backup was fine.
Didn't get any errors in RMAN log file.
Can anybody tell me what's the problem and solution?
----------- alert log file --------------------
Thu Mar 9 02:14:13 2006
Errors in file /app/oracle/admin/SOFPDWB4/udump/sofpdwb4_ora_950328.trc:
ORA-27037: unable to obtain file status
IBM AIX RISC System/6000 Error: 2: No such file or directory
Additional information: 4
Thu Mar 9 02:14:13 2006
Errors in file /app/oracle/admin/SOFPDWB4/udump/sofpdwb4_ora_1769540.trc:
ORA-27037: unable to obtain file status
IBM AIX RISC System/6000 Error: 2: No such file or directory
Additional information: 4
Thu Mar 9 02:14:13 2006
Errors in file /app/oracle/admin/SOFPDWB4/udump/sofpdwb4_ora_1392642.trc:
ORA-27037: unable to obtain file status
IBM AIX RISC System/6000 Error: 2: No such file or directory
Additional information: 4
----------- trace files -------------------
/app/oracle/admin/SOFPDWB4/udump/sofpdwb4_ora_950328.trc
Oracle9i Enterprise Edition Release 9.2.0.5.0 - 64bit Production
With the Partitioning and Oracle Data Mining options
JServer Release 9.2.0.5.0 - Production
ORACLE_HOME = /app/oracle/product/9.2.0
System name: AIX
Node name: sof016
Release: 1
Version: 5
Machine: 000CEF9C4C00
Instance name: SOFPDWB4
Redo thread mounted by this instance: 1
Oracle process number: 24
Unix process pid: 950328, image: oracle@sof016 (TNS V1-V3)
*** 2006-03-09 02:14:13.053
*** SESSION ID:(77.60408) 2006-03-09 02:14:13.040
ORA-27037: unable to obtain file status
IBM AIX RISC System/6000 Error: 2: No such file or directory
Additional information: 4
~
/app/oracle/admin/SOFPDWB4/udump/sofpdwb4_ora_1769540.trc
Oracle9i Enterprise Edition Release 9.2.0.5.0 - 64bit Production
With the Partitioning and Oracle Data Mining options
JServer Release 9.2.0.5.0 - Production
ORACLE_HOME = /app/oracle/product/9.2.0
System name: AIX
Node name: sof016
Release: 1
Version: 5
Machine: 000CEF9C4C00
Instance name: SOFPDWB4
Redo thread mounted by this instance: 1
Oracle process number: 25
Unix process pid: 1769540, image: oracle@sof016 (TNS V1-V3)
*** 2006-03-09 02:14:13.311
*** SESSION ID:(53.5721) 2006-03-09 02:14:13.310
ORA-27037: unable to obtain file status
IBM AIX RISC System/6000 Error: 2: No such file or directory
Additional information: 4
/app/oracle/admin/SOFPDWB4/udump/sofpdwb4_ora_1392642.trc
Oracle9i Enterprise Edition Release 9.2.0.5.0 - 64bit Production
With the Partitioning and Oracle Data Mining options
JServer Release 9.2.0.5.0 - Production
ORACLE_HOME = /app/oracle/product/9.2.0
System name: AIX
Node name: sof016
Release: 1
Version: 5
Machine: 000CEF9C4C00
Instance name: SOFPDWB4
Redo thread mounted by this instance: 1
Oracle process number: 27
Unix process pid: 1392642, image: oracle@sof016 (TNS V1-V3)
*** 2006-03-09 02:14:13.549
*** SESSION ID:(59.52476) 2006-03-09 02:14:13.548
ORA-27037: unable to obtain file status
IBM AIX RISC System/6000 Error: 2: No such file or directory
Additional information: 4

Hello looks like when backing up database using RMAN it did not find the archivelogs hence you got the errors. Try doing "Crosscheck archivelog all" and see.
-Sri
<< Symptoms >>
Archivelog backup using RMAN failed with error :
RMAN-03002: failure of backup command at 08/18/2005 14:51:16
RMAN-06059: expected archived log not found, lost of archived log compromises recoverability
ORA-19625: error identifying file /arch/arch2/1_266_563489673.dbf
ORA-27037: unable to obtain file status
IBM AIX RISC System/6000 Error: 2: A file or directory in the path name does not exist.
Additional information: 3
<<Cause>>
RMAN get the information about what archivelog files are required to back up from the v$archived_log view.
RMAN cannot find the file archivelog in the archivelog destination. So itscannot continue taking the backup because this file does not exist.
<<Solution>>
Check if the archivelog exist in the log archive destination. If the is moved to some other location then restore the file back to its original location and then do RMAN back.
else
RMAN> crosscheck archivelog all;
After the crosscheck all take the rman backup.

RMAN, RAC, NFS, and server lock ups

Good day. My environment is:
--a 2-node RAC
--Enterprise Edition 11.2.0.3
--RHEL 5.1
The goal is to use RMAN to push backups to a shared NFS mount (on a different server). Both nodes will have access to this location (in the event one node goes down, the other can still run backups). Easy, right?
Wrong.
I've tried every NFS mount option in the book. Most work just fine, some don't. When I use the recommended NFS mount options:
rw,bg,hard,nointr,rsize=32768,wsize=32768,tcp, vers=3,timeo=600, actimeo=0
or
rw,bg,hard,nointr,rsize=32768,wsize=32768,proto=tcp,noac,forcedirectio, vers=3,suid
The mount works normally. I can "ls" and "mkdir" and "touch" and "vi" and "cp" files back and forth from the NFS backup location to the RAC node all day long. No problems. However, when I try to do almost anything in RMAN which requires writing to the NFS backup location such as the command "backup archive all delete input;" (or even things as simple as a Crosscheck or RMAN configuration change which writes any changes back to the autobackup ControlFile) the node locks up. There are no errors (or if there are, I don't know where to find them), even when I use RMAN log.
Just to recap: I run a Crosscheck (or any RMAN process that writes to the NFS backup location), the node will lock up, and I can let it sit for a day, inaccessible, with CRSCTL on the other node saying it's offline, and the node will never come out of a "frozen" state. It cannot be pinged or connected to.
I think I can safely rule out NFS mount options at this point.
I understand (after extensive reading of MOS docs and testing) that RAC RMAN can and does suffer from inefficient I/O when writing to an NFS mount. I don't think that's the culprit either. The autobackup ControlFile is not that big and I cannot see how running a simple Crosscheck would lock an entire node.
I am hoping someone has encountered this in the past and hopefully it's just a simple misconfiguration somewhere.

My NFS line in /etc/fstab is (these options are for supporting 11.2.0.3, 11.1.0.7, and 10.2.0.4/5 simultaneously): server.domain:/NFS_Export /backup nfs rw,bg,hard,nointr,rsize=32768,wsize=32768,tcp,actimeo=0,vers=3,timeo=600 0 0
Before you installed GI, did you by chance do a yum update? I've encountered a similar issue which ended up being due to mkinitrd creating a corrupted kernel; mkinitrd is invoked during the GI installation when the ADVM drivers are added and in my case mkinitrd created a new kernel prior to the new kernel being installed. Second to that, make sure you have the matching kernel headers to your kernel version. If they are different then you could probably get away with just creating a new kernel with mkinitrd and relinking GI/RDBMS homes, but be prepared to wipe GI and reinstall.

ORA-19505: failed to identify file - RMAN in creating standby DR database.

I got this error when creating standby database at remote target server.
ORA-19505: failed to identify file "/backup/dxp1p/online/DXP1P_CF_c-2027711285-20131204-01"
Here is what I did:
1.   started the listener and created corresponding tnsnames entry at remote standyb server
2. startup nomount to the standby database at remote server for an empty instance (instance name dxp1p).
3. All rman backups are in the /backup mount point at primary and the mount point is shared on the remote server as nfs.   So, whatever have in the backup we should be able to see and read from the remote as well.
4. Run the following at primary rman:
sql 'alter system archive log current';
backup current controlfile for standby;
sql 'alter system archive log current';
crosscheck backup;
crosscheck archivelog all;
exit
5.   Start the rman command from primary after connected to the standby server, as the primary DB uses ASM and the standby DB uses file system for the database files:
RUN
SET NEWNAME FOR DATAFILE 1 to '/u01/dxp1p/data/system01.dbf';
SET NEWNAME FOR DATAFILE 2 to '/u01/dxp1p/data/sysaux01.dbf';
SET NEWNAME FOR DATAFILE 3 to '/u01/dxp1p/data/undotbs01.dbf';
SET NEWNAME FOR DATAFILE 4 to '/u01/dxp1p/data/users01.dbf';
SET NEWNAME FOR DATAFILE 5 to '/u01/dxp1p/data/fxtntdata.dbf';
SET NEWNAME FOR DATAFILE 6 to '/u01/dxp1p/data/fxtntindex.dbf';
SET NEWNAME FOR DATAFILE 7 to '/u01/dxp1p/data/mlogs.dbf';
SET NEWNAME FOR DATAFILE 8 to '/u01/dxp1p/data/dts.dbf';
SET NEWNAME FOR DATAFILE 9 to '/u01/dxp1p/data/dxpsoa.dbf';
SET NEWNAME FOR DATAFILE 10 to '/u01/dxp1p/data/expresso_ts.dbf';
SET NEWNAME FOR DATAFILE 11 to '/u01/dxp1p/data/jms_ts.dbf';
SET NEWNAME FOR DATAFILE 12 to '/u01/dxp1p/data/uup_ts.dbf';
SET NEWNAME FOR DATAFILE 13 to '/u01/dxp1p/data/newpage_ts.dbf';
ALLOCATE AUXILIARY CHANNEL aux1 DEVICE TYPE DISK;
ALLOCATE AUXILIARY CHANNEL aux2 DEVICE TYPE DISK;
DUPLICATE TARGET DATABASE for standby
nofilenamecheck
dorecover;
========================================================================
But I got this error from the rman log:
contents of Memory Script:
   set until scn 12245784375453;
   restore clone standby controlfile;
executing Memory Script
executing command: SET until clause
Starting restore at 04-DEC-13
channel aux1: starting datafile backup set restore
channel aux1: restoring control file
channel aux1: reading from backup piece /backup/dxp1p/online/DXP1P_CF_c-2027711285-20131204-01
channel aux1: ORA-19870: error while restoring backup piece /backup/dxp1p/online/DXP1P_CF_c-2027711285-20131204-01
ORA-19505: failed to identify file "/backup/dxp1p/online/DXP1P_CF_c-2027711285-20131204-01"
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
failover to previous backup
channel aux1: starting datafile backup set restore
channel aux1: restoring control file
channel aux1: reading from backup piece /backup/dxp1p/online/DXP1P_20131204_833310136_464
channel aux1: ORA-19870: error while restoring backup piece /backup/dxp1p/online/DXP1P_20131204_833310136_464
ORA-19505: failed to identify file "/backup/dxp1p/online/DXP1P_20131204_833310136_464"
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
failover to previous backup
channel aux1: starting datafile backup set restore
channel aux1: restoring control file
channel aux1: reading from backup piece /backup/dxp1p/online/DXP1P_CF_c-2027711285-20131204-00
channel aux1: ORA-19504: failed to create file "/oracle/product/11g/dbs/u02/dxp1p/control/control02.ctl"
ORA-27040: file create error, unable to create file
Linux-x86_64 Error: 2: No such file or directory
Additional information: 1
ORA-19600: input file is control file (/u01/dxp1p/control/control01.ctl)
ORA-19601: output file is control file (/oracle/product/11g/dbs/u02/dxp1p/control/control02.ctl)
Finished restore at 04-DEC-13
contents of Memory Script:
   sql clone 'alter database mount standby database';
executing Memory Script
sql statement: alter database mount standby database
released channel: aux1
released channel: aux2
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 12/04/2013 19:06:13
RMAN-05501: aborting duplication of target database
RMAN-03015: error occurred in stored script Memory Script
RMAN-03009: failure of sql command on clone_default channel at 12/04/2013 19:06:13
RMAN-11003: failure during parse/execution of SQL statement: alter database mount standby database
ORA-00205: error in identifying control file, check alert log for more info
=========================================
Not sure why, can somebody help?   Appreciated!

I used company regular script to login to standby instance as sys user from primary DB RMAN as oracle OS user and sys DB user.   We normally run this way for years.
Like this:
$ORACLE_HOME/bin/rman target=/ auxiliary 'sys/sys0rapr321!'@dxp1p_s11 CMDFILE=${HOME}/dba/scripts/rman_cr_dr.cmd
rman_cr_dr.cmd:
RUN
SET NEWNAME FOR DATAFILE 1 to '/u01/dxp1p/data/system01.dbf';
SET NEWNAME FOR DATAFILE 2 to '/u01/dxp1p/data/sysaux01.dbf';
SET NEWNAME FOR DATAFILE 3 to '/u01/dxp1p/data/undotbs01.dbf';
SET NEWNAME FOR DATAFILE 4 to '/u01/dxp1p/data/users01.dbf';
SET NEWNAME FOR DATAFILE 5 to '/u01/dxp1p/data/fxtntdata.dbf';
SET NEWNAME FOR DATAFILE 6 to '/u01/dxp1p/data/fxtntindex.dbf';
SET NEWNAME FOR DATAFILE 7 to '/u01/dxp1p/data/mlogs.dbf';
SET NEWNAME FOR DATAFILE 8 to '/u01/dxp1p/data/dts.dbf';
SET NEWNAME FOR DATAFILE 9 to '/u01/dxp1p/data/dxpsoa.dbf';
SET NEWNAME FOR DATAFILE 10 to '/u01/dxp1p/data/expresso_ts.dbf';
SET NEWNAME FOR DATAFILE 11 to '/u01/dxp1p/data/jms_ts.dbf';
SET NEWNAME FOR DATAFILE 12 to '/u01/dxp1p/data/uup_ts.dbf';
SET NEWNAME FOR DATAFILE 13 to '/u01/dxp1p/data/newpage_ts.dbf';
ALLOCATE AUXILIARY CHANNEL aux1 DEVICE TYPE DISK;
ALLOCATE AUXILIARY CHANNEL aux2 DEVICE TYPE DISK;
DUPLICATE TARGET DATABASE for standby
nofilenamecheck
dorecover;
exit
==========================
Oinstall is a group.   I am not sure to use oinstall as a user?

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' >>>>*

File rename on rman duplicate

Oracle 11.2.0.2 SE-One 64-bit
Oracle Linux 5.6 x86-64
Question I had never considered. When performing an rman duplicate database with no NEWNAME parameters in sight, how does rman know how to set new names? There is something more than just the init parm “db_create_file_dest”.
The setup:
Server SRVPRD,
- ASM instance
- database DBPRD , has files in diskgroups SAN and SMALL
Server SRVDEV
- ASM instance
- database DBSTG, has files in diskgroups LARGE and SMALL
- database DBDEV, has files in diskgroups DEV_LARGE and DEV_SMALL
Shell script on SRVDEV to replicate DBPRD to DBSTG.   Script ftp’s the rman backups from SRVPRD, shuts down the instance DBSTG, deletes all of its files using asmcmd commands, then executes the following:
echo "connect catalog rman/********@rmcat"       > /backup/dbstgvb/dbstgvb_refresh.rman
echo "connect target sys/********@srvprd"       >> /backup/dbstgvb/dbstgvb_refresh.rman
echo "connect auxiliary /"                      >> /backup/dbstgvb/dbstgvb_refresh.rman
echo "run {"                                    >> /backup/dbstgvb/dbstgvb_refresh.rman
echo "set until time \"to_date('`date +%Y-%m-%d` 12:38:00','YYYY-MM-DD hh24:mi:ss')\";" >> /backup/dbstgvb/dbstgvb_refresh.rman
echo "duplicate target database to DBSTGVB;"    >> /backup/dbstgvb/dbstgvb_refresh.rman
echo "}"                                        >> /backup/dbstgvb/dbstgvb_refresh.rman
$ORACLE_HOME/bin/rman < /backup/dbstgvb/dbstgvb_refresh.rman
It runs perfectly and the files that were in the +SAN diskgroup in prod are correctly placed in +LARGE, and the files that were in +SMALL are correctly placed in +SMALL.
Now a new requirement to start doing the same for DBDEV. Made a copy of the script and changed all references from DBSTG to DBDEV. Equivalent changes in the string of asmcmd commands that delete the files, specifying the correct specific disk groups.
With this one, instead of mapping files from the two disk groups in DBPRD to the two diskgroups in DBDEV, they all get put into the one disk group +DEV_SMALL.
On DBSTG, we see
SQL> show parameter db_create_file_dest
NAME TYPE VALUE
db_create_file_dest     string +SMALL
and the rman log output of the replication includes this:
database mounted
contents of Memory Script:
   set until scn 2984496;
   set newname for datafile 1 to
"+SMALL/dbstgvb/system01.dbf";
   set newname for datafile 2 to
"+SMALL/dbstgvb/sysaux01.dbf";
   set newname for datafile 3 to
"+SMALL/dbstgvb/undotbs01.dbf";
   set newname for datafile 4 to
"+SMALL/dbstgvb/users01.dbf";
   set newname for datafile 5 to
"+LARGE/dbstgvb/perfstat_01.dbf";
   set newname for datafile 6 to
"+LARGE/dbstgvb/dw_tbs1.dbf";
   restore
   clone database
executing Memory Script
On DBDEV we see
SQL> show parameter db_create_file_dest
NAME TYPE VALUE
db_create_file_dest     string +DEV_SMALL
and the rman log output of the replication includes this:
database mounted
contents of Memory Script:
   set until scn 2984496;
   set newname for clone datafile 1 to new;
   set newname for clone datafile 2 to new;
   set newname for clone datafile 3 to new;
   set newname for clone datafile 4 to new;
   set newname for clone datafile 5 to new;
   set newname for clone datafile 6 to new;
   restore
   clone database
executing Memory Script
So, I am missing exactly how it is that in the replicate to DBSTG, it is able to correctly identify that files coming from prod diskgroup SAN correctly mapped to diskgroup LARGE? And further, why that mechanism did not work to map to +DEV_LARGE when replicating to DBDEV. In DBDEV it seems to be controlled entirely by db_create_file_dest, but in DBSTG there seems to be something that I am missing that allows the greater complexity of mapping two diskgroups.

Interesting side observation
In making sure all files ended up in the correct location I started noticing differences in the FQFN from the source db to the target.   Doing an asmcmd 'ls -l' on both systems, I discovered things like this:
On the source db, we have
DW_TBS1.dbf => +SAN/DBPRD/DATAFILE/DW_TBS.278.755044731
while on the target it came out
dw_tbs1.dbf => +LARGE/DBSTG/DATAFILE/DW.259.821974713
or
STAGE_CUST_ACCT_I1.ora => +SAN/DBPRD/DATAFILE/STAGE_CUST_ACCT_I.262.754925519
vs
stage_cust_acct_i1.ora => +LARGE/DBSTG/DATAFILE/STG_CUST_ACCT_IDX.266.822009311
Obviously not an operational problem, but a curiosity about the algorithm to generate the base part of the FQFN, and why it generated different names on different systems.

RMAN-00558: error encountered while parsing input commands

Hi,
on 12C on Win 2008
as said in documentation :
@ (at sign)
Example 2-2 Running a Command File Within RMAN
This example shows how you can execute a command file from the RMAN prompt and from within a RUN command. User-entered text appears in bold.
RMAN> @backup_db.rman
I do as follows to run a script to back up :
RMAN> @C:\scripts\RMAN\al_backup_full_cdb.rman LOG=C:\scripts\logs\al_backup_full_log
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "log": expecting one of: "double-quoted-string, identifier, integer, single-quoted-string"
RMAN-01007: at line 1 column 1 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: "double-quoted-string, identifier, integer, single-quoted-string"
RMAN-01007: at line 0 column 1 file: standard input
Thank you.

user10274093 wrote:
yes thank you. Like this :
@C:\scripts\RMAN\al_backup_full_cdb.rman
But how to have a log file ?
You can not use the log= clause *inside* rman, you can only use it on the shell prompt *outside* rman.

Oracle 9i RMAN backup filling up all disk and failing at the very end

Hello to all and thank you in advance for any input from any of you.
I am new in oracle and the only one in my company with a little bit of oracle knowledge, which is not a whole lot.
I inherited a few servers (Linux and Windows based). We mostly run all our production environment on a Linux box hosting oracle 10g release 10.2.0.1 but we had a legacy application server that still runs on 9i release 9.2.0.1.0. This server is a windows 2003 box, the previous DBA or someone else with admin rights to this machine compressed the whole drive where oracle resides, when I started summarying the oracle assets, I saw this server with no backups scheduled and a compressed disk with very limited space after this compression, only 13 GB left, the database if uncompressed would definitively filled up all the disk. The machine is in used and cannot be taken down for more than a couple of hours. We tried adding another disk but the machine only accept it as a hot spare. The database is in archive mode, when I tried to run a RMAN backup, it start filling up the database drive until it's empty and it crashes the whole machine, it seems like the buffer is growing and growing until it fills up the whole drive. The only way to get the server up and running again is to reboot the machine since the server is more than 6 years old we are not please with this action because we are afraid the machine would go south in one of those reboots.
Has anyone heard of similar issues when running RMAN on a compressed drive? Can the compressed disk have any involvement in this kind of odd behaviour? I tried running the backup in debug mode and creating a log in a different disk (the one where the backup is going to) and still the same issue. Again any help is much appreciate,
Sincerely,
Alex

Sybrand,
Thank you for your fast response, I am going to use your previous post to answer one by one your question,
1 The Oracle binaries --- on a compressed drive > Yes
2 The Oracle database control files redo log files and datafiles on that same compressed drive? > Yes
3 The archived redo log ditto? > Yes
I know for a fact (as I have been using that in 9i) you can create a RMAN backup on a compressed drive, and you can have your archived redo go to a compressed drive. No problemo! > Excellent good news!!!
But I would never touch the data files. Please note backup sets are multiplexed files consisting of multiple datafiles, so RMAN would need to do some calculations to decompress several blocks at the same time and to calculate a new block and compress it.
Do you have enough space to:
a) (preferred) to make datafile copies instead of a backup >
Not in the drive that hosts the oracle instance but yes on an external usb drive (1TB) I attached to use as a backup repository, maybe this is why I am having these issues. I only have 13 GB left on that drive where the oracle instance resides (actually as I explained in a previous reply to Mark, the server only has 3 slots for disks, two of them as configured as RAID 1 and the other is a hot spare because the RAID configuration manager cannot can only added as hot-spare. The raided disk are partitioned in two, one small partition is for the OS and the other is for the oracle instance). When you said make a copy of the datafiles, I assumed you are talking about doing manual backups, and copying the database after using using "alter tablespace tablespace_name begin backup; then copy the file; alter tablespace tablespace_name end backup;
b) use filesperset=1 on the backup command line, so the multiplexing (and associated calculations) stop. I have not tried the option of fileperset yet but I can tryi it and see if that helps.
Can you post the last few lines of the RMAN log where RMAN bombs out? Note: the last few lines. Not all of it, or you must send some paracetamol in conjunction! >
When I ran the debug option, I stopped the backup at less than 20% because I didn't want to reboot the system in the middle of the production time, the backup consumed at least 3 GB during the time was running. The times I ran the RMAN backup I didn't used the debug option so I don't have a log long enough to send unless you want the last few lines of what I have.
Thanks again for your input,
Sincerely,
Alex

RMAN backup shell script

Hi,
I am trying to setup incremental backup shell script to run anutomatic every night. I am getting below errors when I run script. What am I missing here?
oradev]/home/oradev ./RMAN_DEV_incr1.sh
RMAN> exit
./RMAN_DEV_incr1.sh[13]: CONFIGURE: not found [No such file or directory]
./RMAN_DEV_incr1.sh[14]: CONFIGURE: not found [No such file or directory]
./RMAN_DEV_incr1.sh[15]: CONFIGURE: not found [No such file or directory]
./RMAN_DEV_incr1.sh[16]: run: not found [No such file or directory]
./RMAN_DEV_incr1.sh[17]: ALLOCATE: not found [No such file or directory]
./RMAN_DEV_incr1.sh[18]: CROSSCHECK: not found [No such file or directory]
./RMAN_DEV_incr1.sh[19]: BACKUP: not found [No such file or directory]
./RMAN_DEV_incr1.sh[20]: sql: not found [No such file or directory]
./RMAN_DEV_incr1.sh[21]: BACKUP: not found [No such file or directory]
./RMAN_DEV_incr1.sh[22]: BACKUP: not found [No such file or directory]
./RMAN_DEV_incr1.sh[23]: CROSSCHECK: not found [No such file or directory]
./RMAN_DEV_incr1.sh[24]: DELETE: not found [No such file or directory]
./RMAN_DEV_incr1.sh[25]: DELETE: not found [No such file or directory]
./RMAN_DEV_incr1.sh[26]: RELEASE: not found [No such file or directory]
./RMAN_DEV_incr1.sh: line 26: syntax error at line 27: `}' unexpected
==============
Here is copy of my shell script:
#!/bin/ksh
# Declare your ORACLE environment variables
export ORACLE_SID=DEV
export ORACLE_BASE=/d01/oracle/DEV
export ORACLE_HOME=/d01/oracle/DEV/db/tech_st/11.1.0
export PATH=$PATH:${ORACLE_HOME}/bin
# Start the rman commands
rman target / msglog=/d01/RMAN/logs/rman_INCR_1_${ORACLE_SID}_${DATE}.log
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/d01/RMAN/autobackup_control_file%F';
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
run {
ALLOCATE CHANNEL RMAN_BACK_CH01 TYPE DISK;
CROSSCHECK BACKUP;
BACKUP AS COMPRESSED BACKUPSET INCREMENTAL LEVEL 1 DATABASE FORMAT '/d01/RMAN/databasefiles_%d_%u_%s_%T';
sql 'ALTER SYSTEM ARCHIVE LOG CURRENT';
BACKUP AS COMPRESSED BACKUPSET ARCHIVELOG ALL FORMAT '/d01/RMAN/archivelogs_%d_%u_%s_%T' DELETE INPUT;
BACKUP AS COMPRESSED BACKUPSET CURRENT CONTROLFILE FORMAT '/d01/RMAN/controlfile_%d_%u_%s_%T';
CROSSCHECK BACKUP;
DELETE NOPROMPT OBSOLETE;
DELETE NOPROMPT EXPIRED BACKUP;
RELEASE CHANNEL RMAN_BACK_CH01;
EXIT;
EOF
#

Hi,
You missed to redirect the rman command
rman target / msglog=/d01/RMAN/logs/rman_INCR_1_${ORACLE_SID}_${DATE}.log <<eof
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/d01/RMAN/autobackup_control_file%F';
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
run {
ALLOCATE CHANNEL RMAN_BACK_CH01 TYPE DISK;
CROSSCHECK BACKUP;
BACKUP AS COMPRESSED BACKUPSET INCREMENTAL LEVEL 1 DATABASE FORMAT '/d01/RMAN/databasefiles_%d_%u_%s_%T';
sql 'ALTER SYSTEM ARCHIVE LOG CURRENT';
BACKUP AS COMPRESSED BACKUPSET ARCHIVELOG ALL FORMAT '/d01/RMAN/archivelogs_%d_%u_%s_%T' DELETE INPUT;
BACKUP AS COMPRESSED BACKUPSET CURRENT CONTROLFILE FORMAT '/d01/RMAN/controlfile_%d_%u_%s_%T';
CROSSCHECK BACKUP;
DELETE NOPROMPT OBSOLETE;
DELETE NOPROMPT EXPIRED BACKUP;
RELEASE CHANNEL RMAN_BACK_CH01;
EXIT;
EOF
#

RMAN log

Similar Messages

Maybe you are looking for