Missing archived logs in v$archived_log

I want to monitor if system accounts such as system, sys or other DBA accounts
did any DML in my application schema. What are the minimal audit statements?
needed to accomplish this. I know using Oracle Database Vault one can set realm to restrict this but I do
not have Data Vault, just looking to audit this using Oracle’s database auditing.
My organization also has Oracle Audi Vault, but Database Auditing Events have to be set in database
first for collection agent to pass this information to Oracle Audit Vault server.
Thanks a lot.

Duplicate post
Please ignore
Missing archived logs in v$archived_log
Handle:      user632098
Status Level:      Newbie
Registered:      Apr 20, 2008
Total Posts:      115
Total Questions:      29 (28 unresolved)
Edited by: sb92075 on Dec 19, 2009 4:49 PM

Similar Messages

Will CDC look for a missing archive log in an alternate log_archive_dest ?

Will CDC look for a missing archive log in an alternate log_archive_dest ?
If a log is deleted from the primary dest, will CDC look in all the altenate destinations before failing? Or is it unaware of the other destinations?

Duplicate post:
missing archive log in backup and restore

Problems Recovering Sysaux table space with missing archive log

Dear All
We have a 10G r2 database running on RHEL 4.2.
Today when updating certain records in one of the databases. whe have started getting the following error:
error occurred at recursive SQL level 2 ORA-00376: file 3 cannot be read at this time ORA-01110: data file 3: '/u02/oradata/EDM/datafile/o1_mf_sysaux_1wwwhpg5_.dbf'
This appears to have occurred as a result of one ofthe users adding a large amount of data to a table in one of the other tablespaces. Checking the V$datafile view shows this file to have a status of RECOVER. However on trying to do a
recover datafile 3;
I'm told that a change number generated back in April 2006 is required, this being in an archive log we no longer have.
My question is how do I recover the datafile to the point in time shown without causing all the other tablespaces to revert to that date.
It seems the SYSAUX tablespace has been in RECOVER status for some time now with no effect on the operation of the database. As such I'm loathe to return all of the database back to 04/2006 and lose 18 months work. Is it possible to just fix the SYSAUX tablespace? If so what is the process? If I recover the TS to the point in time that the missing archive log occurs and then do a reset logs will that truncate all the other tablespaces.
Many Thanks
Paul

Thanks for the reply
WE have a table named mlm_papertrail which, having added about 2000 rows to it, now causes the error shown whenever someone tries to insert a new row into it. Ihave created a new table and pointed the application to it and the problem no longer occurs.
However the SYSAUX tablespace is marked recover as is the datafile that forms it. I can only assume that adding the rows to the table has in turn caused sysaux to expand until it has hit a part of the disk that is damaged or corrupt.
I've tried recovering both the tablespace and the datafile getting the request for the archivelog back in 04/06. Again I can only assume the sysaux file has been damaged at this point, but till now hasn't caused any problems.
I don't want to roll the whole database back to 04/06 since in the main it works fine. But obviously the SYSAUX tablespace needs recovering.
My question is how do I do that with as little pain as possible :-)
Anyway, thanks for the advice. I'll try what you suggest.
regards
paul

Data guard - missed archive log

Hi:
I am on 10.2.0.3, using physical standby. One of my check-up sqls shows missed (not applied) arch log:
SELECT THREAD#, SEQUENCE#, APPLIED FROM V$ARCHIVED_LOG
where applied='NO'
THREAD# SEQUENCE# APP
1 16595 NO
It's relatively old one, my max is 18211i and the log application is going fine.
How can I apply this missed one? Do I have to stop managed recovery and do manual recovery for it?
TIA.

GregX,
Please check if this file actually needs to be applied.
You can find out the when the archived log file was created – FIRST_TIME/NEXT_TIME columns in V$ARCHIVED_LOG.
If the archived log file was created before you created the stand-by DB, you do not need ( nor you can) to apply that file.
Please note that the physical standby would stop applying archivelog if you fail to provide the next required archive log file. Since this has not happened (as per your statement) there is a good chance that you archive redo in question is not needed.
Hope that helps,
Edited by: IordanIotzov on Jan 30, 2009 1:34 PM

