DataGuard, Checking primary & standby DBs

What are the things we should check to confirm that standby Db is upto date.

Better Thing Go Through Oracle Docs.
>>>http://www.oracle.com/technology/documentation/index.html
Note.:According ur Oracle DB Version.
M.S.Taj.

Similar Messages

Dataguard Config - Primary ASM - Standby Non ASM

Hi,
I'm having an issue with a new configuration of dataguard.
Primary Standby
OS Win2008 R2 Win2008 R2
DB 11.2.0.2 11.2.0.2
Storage ASM NTFS
I have created standby logs on the standby and on the primary. I have configured real time apply(maximum availibility) but when I look in the rfs.trc files on standby I receive the following error:
primary database is in maximum protection or maximum availability mode and the standby database does not contain and viable standby redo logs.
I dropped all standby logs on the standby and recreated them, the real time apply then worked until all the standby redo logs filled. Now I'm receiving the error again.
For some reason the standby logs are not clearing and this is the issue. I have looked at metalink notes Error At Standby Database Ora-16086: Standby Database Does Not Contain Available Standby Log Files [ID 1155773.1] and Primary Database Stops with ORA-16098 When Standby Put in Protected Mode [ID 187235.1].
I think the issue may be that the primary databases online redo logs are on asm disks and the standby are on ntfs disks. I can't find any clear documentation that says that this config is unsupported. Any ideas would be greatly appreciated.
Keith
SQL> select group#, thread#, sequence#, used, archived, status, first_change#, n
ext_change#, last_change# from v$standby_log;
GROUP# THREAD# SEQUENCE# USED ARC STATUS FIRST_CHANGE#
NEXT_CHANGE# LAST_CHANGE#
5 2 255 30208 NO ACTIVE 196829409
196829442 196829442
6 2 254 3308032 NO ACTIVE 196826945
196829409 196829409
7 2 256 5200896 NO ACTIVE 196829442
196838727 196838727
8 2 257 6098944 NO ACTIVE 196838727
196849666 196849666
9 2 258 9165312 NO ACTIVE 196849666
196862607 196862607
SQL> SELECT GROUP#, BYTES FROM V$LOG;
GROUP# BYTES
1 52428800
2 52428800
3 52428800
4 52428800
SQL> SELECT GROUP#, BYTES FROM V$STANDBY_LOG;
GROUP# BYTES
5 52428800
6 52428800
7 52428800
8 52428800
9 52428800
Primary Errors:
TO_CHAR(TIMESTAMP,'YYYY-MON-DDHH24:MI:SS')||''||MESSAGE
2011-DEC-08 12:00:12 LGWR: Destination LOG_ARCHIVE_DEST_2 network reconnect ab
andoned
2011-DEC-08 12:00:12 Error 16086 for archive log file 3 to 'PBONDSDR'
2011-DEC-08 12:00:13 LGWR: Failed to archive log 3 thread 2 sequence 503 (1608
6)
2011-DEC-08 12:00:13 ARC3: Beginning to archive thread 2 sequence 502 (1971278
31-197131866)
TO_CHAR(TIMESTAMP,'YYYY-MON-DDHH24:MI:SS')||''||MESSAGE
2011-DEC-08 12:00:13 ARC3: Completed archiving thread 2 sequence 502 (19712783
1-197131866)
standby Errors:
2011-DEC-08 11:54:09 Media Recovery Waiting for thread 2 sequence 501
2011-DEC-08 11:54:09 Primary database is in MAXIMUM AVAILABILITY mode
2011-DEC-08 11:54:09 Standby controlfile consistent with primary
2011-DEC-08 11:54:10 Standby controlfile consistent with primary
2011-DEC-08 11:54:10 RFS[46]: Assigned to RFS process 3956
2011-DEC-08 11:54:10 RFS[46]: No standby redo logfiles available for thread 2
2011-DEC-08 11:54:10 RFS[46]: No standby redo logfiles selected (reason:7)
2011-DEC-08 12:00:09 RFS[47]: Assigned to RFS process 2080
2011-DEC-08 12:00:10 Media Recovery Log C:\ORACLE\FAST_RECOVERY_AREA\PBONDSDR\

