1st RMAN backup database plus archivelog fails

Hi
I've just setup RMAN on Oracle 11g within a two node cluster environment.
I have completed the following:
* Created a recovery catalog
* Registed Database
* Configured retention policy window of 7 days
* Configured default device type to disk
* configured controlfile autobackup on;
* configured device type disk backup type to compressed backupset
* configured channel device type disk format
* validated database
* backup database plus archivelog and I received the following error,
RMAN> backup database plus archivelog;
Starting backup at 24/07/2008 17:37:17
current log archived
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup plus archivelog command at 07/24/2008 17:37:20
RMAN-06059: expected archived log not found, lost of archived log compromises re coverability
ORA-19625: error identifying file /u01/app/product/admin/RAC/arc/rac2_2_4_660689 305.arc
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
On node 2 I can list the file:
SQL> !ls -lt
total 4120
-rw-rw---- 1 rac dba 14336 Jul 24 17:18 rac2_2_5_660689305.arc
-rw-rw---- 1 rac dba 4196352 Jul 24 17:13 rac2_2_4_660689305.arc
SQL>

Read the chapter
http://download.oracle.com/docs/cd/B28359_01/rac.111/b28254/rman.htm#i474611
The node that is doing backups must be configured to have access to archivelogs on all the nodes.
See "RMAN Archiving Configuration Scenarios" -> "Noncluster File System Local Archiving Scheme".

Similar Messages

I can't backup database plus archivelog

Hi.
I lost few previous archivelogs, and can't run "backup database plus archivelog;".
That's what I got from rman:
RMAN> backup database plus archivelog;
Starting backup at 12-APR-09
current log archived
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup plus archivelog command at 04/12/2009 13:06:14
RMAN-06059: expected archived log not found, lost of archived log compromises recoverability
ORA-19625: error identifying file /u01/app/oracle/backup/ORCL/archivelog/2008_08_04/o1_mf_1_11_49f37bn1_.arc
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3
How to fix it ?
Hi
Run commands:
RMAN> CROSSCHECK ARCHIVELOG ALL;
RMAN> DELETE NOPROMPT EXPIRED ARCHIVELOG ALL;
And then "backup database plus archivelog;"
Edited by: val75 on Apr 12, 2009 11:31 AM

After deleting expired archivelogs, backup is working fine...
RMAN>delete noprompt expired archivelog all;
RMAN>crosscheck archivelog all;
RMAN>backup database plus archivelog;
Actually, what is doing while issuing "crosscheck archivelog all" command????
thanks

Error in recovery after BACKUP DATABASE PLUS ARCHIVELOG

Hi,
With Oracle 9.2.0.6 on Unix Aix 5, I made:
rman ...
RUN
ALLOCATE CHANNEL disk1 DEVICE TYPE DISK FORMAT '/base/tempora/%U';
BACKUP DATABASE PLUS ARCHIVELOG;
Copy files from /base/tempora/% to another server in a directory with the same name.
Recreate the pfile and directory structure, and then
rman...
RUN
ALLOCATE CHANNEL disk1 DEVICE TYPE DISK FORMAT '/base/tempora/%U';
restore controlfile to '/base/rcterefo/oracle/o1_mf_19xw2mvb_.ctl';
restore controlfile from '/base/rcterefo/oracle/o1_mf_19xw2mvb_.ctl';
sql 'alter database mount';
restore database;
recover database;
sql 'alter database open resetlogs';
release channel disk1;
But rman fails at -> recover database; by asking an archive log 6 months old (and not in the backupset):
ORA-00279: change 1224563589 generated at 02/09/2006 16:29:46 needed for thread
1
ORA-00289: suggestion : /base/.../arch/arch0000001819.arc
ORA-00280: change 1224563589 for thread 1 is in sequence #1819
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00308: cannot open archived log '/base/.../arch/arch0000001819.arc'
ORA-27037: unable to obtain file status
IBM AIX RISC System/6000 Error: 2: No such file or directory
Additional information: 3
Original base seems to works fine (can be stoped and restarted).
I thought that this BACKUP DATABASE PLUS ARCHIVELOG would contain in itself all the data needed to restart the database. Database has been stopped and restarted last week with no problem and I regularly do full backup with RMAN and TSM (we are testing now backups without TSM for a spacial case).
Has someone an idea of what's wrong?
Thanks

