Dataguard query
I have two queries regarding Dataguard:
1. Do the instance name and service name for Primary and Standby site remain same or are they different (assuming the d/bs are located on 2 different servers)?
I saw a configuration, where init parameters for these were same, but when I query v$instance, it gives different instance names. I am not sure how this could be?
What is the correct setup?
2. How does one setup TAF for Dataguard? Can someone upload sample files?
Thanks in advance
Prachi
Hi Prachi
1.Yes both should be different
like
on prod
SQL> sho parameter instance_name
NAME TYPE VALUE
instance_name string test
SQL> sho parameter service_names
NAME TYPE VALUE
service_names string test
on standby
SQL> sho parameter service
NAME TYPE VALUE
service_names string stby
SQL> sho parameter instance_name
NAME TYPE VALUE
instance_name string stby
2.TAF is used for RAC not for data guard.
Thanks and Regards
Kuljeet Pal Singh
Similar Messages
-
Query related to DataGuard Archicture...
Hi All,
I want to implement DataGuard Archicture in my setup, I'hv one query related to different operating system in my setup, I'hv two server one for primary and the other for standby Database with 10g DB R2. In one server having Linux os and the other own has Solaris, so DataGuard will work on different os or both server os should be same? And if I'hv 2 GB then will it be create any prob?
pl. suggest me.A requirement for standby is both databases must be on the same platform and on the same db version, this requirement applies even if you are on a logical or on a physical dataguard database.
You can verify the Step by Step instructions to create a standby database:
Step-byStep Instructions for Creating a Logical Standby Database
Step-by-Step Instructions for Creating a Physical Standby Database
~ Madrid -
Concept about Query Scn in Dataguard in Oracle 11g
What are the details concepts behind the’ query scn’ in Dataguard in Oracle 11g. I read the concept from Oracle Datagaurd 11g Handbook but it was not clear for me.
It's the highest SCN to which data is synchronised between the primary and secondary in a way that the secondary guaranteed read-consistent. It's therefore not possible to query an active standby for data modified after that SCN. At any given time, there might be transactions committed on the primary but not yet shipped or applied to the standby. You're not allowed to see those on the secondary. Not sure how much more detailed you want to get, really.
Edited by: Catfive Lander on Jan 15, 2013 4:15 AM -
Active Dataguard switchover puts new standby in real time query
Hi Gurus,
If using Active Dataguard ,after swicthover/failover using dg broker and observer does sthe new standby will be put in real time query mode(ADG) or manually have to open the db in read only mode.
Please let me know.
ThanksYes it does:
[uhesse]$ dgmgrl sys/oracle@prima
DGMGRL for Linux: Version 11.2.0.1.0 - Production
Copyright (c) 2000, 2009, Oracle. All rights reserved.
Welcome to DGMGRL, type "help" for information.
Connected.
DGMGRL> show configuration
Configuration - myconf
Protection Mode: MaxAvailability
Databases:
prima - Primary database
logst - Logical standby database
physt - Physical standby database
Fast-Start Failover: DISABLED
Configuration Status:
SUCCESS
DGMGRL> show database physt
Database - physt
Role: PHYSICAL STANDBY
Intended State: APPLY-ON
Transport Lag: 0 seconds
Apply Lag: 0 seconds
Real Time Query: ON
Instance(s):
physt
Database Status:
SUCCESS
DGMGRL> switchover to physt;
Performing switchover NOW, please wait...
New primary database "physt" is opening...
Operation requires shutdown of instance "prima" on database "prima"
Shutting down instance "prima"...
ORA-01109: database not open
Database dismounted.
ORACLE instance shut down.
Operation requires startup of instance "prima" on database "prima"
Starting instance "prima"...
ORACLE instance started.
Database mounted.
Database opened.
Switchover succeeded, new primary is "physt"
DGMGRL> show configuration
Configuration - myconf
Protection Mode: MaxAvailability
Databases:
physt - Primary database
prima - Physical standby database
logst - Logical standby database
Fast-Start Failover: DISABLED
Configuration Status:
SUCCESS
DGMGRL> show database prima
Database - prima
Role: PHYSICAL STANDBY
Intended State: APPLY-ON
Transport Lag: 0 seconds
Apply Lag: 0 seconds
Real Time Query: ON
Instance(s):
prima
Database Status:
SUCCESSKind regards
Uwe Hesse
http://uhesse.wordpress.com -
Hello there,
If I am using external Netapps storage and snapmirror to replicate data to my storage array at the DR site do i still need to use dataguard for log shipping?
I am a little confused where both fit. Are they basically both replication technologies, dataguard being at the database level, and netapps using storage level replication
Advice would be much appreciated
Cheers
CThanks Enrique and I guess that would be easier too... but...
I have spoken twice with them and no luck. They say that would be risky to DMZ, by opening direct communication between those servers (A and C) and bla bla... you know how huge those guys can be, so I think I'm not insisting them anymore... :)
Anyway, thanks for the response!
Charles. -
Log application query not showing correct results
Hi,
We are running Dataguard (DG) in our production environment. EBS 11.5.10.2 and DB 10.2.0.4.
Every morning we run the following query on both primary and standby to confirm that the logs are being transported and applied to the standby:
select sequence#,applied,to_char(first_time,'mm/dd/yy hh24:mi:ss') first from v$archived_log order by first_time;
Once the logs are transported and applied, a response of 'Yes' is returned for each log generated. We have noticed within the last week that when we run the query on primary, 'No' is being returned, but on standby, 'Yes' is returned. I have confirmed that standby is reflecting the correct results. I've tried restarting the DG service (alter database recover managed standby....) in an attempt to have primary 'refresh' itself but that didn't work.
Does anyone have any idea why primary keeps returning 'No' to the query, and how we can get it to reflect to correct results?
Thanks,
Lia.Hi Werner,
Thanks for your response. Given what you're saying I find that a little strange since prior to this, the query would return a value of 'YES' on the primary. Actually, to be exact, on the primary, each log would should up twice. One would show 'NO' and the other 'YES'- the second indicating transporting and shipping was successful.
This is how the results were before:
SEQUENCE APP FIRST
+154623 NO 04/07/09 08:03:22+
+154623 YES 04/07/09 08:03:22+
+154624 NO 04/07/09 08:05:27+
+154624 YES 04/07/09 08:05:27+
This is how the results are now:
SEQUENCE APP FIRST
+154754 NO 04/22/09 07:22:22+
+154754 NO 04/22/09 07:22:22+
+154755 NO 04/22/09 07:25:27+
+154755 NO 04/22/09 07:25:27+
I'm not doubting that what you're saying is correct, it just adds an element of confusion for me...
Lia. -
Hello All,
I have the below question concerning Oracle 11gR2 with Dataguard.
I have one primary database and one Logical standby database.
I have a question about the below scenario:
In case the primary database failed I will apply the below steps:
1. Failover to the logical standby database. Now it is reacting as a primary database.
2. I restored and recovered the failed primary database and I want to build it as a Logical standby database.
My question is, in that specific step when I restored and recovered my failed primary database, the restore and recovery process may take me two days for example, and the primary database is restored to a certain SCN, but the clients are connected to another database (the new primary) and they are modifying the data on the new primary database while i am recover my failed primary database, so when i convert my failed primary database to a Logical stand by database.
SQL Apply will automatically know from which SCN should start applying redo logs ?
These logs are applied from both archive logs of the new primary database and from the standby redo logs? since some redo logs may have been archived before overwriting.
And same question when i first create any logical standby database, i will create it from a backup copy of the primary database, so based on what the SQL apply will start applying the redo logs ?
how it can indicate that it should start applying redo logs from a certain point (or SCN)?
One more question:
During switch over: both primary and standby databases will be started up in restricted mode?
Hope my questions are clear.
Regards.
Edited by: NB on Oct 24, 2011 3:17 PM
Edited by: NB on Oct 24, 2011 3:18 PMthe result of your query is below :
Know that i used: WHERE DEST_ID = 3
is that because i defined my parameters as below?
on primary:
log_archive_dest_1 = "LOCATION=C:\app\oracle\oradata\windb\LOG_ARCHIVE_DEST_1 VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=windb"
log_archive_dest_2 = "LOCATION=USE_DB_RECOVERY_FILE_DEST VALID_FOR=(STANDBY_LOGFILE,STANDBY_ROLE)"
log_archive_dest_3 = "SERVICE=dgwindb ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=dgwindb"on standby:
log_archive_dest_1 = "LOCATION=C:\app\oracle\oradata\dgwindb\LOG_ARCHIVE_DEST_1 VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=dgwindb"
log_archive_dest_2 = "LOCATION=USE_DB_RECOVERY_FILE_DEST VALID_FOR=(STANDBY_LOGFILE,STANDBY_ROLE)"
log_archive_dest_3 = "SERVICE=windb ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=windb"
STAND_BY, SEQUENCE#, APPLIED, COMPLETION_TIME
dgwindb 130 YES 10/26/2011 5:47:28 PM
dgwindb 131 YES 10/26/2011 5:47:35 PM
dgwindb 132 YES 10/27/2011 1:11:51 PM
dgwindb 133 YES 10/27/2011 1:11:52 PM
dgwindb 134 YES 10/27/2011 1:11:52 PM
dgwindb 135 YES 10/27/2011 1:11:52 PM
dgwindb 136 YES 10/27/2011 1:11:52 PM
dgwindb 137 YES 10/27/2011 1:11:52 PM
dgwindb 138 YES 10/26/2011 6:28:09 PM
dgwindb 139 YES 10/26/2011 6:35:11 PM
DGWINDB 140 YES 10/27/2011 1:12:48 PM
DGWINDB 141 YES 10/27/2011 1:12:49 PM
DGWINDB 142 YES 10/27/2011 1:12:49 PM
DGWINDB 143 YES 10/27/2011 1:12:49 PM
dgwindb 144 YES 10/26/2011 7:03:21 PM
dgwindb 145 YES 10/26/2011 7:09:22 PM
dgwindb 146 YES 10/26/2011 7:14:24 PM
dgwindb 147 YES 10/27/2011 1:12:57 PM
dgwindb 148 YES 10/27/2011 1:12:57 PM
dgwindb 149 YES 10/26/2011 7:32:29 PM
dgwindb 150 YES 10/26/2011 7:39:31 PM
dgwindb 151 YES 10/26/2011 7:45:34 PM
dgwindb 152 YES 10/27/2011 1:13:07 PM
dgwindb 153 YES 10/27/2011 1:13:07 PM
dgwindb 154 YES 10/26/2011 8:03:39 PM
dgwindb 155 YES 10/26/2011 8:10:41 PM
dgwindb 156 YES 10/27/2011 1:13:23 PM
dgwindb 157 YES 10/27/2011 1:13:23 PM
dgwindb 158 YES 10/27/2011 1:13:23 PM
dgwindb 159 YES 10/27/2011 1:13:24 PM
dgwindb 160 YES 10/27/2011 1:13:23 PM
dgwindb 161 YES 10/27/2011 1:13:24 PM
dgwindb 162 YES 10/27/2011 1:13:23 PM
dgwindb 163 YES 10/27/2011 1:13:23 PM
dgwindb 164 YES 10/26/2011 8:57:55 PM
dgwindb 165 YES 10/26/2011 9:04:10 PM
dgwindb 166 YES 10/27/2011 1:13:35 PM
dgwindb 167 YES 10/27/2011 1:13:35 PM
dgwindb 168 YES 10/26/2011 9:21:12 PM
dgwindb 169 YES 10/26/2011 9:28:16 PM
dgwindb 170 YES 10/27/2011 1:13:43 PM
dgwindb 171 YES 10/27/2011 1:13:43 PM
dgwindb 172 YES 10/27/2011 1:13:43 PM
dgwindb 173 YES 10/27/2011 12:36:29 PM
dgwindb 174 YES 10/27/2011 12:41:41 PM
dgwindb 175 YES 10/27/2011 1:13:52 PM
dgwindb 176 YES 10/27/2011 1:13:52 PM
dgwindb 177 YES 10/27/2011 1:13:52 PM
dgwindb 178 YES 10/27/2011 1:13:52 PM
dgwindb 179 YES 10/27/2011 1:11:44 PM
dgwindb 180 YES 10/27/2011 1:21:19 PM -
Dataguard in oracle standard edition ?
I am using Oracle 10.2.0.4 standard edition database.
how to check / query can i use dataguard feature in my oracle database. Is there any docs having to expalin more detail?
Rgds,Data Guard is Enterprise Edition only. This link is licensing info for your version.
Database Licensing Information 10g Release 2: http://download.oracle.com/docs/cd/B19306_01/license.102/b14199.pdf -
My Active dataguard is not applying archives.
Dears,
Following is my setup
=====================
Primary:
prod on RAC with 2 nodes
Database : Oracle 11.2.0.3
OS OEL 5.7
storage : ASM
+DATADG
+FLASHDG
Standby:
sync on single node
Database : Oracle 11.2.0.3
storage : ASM
+DATADG
+FLASHDG
I've configured Active dataguard successfully and was able to apply archivelogs successfully instantly.
Archive log locations are +FLASHDG/prod/ARCHIVELOG/ AND /u02/arch --- on primary
Archive log locations are +FLASHDG/stby/ARCHIVELOG/ AND /u02/arch --- on standby
On Standby
===========
SQL> select 'Using Active Data Guard' ADG from v$managed_standby m,v$database d where m.process like 'MRP%' ;
ADG
Using Active Data Guard
SQL> select open_mode,database_role,PROTECTION_MODE,PROTECTION_LEVEL from v$database;
OPEN_MODE DATABASE_ROLE PROTECTION_MODE PROTECTION_LEVEL
READ ONLY WITH APPLY PHYSICAL STANDBY MAXIMUM PERFORMANCE MAXIMUM PERFORMANCE
SQL>
Upto now everything is ok, means same data is sync on primary and standby. As my archive location was getting full, i've used this SQL query to clean them
SELECT 'alter diskgroup '||dg.name||' drop file
''+'||dg.name||''||SYS_CONNECT_BY_PATH(al.name,'/')||''';'
FROM v$asm_alias al, v$asm_file fi, v$asm_diskgroup dg
WHERE al.file_number = fi.file_number(+)
AND al.group_number = dg.group_number
AND fi.type = 'ARCHIVELOG'
START WITH alias_index = 0
CONNECT BY PRIOR al.reference_index = al.parent_index;
SELECT 'alter diskgroup '||dg.name||' drop file
''+'||dg.name||''||SYS_CONNECT_BY_PATH(al.name,'/')||''';'
FROM v$asm_alias al, v$asm_file fi, v$asm_diskgroup dg
WHERE al.file_number = fi.file_number(+)
AND al.group_number = dg.group_number
AND fi.type = 'BACKUPSET'
START WITH alias_index = 0
CONNECT BY PRIOR al.reference_index = al.parent_index;
In order to delete ARCHIVE logs which are stored in ASM FLASHDG, which will have a type of "ARCHIVELOG" and "BACKUPSET" i've used this above two queries.
After performing this steps , my Active dataguard is not applying archives.
On the primary server, check the latest archived redo log
SELECT sequence#, first_time, next_time
FROM v$archived_log
ORDER BY sequence#;
2809 16-APR-13 16-APR-13
2809 16-APR-13 16-APR-13
2809 16-APR-13 16-APR-13
2810 16-APR-13 16-APR-13
2810 16-APR-13 16-APR-13
2810 16-APR-13 16-APR-13
2811 16-APR-13 16-APR-13
2811 16-APR-13 16-APR-13
2811 16-APR-13 16-APR-13
2812 16-APR-13 16-APR-13
2812 16-APR-13 16-APR-13
2812 16-APR-13 16-APR-13
2813 16-APR-13 16-APR-13
2813 16-APR-13 16-APR-13
2814 16-APR-13 16-APR-13
2814 16-APR-13 16-APR-13
2815 16-APR-13 16-APR-13
2815 16-APR-13 16-APR-13
2816 16-APR-13 16-APR-13
2816 16-APR-13 16-APR-13
2817 16-APR-13 16-APR-13
2817 16-APR-13 16-APR-13
2818 16-APR-13 16-APR-13
2818 16-APR-13 16-APR-13
2819 16-APR-13 16-APR-13
2819 16-APR-13 16-APR-13
2820 16-APR-13 16-APR-13
2820 16-APR-13 16-APR-13
2821 16-APR-13 16-APR-13
2821 16-APR-13 16-APR-13
2822 16-APR-13 16-APR-13
2822 16-APR-13 16-APR-13
2823 16-APR-13 16-APR-13
2823 16-APR-13 16-APR-13
2824 16-APR-13 16-APR-13
2824 16-APR-13 16-APR-13
2825 16-APR-13 16-APR-13
2825 16-APR-13 16-APR-13
2826 16-APR-13 16-APR-13
2826 16-APR-13 16-APR-13
2827 16-APR-13 16-APR-13
2827 16-APR-13 16-APR-13
2828 16-APR-13 16-APR-13
2828 16-APR-13 16-APR-13
2829 16-APR-13 16-APR-13
2829 16-APR-13 16-APR-13
2830 16-APR-13 16-APR-13
2830 16-APR-13 16-APR-13
2831 16-APR-13 16-APR-13
2831 16-APR-13 16-APR-13
2832 16-APR-13 16-APR-13
2832 16-APR-13 16-APR-13
2833 16-APR-13 16-APR-13
2833 16-APR-13 16-APR-13
2834 16-APR-13 16-APR-13
2834 16-APR-13 16-APR-13
2835 16-APR-13 16-APR-13
2835 16-APR-13 16-APR-13
2836 16-APR-13 16-APR-13
2836 16-APR-13 16-APR-13
2837 16-APR-13 16-APR-13
2837 16-APR-13 16-APR-13
2838 16-APR-13 16-APR-13
2838 16-APR-13 16-APR-13
2839 16-APR-13 16-APR-13
2839 16-APR-13 16-APR-13
2840 16-APR-13 16-APR-13
2840 16-APR-13 16-APR-13
2841 16-APR-13 16-APR-13
2841 16-APR-13 16-APR-13
2842 16-APR-13 16-APR-13
2842 16-APR-13 16-APR-13
2843 16-APR-13 16-APR-13
2843 16-APR-13 16-APR-13
2844 16-APR-13 16-APR-13
2844 16-APR-13 16-APR-13
2845 16-APR-13 16-APR-13
2845 16-APR-13 16-APR-13
2846 16-APR-13 16-APR-13
2846 16-APR-13 16-APR-13
Check the new archived redo log has arrived at the standby server and been applied.
SELECT sequence#, first_time, next_time, applied
FROM v$archived_log
ORDER BY sequence#;
2801 15-APR-13 15-APR-13 YES
2801 15-APR-13 15-APR-13 YES
2802 15-APR-13 15-APR-13 YES
2802 15-APR-13 15-APR-13 YES
2803 15-APR-13 15-APR-13 YES
2803 15-APR-13 15-APR-13 YES
2804 15-APR-13 15-APR-13 YES
2804 15-APR-13 15-APR-13 YES
2805 15-APR-13 15-APR-13 YES
2805 15-APR-13 15-APR-13 YES
2806 15-APR-13 15-APR-13 YES
2806 15-APR-13 15-APR-13 YES
2807 15-APR-13 15-APR-13 YES
2807 15-APR-13 15-APR-13 YES
2808 15-APR-13 16-APR-13 YES
2808 15-APR-13 16-APR-13 YES
2809 16-APR-13 16-APR-13 YES
2809 16-APR-13 16-APR-13 YES
2810 16-APR-13 16-APR-13 YES
2810 16-APR-13 16-APR-13 YES
2811 16-APR-13 16-APR-13 YES
2811 16-APR-13 16-APR-13 YES
2812 16-APR-13 16-APR-13 IN-MEMORY
2812 16-APR-13 16-APR-13 YES
So could anyone help me to resolve this issue. Anticipating your response at the earliest.
Regards,
VIKHAR
Edited by: VIKHARAHMED on Apr 16, 2013 9:38 AMHere is the alert log file
Media Recovery Log +FLASHDG/stby/archivelog/2013_04_16/thread_2_seq_1476.1987.812900733
Tue Apr 16 18:56:42 2013
Primary database is in MAXIMUM PERFORMANCE mode
RFS[1]: Assigned to RFS process 16803
RFS[1]: Selected log 12 for thread 2 sequence 1485 dbid 220323208 branch 808484882
Tue Apr 16 18:56:42 2013
RFS[2]: Assigned to RFS process 16807
RFS[2]: Opened log for thread 2 sequence 1484 dbid 220323208 branch 808484882
Archived Log entry 6324 added for thread 2 sequence 1484 rlc 808484882 ID 0xd21a288 dest 10:
Tue Apr 16 19:09:02 2013
RFS[1]: Selected log 11 for thread 2 sequence 1486 dbid 220323208 branch 808484882
Tue Apr 16 19:09:02 2013
Archived Log entry 6325 added for thread 2 sequence 1485 ID 0xd21a288 dest 1:
Archived Log entry 6326 added for thread 2 sequence 1485 ID 0xd21a288 dest 2:
Tue Apr 16 19:12:23 2013
RFS[1]: Selected log 12 for thread 2 sequence 1487 dbid 220323208 branch 808484882
Tue Apr 16 19:12:23 2013
Archived Log entry 6327 added for thread 2 sequence 1486 ID 0xd21a288 dest 1:
Archived Log entry 6328 added for thread 2 sequence 1486 ID 0xd21a288 dest 2:
Tue Apr 16 19:14:41 2013
"alert_stby.log" 845L, 33990C 782,1 94%
Tue Apr 16 19:17:27 2013
Archived Log entry 6331 added for thread 2 sequence 1488 ID 0xd21a288 dest 1:
Archived Log entry 6332 added for thread 2 sequence 1488 ID 0xd21a288 dest 2:
Tue Apr 16 19:25:51 2013
RFS[1]: Selected log 11 for thread 2 sequence 1490 dbid 220323208 branch 808484882
Tue Apr 16 19:25:51 2013
Archived Log entry 6333 added for thread 2 sequence 1489 ID 0xd21a288 dest 1:
Archived Log entry 6334 added for thread 2 sequence 1489 ID 0xd21a288 dest 2:
Tue Apr 16 19:51:02 2013
RFS[1]: Selected log 12 for thread 2 sequence 1491 dbid 220323208 branch 808484882
Tue Apr 16 19:51:02 2013
Archived Log entry 6335 added for thread 2 sequence 1490 ID 0xd21a288 dest 1:
Archived Log entry 6336 added for thread 2 sequence 1490 ID 0xd21a288 dest 2:
Tue Apr 16 20:37:12 2013
RFS[1]: Selected log 11 for thread 2 sequence 1492 dbid 220323208 branch 808484882
Tue Apr 16 20:37:12 2013
Archived Log entry 6337 added for thread 2 sequence 1491 ID 0xd21a288 dest 1:
Archived Log entry 6338 added for thread 2 sequence 1491 ID 0xd21a288 dest 2:
Tue Apr 16 21:08:23 2013
RFS[1]: Selected log 12 for thread 2 sequence 1493 dbid 220323208 branch 808484882
Tue Apr 16 21:08:23 2013
Archived Log entry 6339 added for thread 2 sequence 1492 ID 0xd21a288 dest 1:
Archived Log entry 6340 added for thread 2 sequence 1492 ID 0xd21a288 dest 2:
Tue Apr 16 22:16:06 2013
RFS[1]: Selected log 11 for thread 2 sequence 1494 dbid 220323208 branch 808484882
Tue Apr 16 22:16:06 2013
Archived Log entry 6341 added for thread 2 sequence 1493 ID 0xd21a288 dest 1:
Archived Log entry 6342 added for thread 2 sequence 1493 ID 0xd21a288 dest 2:
Tue Apr 16 22:31:46 2013
RFS[1]: Selected log 12 for thread 2 sequence 1495 dbid 220323208 branch 808484882
Tue Apr 16 22:31:46 2013
Archived Log entry 6343 added for thread 2 sequence 1494 ID 0xd21a288 dest 1:
Archived Log entry 6344 added for thread 2 sequence 1494 ID 0xd21a288 dest 2:
Wed Apr 17 09:31:59 2013
RFS[1]: Selected log 11 for thread 2 sequence 1496 dbid 220323208 branch 808484882
Wed Apr 17 09:32:00 2013
Archived Log entry 6345 added for thread 2 sequence 1495 ID 0xd21a288 dest 1:
Archived Log entry 6346 added for thread 2 sequence 1495 ID 0xd21a288 dest 2: -
Hi Experts,
I have one query, I have a primary database and physical standby database running in a unix box. Everytime there is a sync problem with the primary and standby, i have to copy the logfile and then register one by one it in the standby database
alter database register logfile
'..../arch_1001.arc';
Is there any other solution do we have for this kind of issues.
Thanks
ShaanAs I already explained, the very purpose of the FAL process is to resolve gaps.
As far as I am concerned this is a quite unequivocal message.
You should have drawn the following conclusion 'This means my FAL process isn't working, I need to investigate why it isn't working' instead of to continue symptom fighting.
You have a problem.
You need to find it's cause.
You don't need symptom fighting.
You don't need workarounds different from the symptom figthing your already do.
You also need to fix the network problem.
Dataguard isn't the problem, your configuration is.
Sybrand Bakker
Senior Oracle DBA -
DataGuard FAL Client not re-transfering log
Hey, in my dataguard config the standby system detects a log gap.
The log on the primary site was not marked for the standby location - thats a known bug. OK.
But anyway, when the standby system detects a log gap, why is it not requesting the missing logfile from the primary site. Its still available on the primary site in the FRA.
#Standbysite - Detecting log-gap
*** 2011-05-30 09:22:57.602 64207 kcrr.c
Media Recovery Waiting for thread 2 sequence 164952
*** 2011-05-30 09:22:57.602 64207 kcrr.c
Fetching gap sequence in thread 2, gap sequence 164952-164952
Redo shipping client performing standby login
#Primiary Site - check for missing logfile
SQL> SELECT name FROM v$archived_log where sequence# like'164952';
NAME
(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=stdynode3-vip.local)(PORT
=1521)))(CONNECT_DATA=(SERVICE_NAME=TEST_XPT.local)(INSTANCE_NAME=TEST3)(SERVER
=dedicated)))
+FLASH/testp/1_164952_692118044.dbf
+FLASH/testp/2_164952_692118044.dbf
SQL>Christian wrote:
Hey, in my dataguard config the standby system detects a log gap.
The log on the primary site was not marked for the standby location - thats a known bug. OK.
But anyway, when the standby system detects a log gap, why is it not requesting the missing logfile from the primary site. Its still available on the primary site in the FRA.
#Standbysite - Detecting log-gap
*** 2011-05-30 09:22:57.602 64207 kcrr.c
Media Recovery Waiting for thread 2 sequence 164952
*** 2011-05-30 09:22:57.602 64207 kcrr.c
Fetching gap sequence in thread 2, gap sequence 164952-164952
Redo shipping client performing standby login
#Primiary Site - check for missing logfile
SQL> SELECT name FROM v$archived_log where sequence# like'164952';
NAME
(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=stdynode3-vip.local)(PORT
=1521)))(CONNECT_DATA=(SERVICE_NAME=TEST_XPT.local)(INSTANCE_NAME=TEST3)(SERVER
=dedicated)))
+FLASH/testp/1_164952_692118044.dbf
+FLASH/testp/2_164952_692118044.dbf
SQL>and also make sure is it priamary is two node rac?
Post the output of below query. from standby
select name,applied from v$archived_log where sequence#=164952 and thread#=2;and from primary:
select name from v$archived_log where sequence#=164952 and thread#=2; -
Enabling the Active Dataguard and Real Time Apply
11.2.0.2 on AIX
I gather that , to enable Active Dataguard, you need to execute
STARTUP ; ----not startup mount
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT;The above commands will enable both Active Dataguard (Real Time QUERY) and Real Time Apply. Right?
To enable just 'Real Time Apply' , I need to
startup mount
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT;Am I right ?
Question on 'WITH SESSION SHUTDOWN' clause
While googling I've come across the following variant with an additonal 'WITH SESSION SHUTDOWN' clause
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE WITH SESSION SHUTDOWN;What difference does this clause bring ?
Is this claused used to enable Active Dataguard feature or 'Real Time Apply' or both ?I gather that , to enable Active Dataguard, you need to execute
STARTUP ; ----not startup mount
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT;
The above commands will enable both Active Dataguard (Real Time QUERY) and Real Time Apply. Right? Yes, It will be in both recovery / realtime + Read only mode, Also you can use
To enable just 'Real Time Apply' , I need to
startup mount
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT;Am I right ?Yes. It will be in just recovery/real time mode.
Question on 'WITH SESSION SHUTDOWN' clause
While googling I've come across the following variant with an additonal 'WITH SESSION SHUTDOWN' clause
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE WITH SESSION SHUTDOWN;What difference does this clause bring ?
Is this claused used to enable Active Dataguard feature or 'Real Time Apply' or both ?It has multiple options based on startup type
For this example check link of Julian Dyke.
http://juliandyke.wordpress.com/2010/10/14/oracle-11gr2-active-data-guard/ -
When queried v$dataguard_stats results no rows selected at standby db?
Hi Chaps,
I have oracle database 10g 10.2.0.4.0 on AIX version 5.3
I am curious about standby database that whether it is in sync with the primary database or not?
when I queried at standby to know dataguard stats the result was 'no rows selected'
SELECT * FROM V$DATAGUARD_STATS ;
then I tried to know the role of the database on standby like this
SYS@prod>select name,database_role from v$database;
then the result was as follows:
NAME DATABASE_ROLE
PROD PRIMARY
is this mean that it is still a primary database and not replicating the changes from primary DB?
please enlight your thoughts to confirm a standby db is doing right job or not?
Thanks
QAHi, here is the init parameters from standby db
SYS@sisprod>show parameter;
NAME TYPE VALUE
O7_DICTIONARY_ACCESSIBILITY boolean FALSE
active_instance_count integer
aq_tm_processes integer 0
archive_lag_target integer 0
asm_diskgroups string
asm_diskstring string
asm_power_limit integer 1
audit_file_dest string /u01/app/oracle/product/10.2/r
dbms/audit
audit_sys_operations boolean FALSE
audit_syslog_level string
audit_trail string DB
background_core_dump string partial
background_dump_dest string /u01/app/oracle/product/10.2/a
dmin/sisprod/bdump
backup_tape_io_slaves boolean FALSE
bitmap_merge_area_size integer 1048576
blank_trimming boolean FALSE
buffer_pool_keep string
buffer_pool_recycle string
circuits integer
cluster_database boolean FALSE
cluster_database_instances integer 1
cluster_interconnects string
commit_point_strength integer 1
commit_write string
compatible string 10.2.0.1.0
control_file_record_keep_time integer 21
control_files string /u01/oradata/sisprod/control01
.ctl, /u02/oradata/sisprod/con
trol02.ctl, /u05/oradata/sispr
od/control03.ctl
core_dump_dest string /u01/app/oracle/product/10.2/a
dmin/sisprod/cdump
cpu_count integer 2
create_bitmap_area_size integer 8388608
create_stored_outlines string
cursor_sharing string EXACT
cursor_space_for_time boolean FALSE
db_16k_cache_size big integer 0
db_2k_cache_size big integer 0
db_32k_cache_size big integer 0
db_4k_cache_size big integer 0
db_8k_cache_size big integer 0
db_block_buffers integer 0
db_block_checking string TRUE
db_block_checksum string TRUE
db_block_size integer 8192
db_cache_advice string ON
db_cache_size big integer 32M
db_create_file_dest string
db_create_online_log_dest_1 string
db_create_online_log_dest_2 string
db_create_online_log_dest_3 string
db_create_online_log_dest_4 string
db_create_online_log_dest_5 string
db_domain string satelliteinfo.co.uk
db_file_multiblock_read_count integer 16
db_file_name_convert string
db_files integer 200
db_flashback_retention_target integer 1440
db_keep_cache_size big integer 0
db_name string sisprod
db_recovery_file_dest string
db_recovery_file_dest_size big integer 0
db_recycle_cache_size big integer 0
db_unique_name string sisprod
db_writer_processes integer 1
dbwr_io_slaves integer 0
ddl_wait_for_locks boolean FALSE
dg_broker_config_file1 string /u01/app/oracle/product/10.2/d
bs/dr1sisprod.dat
dg_broker_config_file2 string /u01/app/oracle/product/10.2/d
bs/dr2sisprod.dat
dg_broker_start boolean TRUE
disk_asynch_io boolean TRUE
dispatchers string
distributed_lock_timeout integer 60
dml_locks integer 748
drs_start boolean FALSE
event string
fal_client string
fal_server string
fast_start_io_target integer 0
fast_start_mttr_target integer 300
fast_start_parallel_rollback string LOW
file_mapping boolean FALSE
fileio_network_adapters string
filesystemio_options string asynch
fixed_date string
gc_files_to_locks string
gcs_server_processes integer 0
global_context_pool_size string
global_names boolean FALSE
hash_area_size integer 1048576
hi_shared_memory_address integer 0
hs_autoregister boolean TRUE
ifile file
instance_groups string
instance_name string sisprod
instance_number integer 0
instance_type string RDBMS
java_max_sessionspace_size integer 0
java_pool_size big integer 160M
java_soft_sessionspace_limit integer 0
job_queue_processes integer 15
large_pool_size big integer 32M
ldap_directory_access string NONE
license_max_sessions integer 0
license_max_users integer 0
license_sessions_warning integer 0
local_listener string
lock_name_space string
lock_sga boolean FALSE
log_archive_config string
log_archive_dest string
log_archive_dest_1 string LOCATION=/u02/oradata/sisprod/
archive
log_archive_dest_10 string
log_archive_dest_2 string SERVICE=SISPROD_STDBY LGWR ASY
NC AFFIRM NET_TIMEOUT=60 VALID
FOR=(ONLINELOGFILES,PRIMARY_
ROLE) DB_UNIQUE_NAME=SISPROD_S
TDBY
log_archive_dest_3 string
log_archive_dest_4 string
log_archive_dest_5 string
log_archive_dest_6 string
log_archive_dest_7 string
log_archive_dest_8 string
log_archive_dest_9 string
log_archive_dest_state_1 string enable
log_archive_dest_state_10 string enable
log_archive_dest_state_2 string ENABLE
log_archive_dest_state_3 string enable
log_archive_dest_state_4 string enable
log_archive_dest_state_5 string enable
log_archive_dest_state_6 string enable
log_archive_dest_state_7 string enable
log_archive_dest_state_8 string enable
log_archive_dest_state_9 string enable
log_archive_duplex_dest string
log_archive_format string %t_%s_%r.dbf
log_archive_local_first boolean TRUE
log_archive_max_processes integer 2
log_archive_min_succeed_dest integer 1
log_archive_start boolean FALSE
log_archive_trace integer 0
log_buffer integer 14246912
log_checkpoint_interval integer 0
log_checkpoint_timeout integer 1800
log_checkpoints_to_alert boolean FALSE
log_file_name_convert string
logmnr_max_persistent_sessions integer 1
max_commit_propagation_delay integer 0
max_dispatchers integer
max_dump_file_size string UNLIMITED
max_enabled_roles integer 150
max_shared_servers integer
nls_calendar string
nls_comp string
nls_currency string #
nls_date_format string DD/MM/YYYY
nls_date_language string
nls_dual_currency string
nls_iso_currency string UNITED KINGDOM
nls_language string ENGLISH
nls_length_semantics string BYTE
nls_nchar_conv_excp string FALSE
nls_numeric_characters string
nls_sort string
nls_territory string UNITED KINGDOM
nls_time_format string
nls_time_tz_format string
nls_timestamp_format string
nls_timestamp_tz_format string
object_cache_max_size_percent integer 10
object_cache_optimal_size integer 102400
olap_page_pool_size big integer 0
open_cursors integer 1500
open_links integer 4
open_links_per_instance integer 4
optimizer_dynamic_sampling integer 2
optimizer_features_enable string 10.2.0.4
optimizer_index_caching integer 0
optimizer_index_cost_adj integer 100
optimizer_mode string ALL_ROWS
optimizer_secure_view_merging boolean TRUE
os_authent_prefix string ops$
os_roles boolean FALSE
parallel_adaptive_multi_user boolean TRUE
parallel_automatic_tuning boolean FALSE
parallel_execution_message_size integer 2152
parallel_instance_group string
parallel_max_servers integer 20
parallel_min_percent integer 0
parallel_min_servers integer 0
parallel_server boolean FALSE
parallel_server_instances integer 1
parallel_threads_per_cpu integer 2
pga_aggregate_target big integer 221459251
plsql_ccflags string
plsql_code_type string INTERPRETED
plsql_compiler_flags string INTERPRETED, NON_DEBUG
plsql_debug boolean FALSE
plsql_native_library_dir string
plsql_native_library_subdir_count integer 0
plsql_optimize_level integer 2
plsql_v2_compatibility boolean FALSE
plsql_warnings string DISABLE:ALL
pre_11g_enable_capture boolean FALSE
pre_page_sga boolean FALSE
processes integer 150
query_rewrite_enabled string FALSE
query_rewrite_integrity string enforced
rdbms_server_dn string
read_only_open_delayed boolean FALSE
recovery_parallelism integer 0
recyclebin string on
remote_archive_enable string true
remote_dependencies_mode string TIMESTAMP
remote_listener string
remote_login_passwordfile string EXCLUSIVE
remote_os_authent boolean FALSE
remote_os_roles boolean FALSE
replication_dependency_tracking boolean TRUE
resource_limit boolean FALSE
resource_manager_plan string
resumable_timeout integer 0
rollback_segments string
serial_reuse string disable
service_names string sisprod.satelliteinfo.co.uk
session_cached_cursors integer 20
session_max_open_files integer 20
sessions integer 170
sga_max_size big integer 1056M
sga_target big integer 1056M
shadow_core_dump string partial
shared_memory_address integer 0
shared_pool_reserved_size big integer 10905190
shared_pool_size big integer 208M
shared_server_sessions integer
shared_servers integer 0
skip_unusable_indexes boolean TRUE
smtp_out_server string
sort_area_retained_size integer 0
sort_area_size integer 524288
spfile string /u01/app/oracle/product/10.2/d
bs/spfilesisprod.ora
sql92_security boolean FALSE
sql_trace boolean FALSE
sql_version string NATIVE
sqltune_category string DEFAULT
standby_archive_dest string ?/dbs/arch
standby_file_management string AUTO
star_transformation_enabled string FALSE
statistics_level string TYPICAL
streams_pool_size big integer 48M
tape_asynch_io boolean TRUE
thread integer 0
timed_os_statistics integer 0
timed_statistics boolean TRUE
trace_enabled boolean TRUE
tracefile_identifier string
transactions integer 187
transactions_per_rollback_segment integer 5
undo_management string AUTO
undo_retention integer 10800
undo_tablespace string UNDOTBS1
use_indirect_data_buffers boolean FALSE
use_sigio boolean TRUE
user_dump_dest string /u01/app/oracle/product/10.2/a
dmin/sisprod/udump
utl_file_dir string /u01/app/oracle/product/10.2/a
dmin/sisprod/udump
workarea_size_policy string AUTO
Thanks
QA -
Hi All,
Can any one provide me a link or tell me, which is the underlying technology on which the active dataguard works?
I mean the details functioning of how active dataguard lets us put the database in read only mode and also keeps the standby database in sync with the Prod.
I know this is a kind of doc question but I did look for it in the docs but I couldnt get what I was looking for.
Regards,
SphinxHi Sphinx,
In 11g the standby database is also called active standby database, coz you can read the database(ie, you can query using select statement) and at same time log shipping also will occur. Flashback database feature is must and should be enabled at both primary and standby databases, So that you can open the standby database in read/write mode which is called snapshot standby database. The reason is , when you open the standby database in read/write mode, it will create a snapshot(restore point) at that state using the flashback what you have enabled. when the snapshot is again converted to active standby (read/log apply), the standby database will be restored using the restore point what its create at the time snapshot standby. So both Active standby and flashback database feature tightly coupled to give us a great option to work with.
Hope this helps.
Regards,
Pradeep. V -
Hi,
in dataguard using oracle 10g r2
when i query on primary side:
select max(sequence#) from v$log where archived='YES';MAX(SEQUENCE#)
19
standby side:
select max(sequence#) from v$log where archived='YES';MAX(SEQUENCE#)
20
why it is showing different log sequences, it has to show similar sequences right?venky wrote:
Hi,
in dataguard using oracle 10g r2
when i query on primary side:
select max(sequence#) from v$log where archived='YES';MAX(SEQUENCE#)
19
standby side:
select max(sequence#) from v$log where archived='YES';MAX(SEQUENCE#)
20
why it is showing different log sequences, it has to show similar sequences right?Do you realize there is an entire forum just for Data Guard: Data Guard
Maybe you are looking for
-
Year end closing for fixed asset
Hi, Currently we run the process AJAB to close the year for fixed assets at the end of the year and can close two years back. So in September 07 I would have closed 2006, then run AJRW to open 2008. So it is my understanding that we can only ha
-
Magic mouse does not swipe correctly
Upgraded to Mavericks. Magic Mouse only swipes between open screens instead of within pages in a document, returning to previous page on web site, etc.
-
How can I install Screensaver on desktop page
How can I install screen saver on my desktop page? This question was solved. View Solution.
-
Sequence doesn't play the sound.. help?
Hey.. I've just got FCE4 and I've encountered some problems. I've managed to overcome the "Not Rendered" issue, but now while I play the imported video already on the timeline, on the canvas, no sound is played. Not from the .dv files, and not from t
-
Can R12.1.3 and R11.5.10 be installed on the same server?
Hello there, We are currently running Oracle eBiz R11.5.10, and would like to install the latest version R12.1.3 for testing purposes. Can R12.1.3 be installed on the same server (for both database and application tiers) as for R11.5.10? Any pitfalls