Redo apply is not done in physical standby database

Please help me to resolve the issue, tnsping are working. but getting following output in data guard configuration.
From primary database,
Code: [Select all] [Show/ hide]
SQL> select max(sequence#), thread# from v$archived_log group by thread#;
MAX(SEQUENCE#) THREAD#
124 1
94 2
SQL> col DESTINATION for a40
SQL> SELECT DESTINATION, STATUS, ARCHIVED_THREAD#, ARCHIVED_SEQ# -
FROM V$ARCHIVE_DEST_STATUS -
WHERE STATUS <> 'DEFERRED' AND STATUS <> 'INACTIVE';SELECT DEST_ID "ID",STATUS "DB_status",DESTINATION "Archive_dest",ERROR "Error" FROM V$ARCHIVE_DEST WHERE DEST_ID =2;
select error from v$archive_dest_status where error is not null;
DESTINATION STATUS ARCHIVED_THREAD#
ARCHIVED_SEQ#
VALID 1
124
bddipdrs ERROR 0
0
SQL> SQL> SQL>
ID DB_status
Archive_dest
Error
2 ERROR
bddipdrs
ORA-16198: Timeout incurred on internal channel during remote
archival
From standby database,
Code: [Select all] [Show/ hide]
SQL> select max(sequence#), thread# from v$archived_log group by thread#;
col DESTINATION for a40
no rows selected
SQL> SQL> SQL> SELECT DESTINATION, STATUS, ARCHIVED_THREAD#, ARCHIVED_SEQ# -
FROM V$ARCHIVE_DEST_STATUS -
WHERE STATUS <> 'DEFERRED' AND STATUS <> 'INACTIVE';SELECT DEST_ID "ID",STATUS "DB_status",DESTINATION "Archive_dest",ERROR "Error" FROM V$ARCHIVE_DEST WHERE DEST_ID =2;
DESTINATION STATUS ARCHIVED_THREAD#
ARCHIVED_SEQ#
VALID 0
0
bddipdrs VALID 0
0
VALID 0
0
SQL> SQL> SQL>
ID DB_status
Archive_dest
Error
2 VALID
bddipdrs
SQL> SQL> select error from v$archive_dest_status where error is not null;
no rows selected
From standby database,
Code: [Select all] [Show/ hide]
<msg time='2010-09-02T21:30:25.422+06:00' org_id='oracle' comp_id='rdbms'
client_id='' type='UNKNOWN' level='16'
host_id='DRS-DB-01' host_addr='192.168.105.101' module='oracle@DC-DB-01 (TNS V1-V3)'
pid='13010'>
<txt>RFS[2]: Possible network disconnect with primary database
</txt>
</msg>
<msg time='2010-09-02T21:31:19.259+06:00' org_id='oracle' comp_id='rdbms'
client_id='' type='UNKNOWN' level='16'
host_id='DRS-DB-01' host_addr='192.168.105.101' module='oracle@DC-DB-01 (TNS V1-V3)'
pid='13014'>
<txt>RFS[6]: Possible network disconnect with primary database
</txt>
</msg>
<msg time='2010-09-02T21:31:19.265+06:00' org_id='oracle' comp_id='rdbms'
client_id='' type='UNKNOWN' level='16'
host_id='DRS-DB-01' host_addr='192.168.105.101' module=''
pid='13014'>
<txt>Deleted Oracle managed file +RECOVERY/bddipdrs/archivelog/2010_09_02/thread_2_seq_90.289.728688311
</txt>
</msg>
<msg time='2010-09-02T21:32:10.314+06:00' org_id='oracle' comp_id='rdbms'
client_id='' type='UNKNOWN' level='16'
host_id='DRS-DB-01' host_addr='192.168.105.101' module='oracle@DC-DB-01 (TNS V1-V3)'
pid='13020'>
<txt>RFS[7]: Possible network disconnect with primary database
</txt>
</msg>
<msg time='2010-09-02T21:32:59.423+06:00' org_id='oracle' comp_id='rdbms'
client_id='' type='UNKNOWN' level='16'
host_id='DRS-DB-01' host_addr='192.168.105.101' module='oracle@DC-DB-01 (TNS V1-V3)'
pid='13026'>
<txt>RFS[10]: Possible network disconnect with primary database
</txt>
</msg>
<msg time='2010-09-02T21:32:59.430+06:00' org_id='oracle' comp_id='rdbms'
client_id='' type='UNKNOWN' level='16'
host_id='DRS-DB-01' host_addr='192.168.105.101' module=''
pid='13026'>
<txt>Deleted Oracle managed file +RECOVERY/bddipdrs/archivelog/2010_09_02/thread_1_seq_107.288.728688311
</txt>
</msg>
<msg time='2010-09-02T21:33:00.664+06:00' org_id='oracle' comp_id='rdbms'
client_id='' type='UNKNOWN' level='16'
host_id='DRS-DB-01' host_addr='192.168.105.101' module=''
pid='13519'>
<txt>Fetching gap sequence in thread 1, gap sequence 107-122
</txt>
</msg>
<msg time='2010-09-02T21:33:45.941+06:00' org_id='oracle' comp_id='rdbms'
client_id='' type='UNKNOWN' level='16'
host_id='DRS-DB-01' host_addr='192.168.105.101' module='oracle@DC-DB-01 (TNS V1-V3)'
pid='13012'>
<txt>RFS[3]: Possible network disconnect with primary database
</txt>
</msg>
<msg time='2010-09-02T21:33:45.947+06:00' org_id='oracle' comp_id='rdbms'
client_id='' type='UNKNOWN' level='16'
host_id='DRS-DB-01' host_addr='192.168.105.101' module=''
pid='13012'>
<txt>Deleted Oracle managed file +RECOVERY/bddipdrs/archivelog/2010_09_02/thread_2_seq_89.301.728688311
</txt>
</msg>
From primary database,
Code: [Select all] [Show/ hide]
<msg time='2010-09-02T21:34:23.966+06:00' org_id='oracle' comp_id='rdbms'
client_id='' type='UNKNOWN' level='16'
host_id='DC-DB-01' host_addr='192.168.100.101' module=''
pid='9533'>
<txt>Reclaiming FAL entry from dead process [pid 5732]
</txt>
</msg>
<msg time='2010-09-02T21:34:23.976+06:00' org_id='oracle' comp_id='rdbms'
client_id='' type='UNKNOWN' level='16'
host_id='DC-DB-01' host_addr='192.168.100.101' module=''
pid='9519'>
<txt>Reclaiming FAL entry from dead process [pid 5720]
</txt>
</msg>
<msg time='2010-09-02T21:34:23.992+06:00' org_id='oracle' comp_id='rdbms'
client_id='' type='UNKNOWN' level='16'
host_id='DC-DB-01' host_addr='192.168.100.101' module=''
pid='9511'>
<txt>Reclaiming FAL entry from dead process [pid 5734]
</txt>
</msg>
<msg time='2010-09-02T21:34:23.999+06:00' org_id='oracle' comp_id='rdbms'
client_id='' type='UNKNOWN' level='16'
host_id='DC-DB-01' host_addr='192.168.100.101' module=''
pid='9523'>
<txt>Reclaiming FAL entry from dead process [pid 5724]
</txt>
</msg>
<msg time='2010-09-02T21:34:24.002+06:00' org_id='oracle' comp_id='rdbms'
client_id='' type='UNKNOWN' level='16'
host_id='DC-DB-01' host_addr='192.168.100.101' module=''
pid='9513'>
<txt>Reclaiming FAL entry from dead process [pid 5730]
</txt>
</msg>
<msg time='2010-09-02T21:34:24.011+06:00' org_id='oracle' comp_id='rdbms'
client_id='' type='UNKNOWN' level='16'
host_id='DC-DB-01' host_addr='192.168.100.101' module=''
pid='9517'>
<txt>Reclaiming FAL entry from dead process [pid 5728]
</txt>
</msg>
<msg time='2010-09-02T21:34:24.013+06:00' org_id='oracle' comp_id='rdbms'
client_id='' type='UNKNOWN' level='16'
host_id='DC-DB-01' host_addr='192.168.100.101' module=''
pid='9509'>
<txt>Reclaiming FAL entry from dead process [pid 5738]
</txt>
</msg>
<msg time='2010-09-02T21:34:24.014+06:00' org_id='oracle' comp_id='rdbms'
client_id='' type='UNKNOWN' level='16'
host_id='DC-DB-01' host_addr='192.168.100.101' module=''
pid='9531'>
<txt>Reclaiming FAL entry from dead process [pid 5740]
</txt>
</msg>
<msg time='2010-09-02T21:34:24.031+06:00' org_id='oracle' comp_id='rdbms'
client_id='' type='UNKNOWN' level='16'
host_id='DC-DB-01' host_addr='192.168.100.101' module=''
pid='9529'>
<txt>Reclaiming FAL entry from dead process [pid 5742]
</txt>
</msg>
<msg time='2010-09-02T21:34:24.048+06:00' org_id='oracle' comp_id='rdbms'
client_id='' type='UNKNOWN' level='16'
host_id='DC-DB-01' host_addr='192.168.100.101' module=''
pid='9539'>
<txt>Reclaiming FAL entry from dead process [pid 5746]
</txt>
</msg>
<msg time='2010-09-02T21:34:24.058+06:00' org_id='oracle' comp_id='rdbms'
client_id='' type='UNKNOWN' level='16'
host_id='DC-DB-01' host_addr='192.168.100.101' module=''
pid='9547'>
<txt>Reclaiming FAL entry from dead process [pid 5750]
</txt>
</msg>
<msg time='2010-09-02T21:34:24.768+06:00' org_id='oracle' comp_id='rdbms'
client_id='' type='UNKNOWN' level='16'
host_id='DC-DB-01' host_addr='192.168.100.101' module=''
pid='5697'>
<txt>ARCt: Archival started
</txt>
</msg>
<msg time='2010-09-02T21:34:24.768+06:00' org_id='oracle' comp_id='rdbms'
client_id='' type='UNKNOWN' level='16'
host_id='DC-DB-01' host_addr='192.168.100.101' module=''
pid='5697'>
<txt>ARC3: STARTING ARCH PROCESSES COMPLETE
</txt>
</msg>
<msg time='2010-09-02T21:34:25.798+06:00' org_id='oracle' comp_id='rdbms'
client_id='' type='UNKNOWN' level='16'
host_id='DC-DB-01' host_addr='192.168.100.101' module=''
pid='5744'>
<txt>ARCq: Standby redo logfile selected for thread 1 sequence 122 for destination LOG_ARCHIVE_DEST_2
</txt>
</msg>
<msg time='2010-09-02T21:34:25.815+06:00' org_id='oracle' comp_id='rdbms'
client_id='' type='UNKNOWN' level='16'
host_id='DC-DB-01' host_addr='192.168.100.101' module=''
pid='5695'>
<txt>ARC2: Standby redo logfile selected for thread 2 sequence 88 for destination LOG_ARCHIVE_DEST_2
</txt>
</msg>
<msg time='2010-09-02T21:34:26.535+06:00' org_id='oracle' comp_id='rdbms'
client_id='' type='UNKNOWN' level='16'
host_id='DC-DB-01' host_addr='192.168.100.101' module=''
pid='9515'>
<txt>ARCd: Standby redo logfile selected for thread 1 sequence 110 for destination LOG_ARCHIVE_DEST_2
</txt>
</msg>
<msg time='2010-09-02T21:34:27.174+06:00' org_id='oracle' comp_id='rdbms'
client_id='' type='UNKNOWN' level='16'
host_id='DC-DB-01' host_addr='192.168.100.101' module=''
pid='9529'>
<txt>ARCk: Standby redo logfile selected for thread 1 sequence 120 for destination LOG_ARCHIVE_DEST_2
</txt>
</msg>
<msg time='2010-09-02T21:34:27.402+06:00' org_id='oracle' comp_id='rdbms'
client_id='' type='UNKNOWN' level='16'
host_id='DC-DB-01' host_addr='192.168.100.101' module=''
pid='9533'>
<txt>ARCm: Standby redo logfile selected for thread 1 sequence 112 for destination LOG_ARCHIVE_DEST_2
</txt>
</msg>
<msg time='2010-09-02T21:34:27.498+06:00' org_id='oracle' comp_id='rdbms'
client_id='' type='UNKNOWN' level='16'
host_id='DC-DB-01' host_addr='192.168.100.101' module=''
pid='9511'>
<txt>ARCb: Standby redo logfile selected for thread 1 sequence 114 for destination LOG_ARCHIVE_DEST_2
</txt>
</msg>
<msg time='2010-09-02T21:34:28.205+06:00' org_id='oracle' comp_id='rdbms'
client_id='' type='UNKNOWN' level='16'
host_id='DC-DB-01' host_addr='192.168.100.101' module=''
pid='9527'>
<txt>ARCj: Standby redo logfile selected for thread 1 sequence 111 for destination LOG_ARCHIVE_DEST_2
</txt>
</msg>
<msg time='2010-09-02T21:34:28.592+06:00' org_id='oracle' comp_id='rdbms'
client_id='' type='UNKNOWN' level='16'
host_id='DC-DB-01' host_addr='192.168.100.101' module=''
pid='9531'>
<txt>ARCl: Standby redo logfile selected for thread 1 sequence 119 for destination LOG_ARCHIVE_DEST_2
</txt>
</msg>

Hi,
I am currently facing the same issue with same set of errors from primary and standby.
Mine is a 11gR2 2 node RAC on RHEL5 with a single node standby.
However in my case, whenever i switch a logfile on the primary database, only 17 MB or less is being shipped per archive where size of redo log is 500 mb.
Any help would be really appreciated.
Thanks,
Rahul Singh.

Similar Messages

Log apply was not sync in physical standby

Hi Gurus,
I am very new to Data Guard , here are few questions , please answer , so that my understanding about DR could be very clear?
This is physical standby database running maximum performance mode , with ARCH as transport service
1.explain below in detail ( standby)
SQL> archive log list
Database log mode Archive Mode
Automatic archival Enabled
Archive destination USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence 60099
Next log sequence to archive 0
Current log sequence 60178
2.where this information is picked from , how it will be updated in stand by before the archived log reached this standby site ?
3.Why there will be more than 1 entry for sequence in v$archived_log (primary) ?
4. One scenario ,
select registrar , sequnce# from v$archived_log ; (primary)
ARCH 60109
ARCH 60171
LGWR 60172
60172 entered the standby site even before the archived logs 600109-601171 reach standby, because REGISTRAR is LGWR
5.Log apply is taking to long time( in-memory ) i.e .sequence is not changing for long time ? How to resolve this?
Please feel free to revert , if any question is unclear
Thanks,
Uday

Hello;
1.explain below in detail ( standby)
SQL> archive log list
Database log mode Archive Mode
Automatic archival Enabled
Archive destination USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence 60099
Next log sequence to archive 0
Current log sequence 60178Not sure how to comment. Try query in question 2.
2.where this information is picked from , how it will be updated in stand by before the archived log reached this standby site ?Would use something else. Try this query :
http://www.visi.com/~mseberg/monitor_data_guard_transport.html
3.Why there will be more than 1 entry for sequence in v$archived_log (primary) ?Because with Data Guard you have more than one destination for Archive so v$archived_log accounts for them all.
4. One scenario ,
select registrar , sequnce# from v$archived_log ; (primary)
ARCH 60109
ARCH 60171
LGWR 60172
60172 entered the standby site even before the archived logs 600109-601171 reach standby, because REGISTRAR is LGWRNot sure how to comment, what are you trying to do?
5.Log apply is taking to long time( in-memory ) i.e .sequence is not changing for long time ? How to resolve this?
Please feel free to revert , if any question is unclearWhat is a long time? If you force a few log switches on the Primary does it take a long time for each one? Or longer?
Best Regards
mseberg

Apply missing log on physical standby database

How to apply the missing log on physical standby database?
I already registered the missing log and started the recovery process.
Still...having log on standby that has status ..not applied.
SQL> SELECT SEQUENCE#,APPLIED FROM V$ARCHIVED_LOG ORDER BY SEQUENCE#;
SEQUENCE# APP
16018 YES
16019 YES
16020 NO ---------------------> Not applied.
16021 YES
Thanks

Not much experience doing this, but according to the 9i doc (http://download-east.oracle.com/docs/cd/B10501_01/server.920/a96653/log_apply.htm#1017352), all you need is properly-configured FAL_CLIENT and FAL_SERVER initialization parameters, and things should take care of themselves automatically. Let us know if that doesn't work for you, we might be able to think of something else.
Daniel

All logs received but not applied | Physical Standby Database

All,
Need your help....
We have physical standby database setup as below
Primary : 2 node RAC
Stdby : Standalone physical standby database.
When I verify the stdby database status, I could see all the logs are received from primary but still not applied many.. Could any one please help me what is the issue and how to resolve it ...?
Primary :
=====
SQL> SELECT THREAD# "Thread",SEQUENCE# "Last Sequence Generated"
FROM V$ARCHIVED_LOG
WHERE (THREAD#,FIRST_TIME ) IN (SELECT THREAD#,MAX(FIRST_TIME) FROM V$ARCHIVED_LOG GROUP BY THREAD#)
ORDER BY 1 2 3 4 ;
Thread Last Sequence Generated
1 8073
1 8073
2 4521
2 4521
stdby:
====
SQL> SELECT ARCH.THREAD# "Thread",
2 ARCH.SEQUENCE# "Last Sequence Received",
3 APPL.SEQUENCE# "Last Sequence Applied",
4 (ARCH.SEQUENCE# - APPL.SEQUENCE#) "Difference"
5 FROM
6 (SELECT THREAD# ,SEQUENCE# FROM V$ARCHIVED_LOG WHERE (THREAD#,FIRST_TIME ) IN
7 (SELECT THREAD#,MAX(FIRST_TIME) FROM V$ARCHIVED_LOG GROUP BY THREAD#)) ARCH,
8 (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
9 10 WHERE ARCH.THREAD# = APPL.THREAD# ORDER BY 1;
Thread Last Sequence Received Last Sequence Applied Difference
1 8073 8055 18
2 4521 4510 11
--Below are tailed messages from standby alert log:
Fri Nov 04 10:45:15 2011
ARCH: Archival stopped, error occurred. Will continue retrying
ORACLE Instance BWFCCSTD - Archival Error
ORA-16014: log 6 sequence# 8058 not archived, no available destinations
ORA-00312: online log 6 thread 1: '+ASM_DATA01/bwfccstd/onlinelog/group_6.418.766235259'
ORA-00312: online log 6 thread 1: '+ASM_FRA01/bwfccstd/onlinelog/group_6.307.766235263'
Fri Nov 04 10:50:15 2011
Archiver process freed from errors. No longer stopped
Fri Nov 04 10:50:15 2011
ARCH: Archival stopped, error occurred. Will continue retrying
ORACLE Instance BWFCCSTD - Archival Error
ORA-16014: log 6 sequence# 8058 not archived, no available destinations
ORA-00312: online log 6 thread 1: '+ASM_DATA01/bwfccstd/onlinelog/group_6.418.766235259'
ORA-00312: online log 6 thread 1: '+ASM_FRA01/bwfccstd/onlinelog/group_6.307.766235263'
Fri Nov 04 10:50:15 2011
Archiver process freed from errors. No longer stopped
Fri Nov 04 10:55:15 2011
ARCH: Archival stopped, error occurred. Will continue retrying
ORACLE Instance BWFCCSTD - Archival Error
ORA-16014: log 6 sequence# 8058 not archived, no available destinations
ORA-00312: online log 6 thread 1: '+ASM_DATA01/bwfccstd/onlinelog/group_6.418.766235259'
ORA-00312: online log 6 thread 1: '+ASM_FRA01/bwfccstd/onlinelog/group_6.307.766235263'
Fri Nov 04 11:00:15 2011
Archiver process freed from errors. No longer stopped
Fri Nov 04 11:00:15 2011
ARCH: Archival stopped, error occurred. Will continue retrying
ORACLE Instance BWFCCSTD - Archival Error
ORA-16014: log 6 sequence# 8058 not archived, no available destinations
ORA-00312: online log 6 thread 1: '+ASM_DATA01/bwfccstd/onlinelog/group_6.418.766235259'
ORA-00312: online log 6 thread 1: '+ASM_FRA01/bwfccstd/onlinelog/group_6.307.766235263'
Fri Nov 04 11:00:15 2011
Archiver process freed from errors. No longer stopped
Fri Nov 04 11:05:16 2011
ARCH: Archival stopped, error occurred. Will continue retrying
ORACLE Instance BWFCCSTD - Archival Error
ORA-16014: log 6 sequence# 8058 not archived, no available destinations
ORA-00312: online log 6 thread 1: '+ASM_DATA01/bwfccstd/onlinelog/group_6.418.766235259'
ORA-00312: online log 6 thread 1: '+ASM_FRA01/bwfccstd/onlinelog/group_6.307.766235263'
Fri Nov 04 11:05:16 2011
Archiver process freed from errors. No longer stopped

Primary:
=====
SQL> archive log list;
Database log mode Archive Mode
Automatic archival Enabled
Archive destination +ASM_FRA01
Oldest online log sequence 8073
Next log sequence to archive 8074
Current log sequence 8074
SQL>
Stdby:
=====
SQL> archive log list;
Database log mode Archive Mode
Automatic archival Enabled
Archive destination ?/dbs/arch
Oldest online log sequence 8074
Next log sequence to archive 0
Current log sequence 8074
Enough space is available :
=================
SQL> set lines 180 pages 50000;
SQL> set lines 100
col name format a60
select name
, floor(space_limit / 1024 / 1024) "Size MB"
, ceil(space_used / 1024 / 1024) "Used MB"
from v$recovery_file_dest
order by nameSQL> SQL> 2 3 4 5 ;
NAME Size MB Used MB
+ASM_FRA01 70000 531
Edited by: 889828 on 2011/11/04 2:26 AM

Issue with physical standby database not in sync with primary

Hi,
I created an physical standby database couple of Hours back . I am trying to keep the standby database in Managed recovery mode to make the standby in sync with primary but it is throwing the below erros. Please share your suggestion ...
SQL> select thread#,max(sequence#) from v$log_history group by thread#;
THREAD# MAX(SEQUENCE#)
1 7
PROCESS STATUS THREAD# SEQUENCE#
ARCH CONNECTED 0 0
ARCH CONNECTED 0 0
RFS OPENING 1 12
ALERT LOG :
Tue Mar 20 07:31:32 2012
alter database recover managed standby database disconnect from session
Tue Mar 20 07:31:32 2012
Attempt to start background Managed Standby Recovery process (PRIMARY)
MRP0 started with pid=18, OS id=16370
Tue Mar 20 07:31:32 2012
MRP0: Background Managed Standby Recovery process started (PRIMARY)
Managed Standby Recovery not using Real Time Apply
parallel recovery started with 8 processes
Media Recovery Log /oracle/STDBY/arch/1_3_777567883.dbf
Tue Mar 20 07:31:39 2012
Completed: alter database recover managed standby database disconnect from session
Tue Mar 20 07:31:54 2012
Incomplete recovery applied all redo ever generated.
Recovery completed through change 9677325080303
Tue Mar 20 07:31:54 2012
MRP0: Media Recovery Complete (PRIMARY)
Tue Mar 20 07:31:55 2012
MRP0: Background Media Recovery process shutdown (PRIMARY)
Thanks,
Rakesh

HI CKPT,
Thanks for the reply. All the Archives from primary are transferred to the standby by RFS. Also i tried to register the log files manually even but it says already registered. They are no errors in the primary instance alert log file. Please find the log
SEVERITY ERROR_CODE MESSAGE TO_CHAR(TIMESTAMP,'D
Informational 0 ARC0: Archival started 20-MAR-2012 06:51:36
Informational 0 ARC1: Archival started 20-MAR-2012 06:51:36
Informational 0 ARC0: Becoming the 'no FAL' ARCH 20-MAR-2012 06:51:36
Informational 0 ARC0: Becoming the 'no SRL' ARCH 20-MAR-2012 06:51:36
Informational 0 ARC1: Becoming the heartbeat ARCH 20-MAR-2012 06:51:36
Informational 0 Redo Shipping Client Connected as PUBLIC 20-MAR-2012 06:52:07
Informational 0 -- Connected User is Valid 20-MAR-2012 06:52:07
Informational 0 RFS[1]: Assigned to RFS process 15934 20-MAR-2012 06:52:07
Informational 0 RFS[1]: Identified database type as 'physical standby' 20-MAR-2012 06:52:07
Warning 0 RFS[1]: No standby redo logfiles created 20-MAR-2012 06:52:07
Control 0 Attempt to start background Managed Standby Recovery process 20-MAR-2012 06:52:42
Control 0 MRP0: Background Managed Standby Recovery process started 20-MAR-2012 06:52:42
Informational 0 Managed Standby Recovery not using Real Time Apply 20-MAR-2012 06:52:47
Informational 0 Media Recovery Log /oracle/STDBY/arch/1_3_777567883.d 20-MAR-2012 06:52:49
bf
Control 0 MRP0: Media Recovery Complete 20-MAR-2012 06:53:04
Control 0 MRP0: Background Media Recovery process shutdown 20-MAR-2012 06:53:06
Informational 0 Managed Standby Recovery not using Real Time Apply 20-MAR-2012 06:53:24
Control 0 Media Recovery Complete 20-MAR-2012 06:53:43
Control 0 Attempt to start background Managed Standby Recovery process 20-MAR-2012 06:54:55
Control 0 MRP0: Background Managed Standby Recovery process started 20-MAR-2012 06:54:55
Informational 0 Managed Standby Recovery not using Real Time Apply 20-MAR-2012 06:55:00
Informational 0 Media Recovery Log /oracle/STDBY/arch/1_3_777567883.d 20-MAR-2012 06:55:01
bf
Control 0 MRP0: Media Recovery Complete 20-MAR-2012 06:55:17
Control 0 MRP0: Background Media Recovery process shutdown 20-MAR-2012 06:55:18
Informational 0 Redo Shipping Client Connected as PUBLIC 20-MAR-2012 07:31:03
Informational 0 -- Connected User is Valid 20-MAR-2012 07:31:03
Informational 0 RFS[2]: Assigned to RFS process 16366 20-MAR-2012 07:31:03
Informational 0 RFS[2]: Identified database type as 'physical standby' 20-MAR-2012 07:31:03
Warning 0 RFS[2]: No standby redo logfiles created 20-MAR-2012 07:31:04
Warning 0 RFS[2]: No standby redo logfiles created 20-MAR-2012 07:31:06
Control 0 Attempt to start background Managed Standby Recovery process 20-MAR-2012 07:31:32
Control 0 MRP0: Background Managed Standby Recovery process started 20-MAR-2012 07:31:32
Informational 0 Managed Standby Recovery not using Real Time Apply 20-MAR-2012 07:31:37
Informational 0 Media Recovery Log /oracle/STDBY/arch/1_3_777567883.d 20-MAR-2012 07:31:38
bf
Control 0 MRP0: Media Recovery Complete 20-MAR-2012 07:31:54
Control 0 MRP0: Background Media Recovery process shutdown 20-MAR-2012 07:31:55
36 rows selected.
SQL> archive log list;
Database log mode Archive Mode
Automatic archival Enabled
Archive destination /oracle/STDBY/arch/
Oldest online log sequence 13
Next log sequence to archive 0
Current log sequence 14
SQL> ho ls -ltra /oracle/STDBY/arch/
total 3754456
drwxr-xr-x 4 oracle dba 4096 Feb 13 17:38 ..
-rw-r----- 1 oracle dba 908516864 Mar 20 06:37 1_8_777567883.dbf
-rw-r----- 1 oracle dba 770419200 Mar 20 06:40 1_3_777567883.dbf
-rw-r----- 1 oracle dba 757698048 Mar 20 06:41 1_4_777567883.dbf
-rw-r----- 1 oracle dba 5171712 Mar 20 06:41 1_5_777567883.dbf
-rw-r----- 1 oracle dba 1060801024 Mar 20 06:43 1_6_777567883.dbf
-rw-r----- 1 oracle dba 323025920 Mar 20 06:43 1_7_777567883.dbf
-rw-r----- 1 oracle dba 1558016 Mar 20 06:43 1_9_777567883.dbf
-rw-r----- 1 oracle dba 4608 Mar 20 06:43 1_10_777567883.dbf
-rw-r----- 1 oracle dba 1579008 Mar 20 06:52 1_11_777567883.dbf
-rw-r----- 1 oracle dba 11876864 Mar 20 07:31 1_12_777567883.dbf
-rw-r----- 1 oracle dba 2560 Mar 20 07:31 1_13_777567883.dbf
drwxr-xr-x 2 oracle dba 36864 Mar 20 07:31 .
SQL>

Physical standby database standby redo log problem

Hello
We have a physical standby database , I've created some standby redo log files but my problem is that they aren't used,
their status in v$stanby_log view is UNASSIGNED
and I see this message (ORA-16086: standby database does not contain available standby log files) in primary database alert_log file
while when I run "alter system switch logfile" in the primary database it transfer redo logs to the physsical standby database
and archive log file will be created in standby database
I've even recreated the standby redo log files and I added new ones to them but the problem wasn't solved
Do you know what is problem ?
elect group#,THREAD#,BYTES,STATUS from V$STANDBY_LOG;
group#     THREAD#      BYTES       STATUS
1                   0                   524288000                   UNASSIGNED
2                   0                   524288000                   UNASSIGNED
3                   0                   524288000                   UNASSIGNED
8                   0                   524288000                   UNASSIGNED
9                   0                   524288000                   UNASSIGNED
10                   0                   524288000                   UNASSIGNED
select group#,THREAD#,BYTES,MEMBERS,STATUS from v$log;
group#                    THREAD#                    BYTES                    MEMBERS                    STATUS
4                   1                   524288000                   2                   CLEARING
7                   1                   524288000                   2                   CLEARING_CURRENT
6                   1                   524288000                   2                   CLEARING
5                   1                   524288000                   2                   CLEARING
thanks

Hello Anurag
Thank you for your reply
I have found some issue in the standby database alert_log too , in the standby database alert_log it has been written:
RFS[782]: Assigned to RFS process 3919
RFS[782]: Identified database type as 'physical standby'
Primary database is in MAXIMUM AVAILABILITY mode
Standby controlfile consistent with primary
Primary database is in MAXIMUM AVAILABILITY mode
Standby controlfile consistent with primary
RFS[782]: No standby redo logfiles selected (reason:6)
Sun Jan 31 13:59:43 2010
Errors in file /u01/app/oracle/admin/tehrep/udump/tehrep_rfs_3919.trc:
ORA-16086: standby database does not contain available standby log files
Sun Jan 31 13:59:48 2010
RFS[781]: Archived Log: '/disks/sda/tehrep/archivelogs/1_6516_670414641.dbf'
Sun Jan 31 13:59:50 2010
and the context "/u01/app/oracle/admin/tehrep/udump/tehrep_rfs_3919.trc" is below :
+/u01/app/oracle/admin/tehrep/udump/tehrep_rfs_3919.trc+
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
ORACLE_HOME = /u01/app/oracle/product/10.2.0/db_1
System name:    Linux
Node name:      linserver2.com
Release:        2.6.9-42.ELsmp
Version:        #1 SMP Wed Jul 12 23:27:17 EDT 2006
Machine:        i686
Instance name: tehrep
Redo thread mounted by this instance: 1
Oracle process number: 58
Unix process pid: 3919, image: [email protected]
*** SERVICE NAME:() 2010-01-31 13:59:43.865
*** SESSION ID:(109.1225) 2010-01-31 13:59:43.865
KCRRFLAS
KCRRSNPS
No space in recovery area for active standby redo logs
The primary database is operating in MAXIMUM PROTECTION
or MAXIMUM AVAILABILITY mode, and the standby database
does not contain adequate disk space in the recovery area
to safely archive the contents of the standby redo logfiles.
ORA-16086: standby database does not contain available standby log files
when I saw this line "No space in recovery area for active standby redo logs" I thought that STANDBY_ARCHIVE_DEST parameter points where that there is no enough space , but when I consider I found out that points a directory on disk a "sda" that has enough space , I don't know what that means
by the way, at below I've written a section of the primary database alert_log context and "lgwr" trace file around Sun Jan 31 13:30:34 2010
alert_log :
ORA-16086: standby database does not contain available standby log files
Sun Jan 31 13:30:34 2010
LGWR: Failed to archive log 7 thread 1 sequence 6512 (16086)
Thread 1 advanced to log sequence 6512
Current log# 7 seq# 6512 mem# 0: /disks/sdb/tehrep/redo71.log
Current log# 7 seq# 6512 mem# 1: /disks/sdd/tehrep/redo72.log
LNSc started with pid=53, OS id=11451
Sun Jan 31 13:36:34 2010
Errors in file /u01/app/oracle/admin/tehrep/bdump/tehrep_lgwr_3692.trc:
ORA-16086: standby database does not contain available standby log files
Sun Jan 31 13:36:34 2010
LGWR: Failed to archive log 5 thread 1 sequence 6513 (16086)
Thread 1 advanced to log sequence 6513
Current log# 5 seq# 6513 mem# 0: /disks/sdb/tehrep/redo51.log
Current log# 5 seq# 6513 mem# 1: /disks/sdd/tehrep/redo52.log
*/u01/app/oracle/admin/tehrep/bdump/tehrep_lgwr_3692.trc file :*
Error 16086 creating standby archive log file at host '(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=linserver2.com
+)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=tehrep_XPT.com)(INSTANCE_NAME=tehrep)(SERVER=dedicated)))'+
*** 2010-01-31 13:30:34.712 60679 kcrr.c
LGWR: Attempting destination LOG_ARCHIVE_DEST_3 network reconnect (16086)
*** 2010-01-31 13:30:34.712 60679 kcrr.c
LGWR: Destination LOG_ARCHIVE_DEST_3 network reconnect abandoned
ORA-16086: standby database does not contain available standby log files
*** 2010-01-31 13:30:34.712 60679 kcrr.c
LGWR: Error 16086 creating archivelog file '(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=linserver2.com)(PORT=1521
+)))(CONNECT_DATA=(SERVICE_NAME=tehrep_XPT.com)(INSTANCE_NAME=tehrep)(SERVER=dedicated)))'+
*** 2010-01-31 13:30:34.712 58941 kcrr.c
kcrrfail: dest:3 err:16086 force:0 blast:1
Receiving message from LNSc
*** 2010-01-31 13:30:34.718 55444 kcrr.c
Making upidhs request to LNSc (ocis 0x0xb648db48). Begin time is <01/31/2010 13:30:30> and NET_TIMEOUT <180> seconds
NetServer pid:11196
*** 2010-01-31 13:30:38.718 55616 kcrr.c
upidhs done status 0
*** 2010-01-31 13:36:31.062
LGWR: Archivelog for thread 1 sequence 6513 will NOT be compressed
*** 2010-01-31 13:36:31.062 53681 kcrr.c
+Initializing NetServer[LNSc] for dest=(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=linserver2.com)(PORT=1521)))(CO+
NNECT_DATA=(SERVICE_NAME=tehrep_XPT.com)(INSTANCE_NAME=tehrep)(SERVER=dedicated))) mode SYNC
LNSc is not running anymore.
New SYNC LNSc needs to be started
Waiting for subscriber count on LGWR-LNSc channel to go to zero
Subscriber count went to zero - time now is <01/31/2010 13:36:31>
Starting LNSc ...
Waiting for LNSc to initialize itself
*** 2010-01-31 13:36:34.116 53972 kcrr.c
+Netserver LNSc [pid 11451] for mode SYNC has been initialized+
Performing a channel reset to ignore previous responses
+Successfully started LNSc [pid 11451] for dest (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=linserver2.com)(PORT=1+
+521)))(CONNECT_DATA=(SERVICE_NAME=tehrep_XPT.com)(INSTANCE_NAME=tehrep)(SERVER=dedicated))) mode SYNC ocis=0x0xb648db48+
*** 2010-01-31 13:36:34.116 54475 kcrr.c
+Making upiahm request to LNSc [pid 11451]: Begin Time is <01/31/2010 13:36:31>. NET_TIMEOUT = <180> seconds+
Waiting for LNSc to respond to upiahm
*** 2010-01-31 13:36:34.266 54639 kcrr.c
upiahm connect done status is 0
Receiving message from LNSc
Receiving message from LNSc
Destination LOG_ARCHIVE_DEST_3 is in STANDBY RESYNCHRONIZATION mode
Receiving message from LNSc