Hi,
Thanks for taking care of my problem.
When I try to do a set until sequence..., the RESTORE CONTROLFILE fails, telling it has nothing to restore. I think this is the same kind of problem I encounter with the full restore.
Aniway, the restore being good, i try to finish the recover and it fails, asking for a very old archive. Is it possible a transaction to be active after so much time?
In fact, I just decovered a file is in RECOVER status. I did an :
alter database datafile '...' offline drop;
since that, the recover is ok, from oracle (not rman):
recover database using backup controlfile until cancel;
Thanks again to everyone.
Regards.

Backup database plus archivelog

Hi
I am using 10.2.0.3. What is the difference between "backup database plus archivelog" and "backup database"?
I deleted the archive logs after disabling the archive log option. How to fix the below problem? thank you
When I do backup database plus archivelog;
ORACLE error from target database:
ORA-00258: manual archiving in NOARCHIVELOG mode must identify log
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=869 devtype=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: sid=434 devtype=DISK
archived log /export/home/oracle/archivelog/2008_06_23/o1_mf_1_82_45ymxtqd_.arc not found or out of sync with catalog
trying alternate file for archivelog thread 1, sequence 82
archived log /export/home/oracle/archivelog/2008_06_23/o1_mf_1_83_45ymxwcs_.arc not found or out of sync with catalog
trying alternate file for archivelog thread 1, sequence 83
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup plus archivelog command at 02/16/2009 11:48:41
RMAN-06059: expected archived log not found, lost of archived log compromises re
coverability
ORA-19625: error identifying file /export/home/oracle/archivelog/2008_06_23/o1_mf_1_84_45ymxxyf_.arc
ORA-27037: unable to obtain file status
Intel SVR4 UNIX Error: 2: No such file or directory
Additional information: 3

Even if you've switched your database to NOARCHIVELOG mode, the ArchiveLogs that were generated earlier are still "known" as they are still cataloged in the control file (a query on V$ARCHIVED_LOG would show them).
As you are running NOARCHIVELOG, you really do not need to do BACKUP DATABASE PLUS ARCHIVELOG;
Your backup would be in MOUNT but not OPEN state so there would be no transactions.
If you really want to "clear" those older archivelogs so that RMAN doesn't attempt to backup them, you need to run these commands in RMAN :
Crosscheck Archivelog All;
Delete Expired ArchiveLog All;The first command will verify the controlfile records against the files actually present on disk and mark as "Expired" all those they do not exist on disk. The second command will "delete" them in that RMAN will no longer look for them.
Hemant K Chitale
http://hemantoracledba.blogspot.com

Should I keep media after "BACKUP DATABASE PLUS ARCHIVELOG"?

Hi there,
If I do full backup like this ...
BACKUP DATABASE PLUS ARCHIVELOG
... do I have to keep copy of media (database files)? I am under impression that as long as my recovery window falls between "BACKUP DATABASE PLUS ARCHIVELOG" and NOW ... I don't have to keep media files.
Am I right or wrong?
Thanks to all answers!

Sure..if you don't need to restore back to one of the previous backups, then they are no longer needed.
Configuring a retention policy will handle this maintenance for you automatically.
However, some people will keep them around as a fall back if something should happen to their most recent backup. It depends on your paranoia level and amount of disk/tape space that you have.

Newbie.. is 'backup database plus archivelog...' needed?

On my Oracle 11.1, I'm performing full backup with command:
backup incremental level 0 database plus archivelog delete input tag LEVEL_0_INC;Since this database is not in flashback mode, I'm wondering is it needed to backup archivelogs together with datafiles?
could I done it without achivelogs and to delete them after that?
regards

799165 wrote:
On my Oracle 11.1, I'm performing full backup with command:
backup incremental level 0 database plus archivelog delete input tag LEVEL_0_INC;Since this database is not in flashback mode, I'm wondering is it needed to backup archivelogs together with datafiles?
could I done it without achivelogs and to delete them after that?
regardsYou need to have archived redo log files with your backup in order to perform a complete recovery

