Logical standby | archive log deleted | how to remove gap ???

hi gurus...
i have problem on logical standby
by mistake standby log coming to logical standby has been deleted , now how to fill up the gap ???
ON STANDBY
SEQUENCE# FIRST_CHANGE# NEXT_CHANGE# APPLIED
228 674847 674872 YES
229 674872 674973 CURRENT
230 674973 674997 NO
231 674997 675023 NO
232 675023 675048 NO
233 675048 675109 NO
234 675109 675135 NO
235 675135 675160 NO
236 675160 675183 NO
237 675183 675208 NO
238 675208 675232 NO
239 675232 675257 NO
240 675257 675282 NO
241 675282 675382 NO
242 675382 675383 NO
243 675383 675650 NO
244 675650 675652 NO
245 675652 675670 NO
246 675670 675688 NO
247 675688 675791 NO
248 675791 678524 NO
archive log are shipping to standby location also and getting registered
ALERT LOG OF STANDBY
Fri May 7 12:25:36 2010
Primary database is in MAXIMUM PERFORMANCE mode
RFS[21]: Successfully opened standby log 5: '/u01/app/oracle/oradata/BEST/redo05.log'
Fri May 7 12:25:37 2010
RFS LogMiner: Registered logfile [u01/app/oracle/flash_recovery_area/BEST/archivelog/archBEST_248_1_715617824.dbf] to LogMiner session id [1]
but i dont have standby log after 229 sequence ...
ON PRIMARY
SYS@TEST AS SYSDBA> archive log list
Database log mode Archive Mode
Automatic archival Enabled
Archive destination /u01/app/oracle/flash_recovery_area/TEST/standlogOldest online log sequence 247
Next log sequence to archive 249
Current log sequence 249
what to do next to apply sequences and bring both in sync.
please help me ,,,,
Edited by: user12281508 on May 7, 2010 9:45 AM

thanks for response.
no its pure logical standby
i have tried to ftp the archive logs of primary to standby and applied manually
SYS@BEST AS SYSDBA> alter database register logfile '/u01/app/oracle/flash_recovery_area/BEST/archivelog/archBEST_230_1_715617824.dbf';
alter database register logfile '/u01/app/oracle/flash_recovery_area/BEST/archivelog/archBEST_230_1_715617824.dbf'
ERROR at line 1:
ORA-01289: cannot add duplicate logfile
SYS@BEST AS SYSDBA> alter database register logfile '/u01/app/home/archTEST_230_1_715617824.dbf';
alter database register logfile '/u01/app/home/archTEST_230_1_715617824.dbf'
ERROR at line 1:
ORA-01289: cannot add duplicate logfile
any other way ????

Similar Messages

Delete standby archived log

I need to delete some standby archived log from my downstreams database but I not find the way, please help me.

