7.5 Standby apply log issue - Cold backup of standby

We are in the process of migrating to 7.8 from 7.5 and have a 7.5 standby. Needed to test the time is takes to backup from the standby once we go-live on the 7.8 64bit server. Logs have been applied to the 7.5 standby for more than a month just fine prior to doing a "cold" backup test on the standby. Now the logs will not apply to the standby.
ERR 20039 Log
Logrecovery is not allowed, because state of log volume is 'HistoryLost' (log must be cleared)
2014-05-04 10:02:16
0xF28 WRN 20026 Admin
Initialization of log for 'restore log' failed with 'LogAndDataIncompatible'
First - backing up the standby in ADMIN mode / cold backup on the standby database, right? The source and target (standby) have different server names.
Is it possible to clear the log area or some other process to fix the issue?

Hi Mike,
You may need to restore the database with re-intialization and clear the logs
Refer to the copy steps described in the thread
Error while recover logs
Hope this helps.
Regards,
Deepak Kori

Similar Messages

Restoring archive log after cold backup

Hello forums users,
I read many thing on this topic but I didn't find the good answer.
I performed a cold backup each sunday.
My database is in ARCHIVE LOG mode.
Is it possible to restore ARCHIVE LOG files after restoring COLD backup?
Sunday : cold backup
Monday : new archive log have been created since cold backup
Tuesday : same as Monday
Wednesday : I would like to restore to Monday 22:00 for example
Can I restore cold backup + apply archive log until Monday 22:00 ?
Regards,
Guillaume

recover database using backup controlfile until cancel|time|logseq|scn
will do this and prompt you for the archivelogs.
Known as 'incomplete recovery'
Hth
Sybrand Bakker
Senior Oracle DBA

Rman cold backup on Standby

10.2.0.4 + RMAN + catalog + Data Guard
Hi, I am confused about couple of things here :) Wondering if anyone has faced the same issues.
1. Documentation states the following about taking backups on standby, rather then on primary:
Only the backups that have been written to tape are available to the primary database for restoration and recovery.So if I took a backup to disk and then it went to tape (not directly to tape via RMAN), I cannot use this backup to restore my primary? This doesn't make sense.
2. Oracle recommends to use incrementally-updateable image copy backups as the best practice of backing up standby database. Does anyone have a link to a good explanation of this? Thank you!

Oracle documentation reads:
The accessibility of a backup is different from its association. In a Data Guard environment, the recovery catalog considers disk backups as accessible only to the database with which it is associated, whereas tape backups created on one database are accessible to all databases. If a backup file is not associated with any database, then the row describing it in the recovery catalog view shows null for the SITE_KEY column. By default, RMAN associates files whose SITE_KEY is null with the target database.
http://download.oracle.com/docs/cd/B28359_01/server.111/b28294/rman.htm#BAJFFFFJ
If I take backups to disk on the standby and they don't go to FRA (due to space limitations there) and I then move those disk backups to tape (outside of RMAN), can I use those backups to restore on primary?
Oracle documentation further reads (same site):
When deciding on your backup strategy, Oracle recommends that you take advantage of daily incremental backups. Datafile image copies can be rolled forward with the latest incremental backups, thereby providing up-to-date datafile image copies at all times. RMAN uses the resulting image copy for media recovery just as it would use a full image copy taken at that system change number (SCN), without the overhead of performing a full image copy of the database every day. An additional advantage is that the time-to-recover is reduced because the image copy is updated with the latest block changes and fewer redo logs are required to bring the database back to the current state.
When you take a backup on standby, you still have to take a control backup on BOTH.
Edited by: rysalka on Aug 6, 2009 7:47 AM

DataGuard Applied Log Issue