RMAN backup in no archivelog mode

what are possible ways to backup the database which is in no archivelog mode using RMAN
regards,
Sakthivel
Edited by: SAKTHIVEL on Jul 22, 2011 1:02 AM

Hi;
Please check:
backup in noarchivelog mode using RMAN
backup in noarchivelog mode using RMAN
Regard
Helios

Rman backup excluding missing archivelogs

Please help me in the following scenario :
I have 2 months old archivelog in my disk..am taking full rman database backup daily at night..but not the archivelog. once I moved some of my archivelog files to another mount point as the archivelog destination is almost filled.
when i try to take the backup of archivelogs,I got the message
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 11/24/2008 23:16:23
RMAN-06059: expected archived log not found, lost of archived log compromises recoverability
ORA-19625: error identifying file /archv/PROD/PROD1_234_662754021.arc
ORA-17503: ksfdopn:4 Failed to open file /archv/PROD/PROD1_234_662754021.arc
ORA-17500: ODM err:File does not exist
which is expected, since I moved the file /archv/PROD/PROD1_234_662754021.arc to another location inorder to have that as a temp.solution ..
now , I have all my archivelogs starting from nov-3 till date in the log_archive_dest_1
RMAN> run
ALLOCATE CHANNEL ch00 TYPE 'SBT_TAPE';
ALLOCATE CHANNEL ch01 TYPE 'SBT_TAPE';
BACKUP FORMAT 'arch_u%u_s%s_p%p_t%t'
Archivelog
FROM TIME "TO_DATE('11-03-2008:23:46:15', 'MM-DD-YYYY:HH24:MI:SS')"
UNTIL TIME "TO_DATE('11-24-2008:23:46:15', 'MM-DD-YYYY:HH24:MI:SS')"
DELETE INPUT;
release channel ch00;
release channel ch01;
now, is there anyway i can include the old archivelogs in the rman by restoring from the temporay location and taking backup. I know that I have a full database backup, but I need to have my old archivelogs also included in that ? or () does backup arhcivelog all will give any error message now ?(ORA-17500: ODM err:File does not exist)
Any way ?
Kai

You need to unregister the old archivelog path and register the new archivelog path for the backup to be successful without changing the backup command.
Assuming you're using 9i or 10g (although 'SBT_TAPE' hints 8i), you can either
1. use the 'change' and 'catalog' command to unregister the archivelogs from the old place and re-register the archivelogs in the new place:
change archivelog 'oldpath\archivelogname' unregister';
catalog archivelog 'newpath\archivelogname';
or
change archivelog 'oldpath\archivelogname' unregister';
catalog start with 'newpath';
2. Not include the archivelog clause in the backup (not recommended)
I generally backup archivelogs at least 2-3 times before deleting them and make sure they are on seperate tapes (if possible). Deleting on input has one point of failure.
References: http://download.oracle.com/docs/cd/B19306_01/backup.102/b14194/toc.htm

Rman backup with no archivelog mode