Standby database
QL> select group#, thread#, status from v$standby_log;
GROUP# THREAD# STATUS
5 2 ACTIVE
6 2 ACTIVE
7 2 ACTIVE
8 2 ACTIVE
9 2 ACTIVE
Primary DB
SQL> select group#, thread#, members, status from v$log;
GROUP# THREAD# MEMBERS STATUS
1 1 2 INACTIVE
2 1 2 INACTIVE
3 2 2 CURRENT
4 2 2 ACTIVE
Minimally, the configuration should have one more standby redo log file group than the number of online redo log file groups on the primary database. However, the recommended number of standby redo log file groups is dependent on the number of threads on the primary database. Use the following equation to determine an appropriate number of standby redo log file groups:
(maximum number of logfiles for each thread + 1) * maximum number of threads
Using this equation reduces the likelihood that the primary instance's log writer (LGWR) process will be blocked because a standby redo log file cannot be allocated on the standby database. For example, if the primary database has 2 log files for each thread and 2 threads, then 6 standby redo log file groups are needed on the standby database.
I'm a bit confused by above note does that mean I should create (2+1)*2 =6 standby logs?
Thanks,
keith

Is Dataguard and standby dbs is HA

Hi
is Dataguard and standby dbs is HA or RAC is the only oracle HA?
is Dataguard is only DR?
Thanks

RAC and DATAGAURD are two different approches for high availability and desaster recovery.
We are planning to implememt RAC and DATAGAURD but there are budget issues also.
With RAC As i understand we have multiple instances governing a single database. So multiple node/machines governing a single database server.
With DATAGAURD,we have a DR solution at another location.If the primary server fails,standby database takes up the role of primary.
With RAC alone,if any node fails, there is another node to do instance recovery or the server still continues. But what if database server crashes. WIth RAC alone and no dataguard, won't it allow downtime?

Dataguard the achivelog not transfort between primary & standby db

Dear all Dataguard gurus
i tried to install oracle 10g dataguard on 2 machines with Centos 4.6 for development
after finish the installation, i 've got some "STRANGE" ..when i do a query at dataguard1
dataguard1 is primary database
dataguard2 is standby database
sys@dataguard1> select sequence#, first_time, next_time from v$archived_log;
SEQUENCE# FIRST_TIM NEXT_TIME
16 24-JUL-09 24-JUL-09
17 24-JUL-09 24-JUL-09
18 24-JUL-09 24-JUL-09
19 24-JUL-09 24-JUL-09
20 24-JUL-09 24-JUL-09
21 24-JUL-09 24-JUL-09
22 24-JUL-09 11-AUG-09
23 11-AUG-09 12-AUG-09
24 12-AUG-09 12-AUG-09
25 12-AUG-09 12-AUG-09
26 12-AUG-09 12-AUG-09
sys@dataguard1>select sequence#,applied
2 from v$archived_log
3 order by sequence#;
SEQUENCE# APP
16 NO
17 NO
18 NO
19 NO
20 NO
21 NO
22 NO
23 NO
24 NO
but if i do the same quey on standby database
sys@dataguard2> select sequence#, first_time, next_time from v$archived_log;
nothing archive...and not applied
what could be the problem????
thanks for u'r attention & help
Edited by: kang dadang on Aug 12, 2009 7:22 PM