If you are looking for an automatic way to delete them, then you can archive to a flash recovery area on the standby, which can act as a FIFO archivelog bucket:
$ sqlplus / as sysdba
SQL> alter system set db_recovery_file_dest='+datadg' scope=both;
SQL> alter system set db_recovery_file_dest_size=2G scope=both;
SQL> alter system set log_archive_dest_1='location=use_db_recovery_file_dest' scope=both;
$ rman target /
RMAN> configure retention policy to redundancy 1;
RMAN> configure archivelog deletion policy to applied on standby;Of course substitute your own preferred values for above, use the RMAN catalog if you have one, and don't step on any pre-existing retention policy or FRA that you might wish to keep the way it is.
Regards,
Jeremiah Wilton
Blue Gecko, Inc.
[http://www.bluegecko.net|http://www.bluegecko.net]

RMAN-08591: WARNING: invalid archived log deletion policy

Hi,
My database is 11.2.0.1 running on OEL 5.
We have stndby database running on other server, i have configured rman like this
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;
But while running db backup, getting the error
RMAN-08591: WARNING: invalid archived log deletion policy.
RMAN retention policy is set to redundancy 1.
The archive files are deleting even though they are not applied on standby.
Thanks,

kkrm333 wrote:
Hi,
My database is 11.2.0.1 running on OEL 5.
We have stndby database running on other server, i have configured rman like this
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;
But while running db backup, getting the error
RMAN-08591: WARNING: invalid archived log deletion policy.
RMAN retention policy is set to redundancy 1.
The archive files are deleting even though they are not applied on standby.
Thanks,
bcm@bcm-laptop:~$ oerr rman 8591
8591, 3, "WARNING: invalid archived log deletion policy"
// *Cause: An invalid ARCHIVELOG DELETION POLICY was supplied. The archived
//         log deletion policy was APPLIED but there was no mandatory
//         archived log destinations.
// *Action: One of the following:
//          1) Change archived log deletion policy using CONFIGURE command
//          2) Make one or more of standby destination as MANDATORY.

Question about Archive Log Deletion policy

I've a problem to understand the Archive Log Deletion policy, and I I'd like to this problem explain with the following example.
Messages of the database are in German, but I guess you'll understand them.
SQL> startup
ORACLE-Instance hochgefahren.
Total System Global Area 5344731136 bytes
Fixed Size                  2129240 bytes
Variable Size            2684355240 bytes
Database Buffers         2617245696 bytes
Redo Buffers               41000960 bytes
Datenbank mounted.
Datenbank geöffnet.
SQL> archive log list
Datenbank-Log-Modus              Archive-Modus
Automatische Archivierung             Aktiviert
Archivierungsziel            E:\oracle\thetis_iv\arch
Älteste Online-Log-Sequenz     17917
Nächste zu archivierende Log-Sequenz   17919
Aktuelle Log-Sequenz           17919
SQL> alter system switch logfile;
System wurde geändert.I created a brand new archive log.
SQL> exit
Verbindung zu Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options beendet
D:\OracleDB\product\11.1.0\db_1\BIN>dir E:\oracle\thetis_iv\arch
Datenträger in Laufwerk E: ist Volume
Volumeseriennummer: 3EBD-77E5
Verzeichnis von E:\oracle\thetis_iv\arch
06.04.2011 15:04    <DIR>          .
06.04.2011 15:04    <DIR>          ..
06.04.2011 15:04        17.137.152 ARC17919_0721667907.001
               1 Datei(en),     17.137.152 Bytes
               2 Verzeichnis(se), 41.073.258.496 Bytes freiand this is the only archive log in the directory. Now I start rman:
D:\OracleDB\product\11.1.0\db_1\BIN>rman target / catalog rmanrepo@rmanrepo
Recovery Manager: Release 11.1.0.7.0 - Production on Mi Apr 6 15:05:35 2011
Copyright (c) 1982, 2007, Oracle. All rights reserved.
Mit Ziel-Datenbank verbunden: ENTWIV (DBID=21045568)
Kennwort für Recovery-Katalog-Datenbank:
Verbindung mit Datenbank des Recovery-Katalogs
RMAN> show all;
RMAN-Konfigurationsparameter für Datenbank mit db_unique_name ENTWIV sind:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 1 DAYS;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';
CONFIGURE CONTROLFILE AUTOBACKUP OFF;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'E:\oracle\thetis_iv\backup\CF_%F_ENTWIV.ORA';
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE SBT_TAPE TO '%F'; # default
CONFIGURE DEVICE TYPE SBT_TAPE PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' PARMS 'ENV=(TPDO_OPTFILE=D:\Services\Tivoli\TSM\AgentOBA64\tpdo.opt)';
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE COMPRESSION ALGORITHM 'BZIP2'; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO BACKED UP 2 TIMES TO 'SBT_TAPE';
CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'D:\ORACLEDB\PRODUCT\11.1.0\DB_1\DATABASE\SNCFENTWIV.ORA'; # defaultThe archive log deletion policy says the the logfiles have to be backed up for two times before they get deleted.
Now I backup all archive logs, that havn't been backed up for at least two times.
RMAN> run { backup archivelog all not backed up 2 times
2>       format '%d_AR_%Y%M%D_%s_%t'
3>       tag 'ARCHIVE LOGS'
4>       DELETE ALL INPUT;
5>     }
Starten backup um 06.04.2011 15:08:01
Aktuelles Log archiviert
Zugewiesener Kanal: ORA_SBT_TAPE_1
Kanal ORA_SBT_TAPE_1: SID=253 Device-Typ=SBT_TAPE
Kanal ORA_SBT_TAPE_1: Data Protection for Oracle: version 5.5.1.0
Kanal ORA_SBT_TAPE_1: Backup Set für Archive Log wird begonnen
Kanal ORA_SBT_TAPE_1: Archive Logs in Backup Set werden angegeben
Eingabe-Archive-Log-Thread=1 Sequence=17919 RECID=147 STAMP=747759899
Eingabe-Archive-Log-Thread=1 Sequence=17920 RECID=148 STAMP=747760081
Kanal ORA_SBT_TAPE_1: Piece 1 wird auf 06.04.2011 15:08:02 begonnen
Kanal ORA_SBT_TAPE_1: Piece 1 auf 06.04.2011 15:08:09 beendet
Piece Handle=ENTWIV_AR_20110406_23_747760082 Tag=ARCHIVE LOGS Kommentar=API Version 2.0,MMS Version 5.5.1.0
Kanal ORA_SBT_TAPE_1: Backup Set vollstõndig, abgelaufene Zeit: 00:00:08
Kanal ORA_SBT_TAPE_1: Archive Logs werden gel÷scht
Archive Log-Dateiname=E:\ORACLE\THETIS_IV\ARCH\ARC17919_0721667907.001 RECID=147 STAMP=747759899
Archive Log-Dateiname=E:\ORACLE\THETIS_IV\ARCH\ARC17920_0721667907.001 RECID=148 STAMP=747760081
Beendet backup um 06.04.2011 15:08:10
RMAN> exit
Recovery Manager abgeschlossen.
D:\OracleDB\product\11.1.0\db_1\BIN> dir E:\oracle\thetis_iv\arch
Datenträger in Laufwerk E: ist Volume
Volumeseriennummer: 3EBD-77E5
Verzeichnis von E:\oracle\thetis_iv\arch
06.04.2011 15:08    <DIR>          .
06.04.2011 15:08    <DIR>          ..
               0 Datei(en),              0 Bytes
               2 Verzeichnis(se), 41.090.396.160 Bytes freirman deleted all archive logs, even I they are on tape only once by now.
Thats not what I expected. Where is my mistake?

Hi,
I do new tests it's very strange.
BACKUP ARCHIVELOG command is not obeying the policy of archivelog.
You can open a SR on MOS. (to check bugs)
I reproduce the same test and the result was the same, it seems that this is a bug.
CONFIGURE ARCHIVELOG DELETION POLICY TO BACKED UP 2 TIMES TO DISK;
RMAN> backup archivelog all not backed up 2 times delete all input;
Starting backup at 06-APR-11
current log archived
using channel ORA_DISK_1
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=15 RECID=16 STAMP=747753711
input archived log thread=2 sequence=20 RECID=17 STAMP=747753714
input archived log thread=1 sequence=16 RECID=19 STAMP=747753729
input archived log thread=2 sequence=21 RECID=18 STAMP=747753729
channel ORA_DISK_1: starting piece 1 at 06-APR-11
channel ORA_DISK_1: finished piece 1 at 06-APR-11
piece handle=+DATA/orcl/backupset/2011_04_06/annnf0_tag20110406t132210_0.304.747753731 tag=TAG20110406T132210 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=+DATA/orcl/archivelog/2011_04_06/thread_1_seq_15.293.747753711 RECID=16 STAMP=747753711
archived log file name=+DATA/orcl/archivelog/2011_04_06/thread_2_seq_20.295.747753715 RECID=17 STAMP=747753714
archived log file name=+DATA/orcl/archivelog/2011_04_06/thread_1_seq_16.294.747753729 RECID=19 STAMP=747753729
archived log file name=+DATA/orcl/archivelog/2011_04_06/thread_2_seq_21.298.747753729 RECID=18 STAMP=747753729
Finished backup at 06-APR-11
RMAN> list archivelog all;
specification does not match any archived log in the repositoryOracle Docs Says:
The BACKUP ARCHIVELOG ... DELETE INPUT command deletes archived log files after they are backed up.
This command eliminates the separate step of manually deleting archived redo logs.
With DELETE INPUT, RMAN deletes only the specific copy of the archived log chosen for the backup set.
With DELETE ALL INPUT, RMAN deletes each backed-up archived redo log file from all log archiving destinations.
As explained in "Configuring an Archived Redo Log Deletion Policy",
the BACKUP ... DELETE INPUT and DELETE ARCHIVELOG commands obey the archived redo log deletion policy
for logs in all archiving locations. For example, if you specify that logs should only be deleted when backed
up at least twice to tape, then BACKUP ... DELETE honors this policy.http://download.oracle.com/docs/cd/E11882_01/backup.112/e10642/rcmbckba.htm#BRADV89524
But in ours case it's not honors this policy.
Only with the FORCE command should this happen. But it is not our case.
Oracle Docs:
If FORCE is not specified on the deletion commands,
then these deletion commands obey the archived log deletion policy.
If FORCE is specified, then the deletion commands ignore the archived log deletion policy.http://download.oracle.com/docs/cd/E11882_01/backup.112/e10643/rcmsynta010.htm#RCMRF113
Alternatively you can do the following:
Set the commands separately.
Check this:
RMAN> run {
2> backup archivelog all not backed up 2 times ;
3> delete archivelog all backed up 2 times to disk;
4> }
Starting backup at 06-APR-11
current log archived
using channel ORA_DISK_1
channel ORA_DISK_1: starting archived log backup set
channel ORA_DISK_1: specifying archived log(s) in backup set
input archived log thread=2 sequence=22 RECID=21 STAMP=747755128
input archived log thread=1 sequence=17 RECID=20 STAMP=747755127
channel ORA_DISK_1: starting piece 1 at 06-APR-11
channel ORA_DISK_1: finished piece 1 at 06-APR-11
piece handle=+DATA/orcl/backupset/2011_04_06/annnf0_tag20110406t134528_0.295.747755129 tag=TAG20110406T134528 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
Finished backup at 06-APR-11
released channel: ORA_DISK_1
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=78 instance=orcl1 device type=DISK
RMAN-08138: WARNING: archived log not deleted - must create more backups
archived log file name=+DATA/orcl/archivelog/2011_04_06/thread_1_seq_17.298.747755127 thread=1 sequence=17
RMAN-08138: WARNING: archived log not deleted - must create more backups
archived log file name=+DATA/orcl/archivelog/2011_04_06/thread_2_seq_22.294.747755129 thread=2 sequence=22
RMAN>Edited by: Levi Pereira on Apr 6, 2011 1:35 PM

RMAN,Data Guard and Archive log deletion

Our DG environment is running Oracle 11g R2
we have a 3 node DG environment with
A being the Primary
B and C being Active Data Guard Standbys
Backups are taken off of B and go directly to tape.
Standby Redo Logs and Fast Recovery Area are being used
Taking recommendation from "Using Recovery Manager with Oracle Data Guard in Oracle Database 10g"
RMAN Setting on Primary ("A")
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY
RMAN Setting on Standby ("B") where Backup is done
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE
RMAN Setting on other Standby ("C")
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY
How can we know what archive logs are eligible to be deleted from "A" and "C" ?
When does the delete take place?
How can we tell when the archive logs are being deleted from "A" and "C" ?

Dear user10260925,
The documentation that you have read is reliable but insufficient.
The Oracle can manage the archivelog directory and knows which one is eligible for the deletion. Those stuff you have posted in here has been taken from the online documentation and is supported and can be used when the Oracle knows and manages the archivelogs. That is simply called the flash recovery area. Please read about the FRA in this very moment.
Under normal circumstances people in the industry uses some scripts to achive the archivelog deletion on the standby system.
Here is a useful example to you;
# Remove old archivelogs
00,30 * * * * /home/oracle/scripts/delete_applied_redo_logs_OPTSTBY.sh
vals3:/home/oracle#cat /home/oracle/scripts/delete_applied_redo_logs_OPTSTBY.sh
export ORACLE_SID=optstby
export ORACLE_HOME=/oracle/product/10.2.0/db_1
cd /db/optima/archive/OPTPROD/archivelog
/oracle/product/10.2.0/db_1/bin/sqlplus "/ as sysdba" @delete_applied_redo_logs.sql
grep arc delete_applied_redo_logs.lst > delete_applied_redo_logs_1.sh
chmod 755 delete_applied_redo_logs_1.sh
sh delete_applied_redo_logs_1.sh
rm delete_applied_redo_logs_1.sh
rm delete_applied_redo_logs.lst
vals3:/home/oracle#cd /db/optima/archive/OPTPROD/archivelog
vals3:/db/optima/archive/OPTPROD/archivelog#cat delete_applied_redo_logs.sql
set echo off
set heading off
spool /db/optima/archive/OPTPROD/archivelog/delete_applied_redo_logs.lst
select 'rm -f ' || name from v$archived_log where applied = 'YES';
spool off
exit
vals3:/db/optima/archive/OPTPROD/archivelog#Hope That Helps.
Ogan

Physycal Standby archive log gap....

Archive log gap caused... The reason being before the logs can be shipped to standby location where deleted by rman backup... So restored the archives on primary database site back again... These old logs from the gap are not getting shipped to the standby site, but the new ones generated currently are getting shipped.
Can some one help what action do I have to take to resolve the gap? And how to know what's causing and not letting this shipping happen?
Or shall I manually ship these gap archive logs to the standby site?

1) Yep running 9i.. But still its not shipping...Are FAL_CLIENT & FAL_SERVER parameters are defined at standby level?
If not, define them at standby level. Those parameter will help to get missing (gap) archives from primary database.
2) If so shipped manually do have to register the archive logs? Just copy from primary to standby and don't need to register any gap, that was in 8i and when there was no background process MRP (media recovery process). If the standby database is in auto media recovery, then, it will automatically applies all the archived logs.
Jaffar

