Differetn redo log names on primary db and standby db.

we are using oracle 10.2.0.2 to run sap. we plan to use data guard.the os is suse linux 10.3.
the archived redo log name's prefix is '1_' like '1_167109_678247864.dbf' on primary db.
if i recover standy database mannuly with cmd 'ALTER DATABASE RECOVER automatic standby database' to fix redo log gap, the required archived redo log name's prefix is 'PRDarch1_' like 'PRDarch1_167260_678247864.dbf'.
i checked the oracle parameter 'LOG_ARCHIVE_FORMAT' on both side were set to '%t_%s_%r.dbf'.
my question is the different name have any effect on datagurad? Or we just can ignore it, because it doesn't matter.
thanks in advance.

I'm not interested in a debate so much as finding the answer. Thanks for the info. And welcome to the forum by the way.
That said I would think B14239-05 would answer your question.
In section 5.7.1 it shows:
LOG_ARCHIVE_FORMAT=log%t_%s_%r.arc
You may be correct on the default, but they only answer I can give you is I have never setup Data Guard that way. I hope this saves you some time.
Where did you find this? (log_archive_dest_1 = "LOCATION=/oracle/PRD/oraarch/PRDarch MANDATORY REOPEN",)
I would consider avoiding the use of MANDATORY. This attribute will cause you a world of trouble if your Standby is unreachable.
Also if you are using a Flash Recovery Area you do not need to setup a local archiving destination.
If you are not using Flash Recovery with Data Guard you should. Try testing a failover without it.
Best Regards
mseberg

Similar Messages

Adding redo logs for dataguard primary server

Dear all:
i have physical dataguard servers
i want to add new redologs for primary server with big size ..
please advice what will be the action with stand by server.
Thanks ,,

Dear all:
i have physical dataguard servers
i want to add new redologs for primary server with
big size ..
please advice what will be the action with stand by
server.
Thanks ,,Most of these information are kept in the control file . You have to recreate your stand by control file after you added the new online redo logs. Transfer this to the standby server , with the the new online redo redo while you standby is down . Your standby system should be able to recognize it when it goes back to stand by mode.

Use of standby redo log files in primary database

Hi All,
What is the exact use of setting up standby redo log files in the primary database on a data guard setup?
any good documents?

A standby redo log is required for the maximum protection and maximum availability modes and the LGWR ASYNC transport mode is recommended for all databases. Data Guard can recover and apply more redo data from a standby redo log than from archived redo log files alone.
You should plan the standby redo log configuration and create all required log groups and group members when you create the standby database. For increased availability, consider multiplexing the standby redo log files, similar to the way that online redo log files are multiplexed.
refer the link,and Perform the following steps to configure the standby redo log.:-
http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/create_ps.htm#i1225703
If the real-time apply feature is enabled, log apply services can apply redo data as it is received, without waiting for the current standby redo log file to be archived. This results in faster switchover and failover times because the standby redo log files have been applied already to the standby database by the time the failover or switchover begins.
refer the link
http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/log_apply.htm#i1023371

Adding STAND BY REDO LOG in the Primary side........

Hi All,
I have set STANDBY_FILE_MANAGEMENT=AUTO in standby side and also LOG_FILE_NAME_CONVERT is pointing to an exiting location at OS level...
When i added a datafile to an existing tablespace in the primary side and performed a log switch on the same . The added datafile got
relflected in STANDBY side ...
But when I am trying to add a standby logfile (new group) is not getting added .........
Please help me on this...........
For this will I need to perform the below steps .
1-Add a standby redolog in the Primary side......
2-then Cancel the managed recovery process from the standby side...
3- Add the same standby redolog (same name and size) in the standby side
4-put the standby in recovery mode ......
Thanks

Thanks for the reply ......
I have gone thgrough it....but i donot find my answer .....
My question is "Why *STANDBY_FILE_MANAGEMENT=AUTO* functionality is not adding a standby redolog in STANDBY SIDE automatically
when i am adding a standby redolog in the PRIMARY SIDE.....
Thanks.......