Hi Friend,
I did this backup many times before, to backup a test db which is not in archivelog mode.
My procedure are the following:
$ rman target /
rman> run {
shutdown immediate;
startup mount;
backup format '/u02/RMAN/%d_LVL0_%T_%u_s%s_p%p' database;
delete obsolete;
But strange I got now error:
ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
Thanks a lot

Hi,
Paste the snap shot of what you actually doing and what error messages are coming. That will help to analyze the problem.
This basically happens when your shutdown is not normal or clean.
One way is to again startup the database and then issue shutdown Normal.
Regards,
Edited by: Navneet on Sep 30, 2008 3:21 AM

Rman backup on physical standby database without cancelling MRP

Hi all,
Could anyone share, is this possible to take RMAN backup on physical standby database without cancelling MRP process.
regarrds,

Hi,
On Standby Side:
SQL> alter database mount;
Database altered.
SQL> alter database recover managed standby database using current logfile disconnect from session;
Database altered.
SQL> select max(Sequence#) from v$archived_log;
MAX(SEQUENCE#)
        405
SQL> select max(Sequence#) from v$archived_log where applied='YES';
MAX(SEQUENCE#)
        404
SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
[oracle@oel62-x64 Desktop]$ rman target /
Recovery Manager: Release 11.2.0.3.0 - Production on Tue May 21 15:31:43 2013
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
connected to target database: ADMDB (DBID=4063877183, not open)
RMAN> backup database plus archivelog delete all input;
Starting backup at 21-MAY-13
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=32 device type=DISK
channel ORA_DISK_1: starting archived log backup set
channel ORA_DISK_1: specifying archived log(s) in backup set
input archived log thread=1 sequence=390 RECID=391 STAMP=815416638
input archived log thread=1 sequence=391 RECID=392 STAMP=815421952
input archived log thread=1 sequence=392 RECID=393 STAMP=815422343
input archived log thread=1 sequence=393 RECID=394 STAMP=815422434
input archived log thread=1 sequence=394 RECID=395 STAMP=815422570
input archived log thread=1 sequence=395 RECID=396 STAMP=815476598
input archived log thread=1 sequence=396 RECID=397 STAMP=815476615
input archived log thread=1 sequence=397 RECID=398 STAMP=815476645
input archived log thread=1 sequence=398 RECID=399 STAMP=815477471
input archived log thread=1 sequence=399 RECID=400 STAMP=815477475
input archived log thread=1 sequence=400 RECID=401 STAMP=815477628
input archived log thread=1 sequence=401 RECID=403 STAMP=815584146
input archived log thread=1 sequence=402 RECID=402 STAMP=815584137
input archived log thread=1 sequence=403 RECID=405 STAMP=816017446
*input archived log thread=1 sequence=404 RECID=404 STAMP=816017444*
*input archived log thread=1 sequence=405 RECID=406 STAMP=816017455*
channel ORA_DISK_1: starting piece 1 at 21-MAY-13
channel ORA_DISK_1: finished piece 1 at 21-MAY-13
piece handle=/u01/app/oracle/fast_recovery_area/stldb/STLDB/backupset/2013_05_21/o1_mf_annnn_TAG20130521T153202_8spm937d_.bkp tag=TAG20130521T153202 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:07
channel ORA_DISK_1: deleting archived log(s)
archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_14/o1_mf_1_390_8s48hfrp_.arc RECID=391 STAMP=815416638
archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_14/o1_mf_1_391_8s4fohwb_.arc RECID=392 STAMP=815421952
archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_14/o1_mf_1_392_8s4g1q0v_.arc RECID=393 STAMP=815422343
archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_14/o1_mf_1_393_8s4g4l8z_.arc RECID=394 STAMP=815422434
archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_14/o1_mf_1_394_8s4g8t9h_.arc RECID=395 STAMP=815422570
archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_15/o1_mf_1_395_8s631622_.arc RECID=396 STAMP=815476598
archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_15/o1_mf_1_396_8s631qjj_.arc RECID=397 STAMP=815476615
archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_15/o1_mf_1_397_8s632od8_.arc RECID=398 STAMP=815476645
archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_15/o1_mf_1_398_8s63whqc_.arc RECID=399 STAMP=815477471
archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_15/o1_mf_1_399_8s63wly4_.arc RECID=400 STAMP=815477475
archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_15/o1_mf_1_400_8s641d8j_.arc RECID=401 STAMP=815477628
archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_16/o1_mf_1_401_8s9d21jk_.arc RECID=403 STAMP=815584146
archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_16/o1_mf_1_402_8s9d1skv_.arc RECID=402 STAMP=815584137
archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_21/o1_mf_1_403_8spm6p4h_.arc RECID=405 STAMP=816017446
archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_21/o1_mf_1_404_8spm6mqj_.arc RECID=404 STAMP=816017444
RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process
archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_21/o1_mf_1_405_8spm6yg0_.arc thread=1 sequence=405
Finished backup at 21-MAY-13
Starting backup at 21-MAY-13
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00001 name=/u01/app/oracle/oradata/stldb/system01.dbf
input datafile file number=00002 name=/u01/app/oracle/oradata/stldb/sysaux01.dbf
input datafile file number=00005 name=/u01/app/oracle/oradata/stldb/example01.dbf
input datafile file number=00003 name=/u01/app/oracle/oradata/stldb/undotbs01.dbf
input datafile file number=00006 name=/u01/app/oracle/oradata/stldb/appdata01.dbf
input datafile file number=00004 name=/u01/app/oracle/oradata/stldb/users01.dbf
channel ORA_DISK_1: starting piece 1 at 21-MAY-13
channel ORA_DISK_1: finished piece 1 at 21-MAY-13
piece handle=/u01/app/oracle/fast_recovery_area/stldb/STLDB/backupset/2013_05_21/o1_mf_nnndf_TAG20130521T153213_8spm9fnc_.bkp tag=TAG20130521T153213 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:02:15
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
including current SPFILE in backup set
channel ORA_DISK_1: starting piece 1 at 21-MAY-13
channel ORA_DISK_1: finished piece 1 at 21-MAY-13
piece handle=/u01/app/oracle/fast_recovery_area/stldb/STLDB/backupset/2013_05_21/o1_mf_ncsnf_TAG20130521T153213_8spmfqxf_.bkp tag=TAG20130521T153213 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
Finished backup at 21-MAY-13
Starting backup at 21-MAY-13
using channel ORA_DISK_1
specification does not match any archived log in the repository
backup cancelled because there are no files to backup
Finished backup at 21-MAY-13
RMAN> exit
Recovery Manager complete.
[oracle@oel62-x64 Desktop]$ sqlplus / as sysdba
SQL*Plus: Release 11.2.0.3.0 Production on Tue May 21 15:34:42 2013
Copyright (c) 1982, 2011, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> select max(Sequence#) from v$archived_log;
MAX(SEQUENCE#)
        405
SQL> select max(Sequence#) from v$archived_log where applied='YES';
MAX(SEQUENCE#)
        404
SQL> There have no problem, backup database when MRP is running. But if you want delete, then you are getting RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process.
And will not delete this archived log, because it is needed for standby or upstream capture process.
Updated
When MRP stoped
SQL> alter database recover managed standby database cancel;
Database altered.
SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
[oracle@oel62-x64 Desktop]$ rman target /
Recovery Manager: Release 11.2.0.3.0 - Production on Tue May 21 15:46:07 2013
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
connected to target database: ADMDB (DBID=4063877183, not open)
RMAN> backup database plus archivelog delete all input;
Starting backup at 21-MAY-13
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=24 device type=DISK
channel ORA_DISK_1: starting archived log backup set
channel ORA_DISK_1: specifying archived log(s) in backup set
input archived log thread=1 sequence=405 RECID=406 STAMP=816017455
channel ORA_DISK_1: starting piece 1 at 21-MAY-13
channel ORA_DISK_1: finished piece 1 at 21-MAY-13
piece handle=/u01/app/oracle/fast_recovery_area/stldb/STLDB/backupset/2013_05_21/o1_mf_annnn_TAG20130521T154617_8spn3s9w_.bkp tag=TAG20130521T154617 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
channel ORA_DISK_1: deleting archived log(s)
archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_21/o1_mf_1_405_8spm6yg0_.arc RECID=406 STAMP=816017455
Finished backup at 21-MAY-13
Starting backup at 21-MAY-13
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00001 name=/u01/app/oracle/oradata/stldb/system01.dbf
input datafile file number=00002 name=/u01/app/oracle/oradata/stldb/sysaux01.dbf
input datafile file number=00005 name=/u01/app/oracle/oradata/stldb/example01.dbf
input datafile file number=00003 name=/u01/app/oracle/oradata/stldb/undotbs01.dbf
input datafile file number=00006 name=/u01/app/oracle/oradata/stldb/appdata01.dbf
input datafile file number=00004 name=/u01/app/oracle/oradata/stldb/users01.dbf
channel ORA_DISK_1: starting piece 1 at 21-MAY-13
channel ORA_DISK_1: finished piece 1 at 21-MAY-13
piece handle=/u01/app/oracle/fast_recovery_area/stldb/STLDB/backupset/2013_05_21/o1_mf_nnndf_TAG20130521T154618_8spn3v4f_.bkp tag=TAG20130521T154618 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:01:16
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
including current SPFILE in backup set
channel ORA_DISK_1: starting piece 1 at 21-MAY-13
channel ORA_DISK_1: finished piece 1 at 21-MAY-13
piece handle=/u01/app/oracle/fast_recovery_area/stldb/STLDB/backupset/2013_05_21/o1_mf_ncsnf_TAG20130521T154618_8spn6779_.bkp tag=TAG20130521T154618 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
Finished backup at 21-MAY-13
Starting backup at 21-MAY-13
using channel ORA_DISK_1
specification does not match any archived log in the repository
backup cancelled because there are no files to backup
Finished backup at 21-MAY-13
RMAN> Apply process is stopped and new redo received from primary.
SQL> select max(Sequence#) from v$archived_log;
MAX(SEQUENCE#)
        407
SQL> select max(Sequence#) from v$archived_log where applied='YES';
MAX(SEQUENCE#)
        405
SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
[oracle@oel62-x64 Desktop]$ rman target /
Recovery Manager: Release 11.2.0.3.0 - Production on Tue May 21 15:49:28 2013
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
connected to target database: ADMDB (DBID=4063877183, not open)
RMAN> backup database plus archivelog delete all input;
Starting backup at 21-MAY-13
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=32 device type=DISK
channel ORA_DISK_1: starting archived log backup set
channel ORA_DISK_1: specifying archived log(s) in backup set
input archived log thread=1 sequence=406 RECID=407 STAMP=816018527
input archived log thread=1 sequence=407 RECID=408 STAMP=816018530
channel ORA_DISK_1: starting piece 1 at 21-MAY-13
channel ORA_DISK_1: finished piece 1 at 21-MAY-13
piece handle=/u01/app/oracle/fast_recovery_area/stldb/STLDB/backupset/2013_05_21/o1_mf_annnn_TAG20130521T154937_8spnb1y3_.bkp tag=TAG20130521T154937 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
channel ORA_DISK_1: deleting archived log(s)
RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process
archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_21/o1_mf_1_406_8spn8hkn_.arc thread=1 sequence=406
RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process
archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_21/o1_mf_1_407_8spn8l69_.arc thread=1 sequence=407
Finished backup at 21-MAY-13
Starting backup at 21-MAY-13
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00001 name=/u01/app/oracle/oradata/stldb/system01.dbf
input datafile file number=00002 name=/u01/app/oracle/oradata/stldb/sysaux01.dbf
input datafile file number=00005 name=/u01/app/oracle/oradata/stldb/example01.dbf
input datafile file number=00003 name=/u01/app/oracle/oradata/stldb/undotbs01.dbf
input datafile file number=00006 name=/u01/app/oracle/oradata/stldb/appdata01.dbf
input datafile file number=00004 name=/u01/app/oracle/oradata/stldb/users01.dbf
channel ORA_DISK_1: starting piece 1 at 21-MAY-13
channel ORA_DISK_1: finished piece 1 at 21-MAY-13
piece handle=/u01/app/oracle/fast_recovery_area/stldb/STLDB/backupset/2013_05_21/o1_mf_nnndf_TAG20130521T154939_8spnb3f5_.bkp tag=TAG20130521T154939 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:01:15
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
including current SPFILE in backup set
channel ORA_DISK_1: starting piece 1 at 21-MAY-13
channel ORA_DISK_1: finished piece 1 at 21-MAY-13
piece handle=/u01/app/oracle/fast_recovery_area/stldb/STLDB/backupset/2013_05_21/o1_mf_ncsnf_TAG20130521T154939_8spndhly_.bkp tag=TAG20130521T154939 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
Finished backup at 21-MAY-13
Starting backup at 21-MAY-13
using channel ORA_DISK_1
specification does not match any archived log in the repository
backup cancelled because there are no files to backup
Finished backup at 21-MAY-13
RMAN> I think, codes is understandable.
Regard
Mahir M. Quluzade
Edited by: Mahir M. Quluzade on May 21, 2013 3:36 PM

About RMAN backup !!!!

Dear Friends,
Let my production server running starts from 1st June .
In 15 june , I take the First rman full (or level0) backup using the command :
RMAN> backup database plus archivelog;
In 20 June I take 2nd rman full backup using : RMAN> backup database plus archivelog;
Again in 30 June , I take the Third(3rd) rman full (or level 0) backup using the command :
RMAN> backup database plus archivelog;
And also my rman policy set as :
CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
In the above scenario , I have the following questions :
1) When I take the Third(3rd) backup then is it the First RMAN backup goes to obsolete as per my rman policy ( RETENTION POLICY TO REDUNDANCY 1) ?
2) Is the above all RMAN backup make a link between them ?
3) If my first RMAN backup goes to obsolete and I have to delete the First RMAN backup , then which types of problem I face ? Can I go to previous state(suppose I need to back in 1st June) of my server if I delete First rman backup ?
4) when I take 3rd rman full backup , then is it all information from 1st january of the server are stored in the 3rd backup ? i.e., is the 3rd rman backup stores all the previous two rman backups information ?so that If I delete the previous two backup , then I get all information form 3rd rman backup .what is the actual scenario ......
plz help me to make clear concept about it .......
thx in advance .....

1) When I take the Third(3rd) backup then is it the First RMAN backup goes to obsolete as per my rman policy ( RETENTION POLICY TO REDUNDANCY 1) ?The REDUNDANCY parameter of the CONFIGURE RETENTION POLICY command specifies how many backups of each datafile and control file that RMAN should keep. In other words, if the number of backups for a specific datafile or control file exceeds the REDUNDANCY setting, then RMAN considers the extra backups as obsolete.So as in your case the redundancy is 1 so the 1st and 2nd backup are obsolete.
To check the obsolete backups run
rman> report obsolete;
To delete them
rman> delete obsolete;
Link:[http://download.oracle.com/docs/cd/B19306_01/backup.102/b14192/setup005.htm#BRBSC400]
Is the above all RMAN backup make a link between them ?I am not very much clear with the question.The RMAN information is stored in the controlfile.You can also create a new recovery catalog and register the target database. The RMAN repository records in the control file will be copied to the new recovery catalog.
when I take 3rd rman full backup , then is it all information from 1st january of the server are stored in the 3rd backup ? i.e., is the 3rd rman backup stores all the previous two rman backups information ?so that If I delete the previous two backup , then I get all information form 3rd rman backupThe 3rd RMAN backup will contain all the information of the DB from the very 1st day.You will get all the information in the 3rd rman backup as its a level 0 or what we say a FULL DATABASE BACKUP.If suppose the 3rd rman backup would have been a incremental backup, then you would have required a full backup, previous to the incremental one, so that after restoring the full backup, you restore the incremental to recover the DB completely.
Link:[http://download.oracle.com/docs/cd/B19306_01/backup.102/b14191/part1.htm#i996723]
[http://download.oracle.com/docs/cd/B19306_01/backup.102/b14192/bkup004.htm#BRBSC133]
Forgot to answer the 3rd question
3) If my first RMAN backup goes to obsolete and I have to delete the First RMAN backup , then which types of problem I face ? Can I go to previous state(suppose I need to back in 1st June) of my server if I delete First rman backup ?well, i am not very much sure , but i think is , if you have the 1st rman backup pieces physically present on the disk, you can catalog it and then use the rman command to restore the data from it of till 1st june.
To catalog the backup pieces use
rman> catalog backuppiece 'filename';
Link: [http://download.oracle.com/docs/cd/B19306_01/backup.102/b14192/maint007.htm]
HTH
Anand
Edited by: Anand... on Oct 15, 2008 10:51 AM

Rman backup on TEVOLI tape

Hi,
Can anybody help me.TSM tape configured for linux RAC oracle database for rman backups.once i start backup its giving me followng error.can anybody provide me help
Recovery Manager: Release 10.2.0.1.0 - Production on Fri Aug 18 20:49:36 2006
Copyright (c) 1982, 2005, Oracle. All rights reserved.
RMAN> connect target;
connected to target database: IPO (DBID=1999149714)
RMAN> BACKUP DATABASE PLUS ARCHIVELOG;
Starting backup at 18-AUG-06
current log archived
using target database control file instead of recovery catalog
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup plus archivelog command at 08/18/2006 20:50:19
ORA-19554: error allocating device, device type: SBT_TAPE, device name:
ORA-27000: skgfqsbi: failed to initialize storage subsystem (SBT) layer
Linux Error: 2534: Unknown system error
Additional information: 7011
ORA-19511: Error received from media manager layer, error text:
SBT error = 7011, errno = 2534, sbtopen: system error
RMAN>

Possible solution is:
The default path where TDPO looks at is '/usr/tivoli/tsm/client/api/bin64'
even if the file DSM.SYS exists in another directory.
The read permission of the file '/usr/tivoli/tsm/client/api/bin64/dsm.sys'
was incorrect:
-rw-r----- i.e. "OTHERS" which is Oracle isn't allowed to read the
file /usr/tivoli/tsm/client/api/bin64/dsm.sys
After changing permissions on /usr/tivoli/tsm/client/api/bin64/dsm.sys in order
to allow oracle to use it then the backup works fine.
$ chmod +r /usr/tivoli/tsm/client/api/bin64/dsm.sys
The problem is on the TSM side. If the solution does not work you have to check TSM logs for further error messages.
Werner

RMAN-20021: database not set

Hi All,
We have database Oracle9i Enterprise Edition Release 9.2.0.1.0 - Production running on RedHat edition 4.
I have done incomplete recovery of database to previous incarnation using autobackup controlfile with RMAN, opened database with resetlogs everything went fine. database is up and running. Now when i tried to take backup of the database i have received following error
Starting backup at 29-APR-08
current log archived
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 04/29/2008 19:21:21
RMAN-20021: database not set
RMAN> set DBID=279496673
executing command: SET DBID
RMAN> backup database plus archivelog ;
Starting backup at 29-APR-08
current log archived
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 04/29/2008 19:22:46
RMAN-20021: database not set
RMAN> backup database;
Starting backup at 29-APR-08
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 04/29/2008 19:23:48
RMAN-20021: database not set
RMAN-06031: could not translate database keyword
Can anyone please advice as what is reason behind this error. searched on the internet but nothing found rather than contacting oracle support
Regards
Vinay

Sorry forgot to add some information.
before recovery we were using recovery catalog which was on the same database.
while doing recovery restored controlfile by
RMAN> restore controlfile from '/oracle/oradata/envdvp/backup/controlfile/C-279496673-20080429-18';
and then performed restore and recovery operation

10g rman database and archivelogs backup with multipled archlog destination

I would like to use the 10g database and archivelogs backup statetement
backup database plus archivelog;
I would like to restrict the location of the archivelogs backed out as I am multiplexing the
archivelogs
I did not find a LIKE statement and the backup database plus archivelog
Did i miss something
patrick boulay

I meant backup
I just want to restrict rman form backing up the two location using the 'one shot' 10g syntax
I used to backup using two steps
1) datafile
2) archlogs with a LIKE expression to tell Rman where to find the archlogs
1+2 with autobackup of control+spfile
the 'backup database plus archivelog ' syntax does accept a 'LIKE' expression
patrick

Why Backup database then backup archivelog from time...

Dear Experts,
I found in one of our rman scripts the 2 following statements:
backup database;
backup archivelog from time 'SYSDATE -8';
It seems to me that a "backup database plus archivelog;" is more simple/accurate instead of these 2 lines as the retention windows is defined (5 days) for this DB so rman will manage the retention of datafiles and archived log, isn't it ?
Why this separate statement for the archivelog ? I find it redondant but is it...
Any advice is as usual greatly appreciated.
Best Regards,
Guillaume

You are right. The use of backup database plus archivelog; is much better and you are sure that you backup all archived log you need.
Probably that is an old script, previous version or the responsable of this script didn't know RMAN so good and the option you posted.
Bye, Aron

1st RMAN backup database plus archivelog fails

Similar Messages

Maybe you are looking for