Logical Standby 'CURRENT' log files

I have an issue with a Logical Standby implementation where although everything in the Grid Control 'Data Guard' page is Normal, when I view Log File Details I have 62 files listed with a status of 'Committed Transactions Applied'.
The oldest (2489) of these files is over 2 days old and the newest (2549) is 1 day old. The most recent applied log is 2564 (current log is 2565).
As for the actual APPLIED_SCN in the standby, it's greater than the highest NEXT_CHANGE# for newest logfile 2549. The READ_SCN is less than the NEXT_CHANGE# of the oldest log (2489) appearing in the the list of files - which is why all these log files appear on this list.
I am confused why the READ_SCN is not advancing. The documentation states that once the NEXT_CHANGE# of a logfile falls below READ_SCN the information in those logs has been applied or 'persistently stored in the database'.
Is it possible that there is a transaction that spans all these log files? More recent logfiles have dropped off the list and have been applied or 'persistently stored'.
Basically I'm unsure how to proceed and clean up this list of files and ensure that everything has been applied.
Regards
Graeme King

Thank you Larry. I have actually already reviewed this document. We are not getting the error they list for long running transactions though.
I wonder if it is related to the RMAN restore we did where I restored the whole standby database while the standby redo log files were not obviously restored and therefore were 'newer' than the restored database?
After I restored I did see lots trace files with this message:
ORA-00314: log 5 of thread 1, expected sequence# 2390 doesn't match 2428
ORA-00312: online log 5 thread 1: 'F:\ORACLE\PRODUCT\10.2.0\PR0D_SRL0.F'
ORA-00314: log 5 of thread 1, expected sequence# 2390 doesn't match 2428
ORA-00312: online log 5 thread 1: 'F:\ORACLE\PRODUCT\10.2.0\PR0D_SRL0.F'
I just stopped and restarted the SQL apply and sure enough it was cycled through all the log files in the list from the (READ_SCN onwards) but they are still in the list. Also there is very little activity on this non-production database.
regards
Graeme

