RMAN Backups for archive logs

Hi,
We are taking daily backups using BCV's and archive backup to tapes using RMAN. Please note we are using RMAN only for archive backups.
We are changing our backup strategy and I need below information on RMAN.
1) Is there any benefit I will be getting if I use RMAN for archive backups ( like finding the courruption in the logs,health of the archive) etc? Any reference note for this would be great.
2) If I use multiplexing of archives using LOG_ ARCHIVE_DEST & LOG_ ARCHIVE_DUPLEX_DEST with this I want RMAN to take the backup of archives and delete from one location only ( Say from LOG_ ARCHIVE_DEST ). And I want the archives in LOG_ ARCHIVE_DUPLEX_DEST to maintain on my own ( Like different purge strategy to zip and keep for 7 days in this location.
If I use command "backup archivelog all delete input" it is picking and removing radomly from either of these locations. Is there a way I can configure RMAN so that it will not touch my secondary locaton?
Thanks in advance.
Thanks,
Varma

>
1) Is there any benefit I will be getting if I use RMAN for archive backups ( like finding the courruption in the logs,health of the archive) etc? Any reference note for this would be great.
You can use validate backupset command to check the health of backup.
2) If I use multiplexing of archives using LOG_ ARCHIVE_DEST & LOG_ ARCHIVE_DUPLEX_DEST with this I want RMAN to take the backup of archives and delete from one location only ( Say from LOG_ ARCHIVE_DEST ). And I want the archives in LOG_ ARCHIVE_DUPLEX_DEST to maintain on my own ( Like different purge strategy to zip and keep for 7 days in this location.
Yes, you can do that.
If I use command "backup archivelog all delete input" it is picking and removing radomly from either of these locations. Is there a way I can configure RMAN so that it will not touch my secondary locaton?
You can allocate channels for that.
regards

Similar Messages

RMAN BACKUPS AND ARCHIVED LOG ISSUES

제품 : RMAN
작성날짜 : 2004-02-17
RMAN BACKUPS AND ARCHIVED LOG ISSUES
=====================================
Scenario #1:
1)RMAN이 모든 archived log들을 삭제할 때 실패하는 경우.
database는 두 개의 archive destination에 archive file을 생성한다.
다음과 같은 스크립트를 수행하여 백업후에 archived redo logfile을 삭제한다.
run {
allocate channel c1 type 'sbt_tape';
backup database;
backup archivelog all delete input;
Archived redo logfile 삭제 유무를 확인하기 위해 CROSSCHECK 수행시 다음과
같은 메시지가 발생함.
RMAN> change archivelog all crosscheck;
RMAN-03022: compiling command: change
RMAN-06158: validation succeeded for archived log
RMAN-08514: archivelog filename=
/oracle/arch/dest2/arcr_1_964.arc recid=19 stamp=368726072
2) 원인분석
이 문제는 에러가 아니다. RMAN은 여러 개의 arhive directory중 하나의
directoy안에 있는 archived file들만 삭제한다. 그래서 나머지 directory안의
archived log file들은 삭제되지 않고 남게 되는 것이다.
3) 해결책
RMAN이 강제로 모든 directory안의 archived log file들을 삭제하게 하기 위해서는
여러 개의 채널을 할당하여 각 채널이 각 archive destination안의 archived file을
백업하고 삭제하도록 해야 한다.
이것은 아래와 같이 구현될 수 있다.
run {
allocate channel t1 type 'sbt_tape';
allocate channel t2 type 'sbt_tape';
backup
archivelog like '/oracle/arch/dest1/%' channel t1 delete input
archivelog like '/oracle/arch/dest2/%' channel t2 delete input;
Scenario #2:
1)RMAN이 archived log를 찾을 수 없어 백업이 실패하는 경우.
이 시나리오에서 database를 incremental backup한다고 가정한다.
이 경우 RMAN은 recover시 archived redo log대신에 incremental backup을 사용할
수 있기 때문에 백업 후 모든 archived redo log를 삭제하기 위해 OS utility를 사용한다.
그러나 다음 번 backup시 다음과 같은 Error를 만나게 된다.
RMAN-6089: archive log NAME not found or out of sync with catalog
2) 원인분석
이 문제는 OS 명령을 사용하여 archived log를 삭제하였을 경우 발생한다. 이때 RMAN은
archived log가 삭제되었다는 것을 알지 못한다. RMAN-6089는 RMAN이 OS 명령에 의해
삭제된 archived log가 여전히 존재하다고 생각하고 백업하려고 시도하였을 때 발생하게 된다.
3) 해결책
가장 쉬운 해결책은 archived log를 백업할 때 DELETE INPUT option을 사용하는 것이다.
예를 들면
run {
allocate channel c1 type 'sbt_tape';
backup archivelog all delete input;
두 번째로 가장 쉬운 해결책은 OS utility를 사용하여 archived log를 삭제한 후에
다음과 같은 명령어를 RMAN prompt상에서 수행하는 것이다.
RMAN>allocate channel for maintenance type disk;
RMAN>change archivelog all crosscheck;
Oracle 8.0:
RMAN> change archivelog '/disk/path/archivelog_name' validate;
Oracle 8i:
RMAN> change archivelog all crosscheck ;
Oracle 9i:
RMAN> crosscheck archivelog all ;
catalog의 COMPATIBLE 파라미터가 8.1.5이하로 설정되어 있으면 RMAN은 찾을 수 없는
모든 archived log의 status를 "DELETED" 로 셋팅한다. 만약에 COMPATIBLE이 8.1.6이상으로
설정되어 있으면 RMAN은 Repository에서 record를 삭제한다.

Very strange, I issue following command in RMAN on both primary and standby machine, but it they don't delete the 1_55_758646076.dbf, I find in v$archived_log, this "/home/oracle/app/oracle/dataguard/1_55_758646076.dbf" had already been applied.
RMAN> connect target /
RMAN> CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;
old RMAN configuration parameters:
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;
new RMAN configuration parameters:
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;
new RMAN configuration parameters are successfully stored
RMAN>
----------------------------------------------------------------------------------

RMAN backup of archive logs

I am sort of new to RMAN, I've been playing with it for a while but that's about as far as I've taken it. My question is does RMAN automatically backup any archive logs needed for recovery when I run "backup database" command or do I have to issue "backup database plus archive log" in order to insure recovery.

Backup database also backups archivelogs.No,it does not. From documentation:
backup database;
Creates a backup set (AS BACKUPSET) or group of image copies (AS COPY) for all datafiles in the database. If generating a backup set, then RMAN can include only datafiles and control files: it cannot include archived redo logs.
Werner

How to control RMAN backup of archive logs in FRA

Setup:
11.2.0.2 GI
ASM Diskgroup for Fast Recovery Area
10.2.0.4 Enterprise Database
Without Catalog Database
To get familiar with Flashback Database we set up RMAN Backups
without deleting the archive logs,
as published in Oracle10g / 11g - Getting Started with Recovery Manager (RMAN) (Doc ID 360416.1)
"These deletions are managed by Oracle when space is required."
We observed that RMAN takes backups of all archive logs every time,
here we go with backing up archive logs every 30 minutes.
So the question is:
Is this (backing up all archive logs every time) the expected behavior or
the result of not using a catalog database or
any other mismatch?
thanx for any hint
Michael

Hi Michael,
In Note 360416.1 it refers to two archivelog backup commands.
BACKUP ARCHIVELOG ALL;and
BACKUP ARCHIVELOG FROM TIME 'SYSDATE-30' UNTIL TIME 'SYSDATE-7';Your question:
Is this (backing up all archive logs every time) the expected behavior or the result of not using a catalog database or any other mismatch?If you used the first script you will backup alle archivelogs everytime.
If you use the second one it will do a subset (probably not the range you want to backup...)
You could implement another script
BACKUP ARCHIVELOG NOT BACKED UP 2 TIMES;So every archivelog is only backed up twice.
Check
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14194/rcmsynta009.htm#i78895
for more information.
Regards,
Tycho

RMAN failure for "archive-log ... not found in controlfile"

Recovery Manager: Release 8.1.6.0.0 - Production
RMAN> connect target sys/XXXX@cldb;
2> connect catalog rman/XXXX@rmandb1;
3>
4> resync catalog;
5>
6> # Backup the database
7> run {
8> allocate channel ch1 type disk;
9> backup incremental level 0 format
10> '/tools/cm/clearquest/orabackup/cldb.cqdbserver/backup/backup_%t_%s_%p' database;
11> sql 'alter system archive log current';
12> }
13>
14> # Backup the archived redo logs
15> run {
16> allocate channel ch1 type disk;
17>
18> backup incremental level 0 format
19> '/tools/cm/clearquest/orabackup/cldb.cqdbserver/backup/archivelog_%t_%s_%p' archivelog all;
20> sql 'alter system archive log current';
21> }
22>
23> # Backup the control file
24> run {
25> allocate channel ch1 type disk;
26> sql 'alter database backup controlfile to trace';
27> copy current controlfile to
28> '/tools/cm/clearquest/orabackup/cldb.cqdbserver/controlfile.bak';
29> }
30>
31>
RMAN-06005: connected to target database: CLDB (DBID=1292102281)
RMAN-06008: connected to recovery catalog database
RMAN-03022: compiling command: resync
RMAN-03023: executing command: resync
RMAN-08002: starting full resync of recovery catalog
RMAN-08004: full resync complete
RMAN-03022: compiling command: allocate
RMAN-03023: executing command: allocate
RMAN-08030: allocated channel: ch1
RMAN-08500: channel ch1: sid=17 devtype=DISK
RMAN-03022: compiling command: backup
RMAN-03023: executing command: backup
RMAN-08008: channel ch1: starting incremental level 0 datafile backupset
RMAN-08502: set_count=816 set_stamp=422358010 creation_time=22-FEB-01
RMAN-08010: channel ch1: specifying datafile(s) in backupset
RMAN-08522: input datafile fno=00001 name=/opt/orabase/oradata/cldb/system01.dbf
---snip----
more like this
---snip----
RMAN-08013: channel ch1: piece 1 created
RMAN-08503: piece handle=/tools/cm/clearquest/orabackup/cldb.cqdbserver/backup/backup_422358010_816_1 comment=NONE
RMAN-08525: backup set complete, elapsed time: 00:01:46
RMAN-03023: executing command: partial resync
RMAN-08003: starting partial resync of recovery catalog
RMAN-08005: partial resync complete
RMAN-03022: compiling command: sql
RMAN-06162: sql statement: alter system archive log current
RMAN-03023: executing command: sql
RMAN-08031: released channel: ch1
RMAN-03022: compiling command: allocate
RMAN-03023: executing command: allocate
RMAN-08030: allocated channel: ch1
RMAN-08500: channel ch1: sid=17 devtype=DISK
RMAN-03022: compiling command: backup
RMAN-03025: performing implicit partial resync of recovery catalog
RMAN-03023: executing command: partial resync
RMAN-08003: starting partial resync of recovery catalog
RMAN-08005: partial resync complete
RMAN-03023: executing command: backup
RMAN-08009: channel ch1: starting archivelog backupset
RMAN-08502: set_count=817 set_stamp=422358179 creation_time=22-FEB-01
RMAN-08014: channel ch1: specifying archivelog(s) in backup set
RMAN-08504: input archivelog thread=1 sequence=85 recid=2610 stamp=422352397
RMAN-08504: input archivelog thread=1 sequence=86 recid=2611 stamp=422352397
----snip----
more similar stuff here
----snip----
RMAN-08504: input archivelog thread=1 sequence=140 recid=2732 stamp=422358121
RMAN-08013: channel ch1: piece 1 created
RMAN-08503: piece handle=/tools/cm/clearquest/orabackup/cldb.cqdbserver/backup/archivelog_422358179_817_1 comment=NONE
RMAN-08525: backup set complete, elapsed time: 00:00:17
RMAN-08009: channel ch1: starting archivelog backupset
RMAN-08502: set_count=818 set_stamp=422358197 creation_time=22-FEB-01
RMAN-08014: channel ch1: specifying archivelog(s) in backup set
----snip----
more like this
----snip----
RMAN-08504: input archivelog thread=1 sequence=164 recid=2756 stamp=422358123
RMAN-08504: input archivelog thread=1 sequence=165 recid=2757 stamp=422358123
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAG E STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03006: non-retryable error occurred during execution of command: backup
RMAN-07004: unhandled exception during command execution on channel ch1
RMAN-10035: exception raised in RPC: ORA-19571: archived-log recid 2011 stamp 419161314 not found in controlfile
RMAN-10031: ORA-19571 occurred during call to DBMS_BACKUP_RESTORE.BACKUPARCHIVEDLOG
I added the resync catalog command to the backup. But I am still getting this error. What is happening? I have the control_file_record_keep_time = 14 in the paramater file. Do I need to change this to something greater?
null

The error message is pointing to an inconsistency between what RMAN "thinks"
should be there and what is in control files.
There are a few things you can try to do
1. Compare V$LOG, V$LOGFILE, etc. Some of these views are based on control files
2. Shutdown and restart the instance.
This may help in synchronizing control files
with internal structures.
3. Trace RMAN session using oradebug and even 10046 to find out what it is doing
4. Dump entire controlfile to trace using
alter session set events 'immediate trace name controlf level 10';
Or dump loghist only
alter session set events 'immediate trace name loghist level 4';
This will dump 2**level entries.
5. Re-create controlfiles with CREATE CONTROLFILE
Regards,
Sev

How to calculate storage space for archive log files and database backups?

Hi all,
I have a 1.8 terabyte Oracle 9i database and need to plan for how much additional disk space I will need to perform nightly backups and for archivelog files. Is there a script or formula available that can help me estimate how much required disk space I will need to hold a days worth of archived logs as well as a nightly export dump file and a full hot RMAN backup on disk?
Thanks!

I'm not sure how to estimate the size of your backups, especially if you use incrementals. However, the space required for archive logs will be equal to the amount of REDO your DB generates. I would count the number of log switches per day with a query like the following:
select trunc(first_time), count(*)
from v$log_history
group by trunc(first_time)
I would then take the average and multiply this count by the size of your redo log files (assuming they are all the same size).

How can I set destination for archived logs?

I would like to know:
how to set destination for archived logs?
how to identify the init.ora that is used for my database?
With rman using compressed backupset by default and and making
backup database;
What does it backup exactly?

Another thing I am wondering, when I make a backup with rman : backup database.
It saves the backups in the directory autobackup from the flash_recovery_area but it seems that it only saves the data files and the control files.Isn't there a way to sava archived logs files, control files, datafiles in a single backup?
In fact I would like to make a full backup using rman on sunday of everything and a incremental backup all days of the week how can I acomplish this with a retention of 7 days?

Validation failed for archived log

Hi,
oracle database version 11.2.0.4
OS centOS 6.5
Recently i have set rman backup scripy on production Database, As we are using dbvisit for standby database for that we have set cron which run in every 10 minutes it generates archive and copy it to standby side,
but sometimes backup failed due to expected archive is not represent at location so i put "crosscheck archivelog all" in script now backup is running fine, But i have analyzed backlog file getting
"validation failed for archived log" the time stamp i have checked validation failed archive is current day and yesterday even though archives are present at the location and CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 14 DAYS;
Guys i am worried it shouldn't be a big issue for me,
please suggest what is wrong

This forum is for Berkeley DB high availability. We do not have the expertise to help you with your Oracle database 11.2.0.4 issue. You'll need to submit this question to one of the Oracle database forums to get the help you are looking for.
Paula Bingham

Rman backup for rac by oem

Br,Hi,
DB : 10.2 and 11.2
How to schedule rman backup for cluster in OEM?How to schedule without OEM?
If one of the node failed,Is it possible to run in another node automatcially?
How to schduel export/datadump in rac by oem?
Br,
Raj

I Am not using oem, without oem you should write several scripts....
for linux hot backup(archive log enabled):
bck.sh
set ORACLE_SID=mydb
set ORACLE_HOME=....
rman target sys/.... @'.../bck.ora'
bck.ora
run
BACKUP AS COMPRESSED BACKUPSET FORMAT "..../db_%d_%T_%s_%p_%U.bak" INCREMENTAL LEVEL 0 DATABASE PLUS ARCHIVELOG DELETE INPUT FORMAT "...../archivelogBackup/arch_%d_%T_%s_%p_%U.bak";
delete force noprompt obsolete redundancy 3;
backup FORMAT '..../ctl_%d_%T_%s_%p_%U' current controlfile spfile;
And create executable job which instance_id=1 and will run your bck.sh script and create schedule for this job, when first node will down you must change instance_id attribute to second one, and be sure that all backup paths exists in all nodes.
Ramin Hashimzade

"recover database until cancel" asks for archive log file that do not exist

Hello,
Oracle Release : Oracle 10.2.0.2.0
Last week we performed, a restore and then an Oracle recovery using the recover database until cancel command. (we didn't use backup control files) .It worked fine and we able to restart the SAP instances. However, I still have questions about Oracle behaviour using this command.
First we restored, an online backup.
We tried to restart the database, but got ORA-01113,ORA-01110 errors :
sr3usr.data1 needed media recovery.
Then we performed the recovery :
According Oracel documentation, "recover database until cancel recovery" proceeds by prompting you with the suggested filenames of archived redo log files.
The probleme is it prompts for archive log file that do not exist.
As you can see below, it asked for SMAarch1_10420_610186861.dbf that has never been created. Therefore, I cancelled manually the recovery, and restarted the database. We never got the message "media recovery complete"
ORA-279 signalled during: ALTER DATABASE RECOVER    LOGFILE '/oracle/SMA/oraarch/SMAarch1_10417_61018686
Fri Sep 7 14:09:45 2007
ALTER DATABASE RECOVER    LOGFILE '/oracle/SMA/oraarch/SMAarch1_10418_610186861.dbf'
Fri Sep 7 14:09:45 2007
Media Recovery Log /oracle/SMA/oraarch/SMAarch1_10418_610186861.dbf
ORA-279 signalled during: ALTER DATABASE RECOVER    LOGFILE '/oracle/SMA/oraarch/SMAarch1_10418_61018686
Fri Sep 7 14:10:03 2007
ALTER DATABASE RECOVER    LOGFILE '/oracle/SMA/oraarch/SMAarch1_10419_610186861.dbf'
Fri Sep 7 14:10:03 2007
Media Recovery Log /oracle/SMA/oraarch/SMAarch1_10419_610186861.dbf
ORA-279 signalled during: ALTER DATABASE RECOVER    LOGFILE '/oracle/SMA/oraarch/SMAarch1_10419_61018686
Fri Sep 7 14:10:13 2007
ALTER DATABASE RECOVER    LOGFILE '/oracle/SMA/oraarch/SMAarch1_10420_610186861.dbf'
Fri Sep 7 14:10:13 2007
Media Recovery Log /oracle/SMA/oraarch/SMAarch1_10420_610186861.dbf
Errors with log /oracle/SMA/oraarch/SMAarch1_10420_610186861.dbf
ORA-308 signalled during: ALTER DATABASE RECOVER    LOGFILE '/oracle/SMA/oraarch/SMAarch1_10420_61018686
Fri Sep 7 14:15:19 2007
ALTER DATABASE RECOVER CANCEL
Fri Sep 7 14:15:20 2007
ORA-1013 signalled during: ALTER DATABASE RECOVER CANCEL ...
Fri Sep 7 14:15:40 2007
Shutting down instance: further logons disabled
When restaring the database we could see that, a recovery of online redo log has been performed automatically, is it the normal behaviour of a recovery using "recover database until cancel" command ?
Started redo application at
Thread 1: logseq 10416, block 482
Fri Sep 7 14:24:55 2007
Recovery of Online Redo Log: Thread 1 Group 4 Seq 10416 Reading mem 0
Mem# 0 errs 0: /oracle/SMA/origlogB/log_g14m1.dbf
Mem# 1 errs 0: /oracle/SMA/mirrlogB/log_g14m2.dbf
Fri Sep 7 14:24:55 2007
Completed redo application
Fri Sep 7 14:24:55 2007
Completed crash recovery at
Thread 1: logseq 10416, block 525, scn 105140074
0 data blocks read, 0 data blocks written, 43 redo blocks read
Thank you very much for your help.
Frod.

Hi,
Let me answer your query.
=======================
Your question: While performing the recovery, is it possible to locate which online redolog is needed, and then to apply the changes in these logs
1.   When you have current controlfile and need complete data (no data loss),
      then do not go for until cancel recovery.
2.   Oracle will apply all the redologs (including current redolog) while recovery
     process is    on.
3. During the recovery you need to have all the redologs which are listed in the    view    V$RECOVERY_LOG and all the unarchived and current redolog. By querying V$RECOVERY_LOG you    can find out about the redologs required.
4. If the required sequence is not there in the archive destination, and if recovery process    asks for that sequence you can query V$LOG to see whether requested sequence is part of the    online redologs. If yes you can mention the path of the online redolog to complete the recovery.
Hope this information helps.
Regards,
Madhukar

Secondary destination for Archived logs

Version: 10.2, 11.1, 11.2
We occasionally get 'archiver error' on our production DBs due to our LOG_ARCHIVE_DEST_1 being full. How can I have a secondary location for archive logs in case my 'primary' location (LOG_ARCHIVE_DEST_1) becomes full ?
I gather that LOG_ARCHIVE_DEST_2 is reserved for shipping archive logs to Dataguard standby DB in which you specify the tns entry of standby using SERVICE parameter.
Can I specify LOG_ARCHIVE_DEST_3 as my secondary location in case LOG_ARCHIVE_DEST_1 becomes full ? Is it what LOG_ARCHIVE_DEST_n meant for ? Although the documentation says you can have upto 10 locations, I am confused if they are meant to store Multiplexed copies of archive logs ? That is not what I am looking for ?

>
Hi again Tom,
I have one more question:
ALTER SYSTEM SET LOG_ARCHIVE_DEST_4 = 'LOCATION=/disk4/arch';
ALTER SYSTEM SET LOG_ARCHIVE_DEST_3 = 'LOCATION=/disk3/arch
    ALTERNATE=LOG_ARCHIVE_DEST_4';
ALTER SYSTEM SET LOG_ARCHIVE_DEST_STATE_4=ALTERNATE;
SQL> SELECT dest_name, status, destination FROM v$archive_dest;
DEST_NAME               STATUS    DESTINATION
LOG_ARCHIVE_DEST_1      VALID     /disk1/arch     -------------> Dest1
LOG_ARCHIVE_DEST_2      VALID     +RECOVERY       -------------> Dest2
LOG_ARCHIVE_DEST_3      VALID     /disk3/arch     -------------> Dest3
LOG_ARCHIVE_DEST_4      ALTERNATE /disk4/archMy understanding is (and I'm not terribly sure at the minute - don't have a test system to hand. I haven't
set up a backup/recovery strategy in a while - I just restore backups from time to time (normally every 4 weeks)
to ensure that the database recovers as it should) - my understanding is that under the scheme above
DEST_3 will be a copy of what's in DEST_1. DEST_4 on the other hand will "step in" should DEST_1
or DEST_3 fill up/fail.
As to DEST_2, I'm not sure - maybe something to do with Fast Recovery Area? I've Googled but can't
find anything - the trouble is that all the pages about this contain the word "recovery" and the "+"
sign doesn't appear to affect the search - does "+" mean something special to Google?
I don't have a system at the moment - if you do, why don't you test and see? On a test system, fill
up the file system for DEST_1 with rubbish and check to see what happens?
All of the above is to be taken with a pinch of salt - I don't have a system to hand and am not certain,
so CAVEAT EMPTOR
HTH,
Paul...
Edited by: Paulie on 21-Jul-2012 17:20

Related to Unused compression in RMAN backup for 10.2.0.4 database

Hi
I recently read through one of the document related to Unused compression in RMAN backup for 10.2.0.4 database. According to this
Unused Block Compression is done, if all of the following conditions apply:
+ The COMPATIBLE initialization parameter is set to 10.2
+ There are currently no guaranteed restore points defined for the database
+ The datafile is locally managed
+ The datafile is being backed up to a backup set as part of a full backup or a level 0 incremental backup
+ The backup set is being created on disk.
I have two queries
1) What is meant by "uaranteed restore points defined for the database"
2) If backup is being directly taken to tape, this feature would not be used
Rgds
Harvinder

