Physical standby query

Friends,
I am applying the ddl changes on the primary database.I have doubt that whether will it automatically apply the sane changes on the physical standby database.
I am new to the Oracle DBA.Could you please guide me.
Thanks,
Roshan.

user602872 wrote:
All,
Thank you so much for your comments.
I am adding only DDL Changes like add column and drop column statments and output of the query.
select force_logging from v$database;
FOR
YES
and also standby_file_mangement parameter has value "auto" so everything is fine ..Thanks again.
Thanks,
Roshan.Then there are no problems,all ddl changes will apply on standby db

Similar Messages

Data guard synchronization after link down b/w primary and physical standby

Hi All,
I have configured data guard on oracle 11gr2 db. Normally switchover between my primary and physical standby happens smoothly and the Apply lag would be zero. Recently We had to test a scenario when the network link between Primary and Physical standby is completely down and Physical standby is isolated completely for more than half an hour.
When we brought up the link every thing worked smoothly but apply lag started increasing from 0 to around 3 hrs. And then it started reducing to 0. Currently Apply lag and transport lag shows 0.
But is this normal behaviour of oracle data guard that when the link between primary and physical standby is completely down, It requires 3-4 hrs for resynchronization ??? Even when during isolation, there were very few transactions happend on primary database ??
Are there any documents available for this scenario??
Thanks

Hi, after the link is up, if there were some transactions and produced archive logs it's normal to take some time for resync. To check if 3-4 hours is normal or not, you can repeat the scenario and this time check
- how many archivelogs does primary produce in this period.
- after the link is up, does archivelog transfer immediately starts from primary to standby? Is primary able to send these archivelogs parallel?
- Is there anything wrong with the apply process?
check primary & standby alert log files, and run this query on standby to check the transport and apply processes:
SELECT PROCESS, STATUS, THREAD#, SEQUENCE#, BLOCK#, BLOCKS FROM V$MANAGED_STANDBY;
regards

How To Check Whether Physical Standby is in Sync with the Primary

hi All,
I'm new in data guard. In our current production, my boss is asking me to write a shell scripts monitoring physical standby and primary archive is sync (archive gap)
I'm referring metalink [ID 861595.1], but when i ran the first query in Primary node, the screen hang.
On 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;
I tried to turn on 10046 SQL trace, the SQL consume a lot of CPU, and it full table scan in X$KCCAL table.
TKPROF result look like below:
call     count       cpu    elapsed       disk      query    current        rows
Parse        1      0.00       0.00          0          0          0           0
Execute      1      0.00       0.00          0          0          0           0
Fetch        1     88.29     115.59          0          0          0           0
total        3     88.30     115.60          0          0          0           0
Misses in library cache during parse: 1
Misses in library cache during execute: 1 Optimizer mode: ALL_ROWS Parsing user id: 80
Rows     Row Source Operation
      0 SORT ORDER BY (cr=0 pr=0 pw=0 time=21 us)
      0   FILTER (cr=0 pr=0 pw=0 time=19 us)
   1124    FIXED TABLE FULL X$KCCAL (cr=0 pr=0 pw=0 time=40537 us)
      0    FILTER (cr=0 pr=0 pw=0 time=115538625 us)
   1122     HASH GROUP BY (cr=0 pr=0 pw=0 time=115530193 us)
7465972      FIXED TABLE FULL X$KCCAL (cr=0 pr=0 pw=0 time=94648975 us)
Elapsed times include waiting on following events:
Event waited on                        Times   Max. Wait Total Waited
-----------------------------------   Waited ---------- ------------
SQL*Net message to client               1        0.00          0.00
control file sequential read        16841        0.05         30.88
SQL*Net break/reset to client           1        0.00          0.00Due to this is production environment, thus i had terminated the session, can anyone teach me or share with me any scripts to monitor physical standby is sync with primary or not? Or do you encounter the above issue when running the SQL?
My db version is Oracle 11.2.0.1.0
Thanks in advance.
Regards,
Klnghau