Hi Gurus,
Oracle Version 9i
OS :- AIX
My query when i am checking the log on Primary database it shows APPLIED=NO' whereas on DR it shows APPLIED=YES for same log sequence.Can you let me know what could be the possible reason and how should i fix it.
I have database is datagurad mode and DG_BROKER=true.
PRIMARY DATABAS_E
On Primary database process running are
SQL> select process,status,sequence# from v$managed_standby;
PROCESS STATUS SEQUENCE#
ARCH CLOSING 596798
ARCH CLOSING 596797
SQL> select sequence#,applied,first_time,next_time,dest_id from v$archived_log where sequence#=596715;
SEQUENCE# APP FIRST_TIM NEXT_TIME DEST_ID
*596715 NO 09-MAR-13 09-MAR-13 1*
*596715 NO 09-MAR-13 09-MAR-13 2*
ON SECONDARY DATABASE_
SQL> select process,status,sequence# from v$managed_standby;
PROCESS STATUS SEQUENCE#
ARCH CONNECTED 0
ARCH CONNECTED 0
MRP0 WAIT_FOR_LOG 596800
RFS RECEIVING 596798
RFS ATTACHED 596797
SQL> show parameter dg_broker_start
NAME TYPE VALUE
dg_broker_start boolean TRUE
SELECT ARCH.THREAD# "Thread", ARCH.SEQUENCE# "Last Sequence Received", APPL.SEQUENCE# "Last Sequence Applied", (ARCH.SEQUENCE# - APPL.SEQUENCE#) "Difference"
FROM
(SELECT THREAD# ,SEQUENCE# FROM V$ARCHIVED_LOG WHERE (THREAD#,FIRST_TIME ) IN (SELECT THREAD#,MAX(FIRST_TIME) FROM V$ARCHIVED_LOG GROUP BY THREAD#)) ARCH,
(SELECT THREAD# ,SEQUENCE# FROM V$LOG_HISTORY WHERE (THREAD#,FIRST_TIME ) IN (SELECT THREAD#,MAX(FIRST_TIME) FROM V$LOG_HISTORY GROUP BY THREAD#)) APPL
WHERE
ARCH.THREAD# = APPL.THREAD#
ORDER BY 1;
Thread Last Sequence Received Last Sequence Applied Difference
1 596799 596799 0
SQL> select sequence#,applied,first_time,next_time,dest_id from v$archived_log where sequence#=596715;
SEQUENCE# APP FIRST_TIM NEXT_TIME DEST_ID
*596715 YES 09-MAR-13 09-MAR-13 0*
Thanks
Meena

Hi Mseberg,
When I am quering on primary database on v$archive_dest_status it shows applied sequence as 596714 . Where as on secondary on v$archived_log i can see all the other log uptil 596799 to be applied
PRIMARY DB_
SQL > select ARCHIVED_THREAD#,ARCHIVED_SEQ#,APPLIED_THREAD#,APPLIED_SEQ# from v$archive_dest_status;
ARCHIVED_THREAD# ARCHIVED_SEQ# APPLIED_THREAD# APPLIED_SEQ#
1 596799 0 0
1 596799 1 596714
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
SECONDARY/DR DB_
SQL> select sequence#,applied,first_time,next_time,dest_id from v$archived_log where sequence#=596714;
SEQUENCE# APP FIRST_TIM NEXT_TIME DEST_ID
596714 YES 09-MAR-13 09-MAR-13 0
SQL> select sequence#,applied,first_time,next_time,dest_id from v$archived_log where sequence#=596715;
SEQUENCE# APP FIRST_TIM NEXT_TIME DEST_ID
596715 YES 09-MAR-13 09-MAR-13 0
SQL> select sequence#,applied,first_time,next_time,dest_id from v$archived_log where sequence#=596716;
SEQUENCE# APP FIRST_TIM NEXT_TIME DEST_ID
596716 YES 09-MAR-13 09-MAR-13 0
Thanks
Meena

The file structure online redo log, archived redo log and standby redo log

I have read some Oracle documentation for file structure and settings in Data Guard environment. But I still have some doubts. What is the best file structure or settings in Oracle 10.2.0.4 on UNIX for a data guard environment with 4 primary databases and 4 physical standby databases. Based on Oracle documents, there are 3 redo logs. They are: online redo logs, archived redo logs and standby redo logs. The basic settings are:
1. Online redo logs --- This redo log must be on Primary database and logical standby database. But it is not necessary to be on physical standby database because physical standby is not open. It doesn't generate redo log. However, if don't set up online redo log on physical standby, when primary failover and switch standby as primary. How can standby perform without online redo logs? In my standby databases, online redo logs have been set up.
2. Archived redo logs --- It is obviously that primary database, logical and physical standby database all need to have this log file being set up. Primary use it to archive log files and ship to standby. Standby use it to receive data from archived log and apply to database.
3. Standby redo logs --- In the document, it says A standby redo log is similar to an online redo log, except that a standby redo log is used to store redo data received from another database. A standby redo log is required if you want to implement: The maximum protection and maximum availability levels of data protection and Real-time apply as well as Cascaded destinations. So it seems that this standby redo log only should be set up on standby database, not on primary database. Am my understanding correct? Because I review current redo log settings on my environment, I have found that Standby redo log directory and files have been set up on both primary and standby databases. I would like to get more information and education from experts. What is the best setting or structure on primary and standby database?

FZheng:
Thanks for your input. It is clear that we need 3 type of redo logs on both databases. You answer my question.
But I have another one. In oracle ducument, it says If you have configured a standby redo log on one or more standby databases in the configuration, ensure the size of the current standby redo log file on each standby database exactly matches the size of the current online redo log file on the primary database. It says: At log switch time, if there are no available standby redo log files that match the size of the new current online redo log file on the primary database. The primary database will shut down
My current one data gurard envirnment setting is: On primary DB, online redo log group size is 512M and standby redo log group size is 500M. On the standby DB, online redo log group size is 500M and standby redo log group size is 750M.
This was setup by someone I don't know. Is this setting OK? or I should change Standby Redo Log on standby DB to 512M to exactly meatch with redo log size on primary?
Edited by: 853153 on Jun 22, 2011 9:42 AM

Number of Standby Redo Logs on Standby Database

Hello All:
Per various docs i calculated and created the number of standby redo logs.
I created 6 standby redo logs in addition to 3 online.
However, i always see only two standby redo logs being used. Any ideas?
Thanks
San~

try:
alter system archive log current;
and get information:
select * from v$logfile;
select * from v$log;
Thanks.

Build standby database using cold backup on a different file system & host

Hi gurus,
The database version is 11.2.0.3. OS is HP UX Itanium 11.31
I am building a standby database using cold backup of primary. The primary mount points are (/p003/oracle, /p004/oracle) on HOST1 and the standby file system on HOST2 are (/s003/oracle,/s004/oracle). I am not using Data Guard to apply logs as we have a script that mounts the log location periodically to standby server and apply the logs to make it current. I am using cold backup as the database is small like 200G and can be taken down. Could someone help me with the steps to build standby using cold backup for a different file location in standby ?? My concern is I can copy the data files from /p003 to /s003. How will I build the controlfile ?
If it was same File system on both HOST 1 and HOST2 I can copy the cold backup to the standby server, build a standby control file on primary and copy and replace the standby control file and everything was set.
Thanks
Cherrish Vaidiyan

Hello;
I have a note on this using a cold copy of the current files instead of a copy backup :
http://www.visi.com/~mseberg/data_guard_on_oracle_10_step_by_step.html
I will post SCP SQL in a moment.
Best Regards
mseberg
set heading off
set feedback off
set pagesize 100
set linesize 400
select 'scp '||a.name ||' server_name:' || a.name as newname from v$datafile a;
select 'scp '||a.name ||' server_name:' || a.name as newname from v$controlfile a;
select 'scp '||a.member ||' server_name:' || a.member as newname from v$logfile a;Edited by: mseberg on May 25, 2013 10:35 AM

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

How to restore cold backup + archived log files

Hi,
Suppose I take a cold backup on 18th. After that I have four days of archived log files. if the database crashes on 5th day, I have to restore the 18th cold back + 4 days of archived log files. How do I restore since it is a cold backup and I cant do incomplete recovery.
can I use
Recover database ( with 18th cold backup) in mount state and apply archived logs.
Prabhath

The details of how you perform forward recovery using a cold backup depends on
1- rman or manual backup
2- using current or backup control file
3- if rman, recovery catalog or no recovery catalog
4- if full database recovered or only a few files
Each of these conditions will affect what is known to Oracle and what needs to be done. For example if you restored the entire cold backup including the control file then Oracle would see a consistent database and not need to perform recovery so you would need to startup mount and tell the database to perform recovery using a backup control file. If using rman and no recovery catalog you might need to catalog some of the archived redo logs, etc....
It is advisable to consult the Backup and Recovery manuals before attempting recovery for any new scenario.
HTH -- Mark D Powell --

Create a standby controlfile using cold backup

Hi All,
We have to setup a DR for a production database.
Here we have the coldbackup which backups all the datafiles and the control file from the production database.
For cloining we generally copy them to another instance and then create controlfile manually. But for setting up as a DR , we would be creating it for standby controlfile.
I tried to google but I am not able to find a way to create a standby controlfile from the existing controlfile cold backup.
OS version solaris 10 , database version 11.2.0.1
Regards
KK
Edited by: Kk on Feb 16, 2012 8:51 AM

Kk wrote:
Hi All,
We have to setup a DR for a production database.
Here we have the coldbackup which backups all the datafiles and the control file from the production database.
For cloining we generally copy them to another instance and then create controlfile manually. But for setting up as a DR , we would be creating it for standby controlfile.
I tried to google but I am not able to find a way to create a standby controlfile from the existing controlfile cold backup.
OS version solaris 10 , database version 11.2.0.1
Regards
KK
Edited by: Kk on Feb 16, 2012 8:51 AMTry as below
My version:
SQL> select * from v$version;
BANNER
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
PL/SQL Release 11.2.0.1.0 - Production
CORE    11.2.0.1.0      Production
TNS for 32-bit Windows: Version 11.2.0.1.0 - Production
NLSRTL Version 11.2.0.1.0 - Production
SQL>1) Taken backup of current controlfile
2) Deleted Current controlfiles
3) Restored using standby clause from current controlfile
4) Mounted & now controlfile type is Standby
Try in this way when you have cold backup. :)
SQL> select controlfile_type from v$database;
CONTROL
CURRENT
RMAN> run
2> {
3> allocate channel ch1 device type disk format 'c:\oracle\control%U.bkp';
4> backup current controlfile;
5> release channel ch1;
6> }
using target database control file instead of recovery catalog
allocated channel: ch1
channel ch1: SID=63 device type=DISK
Starting backup at 16-FEB-12
channel ch1: starting full datafile backup set
channel ch1: specifying datafile(s) in backup set
including current control file in backup set
channel ch1: starting piece 1 at 16-FEB-12
channel ch1: finished piece 1 at 16-FEB-12
piece handle=C:\ORACLE\CONTROL08N3GEA6_1_1.BKP tag=TAG20120216T230334 comment=NONE
channel ch1: backup set complete, elapsed time: 00:00:01
Finished backup at 16-FEB-12
released channel: ch1
RMAN> exit
RMAN> restore standby controlfile from 'C:\ORACLE\CONTROL08N3GEA6_1_1.BKP';
Starting restore at 16-FEB-12
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=66 device type=DISK
channel ORA_DISK_1: restoring control file
channel ORA_DISK_1: restore complete, elapsed time: 00:00:03
output file name=C:\ORACLE\ORADATA\ORCL\CONTROL01.CTL
output file name=C:\ORACLE\FLASH_RECOVERY_AREA\ORCL\CONTROL02.CTL
Finished restore at 16-FEB-12
SQL> alter database mount;
Database altered.
SQL> select controlfile_type from v$database;
CONTROL
STANDBY
SQL>
Some More information:-
Even if your database backup is old, still you can create a new standby controlfile and restore new controlfile and restore database. Later after starting MRP all will be synchronized. No issues
SQL> select controlfile_type from v$database;
CONTROL
CURRENT
SQL> alter database create standby controlfile as 'c:\oracle\control_stby.ctl';
Database altered.
SQL> $dir c:\oracle\con*
Volume in drive C is System
Volume Serial Number is 1853-3E21
Directory of c:\oracle
02/16/2012 11:41 PM         9,748,480 CONTROL_STBY.CTL
               1 File(s)     19,546,112 bytes
               0 Dir(s) 177,185,570,816 bytes free