Standby database is not applying redo logs due to missing archive log

We use 9.2.0.7 Oracle Database. My goal is to create a physical standby database.
I have followed all the steps necessary to fulfill this in Oracle Data Guard Concepts and Administration manual. Archived redo logs are transmitted from primary to standby database regularly. But the logs are not applied due to archive log gap.
SQL> select process, status from v$managed_standby;
PROCESS STATUS
ARCH CONNECTED
ARCH CONNECTED
MRP0 WAIT_FOR_GAP
RFS RECEIVING
RFS ATTACHED
SQL> select * from v$archive_gap;
THREAD# LOW_SEQUENCE# HIGH_SEQUENCE#
1 503 677
I have tried to find the missing archives on the primary database, but was unable to. They have been deleted (somehow) regularly by the existing backup policy on the primary database. I have looked up the backups, but these archive logs are too old to be in the backup. Backup retention policy is 1 redundant backup of each file. I didn't save older backups as I didn't really need them from up to this point.
I have cross checked (using rman crosscheck) the archive log copies on the primary database and deleted the "obsolete" copies of archive logs. But, v$archived_log view on the primary database only marked those entries as "deleted". Unfortunately, the standby database is still waiting for those logs to "close the gap" and doesn't apply the redo logs at all. I am reluctant to recreate the control file on the primary database as I'm afraid this occurred through the regular database backup operations, due to current backup retention policy and it probably might happen again.
The standby creation procedure was done by using the data files from 3 days ago. The archive logs which are "producing the gap" are older than a month, and are probably unneeded for standby recovery.
What shall I do?
Kind regards and thanks in advance,
Milivoj

On a physical standby database
To determine if there is an archive gap on your physical standby database, query the V$ARCHIVE_GAP view as shown in the following example:
SQL> SELECT * FROM V$ARCHIVE_GAP;
THREAD# LOW_SEQUENCE# HIGH_SEQUENCE#
1 7 10
The output from the previous example indicates your physical standby database is currently missing log files from sequence 7 to sequence 10 for thread 1.
After you identify the gap, issue the following SQL statement on the primary database to locate the archived redo log files on your primary
database (assuming the local archive destination on the primary database is LOG_ARCHIVE_DEST_1):
SQL> SELECT NAME FROM V$ARCHIVED_LOG WHERE THREAD#=1 AND DEST_ID=1 AND 2> SEQUENCE# BETWEEN 7 AND 10;
NAME
/primary/thread1_dest/arcr_1_7.arc /primary/thread1_dest/arcr_1_8.arc /primary/thread1_dest/arcr_1_9.arc
Copy these log files to your physical standby database and register them using the ALTER DATABASE REGISTER LOGFILE statement on your physical standby database. For example:
SQL> ALTER DATABASE REGISTER LOGFILE
'/physical_standby1/thread1_dest/arcr_1_7.arc';
SQL> ALTER DATABASE REGISTER LOGFILE
'/physical_standby1/thread1_dest/arcr_1_8.arc';
After you register these log files on the physical standby database, you can restart Redo Apply.
Note:
The V$ARCHIVE_GAP fixed view on a physical standby database only returns the next gap that is currently blocking Redo Apply from continuing. After resolving the gap and starting Redo Apply, query the V$ARCHIVE_GAP fixed view again on the physical standby database to determine the next gap sequence, if there is one. Repeat this process until there are no more gaps.
Restoring the archived logs from the backup set
If the archived logs are not available in the archive destination then at that time we need to restore the required archived logs from the backup step. This task is accomplished in the following way.
To restore range specified archived logs:
Run {
Set archivelog destination to '/oracle/arch/arch_restore'
Restore archivelog from logseq=<xxxxx> until logseq=<xxxxxxx>
To restore all the archived logs:
Run {
Set archivelog destination to '/oracle/arch/arch_restore';
Restore archivelog all;
}

Two entries for each archive log in v$archived_log

Hi,
I have noticied that there are two entries for each archive log. Why this is so...?
I have fired following command.
==================
set pages 300
set lines 120
ALTER SESSION SET nls_date_format='DD-MON-YYYY HH24:MI:SS';
SELECT sequence#, first_time, next_time
FROM v$archived_log
ORDER BY sequence#;
==================
output is as follows.
==================
1436 24-FEB-2012 00:04:09 24-FEB-2012 08:24:21
1436 24-FEB-2012 00:04:09 24-FEB-2012 08:24:21
1437 24-FEB-2012 08:24:21 24-FEB-2012 15:45:01
1437 24-FEB-2012 08:24:21 24-FEB-2012 15:45:01
1438 24-FEB-2012 15:45:01 24-FEB-2012 15:45:04
1438 24-FEB-2012 15:45:01 24-FEB-2012 15:45:04
1439 24-FEB-2012 15:45:04 24-FEB-2012 15:45:57
1439 24-FEB-2012 15:45:04 24-FEB-2012 15:45:57
1440 24-FEB-2012 15:45:57 24-FEB-2012 17:26:41
1440 24-FEB-2012 15:45:57 24-FEB-2012 17:26:41
1441 24-FEB-2012 17:26:41 24-FEB-2012 18:40:07
1441 24-FEB-2012 17:26:41 24-FEB-2012 18:40:07
1442 24-FEB-2012 18:40:07 24-FEB-2012 19:36:17
1442 24-FEB-2012 18:40:07 24-FEB-2012 19:36:17
1443 24-FEB-2012 19:36:17 24-FEB-2012 19:36:18
1443 24-FEB-2012 19:36:17 24-FEB-2012 19:36:18
==================
Regards
DBA.

I have noticied that there are two entries for each archive log. Why this is so...?Mseberg already mentioned.. little in detail as below
Check for the name column in v$archived_log,
One location refers to Local destination LOG_ARCHIVE_DEST_1
Other location refers to your standby/DR location, But it will shows you only service name instead of full archive name.
select dest_id,name from v$archived_log where name is not null and completion_time like '%24%FEB%'
   DEST_ID NAME
         1 +ORAARCHIVE/prod1/archivelogs/arch_0001_0671689302_0000240097.arc
         2 (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=sldb1srv)(POR
           T=9101)))(CONNECT_DATA=(SERVICE_NAME=prod_sldb1srv_XPT)(INSTANCE_N
           AME=prod1)(SERVER=dedicated)))Edited by: CKPT on Feb 24, 2012 8:26 PM