How to identify that my physical standby database in use real time apply?

Hi,
Can any one give me the SQL to identifiy that my physical standby database is in real time applying redo logs?
Its urgen please....
Thanks.

You could just look at the alert log. Look for "Recovery of Online Redo Log"
Or you could select from v$standby_apply_snapshot to see if the standby is up-to-date.
select thread#, to_char(snapshot_time,'dd-mon-yyyy:hh24:mi'),
to_char(applied_time,'dd-mon-yyyy:hh24:mi'),
to_char(newest_time,'dd-mon-yyyy:hh24:mi') from V$STANDBY_APPLY_SNAPSHOT;

How to apply Oracle patch when physical standby database in place

Dear All,
I want to apply Oracle patchset 8 on 10.2.0.5 when physical standby database in place. What are the steps for Primary site and for standby site.
Thanks in advance
Kamran Laeeq

Hi Kamran,
You will not upgrade or patch the standby database by importing offline redologs. On the contrary, there is a procedure to do this. Please note that you will not transitiate the role from standby to primary or startup the database. You will just startup the database by executing "startup mount" and "startup upgrade", during the upgrade. It means that you will not change database role standby to primary and you will be able to continue to the log shipment after the respective upgrade.
But, it is very important that you should stop the log shipment and apply all the offline redologs, before the upgrade. Technically, you can import offline redologs after the upgrade, by changing "compatibility" parameter in oracle, but regarding to my experiences it may cause some problems after you transitiate the role from standby to primary.
In short;
In order to stop log shipment, at the primary site;
alter system set log_archive_dest_state_2=defer;
In order to import all the offline redologs without a delay, at the standby site;
alter database recover managed standby database cancel;
alter database recover managed standby database nodelay disconnect from session;
I hope that I clarified the issue,
Best regards,
Orkun Gedik