SQL>Now Just restore database. You already have backup.
Or
If you have opportunity you can go ahead for Duplicate/Duplicate from active database
Edited by: CKPT on Feb 16, 2012 11:41 PM

Dataguard - Primary not applying logs to Standby

Having an issue applying logs to the standby, seemingly it's not setup correctly. I am sure I'm missing something simple here, but would love any input or help. Thanks in advance.
Background:
Primary: CDPMTSB (Single Stand alone)
Standby: CDPMT (RAC)
Error Message on Primary (Alert Log):
Errors in file /data/oracle/app/oracle/diag/rdbms/cdpmtsb/CDPMTSB/trace/CDPMTSB_arc6_9571.trc:
ORA-16014: log 3 sequence# 4071 not archived, no available destinations
ORA-00312: online log 3 thread 2: '+FRA_DG_01/cdpmtsb/onlinelog/group_3.291.799379949'
ARCH: Archival error occurred on a closed thread. Archiver continuing
ORACLE Instance CDPMTSB - Archival Error. Archiver continuing.
Mon Nov 19 19:54:24 2012
Changing destination 4 from remote to local during archival of log#: 3 sequence#: 4071 thread#: 2
Changing destination 4 from remote to local during archival of log#: 3 sequence#: 4071 thread#: 2
ARC6: LGWR is actively archiving destination LOG_ARCHIVE_DEST_2
ARC6: Archive log rejected (thread 2 sequence 4071) at host 'CDPMT'
Errors in file /data/oracle/app/oracle/diag/rdbms/cdpmtsb/CDPMTSB/trace/CDPMTSB_arc6_9571.trc:
ORA-16401: archivelog rejected by RFS
Errors in file /data/oracle/app/oracle/diag/rdbms/cdpmtsb/CDPMTSB/trace/CDPMTSB_arc6_9571.trc:
ORA-16014: log 3 sequence# 4071 not archived, no available destinations
ORA-00312: online log 3 thread 2: '+FRA_DG_01/cdpmtsb/onlinelog/group_3.291.799379949'
ARCH: Archival error occurred on a closed thread. Archiver continuing
ORACLE Instance CDPMTSB - Archival Error. Archiver continuing.
Mon Nov 19 19:59:24 2012
Changing destination 4 from remote to local during archival of log#: 3 sequence#: 4071 thread#: 2
Changing destination 4 from remote to local during archival of log#: 3 sequence#: 4071 thread#: 2
ARC6: LGWR is actively archiving destination LOG_ARCHIVE_DEST_2
ARC6: Archive log rejected (thread 2 sequence 4071) at host 'CDPMT'
Errors in file /data/oracle/app/oracle/diag/rdbms/cdpmtsb/CDPMTSB/trace/CDPMTSB_arc6_9571.trc:
ORA-16401: archivelog rejected by RFS
Errors in file /data/oracle/app/oracle/diag/rdbms/cdpmtsb/CDPMTSB/trace/CDPMTSB_arc6_9571.trc:
ORA-16014: log 3 sequence# 4071 not archived, no available destinations
ORA-00312: online log 3 thread 2: '+FRA_DG_01/cdpmtsb/onlinelog/group_3.291.799379949'
ARCH: Archival error occurred on a closed thread. Archiver continuing
ORACLE Instance CDPMTSB - Archival Error. Archiver continuing.
Mon Nov 19 20:00:00 2012
Errors in file /data/oracle/app/oracle/diag/rdbms/cdpmtsb/CDPMTSB/trace/CDPMTSB_j001_17473.trc:
ORA-12012: error on auto execute of job 72620
ORA-06502: PL/SQL: numeric or value error: character to number conversion error
ORA-06512: at "CD_ADMIN.UTDCD_SURVEY_PKG", line 4926
Standby Alert Log:
ORA-16401: archivelog rejected by RFS
Mon Nov 19 19:32:15 2012
RFS[6]: Assigned to RFS process 4248
RFS[6]: Identified database type as 'physical standby': Client is ARCH pid 9561
Mon Nov 19 19:32:22 2012
RFS[1]: Selected log 6 for thread 1 sequence 4073 dbid 1629723947 branch 769881773
Mon Nov 19 19:32:22 2012
Archived Log entry 1097 added for thread 1 sequence 4072 ID 0x62e7f5cf dest 1:
Archived Log entry 1098 added for thread 1 sequence 4072 ID 0x62e7f5cf dest 3:
Mon Nov 19 19:34:23 2012
Errors in file /opt/app/oracle/diag/rdbms/cdpmt/CDPMT1/trace/CDPMT1_rfs_24994.trc:
ORA-16401: archivelog rejected by RFS
Mon Nov 19 19:38:12 2012
RFS[1]: Selected log 5 for thread 1 sequence 4074 dbid 1629723947 branch 769881773
Mon Nov 19 19:38:12 2012
Archived Log entry 1099 added for thread 1 sequence 4073 ID 0x62e7f5cf dest 1:
Archived Log entry 1100 added for thread 1 sequence 4073 ID 0x62e7f5cf dest 3:
Mon Nov 19 19:39:23 2012
Errors in file /opt/app/oracle/diag/rdbms/cdpmt/CDPMT1/trace/CDPMT1_rfs_24994.trc:
ORA-16401: archivelog rejected by RFS
Mon Nov 19 19:44:24 2012
Errors in file /opt/app/oracle/diag/rdbms/cdpmt/CDPMT1/trace/CDPMT1_rfs_24994.trc:
ORA-16401: archivelog rejected by RFS
Mon Nov 19 19:49:24 2012
Errors in file /opt/app/oracle/diag/rdbms/cdpmt/CDPMT1/trace/CDPMT1_rfs_24994.trc:
ORA-16401: archivelog rejected by RFS
Mon Nov 19 19:54:24 2012
Errors in file /opt/app/oracle/diag/rdbms/cdpmt/CDPMT1/trace/CDPMT1_rfs_24994.trc:
ORA-16401: archivelog rejected by RFS
Mon Nov 19 19:59:24 2012
Errors in file /opt/app/oracle/diag/rdbms/cdpmt/CDPMT1/trace/CDPMT1_rfs_24994.trc:
ORA-16401: archivelog rejected by RFS
Primary Parameters:
NAME TYPE VALUE
log_archive_config string DG_CONFIG=(CDPMT,CDPMTSB)
log_archive_dest string
log_archive_dest_1 string LOCATION=USE_DB_RECOVERY_FILE_
DEST VALID_FOR=(ONLINE_LOGFIL
ES,ALL_ROLES) DB_UNIQUE_NAME=C
DPMTSB
log_archive_dest_10 string
log_archive_dest_2 string SERVICE=CDPMT VALID_FOR=(ONLIN
E_LOGFILES,PRIMARY_ROLE) DB_UN
IQUE_NAME=CDPMT
log_archive_dest_3 string location="+FRA_DG_01/cdpmtsb/s
tandbylog", valid_for=(STANDB
Y_LOGFILE,STANDBY_ROLE)
log_archive_dest_4 string
log_archive_dest_5 string
log_archive_dest_6 string
log_archive_dest_7 string
log_archive_dest_8 string
log_archive_dest_9 string
log_archive_dest_state_1 string enable
log_archive_dest_state_10 string enable
log_archive_dest_state_2 string ENABLE
log_archive_dest_state_3 string ENABLE
log_archive_dest_state_4 string defer
log_archive_dest_state_5 string enable
log_archive_dest_state_6 string enable
log_archive_dest_state_7 string enable
log_archive_dest_state_8 string enable
log_archive_dest_state_9 string enable
log_archive_duplex_dest string
log_archive_format string %t_%s_%r.dbf
log_archive_local_first boolean TRUE
log_archive_max_processes integer 7
log_archive_min_succeed_dest integer 2
log_archive_start boolean FALSE
log_archive_trace integer 0
Standby Parameters:
NAME TYPE VALUE
log_archive_config string dg_config=(CDPMT,CD PMTSB)
log_archive_dest string
log_archive_dest_1 string location="USE_DB_RE COVERY_FILE
_DEST", valid_for= (ALL_LOGFIL
ES,ALL_ROLES)
log_archive_dest_10 string
log_archive_dest_2 string SERVICE=cdpmtsb LGW R ASYNC VAL
ID_FOR=(ONLINE_LOGF ILES,PRIMAR
Y_ROLE) DB_UNIQUE_N AME=cdpmtsb
log_archive_dest_3 string LOCATION=+FRA_DG_01 /CDPMT/STAN
DBYLOG VALID_FOR=( STANDBY_LOG
NAME TYPE VALUE
FILES,STANDBY_ROLE) DB_UNIQUE_
NAME=CDPMT
log_archive_dest_4 string
log_archive_dest_5 string
log_archive_dest_6 string
log_archive_dest_7 string
log_archive_dest_8 string
log_archive_dest_9 string
log_archive_dest_state_1 string ENABLE
log_archive_dest_state_10 string enable
log_archive_dest_state_2 string ENABLE
NAME TYPE VALUE
log_archive_dest_state_3 string enable
log_archive_dest_state_4 string enable
log_archive_dest_state_5 string enable
log_archive_dest_state_6 string enable
log_archive_dest_state_7 string enable
log_archive_dest_state_8 string enable
log_archive_dest_state_9 string enable
log_archive_duplex_dest string
log_archive_format string %t_%s_%r.dbf
log_archive_local_first boolean TRUE
log_archive_max_processes integer 30
NAME TYPE VALUE
log_archive_min_succeed_dest integer 1
log_archive_start boolean FALSE
log_archive_trace integer 0
SQL> show parameter log_ar
NAME TYPE VALUE
log_archive_config string dg_config=(CDPMT,CDPMTSB)
log_archive_dest string
log_archive_dest_1 string location="USE_DB_RECOVERY_FILE
_DEST", valid_for=(ALL_LOGFIL
ES,ALL_ROLES)
log_archive_dest_10 string
log_archive_dest_2 string SERVICE=cdpmtsb LGWR ASYNC VAL
ID_FOR=(ONLINE_LOGFILES,PRIMAR
Y_ROLE) DB_UNIQUE_NAME=cdpmtsb
log_archive_dest_3 string LOCATION=+FRA_DG_01/CDPMT/STAN
DBYLOG VALID_FOR=(STANDBY_LOG
NAME TYPE VALUE
FILES,STANDBY_ROLE) DB_UNIQUE_
NAME=CDPMT
log_archive_dest_4 string
log_archive_dest_5 string
log_archive_dest_6 string
log_archive_dest_7 string
log_archive_dest_8 string
log_archive_dest_9 string
log_archive_dest_state_1 string ENABLE
log_archive_dest_state_10 string enable
log_archive_dest_state_2 string ENABLE
NAME TYPE VALUE
log_archive_dest_state_3 string enable
log_archive_dest_state_4 string enable
log_archive_dest_state_5 string enable
log_archive_dest_state_6 string enable
log_archive_dest_state_7 string enable
log_archive_dest_state_8 string enable
log_archive_dest_state_9 string enable
log_archive_duplex_dest string
log_archive_format string %t_%s_%r.dbf
log_archive_local_first boolean TRUE
log_archive_max_processes integer 30
NAME TYPE VALUE
log_archive_min_succeed_dest integer 1
log_archive_start boolean FALSE
log_archive_trace integer 0
SQL>
DGMGRL> show configuration verbose;
Configuration
Name: cdpmtqa
Enabled: YES
Protection Mode: MaxPerformance
Databases:
cdpmtsb - Primary database
cdpmt - Physical standby database
Fast-Start Failover: DISABLED
Current status for "cdpmtqa":
Warning: ORA-16608: one or more databases have warnings
DGMGRL> show database verbose CDPMT
Database
Name: cdpmt
Role: PHYSICAL STANDBY
Enabled: YES
Intended State: APPLY-ON
Instance(s):
CDPMT1
CDPMT2 (apply instance)
Properties:
DGConnectIdentifier = 'cdpmt'
ObserverConnectIdentifier = ''
LogXptMode = 'ASYNC'
DelayMins = '0'
Binding = 'OPTIONAL'
MaxFailure = '0'
MaxConnections = '1'
ReopenSecs = '300'
NetTimeout = '30'
RedoCompression = 'DISABLE'
LogShipping = 'ON'
PreferredApplyInstance = ''
ApplyInstanceTimeout = '0'
ApplyParallel = 'AUTO'
StandbyFileManagement = 'AUTO'
ArchiveLagTarget = '0'
LogArchiveMaxProcesses = '4'
LogArchiveMinSucceedDest = '1'
DbFileNameConvert = ''
LogFileNameConvert = ''
FastStartFailoverTarget = ''
StatusReport = '(monitor)'
InconsistentProperties = '(monitor)'
InconsistentLogXptProps = '(monitor)'
SendQEntries = '(monitor)'
LogXptStatus = '(monitor)'
RecvQEntries = '(monitor)'
HostName(*)
SidName(*)
StaticConnectIdentifier(*)
StandbyArchiveLocation(*)
AlternateLocation(*)
LogArchiveTrace(*)
LogArchiveFormat(*)
LatestLog(*)
TopWaitEvents(*)
(*) - Please check specific instance for the property value
Current status for "cdpmt":
Warning: ORA-16809: multiple warnings detected for the database
Any help would be really appreciated. Thanks!
Edited by: 972075 on Nov 19, 2012 3:09 PM