thanks for response jerald
everything is same, all pass for sys on primary & standby are the same, password file on both machine are same
here my parameter file[not all parameter included]
[primary db]..on dataguard1 machines [dbname : dgtest]
*.db_file_name_convert='/u01/app/oracle/oradata/dgtest','/u01/app/oracle/oradata/dgtest'
*.db_name='dgtest'
*.DB_UNIQUE_NAME='dgtest'
*.fal_client='dgtest2'
*.fal_server='dgtest'
*.job_queue_processes=10
*.log_archive_config='DG_CONFIG=(dgtest,dgtest2)'
*.log_archive_dest_1='LOCATION=/u02/oradata/archive/dgtest/
valid_for=(all_logfiles,all_roles)
db_unique_name=dgtest'
*.log_archive_dest_2='service=dgtest2 lgwr async
valid_for=(online_logfiles,primary_roles)
db_unique_name=dgtest2'
*.log_archive_dest_state_1='enable'
*.log_archive_dest_state_2='enable'
*.log_archive_format='%s_%t_%r.arc'
*.log_file_name_convert='/u01/app/oracle/oradata/dgtest','/u01/app/oracle/oradata/dgtest',
'/u01/app/oracle/flash_recovery_area/DGTEST/onlinelog/','/u01/app/oracle/flash_recovery_area/DGTEST/onlinelog/'
*.service_names='dgtest'
*.standby_file_management='auto'
[standby] on dataguard1 machines..[dbname : dgtest2]
*.db_file_name_convert='/u01/app/oracle/oradata/dgtest','/u01/app/oracle/oradata/dgtest'
*.db_name='dgtest'
*.DB_UNIQUE_NAME='dgtest2'
*.fal_client='dgtest2'
*.fal_server='dgtest'
*.log_archive_config='DG_CONFIG=(dgtest,dgtest2)'
*.log_archive_dest_1='LOCATION=/u02/oradata/archive/dgtest/
valid_for=(all_logfiles,all_roles)
db_unique_name=dgtest2'
*.log_archive_dest_2='service=dgtest lgwr async
valid_for=(online_logfiles,primary_roles)
db_unique_name=dgtest'
*.log_archive_dest_state_1='enable'
*.log_archive_dest_state_2='enable'
*.log_archive_format='%s_%t_%r.arc'
*.log_file_name_convert='/u01/app/oracle/oradata/dgtest','/u01/app/oracle/oradata/dgtest',
'/u01/app/oracle/flash_recovery_area/DGTEST/onlinelog/','/u01/app/oracle/flash_recovery_area/DGTEST/onlinelog/'
*.remote_login_passwordfile='EXCLUSIVE'
*.service_names='dgtest'
*.standby_file_management='auto'
thanks for all...jerald
Edited by: kang dadang on Aug 12, 2009 11:52 PM

How to switch primary role to one of standby DBs without interruption?

We have a primary database with 2 standby databases running. We would like to switch role of primary to one of the standby with other 2 (one is standby and the other was primary) standby without interruption and rebuild? What is the detail procedure for it?
Thanks a lot!

The detailed procedure for anything in Oracle more complex than
SELECT * FROM dualrequires a version number. Since you thought it unimportant to provide that no help is possible.
In this case, in addition to the version number, little things such as:
1. What type of Data Guard implementation? Active? Logical? Snapshot Standby? would be useful information for anyone trying to help you.
2. Is this stand-alone or RAC? Again you provide no information and this is critically important?
3. What is the geographical distance between the primary and the standby?
4. What is the protection mode?
If you are not a student you need to read the Oracle online docs and understand the technology. To ask this question, without providing obviously essential information, indicates you may be a danger to your database: Something I am sure you do not wish to be.

Primary & standby db on same OS plaform but having different OS version

Hi,
I have primary & standby database 10.2.0.4 on AIX 5.3 Operating System platform .
I would like to Upgrade my Operating System(AIX) of standby databse server from 5.3 to 6.0.
Will diffenet Operating System version for primary & standby databases support ?
Thnaks.

so, if my primary db on aix 5.3 & standby db on aix 6.1 plaform, then it will not work
or oracle db will not support for this differnent os versions.
is it right?Yes, along with that I'm asking why you want to choose different versions/releases of OS?
I seen there some issues even if some RPM's are missing. So if the complete version changes then think of it.
Moreover check the certification in support.oracle.com
Recently i checked for Linux 6, it's not yet certified. I'm not sure of unix here. So please do refer http://support.oracle.com
Thanks.

Switchover_status "FAILED DESTINATION" on both primary-standby databases

Hi,
I setup primary-standby databases and try to test the switchover functionality between them using the following commands:
alter database commit to switchover to primary with session shutdown;
alter database commit to switchover to physical standby with session shutdown;
Currently, both DBs are showing
open_mode= READ WRITE for "select open_mode_from v$database;" and
switchover_status = FAILED DESTINATION for "select switchover_status from v$database"
When both databases get into these states, how can I return them back to primary and standby roles? Could you please provide me a sequence of steps that I can execute to return them back to normal primary-standby states?
Thanks in advance for your suggestion.