Redo log files are not applying to standby database

Hi everyone!!
I have created standby database on same server ( windows XP) and using oracle 11g . I want to synchronize my standby database with primary database . So I tried to apply redo logs from primary to standby database as follow .
My standby database is open and Primary database is not started (instance not started) because only one database can run in Exclusive Mode as DB_NAME is same for both database. I run the following command on the standby database.
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;
It returns "Database altered" . But when I checked the last archive log on primary database, its sequence is 189 while on standby database it is 177. That mean archived redo logs are not applied on standby database.
The tnsnames.ora file contains entry for both service primary & standby database and same service has been used to transmit and receive redo logs.
1. How to resolve this issue ?
2.Is it compulsory to have Primary database open ?
3. I have created standby control file by using command
SQL> ALTER DATABASE CREATE STANDBY CONTROLFILE AS ‘D:\APP\ORACLE\ORADATA\TESTCAT\CONTROLFILE\CONTROL_STAND1.CTL‘;
So database name in the standby control file is same as primary database name (PRIM). And hence init.ora file of standby database also contains DB_NAME = 'PRIM' parameter. I can't change it because it returns error of mismatch database name on startup. Should I have different database name for both or existing one is correct ?
Can anybody help me to come out from this stuck ?
Thanks & Regards
Tushar Lapani

Thank you Girish. It solved my redo apply problem. I set log_archive_dest parameter again and then I checked archive redo log sequence number. It was same for both primary and standby database. But still table on standby database is not being refresh.
I did following scenario.
1. Inserted 200000 rows in emp table of Scott user on Primary database and commit changes.
2. Then I synchronized standby database by using Alter database command. And I also verify that archive log sequence number is same for both database. It mean archived logs from primary database has been applied to standby database.
3. But when I count number of rows in emp table of scott user on standby database, it returns only 14 rows even of redo log has been applied.
So my question is why changes made to primary database is not reflected on standby database although redo logs has been applied ?
Thanks

Switchover between primary RAC and standby single instance

Hello All,
I am using Oracle 11gR2.
I am trying to do a switch over between primary database (RAC 2 nodes) and physical standby (single instance)
If my Primary is single instance i was following the below steps:
On the standby
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT;
On the primary database:
alter database commit to switchover to standby with session shutdown;
shutdown immediate;
startup nomount;
alter database mount standby database;
On the standby again:
alter database commit to switchover to primary WITH SESSION SHUTDOWN;
On the new standby:
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT FROM SESSION;now, and since my primary is RAC when i am trying switch over I am getting the below error:
SQL> alter database commit to switchover to standby with session shutdown;
alter database commit to switchover to standby with session shutdown
ERROR at line 1:
ORA-01105: mount is incompatible with mounts by other instancesPlus that when I want to apply the remaining steps (below step), should I do it on each instance alone? or is there anyway to do it using the srvctl command:
alter database mount standby database;Regards,