Thanks MSEBERG,
Here's what I found. FRA seems to have enough space on ASM and there are other logs there, not sure what the issue is:
14:31:58 SYS: CDPMTSB> show parameter db_recovery
NAME TYPE VALUE
db_recovery_file_dest string +FRA_DG_01
db_recovery_file_dest_size big integer 60G
DGMGRL> show database CDPMTSB logxptstatus;
LOG TRANSPORT STATUS
PRIMARY_INSTANCE_NAME STANDBY_DATABASE_NAME STATUS
CDPMTSB cdpmt
DGMGRL> SHOW DATABASE CDPMTSB InconsistentProperties;
INCONSISTENT PROPERTIES
INSTANCE_NAME PROPERTY_NAME MEMORY_VALUE SPFILE_VALUE BROKER_VALUE
DGMGRL> show database CDPMTSB InconsistentLogXptProps;
INCONSISTENT LOG TRANSPORT PROPERTIES
INSTANCE_NAME STANDBY_NAME PROPERTY_NAME MEMORY_VALUE BROKER_VALUE
DGMGRL> show database CDPMT logxptstatus;
Error: ORA-16757: unable to get this property's value
DGMGRL> SHOW DATABASE CDPMT InconsistentProperties;
INCONSISTENT PROPERTIES
INSTANCE_NAME PROPERTY_NAME MEMORY_VALUE SPFILE_VALUE BROKER_VALUE
CDPMT2 DbFileNameConvert DG_01/cdpmtsb, DG_01/cdpmt
CDPMT2 LogFileNameConvert FRA_DG_01/cdpmtsb, FRA_DG_01/cdpmt, DG_01/cdpmtsb, DG_01/cdpmt
CDPMT1 LogArchiveMaxProcesses 4 30 4
CDPMT1 DbFileNameConvert DG_01/cdpmtsb, DG_01/cdpmt DG_01/cdpmtsb,DG_01/cdpmt
CDPMT1 LogFileNameConvert FRA_DG_01/cdpmtsb, FRA_DG_01/cdpmt, DG_01/cdpmtsb, DG_01/cdpmt FRA_DG_01/cdpmtsb,FRA_DG_01/cdpmt,+DG_01/cdpmtsb,+DG_01/cdpmt
DGMGRL> show database CDPMT InconsistentLogXptProps;
Error: ORA-16757: unable to get this property's value
Errors in the Alert (from Primary):
ARCH: Archival error occurred on a closed thread. Archiver continuing
ORACLE Instance CDPMTSB - Archival Error. Archiver continuing.
Tue Nov 20 14:34:43 2012
Changing destination 4 from remote to local during archival of log#: 3 sequence#: 4071 thread#: 2
Changing destination 4 from remote to local during archival of log#: 3 sequence#: 4071 thread#: 2
ARC6: LGWR is actively archiving destination LOG_ARCHIVE_DEST_2
ARC6: Archive log rejected (thread 2 sequence 4071) at host 'cdpmt'
Errors in file /data/oracle/app/oracle/diag/rdbms/cdpmtsb/CDPMTSB/trace/CDPMTSB_arc6_9571.trc:
ORA-16401: archivelog rejected by RFS
Errors in file /data/oracle/app/oracle/diag/rdbms/cdpmtsb/CDPMTSB/trace/CDPMTSB_arc6_9571.trc:
ORA-16014: log 3 sequence# 4071 not archived, no available destinations
ORA-00312: online log 3 thread 2: '+FRA_DG_01/cdpmtsb/onlinelog/group_3.291.799379949'
ARCH: Archival error occurred on a closed thread. Archiver continuing
ORACLE Instance CDPMTSB - Archival Error. Archiver continuing.
DGMGRL> DGMGRL> show database verbose CDPMT
Database
Name: cdpmt
Role: PHYSICAL STANDBY
Enabled: YES
Intended State: APPLY-ON
Instance(s):
CDPMT1
CDPMT2 (apply instance)
Properties:
DGConnectIdentifier = 'cdpmt'
ObserverConnectIdentifier = ''
LogXptMode = 'ASYNC'
DelayMins = '0'
Binding = 'OPTIONAL'
MaxFailure = '0'
MaxConnections = '1'
ReopenSecs = '300'
NetTimeout = '30'
RedoCompression = 'DISABLE'
LogShipping = 'ON'
PreferredApplyInstance = ''
ApplyInstanceTimeout = '0'
ApplyParallel = 'AUTO'
StandbyFileManagement = 'AUTO'
ArchiveLagTarget = '0'
LogArchiveMaxProcesses = '4'
LogArchiveMinSucceedDest = '1'
DbFileNameConvert = ''
LogFileNameConvert = ''
FastStartFailoverTarget = ''
StatusReport = '(monitor)'
InconsistentProperties = '(monitor)'
InconsistentLogXptProps = '(monitor)'
SendQEntries = '(monitor)'
LogXptStatus = '(monitor)'
RecvQEntries = '(monitor)'
HostName(*)
SidName(*)
StaticConnectIdentifier(*)
StandbyArchiveLocation(*)
AlternateLocation(*)
LogArchiveTrace(*)
LogArchiveFormat(*)
LatestLog(*)
TopWaitEvents(*)
(*) - Please check specific instance for the property value
Current status for "cdpmt":
Warning: ORA-16809: multiple warnings detected for the database
DGMGRL> show database verbose CDPMTSB
Database
Name: cdpmtsb
OEM Name: CDPMTSB_devdb40.utd.com
Role: PRIMARY
Enabled: YES
Intended State: TRANSPORT-ON
Instance(s):
CDPMTSB
Properties:
DGConnectIdentifier = 'cdpmtsb'
ObserverConnectIdentifier = ''
LogXptMode = 'ASYNC'
DelayMins = '0'
Binding = 'OPTIONAL'
MaxFailure = '0'
MaxConnections = '1'
ReopenSecs = '300'
NetTimeout = '30'
RedoCompression = 'DISABLE'
LogShipping = 'ON'
PreferredApplyInstance = ''
ApplyInstanceTimeout = '0'
ApplyParallel = 'AUTO'
StandbyFileManagement = 'AUTO'
ArchiveLagTarget = '0'
LogArchiveMaxProcesses = '7'
LogArchiveMinSucceedDest = '2'
DbFileNameConvert = '+DG_01/cdpmt, +DG_01/cdpmtsb'
LogFileNameConvert = '+FRA_DG_01/cdpmt, FRA_DG_01/cdpmtsb, DG_01/cdpmt, +DG_01/cdpmtsb'
FastStartFailoverTarget = ''
StatusReport = '(monitor)'
InconsistentProperties = '(monitor)'
InconsistentLogXptProps = '(monitor)'
SendQEntries = '(monitor)'
LogXptStatus = '(monitor)'
RecvQEntries = '(monitor)'
HostName = 'devdb40.utd.com'
SidName = 'CDPMTSB'
StaticConnectIdentifier = '(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=devdb40.utd.com)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=CDPMTSB_DGMGRL)(INSTANCE_NAME=CDPMTSB)(SERVER=DEDICATED)))'
StandbyArchiveLocation = '+FRA_DG_01/cdpmtsb/standbylog'
AlternateLocation = ''
LogArchiveTrace = '0'
LogArchiveFormat = '%t_%s_%r.dbf'
LatestLog = '(monitor)'
TopWaitEvents = '(monitor)'
Current status for "cdpmtsb":
SUCCESS
Thanks for your help btw, I'm really at a loss here as to what is going on with this.