Archive log can not ship to GAP logfiles to standby DB automatically

we have a non-real time standby database, which will receive the archive file from the primary database server most of the time, and will apply the logfiles only at one point of time daily.
Some times, we need to shutdown the Standby DB server for a while ( 3-4 hours).
The missed logfiles will catch up during the standby down time later.
But since last week we had an storage incident, the primary DB server stops to catch up the missed logfiles, and saw this message at the archvie trace file:
ABC: tkrsf_al_read: No mirror copies to re-read data
Current, we found the archive log gaps on the standby server, and have to manually copy those logfiles over and register them.
Saw some tips on the internet to change the parameter "log_archive_max_processes", but no help for us at all.
Here is the parameter on the Primary DB server:
log_archive_dest_2 = SERVICE=Standby_server reopen=300

which will receive the archive file from the primary database server most of the timeMost times from primary. Then remaining times? so you Copy manually and register?
Then it's dataguard not an manual standby.
Error 1034 received logging on to the standby
Errors in file /******/***arc210536.trc:
ORA-01034: ORACLE not available
FAL[server, ARC2]: FAL archive failed, see trace file.these errors in primary when , stanby is down and when primary tries to connect to standby, so tese errors not considerable to investigate ,
When you don't want to apply archives on standby no need to shutdown. Just put this value log_archive_dest_state_2='defer'
Once you enable check what are the errors in primary alert log file.
How is your network band width speed? Is it capable to hold that much archive data?
May be it will take some time when you pause & start.
Also use LGWR in log_archive_dest_2 for real time apply after creatin standby redo logs.
So post the alert log information once you enable standby database.