1. Normal and Garanteed Restore Points
2. No

RMAN backup in noarchived log mode

Hi,
can we take RMAN backup in noarchived log mode?
If yes, how? just run backup database command or ?
thanks

You can use RMAN to backup a database in noarchivelog mode but you need to shutdown and mount the database. e.g.:
rman target /
RMAN> shutdown immediate
RMAN> startup mount
RMAN> backup database

RMAN-08120: WARNING: archived log not deleted, not yet applied by standby

i get RMAN-08120: WARNING: archived log not deleted, not yet applied by standby on primary
but when i run below query i get the same result from primary and standby
SQL> select max(sequence#) from v$archived_log;
MAX(SEQUENCE#)
44051
SQL>
standby is one log switch behind only!

i get RMAN-08120: WARNING: archived log not deleted, not yet applied by standby on primary You already have answer by post of Mseberg.
but when i run below query i get the same result from primary and standby
SQL> select max(sequence#) from v$archived_log;
MAX(SEQUENCE#)
44051
SQL>
standby is one log switch behind only!this is wrong query used on primary & standby. even if any one of archive gap available lets suppose sequence *44020* , this archive not transported to standby due to some network problem and so on. later if archives from *44021* all the archives transported on standby upto *44051* , then it shows the maximum sequence transferred to standby, It wont shows applied sequence.
Check the below queries.
Primary:-
SQL> select thread#,max(sequence#) from v$archived_log group by thread#;
Standby:-
SQL> select thread#,max(sequence#) from v$archived_log where applied='YES' group by thread#;
HTH.

What is the meaning of stream capture waiting for archive log ?

today I fing the oracle alert that stream capture waiting for archive log in other class,and use a lot of database time.
What is it? And Can I prevent it happening ?

today I fing the oracle alert that stream capture waiting for archive log in other class,and use a lot of database time.
What is it? And Can I prevent it happening ?

RMAN Backups for archive logs

Similar Messages

Maybe you are looking for