Ora-38500 physical standby database not started

hiiii,
When i executed the command at physical standby database server.
it give error:
To start real-time apply:
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE
2> USING CURRENT LOGFILE;
Error at line 1:
ORA: 38500 using current logfile option not available without stand.
please help me how could i start physical standby database
Regards
Vaibhav Dixit

Hi Vaibhav,
What exactly do you want to do?
Alter database recover managed standby database; --->it will be in Manged Recovery mode.
Alter database mount standby database; ----> it will be mounted, but no log files applies.
Alter database open read only; ----> it will be open with read only option, but archeive logs will NOT be applied
If you want to apply the Archive logs which are trasfered from Primary, then you need to fire the below commands
Alter database recover managed standby database;
Alter database recover managed standby database using current logfile;
Alter database recover managed standby database using current logfile disconnect from session;
To stop applying archives then,
Alter database recover managed standby database cancel;
Thanks and Regards.
tnaresh1982

The redo apply seems not work

I use Oracle 11g r2 configure a data guard and fast_start fail over (using data guard broker) environment on linux.
The standby database only sync the data from the primary if
1. Issue 'alter system switch logfile;' on primary machine.
2. Cancel the redo apply and restart it on the standby.
And real-time redo apply can't start, when I issued 'ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE', the sqlplus is hanging and no response.
And in the broker, there always following warning:
Databases:
orclPri - Primary database
Warning: ORA-16829: fast-start failover configuration is lagging
orclStd - (*) Physical standby database
Warning: ORA-16829: fast-start failover configuration is lagging
Edited by: user1665703 on 2011-7-29 下午5:02
Edited by: user1665703 on 2011-7-29 下午5:04