The OS is Red hat 4.1.2-500.
Oracle version is 11g.
Here is the sequence of steps that lead to this issue:
1. switchover_status on primary = to standby, switchover_status on secondary = not allowed
So on primary, I execute
alter database commit to switchover to physical standby with session shutdown;
and could be shutdown/startup mount ( I don't remember exactly)
2. switchover_status on secondary = to primary
So on secondary, I execute
alter database commit to switchover to primary with session shutdown;
alter database open;
3. Now on secondary, the switchover_status = FAILED DESTINATION
On primary, I execute
alter database commit to switchover to primary with session shutdown;
and could be "alter database open" ( I don't remember exactly)
The switchover_status in step 1) and 2) above should indicates that the data guard is working. At the end of the above steps, I cause both databases to get into switchover_status = "FAILED DESTINATION".
I hope to get one of the DBs back into standby role.
If I execute "alter database commit to switchover to physical standby with session shutdown", I will get
"ORA-16416: No viable Physical Standby switchover targets available"
In this situation, is there any recommendation for rescue?

Physical stndby doesn'1 apply redo or primary standby didn't transport redo

I setup physical standby (OEL5.0, DB 11.2), every things seem right. But when i create table on primary DB, it does not appear on standby database. The Physical standby doesn'1 apply redo or primary standby didn't transport redo to standby Datadase
Please consider mine configuration
----Standby :
SQL> select database_role, protection_mode, log_mode from v$database;
DATABASE_ROLE PROTECTION_MODE LOG_MODE
PHYSICAL STANDBY MAXIMUM PERFORMANCE ARCHIVELOG
SQL> archive log list;
Database log mode Archive Mode
Automatic archival Enabled
Archive destination USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence 38
Next log sequence to archive 40
Current log sequence 40
------Primary :
SQL> select database_role, protection_mode, open_mode from v$database;
DATABASE_ROLE PROTECTION_MODE OPEN_MODE
PRIMARY MAXIMUM PERFORMANCE READ WRITE
SQL> create table test_stby (
2 cot_1 number,
3 cot_2 number);
Table created.
SQL> insert into test_stby values (10,11);
1 row created.
SQL> commit;
Commit complete.
SQL> alter system switch logfile;
System altered.
---- Standby :
SQL> SELECT MAX(SEQUENCE#), THREAD# FROM V$ARCHIVED_LOG GROUP BY THREAD#;
no rows selected
SQL> SELECT PROCESS, STATUS,SEQUENCE#,BLOCK#,BLOCKS,DELAY_MINS FROM V$MANAGED_STANDBY;
PROCESS STATUS SEQUENCE# BLOCK# BLOCKS DELAY_MINS
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
MRP0 WAIT_FOR_LOG 40 0 0 0
- Standby cancel redo apply, open read only and query for table test_stby, it does not have this table
Please help
Ch

I did solved this problem :)

How to Refresh UAT Primary/standby from Production primary/standby

Hi ,
We have the following setup :
Primary/standby - Production
Primary/Standby - UAT
I need to know the process on how to refresh the UAT primary/standby .
I'm thinking on the following lines :
1] If we have the export dump of production , can we go ahead and drop the schemas to be refreshed on both UAT Primary and UAT Standby UAT then perform the schema import on Primary UAT .
2] In case if I have to do a full refresh of UAT , do I need to rebuild the UAT environment from the proudction backups Ie,
(i) Drop both the UAT primary and UAT standby database .
(ii) using the produciton backup built the UAT Primary . Take the UAT primary backup and build the UAT standby .
Appricaite if any one can provide some best practices to refresh UAT from Production.

That setup seems to be rare. We assume that the Standby Database is used for testing and have a feature for that called Snapshot Standby.
But in your scenario, you need to develop your own techniques for "refreshment of the UAT Primary".
An easy way (if your Primary is not too large): Throw away your UAT env each time the "Production Primary" changes and RMAN clone it to "UAT Primary" then.
Then RMAN duplicate "UAT Standby" again. Could be relatively easily scripted.
But again: Why not just create an ordinary Standby on your UAT hardware and use it for testing with Snapshot Standby feature? Much easier to maintain.
Kind regards
Uwe Hesse
http://uhesse.wordpress.com