Missing archived logs when recovering database

Scenario is
1-10 archived logs required to recover database.
5 Number log is missing
It means that 6,7,8,9,10 are useless for me
yes/no Please explain it to me
Thanks a Lot

Hi,
Yes all archivelog after the missing sequence of archivelog will be useless for recovery.
in ur case 6,7,8,9,10 are useless for you.
So only incomplete recovery is the solution.
Thanks
Kuljeet Pal Singh

HELP....How to delete archive log from v$archived_log table...

Hi All
Our prod database was running in Archive log mode and now it is in NO Archive log mode. I deleted all archive logs from the disk but I can still see them in v$archived_log table. How do I delete them from this table.
Environment is Oracle8i(8.1.7) running on Windows 2000 Advanced Server.
Thank you
Amit

Hi,
Recreating the controlfile is the only way to force a cleanup of all entries in v$archived_log.
You can see information on Metalink Note:1012929.6
Paolo

Error after Restoring Datafiles in Archivelog but missing archive log files

Hi all,
I have taken backup yesterday monrning in Archive log mode but have lost all the archive log files. Yesterday night i have restored my DB .
I m happy to have my datafile contents till yesterday morning.
But after restoring when i try to open th DB, i m facing the following errors:
SQL>          Startup open;
Oracle instance started but in mounted stagell
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
SQL>         alter database open resetlogs;
Error: ORA-01113: file 1 needs media recovery
          ORA-01110: data file 1: 'E:\oracle\'<SID>\sapdata1\SYSTEM_1\SYSTEM.DATA1'