Hello;
Note 861595.1 has not been subject to an independent technical review. Not sure if that make it bad or not.
This is what I'm using: ( I spool this to a file and have it e-mailed to me daily)
PROMPT
PROMPT Checking last sequence in v$archived_log
PROMPT
clear screen
set linesize 100
column STANDBY format a20
column applied format a10
SELECT name as STANDBY, SEQUENCE#, applied, completion_time from v$archived_log WHERE DEST_ID = 2 AND NEXT_TIME > SYSDATE -1;
prompt
prompt----------------Last log on Primary--------------------------------------|
prompt
select max(sequence#) from v$archived_log where NEXT_TIME > sysdate -1;
Best Regards
mseberg

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

Problem creating physical Standby database with RMAN

Hi All
I am trying to learn oracle dataguard and as part of the process learning creating standby database.
Platform : Sun-Fire-V250 Sparc, Solaris 10
Database Version - Oracle 11R2
I am creating standby database on same server, so directory structure is different.
Following the instructions on Oracle site I managed to create a functional physical standby database. But I am not able to create standby database using RMAN. These are the steps that I followed-
1.Set up all necessary parameters on primary database as done while creating physical standby database manually, eg setting force logging, creating standby logs etc.
2.Edited parameter file on primary database as done while creating manual pysical standby database creation. Some of the changes done are-
On Primary Database:
*.FAL_CLIENT='orcl11020' #Primary database unique name
*.FAL_SERVER='stdby_11' #Standby database unique name
db_file_name_convert='/<dir>/oradata/stdby_11','/<dir>/oradata/orcl11020'
log_file_name_convert='/<dir>/oradata/stdby_11','/<dir>/oradata/orcl11020','/<dir>/oradata/stdby_11/redo_mem','/<dir>/oradata/orcl11020/redo_mem'
standby_file_management=auto
*.log_archive_config='DG_CONFIG=(orcl11020,stdby_11)'
*.log_archive_dest_1='LOCATION=/<dir>/flash_recovery_area/ORCL11020/archivelog
VALID_FOR=(ALL_LOGFILES,ALL_ROLES) db_unique_name=orcl11020'
*.log_archive_dest_2='SERVICE=stdby_11 LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) db_unique_name=stdby_11'
*.LOG_ARCHIVE_DEST_STATE_1='ENABLE'
*.LOG_ARCHIVE_DEST_STATE_2='ENABLE'
*.LOG_ARCHIVE_FORMAT='%t_%s_%r.arc'
*.LOG_ARCHIVE_MAX_PROCESSES=30
Copied same pfile for standby database and modified following-
*.control_files='/<dir>/oradata/stdby_11/stdby_11.ctl','/<dir>/fra_stdby/stdby_11/stdby_11.ctl'
*.db_name='orcl1102'
*.db_unique_name='stdby_11'
*.FAL_CLIENT='stdby_11'
*.FAL_SERVER='orcl11020'
db_file_name_convert='/<dir>/oradata/orcl11020','/<dir>/oradata/stdby_11'
log_file_name_convert='/<dir>/oradata/orcl11020','/<dir>/oradata/stdby_11','/<dir>/oradata/orcl11020/redo_mem','/<dir>/oradata/stdby_11/redo_mem'
standby_file_management=auto
*.log_archive_dest_1='LOCATION=/<dir>/fra_stdby/STDBY_11/archivelog
VALID_FOR=(ALL_LOGFILES,ALL_ROLES) db_unique_name=stdby_11'
*.log_archive_dest_2='SERVICE=orcl11020 LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE)
db_unique_name=orcl11020'
3. Add relevant information in tnsnames.ora and listener.ora files and then restart listener.
3. Created password file with same credential as primary database.
4.Up-to-date RMAN backup of primary database available.
5.Create standby controlfile with rman
While primary database s open (I tried with primary database in mount mode as well)-
$>rman catalog rman/paswd@rman target /
RMAN> BACKUP CURRENT CONTROLFILE FOR STANDBY;
6. Open a new terminal and startup standby database in nomount mode using parameter file created -
$>ORACLE_SID=stdby_11
$>export ORACLE_SID
$>sqlplus / as sysdba
SQL>STARTUP NOMOUNT pfile='<location/initfilename.ora'
SQL>quit
$> rman AUXILIARY / target sys/passwd@orcl11020 catalog rman/passwd@rman
RMAN>DUPLICATE TARGET DATABASE FOR STANDBY DORECOVER;
RMAN finishes without error but archive logs are not being tranported. Looking at the log, following caught my eye-
Error 1017 received logging on to the standby
Check that the primary and standby are using a password file
and remote_login_passwordfile is set to SHARED or EXCLUSIVE,
and that the SYS password is same in the password files.
returning error ORA-16191
FAL[client, ARC2]: Error 16191 connecting to orcl11020 for fetching gap sequence
Errors in file /<>dir>/diag/rdbms/stdby_11/stdby_11/trace/stdby_11_arc2_24321.trc:
ORA-16191: Primary log shipping client not logged on standby
Errors in file /<dir>/diag/rdbms/stdby_11/stdby_11/trace/stdby_11_arc2_24321.trc:
ORA-16191: Primary log shipping client not logged on standby
So on both primary and standby I confirmed
SQL> show parameter remote_login_passwordfile
NAME TYPE VALUE
remote_login_passwordfile string EXCLUSIVE
To make double sure that password files are same, I shutdown both databases, delete password files and recreated with same credentials.
Password files are called - orapworcl11020 and orapwstdby_11
Can someone guide me where thisngs are going wrong here please.

Not sure if I understood it clearly.
SELECT * FROM V$ARCHIVE_GAP;
returns no rows so there is no gap.
But could you please explain me the result of the previous query. To catch up again, on standby when I check
SELECT SEQUENCE#,APPLIED FROM V$ARCHIVED_LOG
SEQUENCE# APPLIED
75 NO
74 NO
76 NO
77 NO
I understand that though archive files have been copied across but they are not applied yet.
On primary when I give your query -
SELECT name as STANDBY,SEQUENCE#,applied, completion_time
2 FROM v$archived_log
3 where dest_id=2
4 and sequence# BETWEEN 74 and 80;
I get -
STANDBY SEQUENCE# APPLIED COMPLETIO
stdby_11 74 YES 28-JUN-11
stdby_11 75 YES 28-JUN-11
stdby_11 76 YES 29-JUN-11
stdby_11 77 YES 29-JUN-11
stdby_11 78 YES 29-JUN-11
stdby_11 79 YES 29-JUN-11
stdby_11 80 YES 29-JUN-11
stdby_11 75 NO 07-JUL-11
stdby_11 74 NO 07-JUL-11
stdby_11 76 NO 07-JUL-11
stdby_11 77 NO 07-JUL-11
stdby_11 78 NO 07-JUL-11
I have intentionally given
sequence# BETWEEN 74 and 80
because I know in the current incarnaion of the database, max sequence is 78.
So my understanding is, the rows between 28-29 June are from previous incarnation, correct me if I am wrong
Archive files of the current incarnation, since I successfully created standby database are shipped but yet to be applied - am I right?
Then my final question is, when will these archives be applied to standby database?
I am sorry to ask too many questions but I am just trying to understand how it all works.
Thanks for your help again

How Real Time Apply works while physical standby is open in Read Only mode

Hi,
With Active data guard option, we can open physical standby DB in read only mode, while redo log are being applied. (Real Time Query)
Standby Redo log (SRL) enables Real Time Apply (with "USING CURRENT LOGFILE" clause in recover database command on standby DB)
I am interested to know, how Real Time Query works ?
What is the mechanism with allows us to open physical standby DB in read only mode while redo logs are being applied continuously ?
Regards,
Sujit

Dear user7419391,
That is a new feature in Oracle Database 11g. MRP can use the real time apply in 10g but the concept here is different.
Taken from the following document;
http://www.ascent.co.za/documents/oracle/Oracle%20databse%2011g%20Active-Data-Guard%20datasheet.pdf
*Unique Advantages of Oracle Active Data Guard*
+Active Data Guard is an evolution of Data Guard technology, providing unique+
+performance advantages while leveraging all other enhancements included in Oracle+
+Data Guard 11g. For example, any Data Guard 11g physical standby database can+
+be easily converted to a Snapshot Standby. A Snapshot Standby is open read-write+
+and is ideally suited as a test system, able to process transactions independent of the+
+primary database. A Snapshot Standby maintains protection by continuing to receive+
+data from the production database, archiving it for later use. When tests are+
+complete, a single command discards changes made while open read-write and+
+quickly resynchronizes the standby database with the primary.+
The other link in the previous post is excellent and you really have to read it to understand the active data guard aspects.
Regards.
Ogan

ORA-326/ORA-334 Physical Standby DB - Not applying logs

Hi, all, I have a Dataguard, the primary db is a RAC with three nodes, the standby db is a physical standby. the dataguard are all oracle 10.2.0.3 on solaris 9 sparc system
Now, my standby db did not apply the archivelogs,there are some errors in standby alert log :
Thu Jan 8 15:44:31 2009
Errors in file /oracle/admin/xxxx/bdump/whut_mrp0_12863.trc:
ORA-00326:log begins at change 2984028173, need earlier change 2984013192
ORA-00334:archived log '+DGARCH/whut/3_22648_611942629.dbf'
Managed Standby Recovery not using Real Time Apply
Recovery interrupted!
Thu Jan 8 15:44:34 2009
Errors in file /export/home/oracle/admin/whut/bdump/whut_mrp0_12863.trc:
ORA-00326:log begins at change 2984028173, need earlier change 2984013192
ORA-00334:archived log '+DGARCH/whut/3_22648_611942629.dbf'
Thu Jan 8 15:44:34 2009
MRP0: Background Media Recovery process shutdown (whut)
and the archivelogs on the standby db like this :
NAME APP DEL
+DGARCH/whut/3_22651_611942629.dbf                           NO NO
+DGARCH/whut/3_22650_611942629.dbf                           NO NO
+DGARCH/whut/3_22649_611942629.dbf                           NO NO
+DGARCH/whut/3_22648_611942629.dbf                           NO NO
+DGARCH/whut/3_22648_611942629.dbf                           NO NO
+DGARCH/whut/3_22648_611942629.dbf                           NO YES
+DGARCH/whut/3_22291_611942629.dbf                           YES YES
+DGARCH/whut/2_62553_611942629.dbf                           NO NO
+DGARCH/whut/2_62552_611942629.dbf                           NO NO
+DGARCH/whut/2_62551_611942629.dbf                           NO NO
+DGARCH/whut/2_62550_611942629.dbf                           NO NO
query the first_change# on the standby db like this :
SEQUENCE# FIRST_CHANGE# APP ARC
22646 2983721221 NO YES
22647 2983911304 NO YES
22648 2984028173 NO YES
23813 2984013365 NO YES
23814 2984118027 NO YES
62546 2984027708 NO YES
SEQUENCE# FIRST_CHANGE# APP ARC
62547 2984163823 NO YES
23815 2984132128 NO YES
23816 2984312713 NO YES
62548 2984255538 NO YES
62549 2984312692 NO YES
22649 2984028196 NO YES
23817 2984351070 NO YES
then ,how to fix the dataguard and apply the archivelog on standby db ?
why I can found 2984028173 with 22648,but can not found 2984013192 ??
and why there have three 22648 with different applied status and deleted status on standby db ???
Thanks all.

Thank you for your reply.
the trc file like this:
/oracle/admin/xxx/bdump/xxx_mrp0_12863.trc
Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
ORACLE_HOME = /oracle/product/10.2.0/database
System name:     SunOS
Node name:     stdb
Release:     5.9
Version:     Generic_122300-25
Machine:     sun4u
Instance name: xxx
Redo thread mounted by this instance: 1
Oracle process number: 27
Unix process pid: 12863, image: oracle@stdb (MRP0)
*** SERVICE NAME:() 2009-01-08 15:44:24.179
*** SESSION ID:(197.3) 2009-01-08 15:44:24.179
ARCH: Connecting to console port...
*** 2009-01-08 15:44:24.180 61287 kcrr.c
MRP0: Background Managed Standby Recovery process started
*** 2009-01-08 15:44:29.191 1103 krsm.c
Managed Recovery: Initialization posted.
*** 2009-01-08 15:44:29.192 61287 kcrr.c
Managed Standby Recovery starting Real Time Apply
Recovery target incarnation = 5, activation ID = 721050634
Influx buffer limit = 152383 (50% x 304766)
Successfully allocated 3 recovery slaves
Using 367 overflow buffers per recovery slave
Start recovery at thread 3 ckpt scn 2984013192 logseq 22648 block 2
*** 2009-01-08 15:44:31.181
Media Recovery add redo thread 3
*** 2009-01-08 15:44:31.181
Media Recovery add redo thread 1
*** 2009-01-08 15:44:31.182
Media Recovery add redo thread 2
*** 2009-01-08 15:44:31.184 1103 krsm.c
Managed Recovery: Active posted.
*** 2009-01-08 15:44:31.838
Media Recovery Log +DGARCH/whut/3_22648_611942629.dbf
*** 2009-01-08 15:44:31.851 61287 kcrr.c
MRP0: Background Media Recovery terminated with error 326
ORA-00326: log begin at 2984028173, need earlier 2984013192
ORA-00334: archivelog: '+DGARCH/whut/3_22648_611942629.dbf'
*** 2009-01-08 15:44:31.851 61287 kcrr.c
Managed Standby Recovery not using Real Time Apply
*** 2009-01-08 15:44:31.851
Media Recovery drop redo thread 3
*** 2009-01-08 15:44:31.851
Media Recovery drop redo thread 1
*** 2009-01-08 15:44:31.851
Media Recovery drop redo thread 2
*** 2009-01-08 15:44:34.269 1103 krsm.c
Managed Recovery: Not Active posted.
ORA-00326: log begin at 2984028173,need earlier 2984013192
ORA-00334: archivelog: '+DGARCH/whut/3_22648_611942629.dbf'
ARCH: Connecting to console port...
*** 2009-01-08 15:44:34.359 61287 kcrr.c
MRP0: Background Media Recovery process shutdown
*** 2009-01-08 15:44:34.359 1103 krsm.c

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

Physical Standby database Vs. Logical Standby database

I have few questions regarding capability of Logical Standby Database against Physical Standby database.
1. How efficient is Logical Standby database in terms of Physical Standby Database?? How both differ from each other and can I use Logical Standby Database for disaster Recovery?? Can It be use for recovering the failed Primary Instance?? If yes how efficient and reliable it is??
2. What are the known bugs and roadblocks for logical standby database on Oracle 10.2.0.1 on Soalris X86-64?
3.As logical standby database not going to replicate each and every schema of Primary database?? how is the change management effects to the logical standby from primary?? I mean there are some parameters and job that we create on primary how can it be transferred over to the logical standby??

1. How efficient is Logical Standby database in terms
of Physical Standby Database?? How both differ from
each other and can I use Logical Standby Database for
disaster Recovery?? Can It be use for recovering the
failed Primary Instance?? If yes how efficient and
reliable it is??I'm not sure what sort of "efficiency" you're talking about here...
Physical standby is just the old, tried and true application of archived logs to recover a database. Very solid, very old school.
Logical standby, on the other hand, is parsing the redo log, extracting logical change records, and applying them to the standby database. This obviously takes a bit more processing effort, it's newer technology, it doesn't have quite the level of support that physical standby does (i.e. certain data types are excluded), etc. You certainly can use it for failover, but it isn't quite as robust as a physical standby. Of course, this is getting better and better all the time and is definitely a focus of Oracle's development efforts.
On the other hand, logical standby systems can do things other than act as a warm standby. They can be open serving reports, for example. You can create additional structures (i.e. new materialized views) to support reporting. A physical standby is pretty much always going to be in managed recovery mode, so it cannot be queried.
2. What are the known bugs and roadblocks for logical
standby database on Oracle 10.2.0.1 on Soalris
X86-64?a) You'll want to do a Metalink search
b) If you're talking about a high-availability solution, why are you looking at a base release of the database? Why wouldn't you apply the latest patchset?
3.As logical standby database not going to replicate
each and every schema of Primary database?? how is
the change management effects to the logical standby
from primary?? I mean there are some parameters and
job that we create on primary how can it be
transferred over to the logical standby??I'm not sure I understand... Changes made to the primary generate redo. Oracle parses that redo, generates a LCR, and sends that to the standby database where that change record gets applied.
Justin

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?