Applying logs in a semi-standby instance

Oracle Version: 10.2.0.3 Standard Edition
OS: Windows 2003 Server
I setup oracle standby (followed the steps in metalink doc 432514.1)..
I am running 10.2.0.3 standard edition.. so teh standby have to be done manually (which is fine)..
I shutdown production last night with shutdown immediate.. copy all the logs, datafiles, pfile..etc to the standby server.. I recreated the controlfile on the standby (NORESETLOGS and NOARCHIVELOGS).. the database is mounted and it's ok:
SQL> select status from v$instance;
STATUS
MOUNTED
SQL>
SQL> select * from v$log;
GROUP# THREAD# SEQUENCE# BYTES MEMBERS ARC STATUS FIRST_CHANGE# FIRST_TIM
1 1 6764 52428800 2 NO INACTIVE 2437870303 07-MAY-09
3 1 6765 52428800 2 NO INACTIVE 2437871111 07-MAY-09
2 1 6766 52428800 2 NO CURRENT 2437886254 07-MAY-09
SQL>
then after that I restarted production, after a while, I did a couple of switch logs and generated 2 archive logs of which I transferred to the standby to apply them.. now at this stage prod redo logs are:
SQL> select * from v$log
GROUP# THREAD# SEQUENCE# BYTES MEMBERS ARC STATUS FIRST_CHANGE# FIRST_TIM
1 1 6767 52428800 2 YES INACTIVE 2438366118 08-MAY-09
2 1 6766 52428800 2 YES INACTIVE 2437886254 07-MAY-09
3 1 6768 52428800 2 NO CURRENT 2438369450 08-MAY-09
SQL>
On the standby, I logged in as sysdba and tried to just apply the logs as you do normally:
C:\scheduled_scripts>sqlplus "/as sysdba"
SQL*Plus: Release 10.2.0.3.0 - Production on Fri May 8 08:58:03 2009
Copyright (c) 1982, 2006, Oracle. All Rights Reserved.
Connected to:
Oracle Database 10g Release 10.2.0.3.0 - Production
SQL> select status from v$instance;
STATUS
MOUNTED
SQL>
SQL>
SQL> recover database using backup controlfile until cancel;
ORA-00279: change 2438369450 generated at 05/08/2009 07:45:07 needed for thread
1
ORA-00289: suggestion :
D:\ORACLE\PRODUCT\FLASH_RECOVERY_AREA\EBCP01\ARCHIVELOG\2009_05_08\O1_MF_1_6768_%U_.ARC
ORA-00280: change 2438369450 for thread 1 is in sequence #6768
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
D:\ORACLE\PRODUCT\FLASH_RECOVERY_AREA\EBCP01\ARCHIVELOG\2009_05_08\O1_MF_1_6767_508KCMM0_.ARC
ORA-00310: archived log contains sequence 6767; sequence 6768 required
ORA-00334: archived log:
'D:\ORACLE\PRODUCT\FLASH_RECOVERY_AREA\EBCP01\ARCHIVELOG\2009_05_08\O1_MF_1_6767_508KCMM0_.ARC'
SQL>
So my question is why isn't it applying the 6767 change? (keep in mind that at this stage production has not yet generated archive log 6768).. shouldn't it be applying 6767? or is it bcoz it's Inactive, it doesn't need to do that?
More over, I did the following:
I did a switch log on production to create the 6768 archive log:
SQL> select * from v$log
GROUP# THREAD# SEQUENCE# BYTES MEMBERS ARC STATUS FIRST_CHANGE# FIRST_TIM
1 1 6767 52428800 2 YES INACTIVE 2438366118 08-MAY-09
2 1 6766 52428800 2 YES INACTIVE 2437886254 07-MAY-09
3 1 6768 52428800 2 NO CURRENT 2438369450 08-MAY-09
SQL>
SQL>
SQL> alter system switch logfile;
System altered.
SQL> select * from v$log;
GROUP# THREAD# SEQUENCE# BYTES MEMBERS ARC STATUS FIRST_CHANGE# FIRST_TIM
1 1 6767 52428800 2 YES INACTIVE 2438366118 08-MAY-09
2 1 6769 52428800 2 NO CURRENT 2438387289 08-MAY-09
3 1 6768 52428800 2 YES ACTIVE 2438369450 08-MAY-09
this generated teh archive log: O1_MF_1_6768_508VGSS5_.ARC
I copied the archive log to the standby serve.. checked teh current sequence (database only mounted on standby):
SQL> select * from v$log
GROUP# THREAD# SEQUENCE# BYTES MEMBERS ARC STATUS FIRST_CHANGE# FIRST_TIM
1 1 6764 52428800 2 NO INACTIVE 2437870303 07-MAY-09
3 1 6765 52428800 2 NO INACTIVE 2437871111 07-MAY-09
2 1 6766 52428800 2 NO CURRENT 2437886254 07-MAY-09
C:\scheduled_scripts>sqlplus "/as sysdba"
SQL*Plus: Release 10.2.0.3.0 - Production on Fri May 8 10:46:38 2009
Copyright (c) 1982, 2006, Oracle. All Rights Reserved.
Connected to:
Oracle Database 10g Release 10.2.0.3.0 - Production
SQL> recover database using backup controlfile until cancel;
ORA-00279: change 2438369450 generated at 05/08/2009 07:45:07 needed for thread1
ORA-00289: suggestion :
D:\ORACLE\PRODUCT\FLASH_RECOVERY_AREA\EBCP01\ARCHIVELOG\2009_05_08\O1_MF_1_6768_%U_.ARC
ORA-00280: change 2438369450 for thread 1 is in sequence #6768
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
AUTO
ORA-00279: change 2438387289 generated at 05/08/2009 10:37:29 needed for thread1
ORA-00289: suggestion :
D:\ORACLE\PRODUCT\FLASH_RECOVERY_AREA\EBCP01\ARCHIVELOG\2009_05_08\O1_MF_1_6769_%U_.ARC
ORA-00280: change 2438387289 for thread 1 is in sequence #6769
ORA-00278: log file
'D:\ORACLE\PRODUCT\FLASH_RECOVERY_AREA\EBCP01\ARCHIVELOG\2009_05_08\O1_MF_1_6768_508VGSS5_.ARC' no longer needed for this recovery
ORA-00308: cannot open archived log
'D:\ORACLE\PRODUCT\FLASH_RECOVERY_AREA\EBCP01\ARCHIVELOG\2009_05_08\O1_MF_1_6769_%U_.ARC'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
and as you can see.. now that it has 6768, it's doing the same thing by not wanting it anymore and wanting the next one in teh sequence which is 6769 (which has not been generated on production yet).. I'm just not making any sense out of this!!
now afer few changes, the production sequence is:
SQL> select * from v$log;
GROUP# THREAD# SEQUENCE# BYTES MEMBERS ARC STATUS FIRST_CHANGE# FIRST_TIM
1 1 6773 52428800 2 YES ACTIVE *2438396976* 08-MAY-09
2 1 6772 52428800 2 YES INACTIVE 2438394852 08-MAY-09
3 1 6774 52428800 2 NO CURRENT 2438398862 08-MAY-09
standby sequence is:
SQL> SELECT * FROM V$LOG;
GROUP# THREAD# SEQUENCE# BYTES MEMBERS ARC STATUS FIRST_CHANGE# FIRST_TIM
1 1 6764 52428800 2 NO INACTIVE 2437870303 07-MAY-09
3 1 6765 52428800 2 NO INACTIVE 2437871111 07-MAY-09
2 1 6766 52428800 2 NO CURRENT 2437886254 07-MAY-09
If I try to do the following on standby (archived has been shipped to standby at this stage) and do the AUTO option, it doesnt like the file:
SQL> RECOVER DATABASE using backup controlfile UNTIL CHANGE 2438396976;
ORA-00279: change 2438396976 generated at 05/08/2009 11:45:02 needed for thread 1
ORA-00289: suggestion : D:\ORACLE\PRODUCT\FLASH_RECOVERY_AREA\EBCP01\ARCHIVELOG\2009_05_08\O1_MF_1_6773_%U_.ARC
ORA-00280: change 2438396976 for thread 1 is in sequence #6773
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
AUTO
ORA-00308: cannot open archived log 'D:\ORACLE\PRODUCT\FLASH_RECOVERY_AREA\EBCP01\ARCHIVELOG\2009_05_08\O1_MF_1_6773_%U_.ARC'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
ORA-00308: cannot open archived log 'D:\ORACLE\PRODUCT\FLASH_RECOVERY_AREA\EBCP01\ARCHIVELOG\2009_05_08\O1_MF_1_6773_%U_.ARC'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
but when i try to do the same and I actuially give it the proper file name (no _%U) then it's ok and does the recovery.. Is there a way of telling Oracle to grab the acual file name, not O1_MF_1_6773_50909L7L_.ARC instead of O1_MF_1_6773_%U_.ARC?
SQL> RECOVER DATABASE using backup controlfile UNTIL CHANGE *2438396976*;
ORA-00279: change 2438396976 generated at 05/08/2009 11:45:02 needed for thread 1
ORA-00289: suggestion : D:\ORACLE\PRODUCT\FLASH_RECOVERY_AREA\EBCP01\ARCHIVELOG\2009_05_08\O1_MF_1_6773_%U_.ARC
ORA-00280: change 2438396976 for thread 1 is in sequence #6773
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
D:\ORACLE\PRODUCT\FLASH_RECOVERY_AREA\EBCP01\ARCHIVELOG\2009_05_08\O1_MF_1_6773_50909L7L_.ARC
Log applied.
Media recovery complete.
hmm.. now when would it actually update the sequence numbers on the logs, I am asking this bcoz the sequence on teh standby still reads:
SQL> SELECT * FROM V$LOG;
GROUP# THREAD# SEQUENCE# BYTES MEMBERS ARC STATUS FIRST_CHANGE# FIRST_TIM
1 1 6764 52428800 2 NO INACTIVE 2437870303 07-MAY-09
3 1 6765 52428800 2 NO INACTIVE 2437871111 07-MAY-09
2 1 6766 52428800 2 NO CURRENT 2437886254 07-MAY-09
I am lost here!!! and I'm not sure what to do about this! Your help is really appreciated.
Thanks