Hi,
Since You are using 2 node RAc as primary, so for switchover operation you need to shutdown
one database instance( Suppose instance 2).
Suppose your node1:
hostname is dcpdb1
and node 2:
hostname is dcpdb2
and standby hostname is drpdb1
So follow this steps for switchover .
How to Switchover from Primary to Standby Database?
Process:
On the primary server, check the latest archived redo log and force a log switch.
*########### Login dcpdb1 as Oracle user #########*
SQL> SELECT sequence#, first_time, next_time
FROM v$archived_log
ORDER BY next_time;
SQL> ALTER SYSTEM SWITCH LOGFILE;
Check the new archived redo log has arrived at the standby server and been applied.
*########### Login drpdb1 as Oracle user #########*
SQL> SELECT sequence#, first_time, next_time, applied
FROM v$archived_log
ORDER BY next_time ;
*########### Login dcpdb2 as Oracle user #########*
SQL> SELECT sequence#, first_time, next_time
FROM v$archived_log
ORDER BY next_time ;
SQL> ALTER SYSTEM SWITCH LOGFILE;
Check the new archived redo log has arrived at the standby server and been applied.
*########### Login drpdb1 as Oracle user #########*
SQL> SELECT sequence#, first_time, next_time, applied
FROM v$archived_log
ORDER BY next_time ;
*########### Login dcpdb1 as Oracle user #########*
SQL> SELECT SWITCHOVER_STATUS FROM V$DATABASE;
SWITCHOVER_STATUS
TO STANDBY
*########### Login dcpdb2 as Oracle user #########*
SQL> SELECT SWITCHOVER_STATUS FROM V$DATABASE;
SWITCHOVER_STATUS
TO STANDBY
*########### Login drpdb1 as Oracle user #########*
SQL> SELECT SWITCHOVER_STATUS FROM V$DATABASE;
SWITCHOVER_STATUS
NOT ALLOWED
*########### Login dcpdb2 as Oracle user #########*
SQL> shutdown immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL>
*########### Login dcpdb1 as Oracle user #########*
SQL> ALTER DATABASE COMMIT TO SWITCHOVER TO PHYSICAL STANDBY WITH SESSION SHUTDOWN;
Database altered.
SQL>
SQL> shutdown immediate
ORA-01507: database not mounted
ORACLE instance shut down.
SQL>
SQL> startup mount
ORACLE instance started.
Total System Global Area 1.5400E+10 bytes
Fixed Size 2184872 bytes
Variable Size 7751076184 bytes
Database Buffers 7616856064 bytes
Redo Buffers 29409280 bytes
Database mounted.
SQL> SELECT SWITCHOVER_STATUS FROM V$DATABASE;
SWITCHOVER_STATUS
TO PRIMARY
SQL>
*########### Login drpdb1 as Oracle user #########*
SQL> SELECT SWITCHOVER_STATUS FROM V$DATABASE;
SWITCHOVER_STATUS
SESSIONS ACTIVE
SQL> alter database commit to switchover to primary with session shutdown;
Database altered.
SQL> shutdown immediate
ORA-01109: database not open
Database dismounted.
ORACLE instance shut down.
SQL>
SQL> startup
ORACLE instance started.
Total System Global Area 1.5400E+10 bytes
Fixed Size 2184872 bytes
Variable Size 7717521752 bytes
Database Buffers 7650410496 bytes
Redo Buffers 29409280 bytes
Database mounted.
Database opened.
*########### Login dcpdb1 as Oracle user #########*
SQL> alter database open read only;
Database altered.
SQL> alter database recover managed standby database using current logfile disconnect;
Database altered.
*########### Login dcpdb2 as Oracle user #########*
SQL> startup mount
ORACLE instance started.
Total System Global Area 1.5400E+10 bytes
Fixed Size 2184872 bytes
Variable Size 7751076184 bytes
Database Buffers 7616856064 bytes
Redo Buffers 29409280 bytes
Database mounted.
SQL> alter database open read only;
Database altered.
SQL> alter database recover managed standby database using current logfile disconnect;
Database altered.
SQL> SELECT SWITCHOVER_STATUS FROM V$DATABASE;
SWITCHOVER_STATUS
NOT ALLOWED
SQL>
*########### Login drpdb1 as Oracle user #########*
SQL> SELECT SWITCHOVER_STATUS FROM V$DATABASE;
SWITCHOVER_STATUS
TO STANDBY
*########### Login dcpdb1 as Oracle user #########*
SQL> SELECT SWITCHOVER_STATUS FROM V$DATABASE;
SWITCHOVER_STATUS
NOT ALLOWED
SQL>
*########### Login dcpdb2 as Oracle user #########*
SQL> SELECT SWITCHOVER_STATUS FROM V$DATABASE;
SWITCHOVER_STATUS
NOT ALLOWED
SQL>
*####################### Finish SwitchOver ########################*
Check
*########### Login drpdb1 as Oracle user #########*
SQL> alter system switch logfile;
SQL>
SELECT sequence#, first_time, next_time
FROM v$archived_log
ORDER BY sequence#;
SQL> archive log list
*########### Login dcpdb1 as Oracle user #########*
SQL>
SELECT sequence#, first_time, next_time, applied
FROM v$archived_log
ORDER BY sequence#;
SQL> archive log list
*########### Login dcpdb2 as Oracle user #########*
SQL>
SELECT sequence#, first_time, next_time, applied
FROM v$archived_log
ORDER BY sequence#;
SQL> archive log list
Thanks
Solaiman
Edited by: 876149 on Apr 12, 2013 11:51 AM