Dataguard physical standby archive log question

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

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

How to make a physical standby database in the read_only state in 11g?

In 10g, we can make a physical standby database in the read_only state. But in 11g, no a read_only state for a physical standby database. How to make a physical standby database in the read_only state in 11g?

Hi
read-only mode (for 11g physical standby)
A mode in which a database can be opened that allows queries, but disallows modifications.
A physical standby database can be opened read-only so that queries may be performed. If a license for the Oracle Active Data Guard option has been purchased, a physical satndby database can be open while redo apply is active. This capability is known as Real-time Query.
For more details have a look at:
http://download.oracle.com/docs/cd/B28359_01/server.111/b28294/manage_ps.htm#SBYDB00706
Hipe this Helps
Regards

Will logical standby database be replaced by physical standby database?

Will logical standby database be deprecated or replaced by physical standby database because of Real Time Query?
As far as I know, because of the emergence of Real Time Query, physiacl standby database is easier to work than logical standby database. There are so many restrictions on using logical standby database.
Will logical standby database be deprecated in the future?
Message was edited by:
frank.qian

Good question - you are right that with the advent of Real Time Query, physical standby databases can provide the 'reporting database' functionality that you used to have to use a logical standby database for.
But remember that logical standby databases allow additional schema objects, like materialized views and indexes, that you can't have with a physical standby (for the reasons Hans mentions). For example, you could have a index-light primary database for OLTP style workload, and an index-heavy logical standby, with MVs and dimensions for reporting, DW, etc.
For this reason I don't expect logical standby will become deprecated.