Dataguard physical standby archive log question

Hi all,
I will try to keep this simple..
I have a 4 node RAC primary shipping logs to a 2 node physical standby.
On the primary when I run 'alter system archive log current' on an instance I only see 1 log being applied on the standby, that is by querying v$archived_log.
If I run the following on the standby:
select thread#,sequence#,substr(name,43,70)"NAME",registrar,applied,status,first_time from v$archived_log where first_time
in
(select max(first_time) from v$archived_log group by thread#)
order by thread#
I get:
THREAD# SEQUENCE# NAME REGISTR APPLIED S FIRST_TIME
1 602 thread_1_seq_602.2603.721918617 RFS YES A 17-jun-2010 12:56:58
2 314 thread_2_seq_314.2609.721918627 RFS NO A 17-jun-2010 12:56:59
3 311 thread_3_seq_311.2604.721918621 RFS NO A 17-jun-2010 12:57:00
4 319 thread_4_seq_319.2606.721918625 RFS NO A 17-jun-2010 12:57:00
Why do we only see the max(sequence#) having been applied and not all of them?
This is the same no matter how many times I archive the current log files on any of the instances on the primary and also the standby does not have any gaps.
Hope this is clear..
any ideas?
jd

ok output from gv$archived_log on standby BEFORE 'alter system archive log current' on primary
THREAD# SEQUENCE# NAME REGISTR APPLIED S FIRST_TIME
1 679 thread_1_seq_679.1267.722001505 RFS NO A 18-jun-2010 11:58:22
1 679 thread_1_seq_679.1267.722001505 RFS NO A 18-jun-2010 11:58:22
2 390 thread_2_seq_390.1314.722001507 RFS NO A 18-jun-2010 11:58:23
2 390 thread_2_seq_390.1314.722001507 RFS NO A 18-jun-2010 11:58:23
3 386 thread_3_seq_386.1266.722001505 RFS YES A 18-jun-2010 11:58:22
3 386 thread_3_seq_386.1266.722001505 RFS YES A 18-jun-2010 11:58:22
4 393 thread_4_seq_393.1269.722001507 RFS NO A 18-jun-2010 11:58:23
4 393 thread_4_seq_393.1269.722001507 RFS NO A 18-jun-2010 11:58:23
Output from v$archived_log on standby AFTER 'alter system archive log current' on primary
THREAD# SEQUENCE# NAME REGISTR APPLIED S FIRST_TIME
1 680 thread_1_seq_680.1333.722004227 RFS NO A 18-jun-2010 11:58:29
1 680 thread_1_seq_680.1333.722004227 RFS NO A 18-jun-2010 11:58:29
2 391 thread_2_seq_391.1332.722004227 RFS NO A 18-jun-2010 11:58:30
2 391 thread_2_seq_391.1332.722004227 RFS NO A 18-jun-2010 11:58:30
3 387 thread_3_seq_387.1271.722004225 RFS NO A 18-jun-2010 11:58:28
3 387 thread_3_seq_387.1271.722004225 RFS NO A 18-jun-2010 11:58:28
4 394 thread_4_seq_394.1270.722004225 RFS YES A 18-jun-2010 11:58:29
4 394 thread_4_seq_394.1270.722004225 RFS YES A 18-jun-2010 11:58:29
as a reminder we have a 4 node RAC system shipping logs to a 2 node RAC standby. There are no gaps but only one log is ever registered as being applied.
Why is that? Why arnt all logs registered as being applied?

Archive log miss : How to restart capture

Hi Gurus,
I configured hotlog CDC distributed on 10.2.0.4 Databases.
I make a mistake: in my source Db I have deleted an Archive log,
and now the state of Capture process in V_$STREAM_CAPTURE is "WAITING FOR REDO: LAST SCN MINED 930696".
Now I'd like to restart the capture process from the next archive (just after the missed archive)
How is it possible?
tnk Fabio

I'm sorry to tell you that, but it's not possible. (Just as it's not possible to recover database with missing logs...)
You will have to recreate the capture process and to re-instantiate the replicated tables.
Regards,

Archive logs deletion using VI or VIM editor

Dear professional,
Recently I moved from one organization to another. In my team all are deleting archive log files using VI editor, They are copying archivelog file names in new vi file and deleting simply.. Can anyone suggest me how to do that (with Deletion command)?
Thanks
Sagar

Thank you for your response..
This is the way we are deleting archivelog files after backups done to make free space in disk.
[root@apps /]# mkdir test
[root@apps /]# cd test
[root@apps test]# vim test1.log
[root@apps test]# vim test2.log
[root@apps test]# vim test3.log
[root@apps test]# vim test4.log
[root@apps test]# vim test5.log
[root@apps test]#
[root@apps test]# ls -lrt
total 20
-rw-r--r-- 1 root root 23 Sep 4 20:36 test1.log
-rw-r--r-- 1 root root 17 Sep 4 20:36 test2.log
-rw-r--r-- 1 root root 7 Sep 4 20:36 test3.log
-rw-r--r-- 1 root root 14 Sep 4 20:37 test4.log
-rw-r--r-- 1 root root 14 Sep 4 20:37 test5.log
[root@apps test]# vim list
test1.log
test2.log
test3.log
test4.log
test5.log
:wq
[root@apps test]# cat list
test1.log
test2.log
test3.log
test4.log
test5.log
[root@apps test]# rm -R `cat list`
[root@apps test]# ls
list
[root@apps test]# rm list
[root@apps test]# ls
[root@apps test]#
Thanks

Auto archive log deletion from single location out of multiple locations.

Hi,
I am running database on 11r1 version.
I have set two archive log locations. now i want archive logs to be deleted through RMAN from only one location the other location shouldn't be affected. what are the specific parameters to be set. Is there any specific command for this please advise.
Thanks in advance.

If you see Hemant's reply in the below link, he had shown how to delete archives from 1 location.
RMAN backup with 2 archive log locations

Archived logs deletion

Hi
I Have deleted 3 of my archivedlogs manually,but they have not marked deleted in V$ARCHIVED_LOG .
so when i'm trying to backup my remained archived logs in RMAN.It doesn't back them up.because RMAN has not been notified with thw deletion.So..
How can I notify RMAN & mark them deleted in V$ARCHIVED_LOG.
Thanks

hi
use crosscheck
SQL> select name from v$archived_log;
NAME
D:\ORACLE\PRODUCT\10.1.0\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2006_11_23\O1_MF_1_
25_2PC98N8M_.ARC
D:\ORACLE\PRODUCT\10.1.0\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2006_11_23\O1_MF_1_
26_2PC9CZF4_.ARC
C:\>del D:\ORACLE\PRODUCT\10.1.0\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2006_11_23\
*.ARC
C:\>sqlplus "sys as sysdba"
SQL*Plus: Release 10.1.0.2.0 - Production on Thu Nov 23 18:54:39 2006
Copyright (c) 1982, 2004, Oracle. All rights reserved.
Enter password:
Connected to:
Oracle Database 10g Enterprise Edition Release 10.1.0.2.0 - Production
With the Partitioning, OLAP and Data Mining options
SQL> select name from v$archived_log;
NAME
D:\ORACLE\PRODUCT\10.1.0\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2006_11_23\O1_MF_1_
25_2PC98N8M_.ARC
D:\ORACLE\PRODUCT\10.1.0\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2006_11_23\O1_MF_1_
26_2PC9CZF4_.ARC
SQL> host rman target=sys
Recovery Manager: Release 10.1.0.2.0 - Production
Copyright (c) 1995, 2004, Oracle. All rights reserved.
target database Password:
connected to target database: ORCL (DBID=1134976990)
RMAN> crosscheck archivelog all;
released channel: ORA_DISK_1
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=215 devtype=DISK
validation failed for archived log
archive log filename=D:\ORACLE\PRODUCT\10.1.0\FLASH_RECOVERY_AREA\ORCL\ARCHIVELO
G\2006_11_23\O1_MF_1_25_2PC98N8M_.ARC recid=1 stamp=607282901
validation failed for archived log
archive log filename=D:\ORACLE\PRODUCT\10.1.0\FLASH_RECOVERY_AREA\ORCL\ARCHIVELO
G\2006_11_23\O1_MF_1_26_2PC9CZF4_.ARC recid=2 stamp=607283007
Crosschecked 2 objects
RMAN> delete expired archivelog all;
released channel: ORA_DISK_1
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=215 devtype=DISK
List of Archived Log Copies
Key     Thrd Seq     S Low Time Name
1       1    25      X 23-NOV-06 D:\ORACLE\PRODUCT\10.1.0\FLASH_RECOVERY_AREA\OR
CL\ARCHIVELOG\2006_11_23\O1_MF_1_25_2PC98N8M_.ARC
2       1    26      X 23-NOV-06 D:\ORACLE\PRODUCT\10.1.0\FLASH_RECOVERY_AREA\OR
CL\ARCHIVELOG\2006_11_23\O1_MF_1_26_2PC9CZF4_.ARC
Do you really want to delete the above objects (enter YES or NO)? yes
deleted archive log
archive log filename=D:\ORACLE\PRODUCT\10.1.0\FLASH_RECOVERY_AREA\ORCL\ARCHIVELO
G\2006_11_23\O1_MF_1_25_2PC98N8M_.ARC recid=1 stamp=607282901
deleted archive log
archive log filename=D:\ORACLE\PRODUCT\10.1.0\FLASH_RECOVERY_AREA\ORCL\ARCHIVELO
G\2006_11_23\O1_MF_1_26_2PC9CZF4_.ARC recid=2 stamp=607283007
Deleted 2 EXPIRED objects
SQL> select name,deleted from v$archived_log;
NAME
DEL
YES
YESHope this helps
Taj

Archive log deletion

Hello,
-rw-r----- 1 oracle dba 193739264 Jun 22 13:23 1_5_754473298.dbf
-rw-r----- 1 oracle dba 193052160 Jun 22 15:00 1_6_754473298.dbf
-rw-r----- 1 oracle dba 492818944 Jun 22 16:14 2_161956_733073720.dbf
-rw-r----- 1 oracle dba 491902976 Jun 22 16:14 2_161955_733073720.dbf
-rw-r----- 1 oracle dba 193459200 Jun 22 16:14 2_161957_733073720.dbf
-rw-r----- 1 oracle dba 193587200 Jun 22 16:14 2_161958_733073720.dbf
-rw-r----- 1 oracle dba 193142272 Jun 22 16:14 2_161959_733073720.dbf
rw-r----- 1 oracle dba 1024 Jun 23 23:17 1_56660_733073720.dbf
-rw-r----- 1 oracle dba 196693504 Jun 23 23:17 2_163084_733073720.dbf
-rw-r----- 1 oracle dba 493167104 Jun 23 23:18 2_163085_733073720.dbf
-rw-r----- 1 oracle dba 492434944 Jun 23 23:19 2_163086_733073720.dbf
-rw-r----- 1 oracle dba 226295808 Jun 24 04:07 c-1981727300-20110624-00
-rw-r----- 1 oracle dba 226263040 Jun 24 10:09 52mfm6c2_1_1
-rw-r----- 1 oracle dba 491752448 Jun 26 23:29 2_164881_733073720.dbf
-rw-r----- 1 oracle dba 192917504 Jun 26 23:31 2_164882_733073720.dbf
-rw-r----- 1 oracle dba 1024 Jun 26 23:31 1_57258_733073720.dbf
-rw-r----- 1 oracle dba 193144320 Jun 26 23:32 2_164883_733073720.dbf
-rw-r----- 1 oracle dba 193007616 Jun 26 23:34 2_164884_733073720.dbf
-rw-r----- 1 oracle dba 194516480 Jun 27 23:48 2_165577_733073720.dbf
-rw-r----- 1 oracle dba 195362816 Jun 27 23:48 2_165578_733073720.dbf
-rw-r----- 1 oracle dba 1024 Jun 27 23:48 1_57490_733073720.dbf
-rw-r----- 1 oracle dba 194276864 Jun 27 23:49 2_165579_733073720.dbf
-rw-r----- 1 oracle dba 494327296 Jun 27 23:51 2_165580_733073720.dbf
-rw-r----- 1 oracle dba 493318656 Jun 27 23:53 2_165581_733073720.dbf
-rw-r----- 1 oracle dba 1024 Jun 27 23:56 1_57491_733073720.dbf
-rw-r----- 1 oracle dba 193768448 Jun 27 23:56 2_165582_733073720.dbf
-rw-r----- 1 oracle dba 193017344 Jun 28 00:10 2_165583_733073720.dbf
-rw-r----- 1 oracle dba 197171712 Jun 28 00:12 2_165584_733073720.dbf
-rw-r----- 1 oracle dba 1024 Jun 28 00:13 1_57492_733073720.dbf
-rw-r----- 1 oracle dba 491688448 Jun 28 00:14 2_165585_733073720.dbf
-rw-r----- 1 oracle dba 494400512 Jun 28 00:15 2_165586_733073720.dbf
-rw-r----- 1 oracle dba 195551232 Jun 28 00:15 2_165587_733073720.dbf
-rw-r----- 1 oracle dba 1024 Jun 28 00:15 1_57493_733073720.dbf
-rw-r----- 1 oracle dba 195021824 Jun 28 00:15 2_165588_733073720.dbf
22,23,24,26,27 of june archive log exist in archive folder when i run
delete archivelog all completed before 'SYSDATE -1'
this command 26 june of some archive deleted but i want to delete above 22,23,24,27 of june archive.how can i delete above dates archivelog.
Thanks,
Umair

Hi;
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF X DAYS; << it says how many days you will keep your db and archive backups If you set it 2 its mean 2 days bakcup will be keep your db backups
For your issue you can set this parameter or you can delete them manualy and then can run crosscheck from rman(Both method mention by Mdtaylor already)
For me i am also using this:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
delete noprompt backup of archivelog until time 'sysdate-4'; << My system is keep my backups 7 days but wiht this command i can delete sysdate-4 hours archivelog from system(Dont forget it will delete wiht hour base,i mean if your time is now 10.00 am than it will delete sysdate-4 until 10.00 am, you can see 10.20 asrchivelog on your system)
Regard
Helios

Redo logs full - how to remove

Hello!
From time to time our database redo logs get full (oracle is running), we go to rman and delete them and everything is fine again.
This time it is the first time we experience this problem when oracle is NOT running.
When we want to start in sqlplus with "startup", oracle DOES NOT start up - we get the error message:
ORA-03113: end-of-file on communication channel
The alert log shows the message:
ORA-19815: WARNING: db_recovery_file_dest_size of 4070572032 bytes is 100.00% used, and has 0 remaining bytes available.
ORA-19809: limit exceeded for recovery files
This time we cannot use RMAN. The problem is, that rman (rman - connect TARGET sys/orac@orcl) only functions with a running database, otherwise we get the error message:
ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
So we deleted the redo logs manually and rebooted, but oracle seems to does not "SEE" this manual deletion. The error message
stays the same.
We wanted to convert our spfile to a pfile, change the redo logs max value to a higher value, and convert this back to a spfile, but this
is also only functionning when the database is running.
Does anybody has a solution for this problem?
Thanks for your help in advance
Wolfgang

Hi,
Its more of a backup policy issue than a technical problem, I would like to go like this....
1. Check if I really need archive logs (in case of Test/Dev environment only export backup should be enough)
2. if you can afford to loose archives better change DB in no arch mode (But you will not be able to take online backup of DB through RMAN)
2. If you need Archives for sure, try getting more space allocated to your archive dest Drive/FS.
Normally we have a practice of keeping the size of arch dest Drive 2 times larger than DB generates in the duration of backup cycle...i.e. if you take arch backup once every day, I would keep archive dest FS size to be able to keep 2 days of archives.
Regards
Rahul

Logical standby | archive log deleted | how to remove gap ???

Similar Messages

Maybe you are looking for