Can I have a primary database and standby database with a different windows version?

Hi
I need your help.
We need to increase the memory in the server where is the standby database , but first, we need to upgrade the windows version.
The actual version is windows 2003 standard edition 64 bits
The new version will be windows 2003 enterprise edition 64 bits
This difference in windows version between primary and standby servers can cause a problem in the synchronization between primary and standby databases ??
What do you recommend? Have both servers in the same windows version?
The databases are in SQL SERVER 2005.
Thanks.
Loreinn

This difference in windows version between primary and standby servers can cause a problem in the synchronization between primary
and standby databases ??<o:p></o:p>
There is no issue with database synchronization as long as SQL Server is of same version.<o:p></o:p>
What do you recommend? Have both servers in the same windows version?<o:p></o:p>
OS(Windows version) has no restriction for using SQL server 2005 database mirroring/log shipping. You can go with upgrade without any worries on SQL
database side.<o:p></o:p>

Primary Database and Standby Database sync

How to know that standby database is in sync with primary database?

Query the V$LOG_HISTORY view on the standby database, which records the latest log sequence number that has been applied. For example, issue the following query:
SQL> SELECT THREAD#, MAX(SEQUENCE#) AS "LAST_APPLIED_LOG"
2> FROM V$LOG_HISTORY
3> GROUP BY THREAD#;
THREAD# LAST_APPLIED_LOG
1 967In this example, the archived redo log with log sequence number 967 is the most recently applied log.
You can also use the APPLIED column in the V$ARCHIVED_LOG fixed view on the standby database to find out which log is applied on the standby database. The column displays YES for the log that has been applied. For example:
SQL> SELECT THREAD#, SEQUENCE#, APPLIED FROM V$ARCHIVED_LOG;
THREAD# SEQUENCE# APP
1 2 YES
1 3 YES
1 4 YES
1 5 YES
1 6 YES
1 7 YES
1 8 YES
1 9 YES
1 10 YES
1 11 NO

Can the instance name of prod. database and standby database may be same

Hi all,
Actually I knew that while configuring Physical Standby
1> Database name should be same
2> Instance name should be different
But,today I saw a DR system where the database name and instance names are the same. So I came to know that it can be done.
I just wanted to know that what are the trade-offs of putting DB name and instance name same?

There isn't a tradeoff. By default, the instance_name is the same as the db_name unless if specified differently in teh pfile. What matters is the service name connecting to the instance.

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

Why do we need standby redo log on Primary database.

Hi Gurus,
I was going through the document in OBE,
http://www.oracle.com/technology/obe/11gr1_db/ha/dataguard/physstby/physstdby.htm
I have two queries:
1) I noticed the statement -
"Configure the primary database to receive redo data, by adding the standby logfiles to the primary. "
Why do we have to create standby redo log on a primary database?
2) There is another statement --
"It is highly recommended that you have one more standby redo log group than you have online redo log groups as the primary database. The files must be the same size or larger than the primary database’s online redo logs. "
Why do we need one additional standby redo log group than in Primary database.
Could anyone please explain to me in simple words.
Thanks
Cherrish Vaidiyan