The "readme" for Patch 9369783 (which covers the AprilCPU for our 11.1.0.7 HPUX-IA64 environment) includes this short reference to DataGuard:
If you are using a Data Guard Physical Standby database, you must first install this patch on the primary database before installing the patch on the physical standby database. It is not supported to install this patch on the physical standby database before installing the patch on the primary database. For more information, see My Oracle Support Note 278641.1.
When checking that note 278641.1 we see that it also appears to only cover 10.2. Although this note has more detail, it is clearly the same procedure as discussed in 813445.1. Therefore, the conclusion that I make is: OPatch works exactly the same with DataGuard in 11g as it did in 10g.
We will be upgrading our DataGuard enviornment to 11g in one-month. At this point, I am completely expecting our OPatch procedures to remain unchanged from what we have done for years with 9i and 10g. I would also note that the upgrade procedures we have tested (involving DG from 10.2.0.4 to 11.1.0.7) are nearly identical to the above mentioned support notes.
Hope that helps,
Stan

Cold backup with online redo logs

I am working on 10G in AIX for a single instance
It is just a general db backup & restore question, but I have something confused.
I am going to perform a cold backup with my ARCHIVELOG database.
No wonder why I perform a cold backup because it is a testing database which can suffer from data lost and down time during backup.
I read some guides. They all mentioned to backup all the datafiles and control files.
During the restoration, I have to copy all the backed up datafiles and control files to the default location.
Then Startup mount;
The last step before open the database is recover database until cancel;
For the acknowledgement, I have to do the command of recover database, because the online redo logs were not backed up, thus we have to recover it in order to reset the redo logs.
For my question,Would I be able to skip the command of recover database, then directly startup the database if I have backed up the online redo logs and copy the default location during the restoration?
However, I read many documents which mention that it is not suggested to backup the online redo logs. Is it just the case which ONLY applied in hot backup? Do you all think that for my case, cold backup for online redo logs is recommended?
Thanks all