SQL>         recover database using backup controlfile until cancel;
ORA-00279 : change 26627919 generated at DATE TIMEneeded for thread 1
ORA-00289 : Suggestion E:\ORACLE\<SID>\ORAARCH\<SID>ARCHARC03020_0683715008.001
ORA-00280: change 266277189 for thread 1 is in sequence #3020
ORA - 01112: media recovery not started
SQL>   recover;
ORA-00283: recovery session cancelled due to errors
ORA-01610: recovery using the BACKUP CONTROLFILE option must be done
Alert Log File:
Starting up ORACLE RDBMS Version: 10.2.0.2.0.
System parameters with non-default values:
processes                = 80
sessions                 = 96
event                    = 10191 trace name context forever, level 1
sga_max_size             = 633339904
shared_pool_size         = 301989888
shared_pool_reserved_size= 30183260
filesystemio_options     = setall
control_files            = E:\ORACLE\IE6\ORIGLOGA\CNTRL\CNTRLIE6.DBF, E:\ORACLE\IE6\ORIGLOGB\CNTRL\CNTRLIE6.DBF, E:\ORACLE\IE6\SAPDATA1\CNTRL\CNTRLIE6.DBF
control_file_record_keep_time= 30
db_block_size            = 8192
db_cache_size            = 301989888
compatible               = 10.2.0
log_archive_dest         = E:\oracle\IE6\oraarch\IE6arch
log_buffer               = 2854912
log_checkpoint_interval = 0
db_files                 = 254
log_checkpoints_to_alert = TRUE
dml_locks                = 4000
undo_management          = AUTO
undo_tablespace          = PSAPUNDO
undo_retention           = 43200
recyclebin               = off
remote_os_authent        = TRUE
remote_login_passwordfile= EXCLUSIVE
job_queue_processes      = 1
background_dump_dest     = E:\ORACLE\IE6\SAPTRACE\BACKGROUND
user_dump_dest           = E:\ORACLE\IE6\SAPTRACE\USERTRACE
core_dump_dest           = E:\ORACLE\IE6\SAPTRACE\BACKGROUND
optimizer_features_enable= 10.2.0.1
sort_area_size           = 2097152
sort_area_retained_size = 0
db_name                  = IE6
open_cursors             = 800
optimpeek_user_binds   = FALSE
pga_aggregate_target     = 402443468
workarea_size_policy     = AUTO
statistics_level         = typical
PMON started with pid=2, OS id=804
PSP0 started with pid=3, OS id=9580
MMAN started with pid=4, OS id=5840
DBW0 started with pid=5, OS id=8136
LGWR started with pid=6, OS id=8712
CKPT started with pid=7, OS id=1620
SMON started with pid=8, OS id=7084
RECO started with pid=9, OS id=9576
CJQ0 started with pid=10, OS id=9156
MMON started with pid=11, OS id=6000
MMNL started with pid=12, OS id=2856
Sat Apr 18 04:01:29 2009
ALTER DATABASE   MOUNT
Sat Apr 18 04:01:33 2009
Setting recovery target incarnation to 1
Sat Apr 18 04:01:33 2009
Successful mount of redo thread 1, with mount id 1124466585
Sat Apr 18 04:01:33 2009
Database mounted in Exclusive Mode
Completed: ALTER DATABASE   MOUNT
Sat Apr 18 04:01:34 2009
ALTER DATABASE OPEN
ORA-1589 signalled during: ALTER DATABASE OPEN...
Sat Apr 18 04:02:13 2009
alter database open resetlogs
Sat Apr 18 04:02:13 2009
ORA-1245 signalled during: alter database open resetlogs...
Sat Apr 18 04:11:05 2009
ALTER DATABASE RECOVER DATABASE UNTIL CANCEL
Sat Apr 18 04:11:05 2009
Media Recovery Start
Sat Apr 18 04:11:06 2009
Media Recovery failed with error 1610
ORA-283 signalled during: ALTER DATABASE RECOVER DATABASE UNTIL CANCEL...
Sat Apr 18 04:11:28 2009
ALTER DATABASE RECOVER DATABASE USING BACKUP CONTROLFILE
Sat Apr 18 04:11:28 2009
Media Recovery Start
parallel recovery started with 3 processes
ORA-279 signalled during: ALTER DATABASE RECOVER DATABASE USING BACKUP CONTROLFILE...
Sat Apr 18 04:17:23 2009
ALTER DATABASE RECOVER database using backup controlfile until cancel
Sat Apr 18 04:17:23 2009
Media Recovery Start
ORA-275 signalled during: ALTER DATABASE RECOVER database using backup controlfile until cancel ...
Any suggestions pls..............
Thanks & Regards,
Subbu