Starting a Physical Standby DB which is configured with real-time apply

Hi,
I wanted to get clarification on the correct procedure for starting and stopping a physical standby database. The Dataguard documentation states the following:
1. Start and mount the database:
SQL> STARTUP MOUNT;
2. Start log apply services:
To start Redo Apply, issue the following statement:
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE
2> DISCONNECT FROM SESSION;
To start real-time apply, issue the following statement:
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE
2> USING CURRENT LOGFILE;
My configuration is using real-time apply based on the information provided by the RECOVERY_MODE column of the V$ARCHIVED_DEST_STATUS view. Should I execute both ALTER statements or just the second one. If only the second one, how will the database re-synchronize, especially after a long down time. Also, must I do anything on the primary database prior to starting up the physical standby?
I'm using Oracle 10g SP1 on a linux server.

No. But you can recover until the last arch file generated on the primary, then you cancel the recovery and then use query#2 to start applying real-time. Refer to Note:343424.1 on Metalink.

How to stop and cancel physical standby database (ORACLE 10g)

Dear All,
I have physical standby setup and I want stopped for the time being that to use the database as an normal DB (standalone inestance).
Kindly advise and show me how do I do that.
Regards,

executing below query on primary db stops log shipping to standby.......i think this is sufficient for disabling your physical standby setup temporary
alter system set log_archive_dest_state_2=defer scope=both;
In future if you want your dataguard setup back..............you can rebuild the standby and enable the log_archive_dest_state_2 parameter.
Edited by: Veeresh.S on Nov 14, 2012 5:45 PM

Physical standby query

Similar Messages

Maybe you are looking for