jgarry wrote:
Edit: And never forget, those test databases are some developers production.Absolutely true according to my experience. Loosing the work of a payed developer is just as bad as loosing the work of a production system and may even be worse because it may not be possible to re-enter missing data into the system.
I think a cold backup is only suitable on special occasions, for instance, to relocate/copy the database to a different storage media, or if the database doesn't change or if loosing changes is absolutely irrelevant. Otherwise, put the database into archivelog mode and do a hot backup. After that you will also have alternative options which can make the restore and recovery of the database very easy and efficient, like flashback database, etc. but it will take substantial additional disk space.

COLD BACKUP을 받은 후 ARCHIVE LOG로 변환하여 사용한 경우 INCOMPLETE RECOVERY.

제품 : ORACLE SERVER
작성날짜 : 2002-04-09
COLD BACKUP을 받은 후 ARCHIVE LOG로 변환하여 사용한 경우 INCOMPLETE RECOVERY.
======================================================================
PURPOSE
COLD BACKUP을 받은 후 ARCHIVE LOG MODE로 변환하여 사용한 경우의 RECOVERY
과정을 TEST로 확인하여 본다.
Examples
No Archive log mode.
SQL> select * from tab ;
TNAME TABTYPE CLUSTERID
EMP TABLE
EMP1 TABLE
EMP2 TABLE
EMP3 TABLE
EMP4 TABLE
10 rows selected.
SQL> select count(*) from emp3 ;
COUNT(*)
0
SQL> select count(*) from emp4 ;
COUNT(*)
0
Cold backup을 받은후 Archive log mode 변경한 경우
SVRMGR> startup mount
SVRMGR> archive log list
Database log mode No Archive Mode
Automatic archival Enabled
Archive destination D:\Oracle\oradata\SNAP\archive
Oldest online log sequence 26
Current log sequence 28
SVRMGR> alter database archivelog ;
SVRMGR> alter database open ; => archive log mode 변경.
SQL> select * from tab ;
TNAME TABTYPE CLUSTERID
EMP TABLE
EMP1 TABLE
EMP2 TABLE
EMP3 TABLE
EMP4 TABLE
10 rows selected.
SQL> insert into emp3 select * from emp ;
14 rows created.
SQL> commit ;
Commit complete.
SQL> insert into emp4 select * from emp1 ;
71680 rows created.
SQL> commit ;
Commit complete.
SQL> select count(*) from emp3 ;
COUNT(*)
14
SQL> select count(*) from emp4 ;
COUNT(*)
71680
## log switch 발생.
SVRMGR> alter system switch logfile ;
SQL> insert into emp3 select * from emp ; -- current log에 반영.
14 rows created.
SQL> commit ;
SQL> select count(*) from emp3 ;
COUNT(*)
28
SQL> select count(*) from emp4 ;
COUNT(*)
71680
# ALL DATABASE CRASH #
# recover 과정... #
1. Restore Cold-backup
2. modify initSID.ora
log_archive_start = true
log_archive_dest_1 = "location=D:\Oracle\oradata\SNAP\archive"
log_archive_format = %%ORACLE_SID%%T%TS%S.ARC
3. svrmgrl
Statement processed.
SVRMGR> startup mount
ORACLE instance started.
Total System Global Area 40703244 bytes
Fixed Size 70924 bytes
Variable Size 23777280 bytes
Database Buffers 16777216 bytes
Redo Buffers 77824 bytes
Database mounted.
SVRMGR> archive log list
Database log mode No Archive Mode
Automatic archival Enabled
Archive destination D:\Oracle\oradata\SNAP\archive
Oldest online log sequence 26
Current log sequence 28
SVRMGR> alter database archivelog ;
Statement processed.
SVRMGR> recover database using backup controlfile until cancel ;
ORA-00279: change 340421 generated at 04/29/2001 23:42:20 needed for thread 1
ORA-00289: suggestion : D:\ORACLE\ORADATA\SNAP\ARCHIVE\SNAPT001S00028.ARC
ORA-00280: change 340421 for thread 1 is in sequence #28
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
Log applied.
ORA-00279: change 340561 generated at 04/29/2001 23:47:29 needed for thread 1
ORA-00289: suggestion : D:\ORACLE\ORADATA\SNAP\ARCHIVE\SNAPT001S00029.ARC
ORA-00280: change 340561 for thread 1 is in sequence #29
ORA-00278: log file 'D:\ORACLE\ORADATA\SNAP\ARCHIVE\SNAPT001S00028.ARC' no longe
r needed for this recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
Log applied.
ORA-00279: change 340642 generated at 04/29/2001 23:47:35 needed for thread 1
ORA-00289: suggestion : D:\ORACLE\ORADATA\SNAP\ARCHIVE\SNAPT001S00030.ARC
ORA-00280: change 340642 for thread 1 is in sequence #30
ORA-00278: log file 'D:\ORACLE\ORADATA\SNAP\ARCHIVE\SNAPT001S00029.ARC' no longe
r needed for this recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
Log applied.
ORA-00279: change 340723 generated at 04/29/2001 23:47:40 needed for thread 1
ORA-00289: suggestion : D:\ORACLE\ORADATA\SNAP\ARCHIVE\SNAPT001S00031.ARC
ORA-00280: change 340723 for thread 1 is in sequence #31
ORA-00278: log file 'D:\ORACLE\ORADATA\SNAP\ARCHIVE\SNAPT001S00030.ARC' no longe
r needed for this recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
Log applied.
ORA-00279: change 340797 generated at 04/29/2001 23:48:01 needed for thread 1
ORA-00289: suggestion : D:\ORACLE\ORADATA\SNAP\ARCHIVE\SNAPT001S00032.ARC
ORA-00280: change 340797 for thread 1 is in sequence #32
ORA-00278: log file 'D:\ORACLE\ORADATA\SNAP\ARCHIVE\SNAPT001S00031.ARC' no longe
r needed for this recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
cancel
Media recovery cancelled.
SVRMGR> alter database open resetlogs ;
Statement processed.
SVRMGR>
SQL> connect scott/tiger
SQL> select count(*) from emp3 ;
COUNT(*)
14
SQL> select count(*) from emp4 ;
COUNT(*)
71680
# 결론...... #
따라서 current log file에 기록된 14 row에 대한 부분은 recover가 될수
없지만 archive log file에 적용된 log에 대한 data는 정상적으로 복구가
가능하다.
# 주의 사항 #
cold backup을 restore한 후 database open후 shutdown 한 다음 archive
log mode로 변경하여 recover를 진행하는 경우 SCN number가 변경되기
때문에 ora-600 error가 발생하며 media recovery를 필요로 하기 때문에
주의하여야 한다.
SVRMGR> startup
ORACLE instance started.
Total System Global Area 40703244 bytes
Fixed Size 70924 bytes
Variable Size 23777280 bytes
Database Buffers 16777216 bytes
Redo Buffers 77824 bytes
Database mounted.
Database opened.
SVRMGR> shutdown
Database closed.
Database dismounted.
ORACLE instance shut down.
SVRMGR> startup mount
ORACLE instance started.
Total System Global Area 40703244 bytes
Fixed Size 70924 bytes
Variable Size 23777280 bytes
Database Buffers 16777216 bytes
Redo Buffers 77824 bytes
Database mounted.
SVRMGR> alter database archivelog ;
Statement processed.
SVRMGR> recover database using backup controlfile until cancel ;
ORA-00279: change 339542 generated at 04/29/2001 23:30:57 needed for thread 1
ORA-00289: suggestion : D:\ORACLE\ORADATA\SNAP\ARCHIVE\SNAPT001S00003.ARC
ORA-00280: change 339542 for thread 1 is in sequence #3
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00283: recovery session canceled due to errors
ORA-00600: internal error code, arguments: [3020], [8390146], [1], [3], [143], [
240], [], []
SVRMGR> exit
Server Manager complete.
Rederence Documents
---------------------