Hi,
1. Standby redo logs are used only when the database_role is standby, it is recommended to be added in primary also so that they can be used on role reversal, however during normal working standby redo logs will not be used at all on primary.
2. In case of 3 online redo log groups, it is recommended to use 4 standby redo log group this is in case if log switching is happening frequently on primary and all 3 standby redo logs are still not completely archived on the standby and 4th can be used here as there will be some delay on standby due to network or slowness of arch on standby.
Use of the standby redo log groups depends on the redo generation rate, you can see only 2 standby redo logs are getting used while you have 4 standby redo log groups, when the redo generation rate is less.
So it is recommended to have one more standby redo log group when redo generation rate is high and all of the existing standby redo log group are getting used.
Regards
Anudeep

When changing redo-logs on Primary, do I need to change my standby also?

Hi, I need to resize my redo logs on a primary db which has a physical standby attached. Do I need to modify this standby or will the change propagate. It seems unlikely to me.
thanx

Only clue that I have found is at
http://download-east.oracle.com/docs/cd/B12037_01/server.101/b10726/configbp.htm
Section "Use Multiplexed Standby Redo Logs and Configure Size Appropriately"
>>
The remote file server (RFS) process for the standby database writes only to an SRL whose size is identical to the size of an online redo log for the production database. If it cannot find an appropriately sized SRL, then RFS creates an archived redo log file directly instead and logs the following message in the alert log:
No standby redo log files of size <#> blocks available.
>>

How could I find specified date of REDO log and archive REDO log ?

we use Oracle11gr2 on win2008R2.
1
How could I find specified date of REDO log(2013/10/17,etc) and archive REDO log ?
2
What is the format of archive REDO log.? (zipped file ?)

user12075536123 wrote:
1)
select * from v$archived_log;
select * from v$log_history;
but there is a possibility there is no old data
below contains no filename column
SQL> desc v$log_history
Name                                      Null?    Type
RECID                                              NUMBER
STAMP                                              NUMBER
THREAD#                                            NUMBER
SEQUENCE#                                          NUMBER
FIRST_CHANGE#                                      NUMBER
FIRST_TIME                                         DATE
NEXT_CHANGE#                                       NUMBER
RESETLOGS_CHANGE#                                  NUMBER
RESETLOGS_TIME                                     DATE
there is NO data when archive mode is disabled

Physical Standby Online Redo log files,

Hi,
I'm trying to create a physical standby database (10.2.0.3). I'm a little confused about the requirement for online redo logs on the standby.
in my standby alert log I get the following when I issue:
SQL> alter database recover managed standby database disconnect from session
"ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '/appl/oradata/prod/prod_1_redo_01_02.log'
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory
Additional information: 3"
/appl/oradata/prod/prod_1_redo_01_02.log is the path to the location of the online redo logs on the production system. This file does not exist on the standby filesystem so the error is correct.
I assume that it gets this information from the standby control file I created on the production system and copied over to the standby.
Do I need to copy the online redo logs from the primary over to the standby site or do I need to create online redo logs on the standby?
Does the standby need to have redo log files?
I'm not talking about 'standby log files' of the type created using 'alter database add standby log file'. I've not got that far yet.
I just need to establish if a physical standby requires online redo log files?
Thanks in advance,
user234564