Hello Subbu,
> I have taken backup yesterday monrning in Archive log mode but have lost all the archive log files.
You mean you have taken an online backup and lost all your archive log files after that online backup?
SQL> alter database open resetlogs;
Error: ORA-01113: file 1 needs media recovery
ORA-01110: data file 1: 'E:\oracle\'<SID>\sapdata1\SYSTEM_1\SYSTEM.DATA1'
SQL> recover database using backup controlfile until cancel;
ORA-00279 : change 26627919 generated at DATE TIMEneeded for thread 1
ORA-00289 : Suggestion E:\ORACLE\<SID>\ORAARCH\<SID>ARCHARC03020_0683715008.001
ORA-00280: change 266277189 for thread 1 is in sequence #3020
To perform a recovery with an online backup you will need all archive log files until the end of the online backup. If you have lost them you are not able to recover (or open) your database in a consistent state.
So the only suggestion we can do is:
You need the archive log files that were created during the online backup to perform an incomplete recovery ... if they are gone you can not restore your database.
Regards
Stefan

Duplicate target database - is failed due to missing archive log

Hi,
"duplicate target database to " is failed due to required archive log is not found on tape.
After mounting the right tape, how to proceed , please suggest
ERROR:-->
RMAN>
connect catalog *******
connect auxiliary /
connect target ******
Run {
set until time '16-NOV-2008 23:50';
allocate auxiliary channel t1 type 'sbt_tape' parms ....
duplicate target database to mydb;
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 11/30/2008 10:27:00
RMAN-03015: error occurred in stored script Memory Script
ORA-19501: read error on file "orcl_ARCHIVES_BACKUP_0811160110_u0jvq7vt_1
_1", blockno 1 (blocksize=512)
ORA-27190: skgfrd: sbtread2 returned error
ORA-19511: Error received from media manager layer, error text:
ANS1314E (RC14) File data currently unavailable on server
Recovery Manager complete.
Thanks In Advance,

This is basically not a RMAN problem,but a media management issue,which has to be addressed to the TSM staff:
ANS1314E
File data currently unavailable on server
Explanation:
The file data is currently unavailable on the server. A retrieve or restore operation was attempted. Possible causes are:
Data was corrupted at the server
Server found a read error
File is temporarily involved in a reclaim operation at the server
Server requested a tape volume that was marked unavailable.
System action:
Processing stopped.
User response:
Retry the operation. If the problem continues, see your system administrator to determine the problem from the server console or the activity log. Check whether any requests were made for a tape volume that was unavailable. A tape volume may be marked unavailable if prior read errors were encountered or the volume is checked out of the tape library.
Werner

CAPTURE process error - missing Archive log

Hi -
I am getting cannot open archived log 'xxxx.arc' message when I try to start a newly created capture process. The archive files have been moved by the DBAs.
Is there a way to set the capture process to start from a new archive ?
I tried
exec DBMS_CAPTURE_ADM.ALTER_CAPTURE ( capture_name => 'STRMADMIN_SCH_CAPTURE', start_scn =>9668840362577);
I got the new scn from DBMS_FLASHBACK.GET_SYSTEM_CHANGE_NUMBER();.
But I still get the same error.
Any ideas ?
Thanks,
Sadeepa

If you are on 9i, I know that trying to reset the scn that way won't work. You have to drop and recreate the capture process. You can leave all the rules and rulesets in place, but I think you have to prepare all of the tables again.

Archived log missed in standby database

Hi,
OS; Windows 2003 server
Oracle: 10.2.0.4
Data Guard: Max Performance
Dataguard missed some of the archivelog files and but latest log files are applying. standby database is not in sync with primary.
SELECT LOCAL.THREAD#, LOCAL.SEQUENCE# FROM (SELECT THREAD#, SEQUENCE# FROM V$ARCHIVED_LOG WHERE DEST_ID=1) LOCAL WHERE LOCAL.SEQUENCE# NOT IN (SELECT SEQUENCE# FROM V$ARCHIVED_LOG WHERE DEST_ID=2 AND THREAD# = LOCAL.THREAD#);
I queried above command and I found some files are missed in standby.
select status, type, database_mode, recovery_mode,protection_mode, srl, synchronization_status,synchronized from V$ARCHIVE_DEST_STATUS where dest_id=2;
STATUS TYPE DATABASE_MODE RECOVERY_MODE PROTECTION_MODE SRL SYNCHRONIZATION_STATUS SYN
VALID PHYSICAL MOUNTED-STANDBY MANAGED MAXIMUM PERFORMANCE NO CHECK CONFIGURATION NO
Anyone can tell me how to apply those missed archive log files.
Thanks in advacne

Deccan Charger wrote:
I got below error.
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION
ERROR at line 1:
ORA-01153: an incompatible media recovery is activeYou need to essentially do the following.
1) Stop managed recovery on the standby.
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;2) Resolve the archive log gap - if you have configured FAL_SERVER and FAL_CLIENT Oracle should do this when you follow step 3 below, as you've manually copied the missed logs you should be OK
3) restart managed recovery using the command shown above.
You can monitor archive log catchup using the alert.log or your original query.
Niall Litchfield
http://www.orawin.info/
Edited by: Niall Litchfield on May 4, 2010 2:29 PM
missed tag