In standby db, can't find sequence number of Last Applied Log.

Hello,
Standby database is behind the primary database for over 200 hours, to repaire this, we are using a incremental backup from primary database and a restored control file.
after starting up standby database, in Grid Control (OEM), can't find "last applied log" sequence number,
go to that standby, do
standby> select max(sequence#) from v$archived_log where applied='YES';
MAX(SEQUENCE#)
go to primary,
do
SQL> select max(sequence#) from v$archived_log where applied='YES';
MAX(SEQUENCE#)
83833
then using OEM grid control, to Verify checks various standby database settings.
Initializing
Connected to instance standby_server:standby
Starting alert log monitor...
Updating Data Guard link on database homepage...
Skipping verification of fast-start failover static services check.
Data Protection Settings:
Protection mode : Maximum Performance
Redo Transport Mode settings:
primary.com: ASYNC
standby.com: ASYNC
Checking standby redo log files.....OK
Checking Data Guard status
primary.com : Normal
standby.com : Normal
Checking inconsistent properties
Checking agent status
Checking applied log on standby........WARNING:
Timed out after 60 seconds waiting for log to be applied.
Processing completed.
so how to fix this?
thanks you very much.
Edited by: 951932 on Oct 18, 2012 7:44 AM

Hello;
Probably nothing to fix. This is a common warning message.
It even occurs in this example :
http://www.databasejournal.com/features/oracle/article.php/10893_3826706_2/Oracle-11g-Data-Guard-Grid-Control-Management.htm
Best Regards
mseberg

7.5 Standby apply log issue - Cold backup of standby

Similar Messages

Maybe you are looking for