As a quick test, go to the primary and say
SQL> select * from v$log;then connect to the standby and say
SQL> select process,status,sequence# from v$managed_standby;Show the output here with copy & paste. Also the output from the primary of
SQL> show parameter log_archive_dest_2or another destination you have setup to reach the standby.
Kind regards
Uwe Hesse
http://uhesse.wordpress.com

Deleting archivelog files once applied to physical standby database

Hi,
Any procedure for automatically deleting the archivelog files after applied to physical standby database.

also pls see DataGuard: auto delete redo logs after applied to physical standby?

Problem in recover physical standby database(Data Guard) by rman

Hello to all
I have created a physical standby database ,I want make backup of it by rman and when I lose it's datafile I can restore it ,making backup and restore is fine but in recovery I encounter some problem
scenarios is follow
1- In rman I create a backup of standby database by this command:
backup database plus archivelog delete all input;
2- I run this comman in rman for recover standby database
run{
2> set until scn 1392701;
3> restore database;
4> recover database;
5> }
(1392701 is extracted from this query "SELECT MAX(NEXT_CHANGE#)+1 UNTIL_SCN FROM V$LOG_HISTORY LH,
V$DATABASE DB WHERE LH.RESETLOGS_CHANGE#=DB.RESETLOGS_CHANGE# AND LH.RESETLOGS_TIME =
DB.RESETLOGS_TIME;" "http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/rman.htm")
but RMAN result is like this:
executing command: SET until clause
Starting restore at 13-DEC-08
using channel ORA_DISK_1
channel ORA_DISK_1: starting datafile backupset restore
channel ORA_DISK_1: specifying datafile(s) to restore from
backup set
restoring datafile 00001 to /u01/app/oracle/oradata/sari/system01.dbf
restoring datafile 00002 to /u01/app/oracle/oradata/sari/undotbs01.dbf
restoring datafile 00003 to /u01/app/oracle/oradata/sari/sysaux01.dbf
restoring datafile 00004 to /u01/app/oracle/oradata/sari/users01.dbf
restoring datafile 00005 to /u01/app/oracle/oradata/sari/example01.dbf
restoring datafile 00006 to /u01/app/oracle/oradata/sari/users02.dbf
channel ORA_DISK_1: reading from backup piece /home/oracle/backup/0ek24dt4_1_1
channel ORA_DISK_1: restored backup piece 1
piece handle=/home/oracle/backup/0ek24dt4_1_1
tag=TAG20081213T042506
channel ORA_DISK_1: restore complete, elapsed time: 00:01:07
Finished restore at 13-DEC-08
Starting recover at 13-DEC-08
using channel ORA_DISK_1
starting media recovery
archive log thread 1 sequence 116 is already on disk as file /u01/app/oracle/oradata/archive/1_116_666786084.arc
archive log thread 1 sequence 117 is already on disk as file /u01/app/oracle/oradata/archive/1_117_666786084.arc
archive log filename=/u01/app/oracle/oradata/archive/1_116_666786084.arc thread=1 sequence=116
archive log filename=/u01/app/oracle/oradata/archive/1_117_666786084.arc thread=1 sequence=117
unable to find archive log
archive log thread=1 sequence=118
RMAN-03002: failure of recover command at 12/13/2008 05:14:13
RMAN-06054: media recovery requesting unknown log: thread 1
seq 118 lowscn 1392700
3- then I decline 1392701 to 1392700 and i run this command
run{
2> set until scn 1392700;
3> restore database ;
4> recover database;
5> }
executing command: SET until clause
Starting restore at 13-DEC-08
using channel ORA_DISK_1
channel ORA_DISK_1: starting datafile backupset restore
channel ORA_DISK_1: specifying datafile(s) to restore from
backup set
restoring datafile 00001 to /u01/app/oracle/oradata/sari/system01.dbf
restoring datafile 00002 to /u01/app/oracle/oradata/sari/undotbs01.dbf
restoring datafile 00003 to /u01/app/oracle/oradata/sari/sysaux01.dbf
restoring datafile 00004 to /u01/app/oracle/oradata/sari/users01.dbf
restoring datafile 00005 to /u01/app/oracle/oradata/sari/example01.dbf
restoring datafile 00006 to /u01/app/oracle/oradata/sari/users02.dbf
channel ORA_DISK_1: reading from backup piece /home/oracle/backup/0ek24dt4_1_1
channel ORA_DISK_1: restored backup piece 1
piece handle=/home/oracle/backup/0ek24dt4_1_1 tag=TAG20081213T042506
channel ORA_DISK_1: restore complete, elapsed time: 00:01:08
Finished restore at 13-DEC-08
Starting recover at 13-DEC-08
using channel ORA_DISK_1
starting media recovery
archive log thread 1 sequence 116 is already on disk as
file /u01/app/oracle/oradata/archive/1_116_666786084.arc
archive log thread 1 sequence 117 is already on disk as
file /u01/app/oracle/oradata/archive/1_117_666786084.arc
archive log filename=/u01/app/oracle/oradata/archive/1_116_666786084.arc thread=1
sequence=116archive log
filename=/u01/app/oracle/oradata/archive/1_117_666786084.arc
thread=1 sequence=117Oracle Error:
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS
would get error below
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '/u01/app/oracle/oradata/sari/system01.dbf'
media recovery complete, elapsed time: 00:00:10
Finished recover at 13-DEC-08
4- if I run
run{
restore database;
recover database;
I will recieve that error of step 2 (RMAN-06054: media recovery requesting unknown log: thread 1
seq 118 lowscn 1392700)
5- if I just restore the database and I don't perform recovery by rman and I restart redo apply all thing seem fine
but in opening database I'll recieve ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '/u01/app/oracle/oradata/sari/system01.dbf' error)
do you know what is problem
thanks
Edited by: ARKH on Dec 12, 2008 11:06 PM

hi
I myself have found the solution , when I recover the standby database
it do recovery but at the end of recovery it raise the error(RMAN-06054: media recovery requesting unknown log: thread 1
seq 118 lowscn 1392700) but if I begain redo apply before open the database
and I wait till all redo apply process start and communication between the
standby database and the primary database start, then I can
open the standby database and no error will raise
but if befor restarting redo apply I open the database I'll recieve the
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '/u01/app/oracle/oradata/sari/system01.dbf' error
thanks

RE logical/physical standby database

1. Why logical standby database is SQL apply, and Physical standby database is redo apply? What ‘s the meaning/objective for that? (pls don’t tell me what is SQL/redo apply)
2. As we know, a logical standby database can be used for reporting and querying if primary database is down, why we still need a physical standby database (it can’t do that during recovering process, it just a same copy of primary database)? Why not just go ahead to set up only a perfect logical standby database? (just because logical one can’t accommodate all kinds of data type???)
3. Combined with Real time Apply and maximum protection, we can achieve a zero data loss, but could we achieve a zero downtime? Why or why not?

Go Through Below link
>>>Can you convert a Logical standby to a Physical Standby?

Physical standby database Version 11g Creation over grid control 10g

We are useing oracale 11g enterprise edition and want to create a physical standby database on another machine:
On primary host we've installed "standard database" and turned on archive log mode over em.
On the standby host we've installed only oracle without a database and without a listener.
On a third machine we've installed grid control and registered the primary and standby hosts. Using EM with Data Grid I'm attempting to create a Physical Standby on standby host. Everything is working except for the last part as noted here:
SQL*Plus: Release 11.1.0.6.0 - Production on Do Apr 3 11:21:17 2008
Copyright (c) 1982, 2007, Oracle. All rights reserved.
SQL> SQL> Bei einer nicht hochgefahrenen Instance angemeldet.
SQL> SQL> ORA-32004: obsolete and/or deprecated parameter(s) specified
ORACLE-Instance hochgefahren.
Total System Global Area 535662592 bytes
Fixed Size          1334380 bytes
Variable Size          167773076 bytes
Database Buffers     360710144 bytes
Redo Buffers          5844992 bytes
SQL>
Datenbank wurde geändert.
SQL> Verbindung zu Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options beendet
dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE 'C:\ORACLE\ORADATA\TTDB1\SYSTEM01.DBF' to 'c:\oracle\product\11.1.0\db_1\oradata\dg3\SYSTEM01.dbf'
dgcreate.DGrenameFiles: SELECT STATUS FROM V$DATAFILE WHERE NAME = 'C:\ORACLE\ORADATA\TTDB1\SYSTEM01.DBF'
dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE 'C:\ORACLE\ORADATA\TTDB1\SYSAUX01.DBF' to 'c:\oracle\product\11.1.0\db_1\oradata\dg3\SYSAUX01.dbf'
dgcreate.DGrenameFiles: SELECT STATUS FROM V$DATAFILE WHERE NAME = 'C:\ORACLE\ORADATA\TTDB1\SYSAUX01.DBF'
dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE 'C:\ORACLE\ORADATA\TTDB1\UNDOTBS01.DBF' to 'c:\oracle\product\11.1.0\db_1\oradata\dg3\UNDOTBS01.dbf'
dgcreate.DGrenameFiles: SELECT STATUS FROM V$DATAFILE WHERE NAME = 'C:\ORACLE\ORADATA\TTDB1\UNDOTBS01.DBF'
dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE 'C:\ORACLE\ORADATA\TTDB1\USERS01.DBF' to 'c:\oracle\product\11.1.0\db_1\oradata\dg3\USERS01.dbf'
dgcreate.DGrenameFiles: SELECT STATUS FROM V$DATAFILE WHERE NAME = 'C:\ORACLE\ORADATA\TTDB1\USERS01.DBF'
dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE 'C:\ORACLE\ORADATA\TTDB1\EXAMPLE01.DBF' to 'c:\oracle\product\11.1.0\db_1\oradata\dg3\EXAMPLE01.dbf'
dgcreate.DGrenameFiles: SELECT STATUS FROM V$DATAFILE WHERE NAME = 'C:\ORACLE\ORADATA\TTDB1\EXAMPLE01.DBF'
dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE 'C:\ORACLE\ORADATA\TTDB1\REDO01.LOG' to 'c:\oracle\product\11.1.0\db_1\oradata\dg3\REDO01.log'
dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE 'C:\ORACLE\ORADATA\TTDB1\REDO02.LOG' to 'c:\oracle\product\11.1.0\db_1\oradata\dg3\REDO02.log'
dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE 'C:\ORACLE\ORADATA\TTDB1\REDO03.LOG' to 'c:\oracle\product\11.1.0\db_1\oradata\dg3\REDO03.log'
dgcreate.DGrenameFiles: ALTER DATABASE CLEAR LOGFILE GROUP 1
dgcreate.DGrenameFiles: ALTER DATABASE CLEAR LOGFILE GROUP 2
dgcreate.DGrenameFiles: ALTER DATABASE CLEAR LOGFILE GROUP 3
dgcreate.DGgetRecoverySCN: SELECT MAX(NEXT_CHANGE#) FROM V$ARCHIVED_LOG
dgcreate.DGrecoverStby: ALTER DATABASE RECOVER AUTOMATIC FROM '%ORACLE_HOME%\RDBMS' STANDBY DATABASE UNTIL CHANGE 1061001
dgcreate.DGrecoverStby: ALTER DATABASE RECOVER CANCEL
dgcreate.DGrecoverStby: ALTER DATABASE OPEN READ ONLY
SQL Error: ORA-16004: Sciherungs-Datenbank muss wiederhergestellt werden
ORA-01152: Backup-Datei zum Wiederherstellen der Datei 1 war nicht alt genug
ORA-01110: Datendatei 1: 'C:\ORACLE\PRODUCT\11.1.0\DB_1\ORADATA\DG3\SYSTEM01.DBF' (DBD ERROR: OCIStmtExecute)
What is to do?
What mean's in this case:
"ORA-01152 file string was not restored from a sufficiently old backup
Cause: An incomplete recovery session was started, but an insufficient number of redo logs were applied to make the database consistent. This file is still in the future of the last redo log applied. The most likely cause of this message is forgetting to restore the file from backup before doing incomplete recovery.
Action: Apply additional redo log files until the database is consistent or restore the datafiles from an older backup and repeat recovery."

Thanks for your immediate reply,
but there's a problem: We don't create the standby database manually. The creation is done by data guard over grid control. And the "automatic" creation stopps at this point.
Unfortunatly we don't know, wich steps of a manuall standby database creation are done and wich steps are not done at this point.
The oracle documentation (for release 11g) to create a manuall standby database is "B28294-02". But there's no step 5 "alter database recover managed standby database disconnect from session". Do you mean step 4 of chapter 3.2.6?
Is there no way, to create a standby database automatically over grid control? Or do we have to do something else before creating the physical standby database? Perhaps we have to create a full backup after switching to archive log mode?

Upgrading with a physical standby database in place

Hi all
I am planning to upgrade my database which is 11.2.0.1 (Windows 32 platform) to 11.2.0.3. It has a primary standby database. I only have 1 server for testing the primary database, so I am looking for some help.
I was reading http://docs.oracle.com/cd/B28359_01/server.111/b28294/upgrades.htm#CHDBJAGG and I confuse about step 4 and 5
+4. Install the new release of the Oracle software into a new Oracle home on the physical standby database system, as described in the Oracle Database Upgrade Guide.+
+5. Mount the physical standby database.+
My question is in step 5, when I mount the physical standby database, does it mounted using new Oracle binary or still using the old version? From my understanding what is step 4 doing is to copying files to new home only. Changing the service to use the new oracle binary is done by dbua. I know this when I test upgrading the primary database.
Regards
Stanley.

Hello;
new Oracle binary or the new Oracle home if you will.
So you install the new software on the standby only, all the upgrade SQL gets done on the Primary and then you ENABLE and startup mount on the new oracle home and the standby gets upgraded from the Primary redo.
Its pretty simple ( My exact plan )
1. Disable log shipping from the Primary
2. Shutdown Standby
3. Install 11.2.0.3 on Standby - Just the software
4. Startup Standby in recovery mode - do NOT run r any SQL at the standby
5. Shutdown Primary
6. Install 11.2.0.3 on Primary
7. Run Upgrade SQL or DBUA at Primary
8. Re-enable log shipping
9. Monitor the redo apply from Primary to Standby - this will also upgrade the Standby data dictionary
Make sure your tnsnames and listener files move to the new Oracle home and edit as needed.
Another oracle note is 278641.1
Best Regards
mseberg
Edited by: mseberg on Jan 29, 2013 8:21 PM

Redo apply is not done in physical standby database

Similar Messages

Maybe you are looking for