Archive logs are missing in hot backup

Hi All,
We are using the following commands to take hot backup of our database. Hot backup is fired by "backup" user on Linux system.
=======================
rman target / nocatalog <<EOF
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '$backup_dir/$date/%F';
run {
allocate channel oem_backup_disk1 type disk format '$backup_dir/$date/%U';
#--Switch archive logs for all threads
sql 'alter system archive log current';
backup as COMPRESSED BACKUPSET database include current controlfile;
#--Switch archive logs for all threads
sql 'alter system archive log current';
#--Backup Archive logs and delete what we've backedup
backup as COMPRESSED BACKUPSET archivelog all not backed up delete all input;
release channel oem_backup_disk1;
allocate channel for maintenance type disk;
delete noprompt obsolete device type disk;
release channel;
exit
EOF
=======================
Due to which after command (used 2 times) "sql 'alter system archive log current';" I see the following lines in alert log 2 times. Because of this all the online logs are not getting archived (Missing 2 logs per day), the backup taken is unusable when restoring. I am worried about this. I there any to avoid this situation.
=======================
Errors in file /u01/oracle/admin/rac/udump/rac1_ora_3546.trc:
ORA-19504: failed to create file "+DATA/rac/1_32309_632680691.dbf"
ORA-17502: ksfdcre:4 Failed to create file +DATA/rac/1_32309_632680691.dbf
ORA-15055: unable to connect to ASM instance
ORA-01031: insufficient privileges
=======================
Regards,
Kunal.

All thanks you for help, pleas find additional information. I goth the following error as log sequence was missing. Everyday during hotbackup, there are 2 missing archive logs, which makes our backup inconsistent and useless.
archive log filename=/mnt/xtra-backup/ora_archivelogs/1_32531_632680691.dbf thread=1 sequence=32531
archive log filename=/mnt/xtra-backup/ora_archivelogs/2_28768_632680691.dbf thread=2 sequence=28768
archive log filename=/mnt/xtra-backup/ora_archivelogs/2_28769_632680691.dbf thread=2 sequence=28769
archive log filename=/mnt/xtra-backup/ora_archivelogs/2_28770_632680691.dbf thread=2 sequence=28770
archive log filename=/mnt/xtra-backup/ora_archivelogs/1_32532_632680691.dbf thread=1 sequence=32532
archive log filename=/mnt/xtra-backup/ora_archivelogs/2_28771_632680691.dbf thread=2 sequence=28771
archive log filename=/mnt/xtra-backup/ora_archivelogs/2_28772_632680691.dbf thread=2 sequence=28772
archive log filename=/mnt/xtra-backup/ora_archivelogs/2_28772_632680691.dbf thread=2 sequence=28773
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 12/13/2012 04:22:56
RMAN-11003: failure during parse/execution of SQL statement: alter database recover logfile '/mnt/xtra-backup/ora_archivelogs/2_28772_632680691.dbf'
ORA-00310: archived log contains sequence 28772; sequence 28773 required
ORA-00334: archived log: '/mnt/xtra-backup/ora_archivelogs/2_28772_632680691.dbf'
Let me try the susggestions provided above.

Archived log not applying

archived logs are not apllying in DR
SQL> select max(sequence#) from v$archived_log where applied='YES';
MAX(SEQUENCE#)
SQL>
SQL> select process,status,sequence# from v$managed_standby;
PROCESS   STATUS        SEQUENCE#
ARCH      CONNECTED             0
ARCH      CONNECTED             0
ARCH      CONNECTED             0
ARCH      CONNECTED             0
RFS       IDLE                  0
RFS       IDLE                  0
RFS       IDLE              34473
MRP0      WAIT_FOR_GAP      31753
RFS       IDLE                  0
RFS       IDLE                  0
RFS       IDLE                  0
11 rows selected.

Hello,
As previously posted, you have a GAP. So, you may have to investigate why the Archived logs cannot be applied.
To do so, you may check for the File System if any Archive destination is FULL. Also, you may have to verify the parameters on the PRIMARY and STANDBY site:
sqlplus "/ as sysdba"
show parameter fal
show parameter dest
show parameter config
show parameter broker
Check also the Alert log on both Primary and Standby.
If the DATAGUARD BROKER is enabled you may also execute this
dgmgrl
show configuration verbose
Also try to "tnsping" the services used in the Archive Destination from both site.
When you are sure that everything is correct then, verify if any Archived logs is missing and try to restore it if possible.
Else if everything is broken, and there's no way to get back the missing Archived logs, you 'll have to "rebuild" the Standby from a new Backup of the PRIMARY.
Hope this help.
Best regards,
Jean-Valentin Lubiez

RMAN-6089: archive log not found or out of sync with catalog

Hi:
I am using OEM, not RMAN, to do a DB backup and got the above error message. I think the problem is caused by some archive logs missing from my NT machine.
I tried to manually copy from an existing archive log and rename it to the missing archive log but it didn't work.
I then tried to backup the archive logs only, not whole DB, and specified "delete input" option, and the process completed successfully.
However, when I tried to re-do the whole DB backup, it failed with the same error.
I looked at v$archived_log and I can see all archive logs, including the ones from previous incarnation and the missing ones from the current incarnation. How can I delete them or change their status (from OEM not from RMAN) from not deleted (NO) to deleted (YES) in order to perform a DB backup?

Hi,
I'm using controlfile for rman. I've issued "change archivelog all validate" before a full backup Before the full backup, I had a incremental backup process crashed(don't know why), which left some entres in v$archived_log. I have no problem completing the rman backup, but "restore archivelog all validate" command gives me "falure of restore..." and all those seq can be found in v$archived_log with "yes" for deleted column. Does that mean controlfile is still not in sync with the system? I don't need those target seq because those were before the full backup. Will there be potential problem later on during recovery? How do I (or when Oracle server will) get rid of those entries in v$archived_log? Thanks.
RMAN> restore archivelog all validate;
Starting restore at 11-AUG-05
using target database controlfile instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=28 devtype=DISK
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 08/11/2005 10:20:24
RMAN-06026: some targets not found - aborting restore
RMAN-06025: no backup of log thread 1 seq 1048 scn 122640071 found to restore
RMAN-06025: no backup of log thread 1 seq 1047 scn 122572176 found to restore
RMAN-06025: no backup of log thread 1 seq 1046 scn 122431604 found to restore
SQL> select name, completion_time,deleted from v$archived_log;
NAME COMPLETIO DEL
/u04/arch/arch_1_1046.arc 10-AUG-05 YES
/u04/arch/arch_1_1047.arc 10-AUG-05 YES
/u04/arch/arch_1_1048.arc 11-AUG-05 YES
/u04/arch/arch_1_1049.arc 11-AUG-05 YES
/u04/arch/arch_1_1050.arc 11-AUG-05 YES

Missing archived logs in v$archived_log

Similar Messages

Maybe you are looking for