Checking primary key or unique in while entry

Hi,
I want to check primary key or unique key while entry the record, without any loop.
Suppose like these
ac_code ac_desc
A1 ASSET
A2 LIABLITY
A3 EXPENESS
If I enter in A2 It will give error already exists( Don't want any when validate record )
Pls help.
Thanks
Reena

See my answer in this thread
Re: duplicate records in a multi record block

How tyo know that primary & standby are syncronyzed(SCN)

Dears,,
If i have data guard solution (Primary and physical standby) databases
How to make sure that both primary & standby are syncronyzed(SCN)
Please,help,,

Hi,
Compared across the sequences applied on standby with primary archive logs generation generation
select max(sequence#) from v$archived_log where applied='YES';
- Pavan Kumar N

Configure primary & standby with OMS IN dataguard

most respectable viewers,
i have a production database "A"
and a standby database "B" (both of these databases are 9i release2 on server 2003)
Now archives are shipped from primary to standby and after that i manualy recover archives on standby database with "RECOVER STANDBY DATABASE" command.
but i want that the archives which are transferred to standby database recover automatically .
How i can achieve this..............? either running this command on standby database "RECOVER STANDBY DATABASE DISCONNECT FROM SESSION" or anyother way?
i want to watch the performance of both of these database through "ORACLE MANAGEMENT SERVER" graphically. How i can move both of my databases to oracle management server
i think my question is clear. plz reply
REHAN

user10204771 wrote:
i want to watch the performance of both of these database through "ORACLE MANAGEMENT SERVER" graphically. How i can move both of my databases to oracle management server
Data Guard Broker is the solution to manage dataguard graphically;
Check link;
http://www.scribd.com/doc/7479230/oracle-9i-data-guard-broker
Edited by: emre baransel on Mar 30, 2009 4:36 PM

Dataguard.... [ the achivelog not transfort between primary & standby db] m

Dear all Dataguard gurus [sorry if i wrong to place this message]
i tried to install oracle 10g dataguard on 2 machines with Centos 4.6 for development
after finish the installation, i 've got some "STRANGE" ..when i do a query at dataguard1
dataguard1 is primary database machines [hostname]
dataguard2 is standby database machines [hostname]
sys@dataguard1> select sequence#, first_time, next_time from v$archived_log;
SEQUENCE# FIRST_TIM NEXT_TIME
--------- 16 24-JUL-09 24-JUL-09
17 24-JUL-09 24-JUL-09
18 24-JUL-09 24-JUL-09
19 24-JUL-09 24-JUL-09
20 24-JUL-09 24-JUL-09
21 24-JUL-09 24-JUL-09
22 24-JUL-09 11-AUG-09
23 11-AUG-09 12-AUG-09
24 12-AUG-09 12-AUG-09
25 12-AUG-09 12-AUG-09
26 12-AUG-09 12-AUG-09
sys@dataguard1>select sequence#,applied
2 from v$archived_log
3 order by sequence#;
SEQUENCE# APP
16 NO
17 NO
18 NO
19 NO
20 NO
21 NO
22 NO
23 NO
24 NO
but if i do the same quey on standby database
sys@dataguard2> select sequence#, first_time, next_time from v$archived_log;
nothing archive...and not applied..
here my parameter file not all parameter included
primary db..on dataguard1 machines dbname : dgtest
*.db_file_name_convert='/u01/app/oracle/oradata/dgtest','/u01/app/oracle/oradata/dgtest'
*.db_name='dgtest'
*.DB_UNIQUE_NAME='dgtest'
*.fal_client='dgtest2'
*.fal_server='dgtest'
*.job_queue_processes=10
*.log_archive_config='DG_CONFIG=(dgtest,dgtest2)'
*.log_archive_dest_1='LOCATION=/u02/oradata/archive/dgtest/
valid_for=(all_logfiles,all_roles)
db_unique_name=dgtest'
*.log_archive_dest_2='service=dgtest2 lgwr async
valid_for=(online_logfiles,primary_roles)
db_unique_name=dgtest2'
*.log_archive_dest_state_1='enable'
*.log_archive_dest_state_2='enable'
*.log_archive_format='%s_%t_%r.arc'
*.log_file_name_convert='/u01/app/oracle/oradata/dgtest','/u01/app/oracle/oradata/dgtest',
'/u01/app/oracle/flash_recovery_area/DGTEST/onlinelog/','/u01/app/oracle/flash_recovery_area/DGTEST/onlinelog/'
*.service_names='dgtest'
*.standby_file_management='auto'
standby on dataguard1 machines..dbname : dgtest2
*.db_file_name_convert='/u01/app/oracle/oradata/dgtest','/u01/app/oracle/oradata/dgtest'
*.db_name='dgtest'
*.DB_UNIQUE_NAME='dgtest2'
*.fal_client='dgtest2'
*.fal_server='dgtest'
*.log_archive_config='DG_CONFIG=(dgtest,dgtest2)'
*.log_archive_dest_1='LOCATION=/u02/oradata/archive/dgtest/
valid_for=(all_logfiles,all_roles)
db_unique_name=dgtest2'
*.log_archive_dest_2='service=dgtest lgwr async
valid_for=(online_logfiles,primary_roles)
db_unique_name=dgtest'
*.log_archive_dest_state_1='enable'
*.log_archive_dest_state_2='enable'
*.log_archive_format='%s_%t_%r.arc'
*.log_file_name_convert='/u01/app/oracle/oradata/dgtest','/u01/app/oracle/oradata/dgtest',
'/u01/app/oracle/flash_recovery_area/DGTEST/onlinelog/','/u01/app/oracle/flash_recovery_area/DGTEST/onlinelog/'
*.remote_login_passwordfile='EXCLUSIVE'
*.service_names='dgtest'
*.standby_file_management='auto'
what could be the problem????
thanks for u'r attention & help
maybe hunterX could help the problem ;)
Edited by: kang dadang on Aug 13, 2009 12:09 AM
Edited by: kang dadang on Aug 13, 2009 12:10 AM

thanks for reply amit..
when i do that query
select * from V$ARCHIVE_DEST where dest_id=2
Status = ERROR
ERROR = ORA-01031: insufficient privileges
ORA-01031: insufficient privileges ????
what could it be the problem??
nb : the passwdfile between db iis same
but i configure direct I/O could it be the problem?
thanks amit
Edited by: kang dadang on Aug 17, 2009 10:08 PM
Edited by: kang dadang on Aug 17, 2009 10:11 PM
Edited by: kang dadang on Aug 17, 2009 10:16 PM
Edited by: kang dadang on Aug 17, 2009 10:25 PM

Shell script to get the mail whenever the primary or standby DBs down

Hi,
Can any one please provide the shell script to monitor the primary and standby databases, such that whenever the primary or standby database is down we have to get the mail.
Thanks,
Mahi

Hi Mahi,
in 10g you can configure this through EM dbconsole which will be very easy.
(i am not sure if this exists in 9i EM)

When using DataGuard, the logical standby DB is already "OPEN"?

When I was setting up the physical standby DB several years ago no DataGuard got involved), I had the impression that the standby DB is in MOUNT status.
But since when using DataGuard to set up the logical standby DB, the logical standby DB can be used as it is already OPENed.
Is it actually in OPEN status? If so, can the primary and logical standby have the same SID without any trouble?
Please help advise. Thanks a lot!

Hello Christy,
yes it is ok that both database are in status OPEN, that is also the main reason for using logical standby databases (you can do changes and queries on standby too).
I hope you don't use a logical standby database in a SAP environment, because of this is NOT supported. Check sapnote #105047 - Point "14. Data Guard". A logical standby database has limitations.
If you just want to use the physical standby database for queries you can open it in read only or you can use flashback technology for read/write. With Oracle 11g you have these features included in data guard itself (Active Data Guard / Snapshot StandBy) to perform such steps automatically.
Regards
Stefan

DataGuard, Checking primary & standby DBs

Similar Messages

Maybe you are looking for