I wanted to update this thread since I've been dealing with the exact same errors. The basic question is: "does a physical standby need the online redo logs?"
Answer: Not really, until one wants to switchover or failover (and become a primary database). Furthermore, whenever the MRP process is started, Oracle prepares for a possible switchover/failover by "clearing" the online redo logs (MetaLink note# 352879.1). It is not a big deal, since Oracle will build the actual redo files when the "alter database open resetlogs" is accomplished during a "role transition."
In our situation, we have decided to use our standby for nightly exports. We stop MRP, open the database read-only, then restart MRP. We built these standby DBs with RMAN. The RMAN duplicate process will not build the online redo log files until the database is opened for read/write (with resetlogs). However, we haven't had a need for read/write (i.e. a switchover).
Thus, every morning we have been getting the same errors that "user234564" posted above. At first the errors seemed scary, then we realized they were just a nusiance. In order to clean things up, all I did was just "cp" our stanby redo logs (SRL) into our online redo directories ensuring the names matched what was in v$logfile. When I restarted MRP, the alert log clearly showed Oracle clearing these "newly found" online redo logs.

Standby Redo Log just sits as IN-MEMORY

Hi, I have shipped an archived redo log from my Primary to my physical standby.
I can see the log arriving at my Standby and being applied
select thread#, max(sequence#) "Last Standby Seq Received"
from v$archived_log val, v$database vdb
where val.resetlogs_change# = vdb.resetlogs_change#
group by thread# order by 1;
returns
   THREAD# Last Standby Seq Received
         1                       151
select thread#, max(sequence#) "Last Standby Seq Applied"
from v$archived_log val, v$database vdb
where val.resetlogs_change# = vdb.resetlogs_change#
and applied='YES'
group by thread# order by 1;
   THREAD# Last Standby Seq Applied
         1                      150
select stamp,name,applied
from v$archived_log
where applied != 'YES'
    STAMP
NAME
APPLIED
827498375
/home/app/oracle/fast_recovery_area/STANDBYL/archivelog/2013_09_30/o1_mf_1_151_9
4lrqpj3_.arc
IN-MEMORY
This log continually sits like this
I know that Redo Appply is active
select * from v$managed_standby where process = 'MRP0';
PROCESS          PID STATUS       CLIENT_P
CLIENT_PID
CLIENT_DBID
GROUP#                                   RESETLOG_ID    THREAD# SEQUENCE#
    BLOCK#     BLOCKS DELAY_MINS KNOWN_AGENTS ACTIVE_AGENTS
MRP0            3068 APPLYING_LOG N/A
N/A
N/A
N/A                                        820252586          1        152
      5038     102400          0            3             3
It looks as if 151 has been applied - yet
select thread#, max(sequence#) "Last Standby Seq Applied"
from v$archived_log val, v$database vdb
where val.resetlogs_change# = vdb.resetlogs_change#
and applied='YES'
group by thread# order by 1;
still shows 150 !
151 is not that big, I still would have expected it to have applied by now ( in excess of 30 mins )
Also I know there is no defer or time delay on the archive_destination setting on the Primary.
Any ideas why this standby redo log just sits IN-MEMORY ?
thanks,
Jim

Hello;
Not able to reproduce issue. Using Oracle 11.2.0.3 without Real-time apply.
select thread#, max(sequence#) "Last Standby Seq Received"
from v$archived_log val, v$database vdb
where val.resetlogs_change# = vdb.resetlogs_change#
group by thread# order by 1;
THREAD#                Last Standby Seq Received
1                      194
select thread#, max(sequence#) "Last Standby Seq Applied"
from v$archived_log val, v$database vdb
where val.resetlogs_change# = vdb.resetlogs_change#
and applied='YES'
group by thread# order by 1;
THREAD#                Last Standby Seq Applied
1                      194
select thread#, max(sequence#) "Last Standby Seq Applied"
from v$archived_log val, v$database vdb
where val.resetlogs_change# = vdb.resetlogs_change#
And Applied='YES'
group by thread# order by 1;
THREAD#                Last Standby Seq Applied
1                      194
SELECT ARCH.THREAD# "Thread", ARCH.SEQUENCE# "Last Sequence Received", APPL.SEQUENCE# "Last Sequence Applied"
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
1                      194                    194
select * from v$managed_standby where process = 'MRP0';
( shows the next sequence 195 on mine )
Is it possible the Standby has one extra archive? I've noticed that sometime you will see one extra on that side which appears to have nothing to do with the Data Guard process.
Best Regards
mseberg

Differetn redo log names on primary db and standby db.

Similar Messages

Maybe you are looking for