About Data Guard - Physical Standby Database

Dear All,
I have read many documents regading Data Guard.
I am about to setup Data Guard in our current environment but want to clear few tings.
I have a confusion between physical and logical standby database.
What I have read from different documents is:
-Physical Standby Database in (11g)
1) It is the most efFicient
2) I can be either in mount or open state
3) Select queries and reporting can be done to improve performance of the primary database.
4) Schema on primary and standby database is always the same
-- Logical Standby Database
1) You can create additional tables, indexes, etc.
2) Always in open mode
3) Select queries and reporting can be done to improve performance of the primary database
Now our scenerio is, that we have one server at the moment, OS is linux and operating system is 11g. We want to setup an other server in another country, will also be 11g on Linux in a way that it acts as standby/backup server. Schema and data is always the same. In case due to unavailability of primary server, standby server acts as the primary server (This has to be automated). The reason for unavailability could be any like maintenance work on primary server, network or hardware failure at primary server. The last and the most important thing is that users from this country where we will setup standby database will insert/update data on the primary server BUT queries and reporting will be done from this newly created standby data.
Kindly recomend the best Data Guard in this scenerio and kindly correct me where I am wrong.
Thanks, Imran

A logical standby has various limitations on things like data types. It's also a much more complex architecture, which makes it more likely that something will break periodically and require attention. Applying redo to a physical standby is code that has been around forever and is as close to bullet-proof as you'll get. And you would generally prefer to fail over to a physical standby-- if you do things like create new objects in the logical standby, you may have to get rid of those objects during a failover to get acceptable OLTP performance.
Justin

Similar Messages

11g Data guard 建physical standby database配置相关问题

General information
OS:red hat Linux 2.6.32-200.13.1.el5uek x86_64(primary,standby)
Home version:11.2.0.3(primary,standby)
Situation:
实验用库，想学习data guard，在另一个服务器上克隆了一个HOME并按照官方文档http://docs.oracle.com/cd/E11882_01/server.112/e25608/create_ps.htm#i1225703
中去实验，步骤均按照官方文档来,最后在mount standby库时校验select sequence# from v$archived_log没有记录，出错日志如下（从mount开如截取）
standby alert_dbacoe.log
Error logs
alter database mount
Completed: alter database mount
Error 604 received logging on to the standby
+FAL[client, ARC2]: Error 604 connecting to PRIMARYSV for fetching gap sequence+
Errors in file /u05/oracle/app/oracle/diag/rdbms/standby/dbacoe/trace/dbacoe_lgwr_1912.trc:
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '/u04/app/oracle/redundancy/dbacoe/redo01_s.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-00312: online log 1 thread 1: '/u03/app/oracle/oradata/dbacoe/redo01.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Errors in file /u05/oracle/app/oracle/diag/rdbms/standby/dbacoe/trace/dbacoe_lgwr_1912.trc:
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '/u04/app/oracle/redundancy/dbacoe/redo01_s.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-00312: online log 1 thread 1: '/u03/app/oracle/oradata/dbacoe/redo01.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Errors in file /u05/oracle/app/oracle/diag/rdbms/standby/dbacoe/trace/dbacoe_lgwr_1912.trc:
ORA-00313: open failed for members of log group 2 of thread 1
ORA-00312: online log 2 thread 1: '/u04/app/oracle/redundancy/dbacoe/redo02_s.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-00312: online log 2 thread 1: '/u03/app/oracle/oradata/dbacoe/redo02.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Errors in file /u05/oracle/app/oracle/diag/rdbms/standby/dbacoe/trace/dbacoe_lgwr_1912.trc:
ORA-00313: open failed for members of log group 2 of thread 1
ORA-00312: online log 2 thread 1: '/u04/app/oracle/redundancy/dbacoe/redo02_s.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-00312: online log 2 thread 1: '/u03/app/oracle/oradata/dbacoe/redo02.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Errors in file /u05/oracle/app/oracle/diag/rdbms/standby/dbacoe/trace/dbacoe_lgwr_1912.trc:
ORA-00313: open failed for members of log group 3 of thread 1
ORA-00312: online log 3 thread 1: '/u04/app/oracle/redundancy/dbacoe/redo03_s.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-00312: online log 3 thread 1: '/u03/app/oracle/oradata/dbacoe/redo03.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Errors in file /u05/oracle/app/oracle/diag/rdbms/standby/dbacoe/trace/dbacoe_lgwr_1912.trc:
ORA-00313: open failed for members of log group 3 of thread 1
ORA-00312: online log 3 thread 1: '/u04/app/oracle/redundancy/dbacoe/redo03_s.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-00312: online log 3 thread 1: '/u03/app/oracle/oradata/dbacoe/redo03.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ARC3: Archival started
ARC0: STARTING ARCH PROCESSES COMPLETE
Addition:
因为是实验用库，所以结构有点怪，大体如下:
Primary
数据文件在BASE所在的oradata下即/u03/app/oracle下,
redo文件每组两份，一份在oradata下，另一份在同机的/u04/app/oracle/redundancy中（以_s结尾命名）
archive文件在/u04/app/oracle/fast_recovery_area中
standby
数据文件在/u05/oracle/app/oracle/oradata下
redundancy中的redo文件随着该目录放到oradata下的red中了
archive文件目录则是/u05/oracle/app/oracle/fast_recovery_area中
接下来是对应的init文件与TNS信息
Primary端的init主要信息
db_unique_name='PRIMARY'
fal_client='PRIMARYSV'
fal_server='STANDBYSV'
log_archive_config='DG_CONFIG=(PRIMARY,STANDBY)'
log_archive_dest_1='location=/u04/app/oracle/fast_recovery_area/DBACOE/archivelog VALID_FOR=(ALL_LOGFILES,ALL_ROLES) db_unique_name=PRIMARY'
log_archive_dest_2='service=STANDBY ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) db_unique_name=STANDBY'
log_archive_dest_state_1='enable'
log_archive_dest_state_2='enable'
db_file_name_convert='/u05/oracle/app/oracle/oradata/dbacoe','/u03/app/oracle/oradata/dbacoe',/u05/oracle/app/oracle/oradata/red','/u04/app/oracle/redundancy'
log_file_name_convert='/u05/oracle/app/oracle/fast_recovery_area/DBACOE/archivelog','/u04/app/oracle/fast_recovery_area/DBACOE/archivelog'
Standby端的init信息
log_archive_config='DG_CONFIG=(PRIMARY,STANDBY)'
db_unique_name='STANDBY'
db_file_name_convert='/u03/app/oracle/oradata/dbacoe','/u05/oracle/app/oracle/oradata/dbacoe','/u04/app/oracle/redundancy','/u05/oracle/app/oracle/oradata/red'
log_file_name_convert='/u04/app/oracle/fast_recovery_area/DBACOE/archivelog','/u05/oracle/app/oracle/fast_recovery_area/DBACOE/archivelog'
log_archive_dest_1='location=/u05/oracle/app/oracle/fast_recovery_area/DBACOE/archivelog VALID_FOR=(ALL_LOGFILES,ALL_ROLES) db_unique_name=STANDBY'
log_archive_dest_state_1=enable
log_archive_format=log%t_%s_%r.arc
log_archive_dest_2='SERVICE=PRIMARYSV ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=PRIMARY'
log_archive_dest_state_2=enable
TNS信息如下(均能tnsping通）
PRIMARYSV =
+(DESCRIPTION =+
+(ADDRESS = (PROTOCOL = TCP)(HOST = db1.ad.xxxxxx.com)(PORT = 1521))+
+(CONNECT_DATA =+
+(SERVER = DEDICATED)+
+(SERVICE_NAME = dbacoe)+
+)+
+)+
STANDBYSV =
+(DESCRIPTION =+
+(ADDRESS = (PROTOCOL = TCP)(HOST = db2.ad.xxxxx.com)(PORT = 1529))+
+(CONNECT_DATA =+
+(SERVER = DEDICATED)+
+(SERVICE_NAME = dbacoe)+
+)+
+)+
PS：请大家花费一点点时间阅读一下这冗长的段子，刚开学data guard，参数上设置都很生疏，（光照着文档做了，是否有redo log相关的操作遗漏？）敬请指教
Edited by: 961394 on Dec 10, 2012 1:52 AM
Edited by: 961394 on 2012-12-10 上午4:58

结贴了，感谢maclean一群的Jesse Lui帮我解决问题

How to check data in physical standby database?

Hi!
I'm maintaining physical standby database system. everyday, i must check tranfer and apply progress. I known, it operate very good. No archive gap is found.
But i want to check data in physical standby database that there is consistant with primary database, there isn't? What method do I use? How to do?
thankS

I hope the following will help
Verifying the Physical Standby Database
==========================================
Once you create the physical standby database and set up log transport services, you may want verify that database modifications are being successfully shipped from the primary database to the standby database.
To see the new archived redo logs that were received on the standby database, you should first identify the existing archived redo logs on the standby database, archive a few logs on the primary database, and then check the standby database again. The following steps show how to perform these tasks.
Step 1 Identify the existing archived redo logs.
On the standby database, query the V$ARCHIVED_LOG view to identify existing archived redo logs. For example:
SQL> SELECT SEQUENCE#, FIRST_TIME, NEXT_TIME
2 FROM V$ARCHIVED_LOG ORDER BY SEQUENCE#;
SEQUENCE# FIRST_TIME NEXT_TIME
8 11-JUL-02 17:50:45 11-JUL-02 17:50:53
9 11-JUL-02 17:50:53 11-JUL-02 17:50:58
10 11-JUL-02 17:50:58 11-JUL-02 17:51:03
3 rows selected.
Step 2 Archiving the current log.
On the primary database, archive the current log using the following SQL statement:
SQL> ALTER SYSTEM ARCHIVE LOG CURRENT;
Step 3 Verify that the new archived redo log was received.
On the standby database, query the V$ARCHIVED_LOG view to verify the redo log was received:
SQL> SELECT SEQUENCE#, FIRST_TIME, NEXT_TIME
2> FROM V$ARCHIVED_LOG ORDER BY SEQUENCE#;
SEQUENCE# FIRST_TIME NEXT_TIME
8 11-JUL-02 17:50:45 11-JUL-02 17:50:53
9 11-JUL-02 17:50:53 11-JUL-02 17:50:58
10 11-JUL-02 17:50:58 11-JUL-02 17:51:03
11 11-JUL-02 17:51:03 11-JUL-02 18:34:11
4 rows selected.
The logs are now available for log apply services to apply redo data to the standby database.
Step 4 Verify that the new archived redo log was applied.
On the standby database, query the V$ARCHIVED_LOG view to verify the archived redo log was applied.
SQL> SELECT SEQUENCE#,APPLIED FROM V$ARCHIVED_LOG
2 ORDER BY SEQUENCE#;
SEQUENCE# APP
8 YES
9 YES
10 YES
11 YES
4 rows selected.

Using streams to capture data from physical standby database.

Does anybody know if it is possible to use streams to capture data from physical standby database instead of PROD database? The standby database is in read only mode. We use Oracle 11gR2.
Thanks in advance.

physical are closed : how will it managed the queues and overspill queues when target is not present? Also the data dictionary must reflect the primary but If you run capture, then you introduce rules that are not on primary: How ?

Data Guard Physical Standby Failover

I need clarification on Physical Standby Failovers. Say I have a Primary db (A) and a physical standby (B), (A) fails and (B) is now the primary, can (A) be setup to become a standby of (B)? I've read 2 different statements in Oracle 10g Data Guard Concepts and Admin
"During failovers involving a physical standby database: In all cases, after a failover, the original primary database can no longer participate in the Data Guard configuration."
vice
"After a fast-start failover occurs, the old primary database will automatically reconfigure itself as a new standby database upon reconnection to the configuration."
Much thanks.

In all cases, after a failover, the original primary database can no longer participate in the Data Guard configuration.
TRUE ! But this doesn't mean that you cannot make your failed primary a new standby database !.
You can achieve this using FLASHBACK DATABASE option:
From the documentation:
After a failover occurs, the original primary database can no longer participate in the Data Guard configuration until it is repaired and established as a standby database in the new configuration. To do this, you can use the Flashback Database feature to recover the failed primary database to a point in time before the failover occurred, and then convert it into a physical or logical standby database in the new configuration.
Read the following documents:
http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/role_management.htm#sthref995
http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/scenarios.htm#i1049997
In addition to this I'd like to mention that you can achieve the same with doing an incomplete recovery instead of using FLASHBACK DATABASE.
"After a fast-start failover occurs, the old primary database will automatically reconfigure itself as a new standby database upon reconnection to the configuration."
TRUE. If you enable Fast-Start Failover:
http://download.oracle.com/docs/cd/B19306_01/server.102/b14230/sofo.htm#CHDDFFEC
Cheers!

Data Guard or Standby Database

Hi all,
Im confused about "physical standby" and "logical standby". Can an entire database export be logical standby? Or the logical standby is only the output of RMAN backup.
Thanks

Physical Standby
A physical standby database is kept synchronized with the primary database, through Redo Apply i.e., block-to-block transfer which recovers the redo data received from the primary database and applies the redo to the physical standby database.
The database schema, including indexes, are the same.
Logical Standby
The logical standby database is kept synchronized with the primary database though SQL Apply, which transforms the data in the redo received from the primary database into SQL statements and then executing the SQL statements on the standby database.
In Logical standby the physical oraganization and structure will be different.
The below link helps you to know much about the difference between Physical and Logical Standby.
http://www.dba-oracle.com/t_difference_logical_physical_standby_database.htm ----------by Burleson
Hope it would be helpful. :)

Read-only agent synching to a Data Guard physical standby?

Hi all,
we are trying to use TimesTen 11.2.2.4.1 as a read-only memory cache for an Oracle 11.2.3.0.7 schema on Linus RedHat 6.3, while using Oracle Data Guard to replicate the Oracle instance over geographically remote sites. On each site we would like to have two TT instances synchronizing with the local Oracle 11g instance. This works fine against the master DB, but are the TT agents going to be able to synchronize against physical standby instances?
The problem it seems is that the TT agent uses dedicated structures in the Oracle master instance (related to the cache grid), which are going to be replicated into the standby instances. Is the TT agent able to use the read-only, replicated structures to complete synchronization, or is this approach unworkable? What would be your advise as how to achieve this?
Thanks for your help,
Chris

Hi again,
so after testing a little bit it appears that this approach works indeed, at least against a limited number of manual DML operations. What I needed to do on the slave instance to have it working is the following:
1 - Entirely exclude TTADMIN and TIMESTEN schemas from the Data Guard replication:
ALTER DATABASE STOP LOGICAL STANDBY APPLY;
execute dbms_logstdby.skip(stmt => 'SCHEMA_DDL', schema_name => 'TTADMIN', object_name => '%');
execute dbms_logstdby.skip(stmt => 'SCHEMA_DDL', schema_name => 'TIMESTEN', object_name => '%');
execute dbms_logstdby.skip(stmt => 'DML', schema_name => 'TTADMIN', object_name => '%');
execute dbms_logstdby.skip(stmt => 'DML', schema_name => 'TIMESTEN', object_name => '%');
ALTER DATABASE START LOGICAL STANDBY APPLY IMMEDIATE;
2 - Erase both schemas from the local instance:
DROP USER TTADMIN CASCADE;
DROP USER TIMESTEN CASCADE;
CREATE USER TTADMIN etc
3 - Temporarily disable the database guard while creating the local ttCache structures, as the scripts seem to need to set a table-level lock on the source table:
ALTER DATABASE GUARD NONE;
ttIsql> CREATE READONLY CACHE GROUP etc
ALTER DATABASE GUARD STANDBY;
4 - Unset the "Fire_Once_Only" property for the local TTADMIN triggers:
execute dbms_ddl.set_trigger_firing_property(trig_owner=> 'TTADMIN', trig_name=> 'TT_06_70560_T', fire_once => FALSE);
At that point the cache seems to replicate properly in the most simple cases. I will try to test with some substantial load and against DG failovers to see how this behaves.
Regards,
Chris

How to deal with tempfiles named '+DATA' on physical standby databases

Hi gurus,
I have a 3-node RAC with 2 standby databases, all of them 11.2.0.3, on CentOS 5.10 64 bits.
I use Active Data Guard (with DB open in read-only mode, obviously).
My problem is that somehow I have 3 tempfiles named '+DATA' on one standby database, so I can't drop nor rename these files. Is there any way to fix this?
Looks like the tempfiles couldn't be created when the database was opened in read-only mode.
Thanks a lot for your help.
# Primary DB:
col TABLESPACE format a10
col TEMPFILE format a50
select a.name TABLESPACE, b.TS#, b.FILE#, b.name TEMPFILE, b.bytes/1024/1024 MB, b.status from v$tablespace a, v$tempfile b where a.name='TEMP';
TABLESPACE        TS#      FILE# TEMPFILE                                                   MB STATUS
TEMP                3          4 +DATA/racdb/tempfile/temp.382.873892319                  8192 ONLINE
TEMP                3          7 +DATA/racdb/tempfile/temp.383.873892341                  8192 ONLINE
TEMP                3          8 +DATA/racdb/tempfile/temp.384.873892341                  8192 ONLINE
# Standby DB:
col TABLESPACE format a10
col TEMPFILE format a50
select a.name TABLESPACE, b.TS#, b.FILE#, b.name TEMPFILE, b.bytes/1024/1024 MB, b.status from v$tablespace a, v$tempfile b where a.name='TEMP';
TABLESPACE        TS#      FILE# TEMPFILE                                                   MB STATUS
TEMP                3          4 +DATA                                                       0 ONLINE
TEMP                3          7 +DATA                                                       0 ONLINE
TEMP                3          8 +DATA                                                       0 ONLINE
TEMP                3          9 /u02/oradata/RACDBSB1/tempfile/temp_01.dbf                512 ONLINE
RMAN> report schema;
using target database control file instead of recovery catalog
RMAN-06139: WARNING: control file is not current for REPORT SCHEMA
Report of database schema for database with db_unique_name RACDBSB1
List of Temporary Files
=======================
File Size(MB) Tablespace           Maxsize(MB) Tempfile Name
4    3072     TEMP                 8192        +DATA
7    3584     TEMP                 8192        +DATA
8    5120     TEMP                 8192        +DATA
9    512      TEMP                 8192        /u02/oradata/RACDBSB1/tempfile/temp_01.dbf
SQL> show parameter db_create_file_dest
NAME                                 TYPE                             VALUE
db_create_file_dest                  string                           /u02/oradata
Thanks!

Hi all,
Regarding Hemant's question, YES, I use that config, and the error I receive is:
SQL> alter database tempfile 4 drop;
alter database tempfile 4 drop
ERROR at line 1:
ORA-01516: archivo log, archivo de datos o archivo temporal "+DATA" inexistente
Segey, yes, I've tried with no luck.
The good news are that today we've resolved the problem, we had to use:
SQL> alter tablespace temp drop tempfile 4;
Tablespace altered.
OMG, what's the difference... alter database tempfile 4, alter tablespace temp drop tempfile 4... they are both the same...!! lol
Thanks guys!

Rman clone ? duplicate database ? data guard ? standby database?

hey there !!
What is the difference between Rman clone , duplicate database , data Guard , standby db?
1 more thing , standby database and duplicate database are same??

RMAN Clone : you take backup of a database on one server ,then take it to other server ,again use RMAN to restore the database,A lot manual intervention is needed in this method
RMAN DUPLICATE: same as above just that manual intervention is less. With 11gR2 there active database duplication in which you can clone your test database directly from production database without taking and then transferring the backup to test server.
Standby Database :they are of two types Physical and logical.The setup is done using RMAN with any of the above methods.Standby is the in-sync (can have some delay) version of primary database either block by block which is physical standby configuration or SQL statment wise which is logical standby.
Data Guard:This is also a standby configuration.Here the failover and switchover are automated with the help of DGMGRL utility.In manual standby this same can be done via SQL*PLUS using sql commands

Data Guard - Physical Standby Setup by RMAN

I am trying to set up a physical standby using RMAN. After I brought up the standby db, I failed to turn on redo apply. I found out that the standby redo log files were not copied over to the standby.
The back up script I use is as follows.
run {
allocate channel ch2 type disk;
backup current controlfile for standby format '/backups/sitv/cf_%d_t%t_s%s_p%p';
backup format '/backups/sitv/%U.bkup' database;
sql 'alter system archive log current';
backup format '/backups/sitv/al_t%t_s%s_p%p.bkup' archivelog all;
release channel ch2;
What command should I use to be able to make a backup of the standby log files as well?
Thanks.

Hi Sybrand,
Thank for the reply. Let me give a little bit more detailed information on what I did.
I followed the documentation as follows to set up the physical standby
http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/create_ps.htm#g88234
I created the standby log files per section 3.1.3 on the primary db before the standby is created.
I used the following command to restore the standby on a different server.
run {
allocate auxiliary channel ch1 device type disk;
duplicate target database for standby dorecover nofilenamecheck;}
My question is the standby log files did not show up on the standby server. However, the log files showed in the v$logfile table. After I tured on the redo apply, the changes I made in primary db did not happen in the standby db.
Any idea on how to fix it?
Thanks.

Data Guard - Physical Standby

I have two questions here, or I would say two cases here to discuss.
1. I have shutdown my standby db and unmount archive location from server for 2 hours. After that mount the file system again and bring up the standby DB. As we we ASYNC Standby recovered successfully, but my worry is we didn't get any of the physical archive file in the standby location for those 2 hours. Can't this automatically get this from Primary DB or two we have to manually copy them from Primary Server. Though we won't require them as Standby DB is in sync. Kindly suggest.
2. Why we have to create 4 standby redo logs in Primary server. Can't we create less number of standby redo logs in Primary.

1) Yes, the archives that don't get transferred will be retried until they do. You could look into Oracle Archive Log gap detection and resolution for more info.
http://www.sc.ehu.es/siwebso/KZCC/Oracle_10g_Documentacion/server.101/b10823/log_transport.htm
2) According to Oracle they have to be exactly the same size but the minimum requirement is to have one more than the primary.
http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/create_ps.htm#SBYDB00426

Anyone has experience using 9i data guard for standby database??

I'll be appreciate if you let me know how you set it up, thanks...

Hi --
Aperture is extremely flexible. You have unlimited use of Keywords. Additional built-in tags are
- Ratings (7 levels, easily shown with Images)
- Color Labels (8 labels, easily shown with Images)
- Location (assigned or based on GPS, has own interface)
- Faces (Aperture comes with a useful face recognition engine, own interface)
- Custom metadata fields (e.g.: Purchaser)
- etc.
It's organizing abilities are second to none in its class (including Lightroom, Capture One Pro).
Provide some details about your research project, and I'm sure we can comment specifically rather than generally.
--Kirby.

Problem with data guard Creating a Physical Standby Database turorial

There is a tutorial of Creating a data guard Physical Standby Database:
http://www.oracle.com/technology/obe/11gr1_db/ha/dataguard/physstby/physstdby.htm
I tried to install it on two servers. One for primary database second for physical standby.
I have error on C. Creating the standby database over the network, action #6:
"On the standby system, set the ORACLE_SID environment variable to your <physical standby SID> (i.e. orclsby1) and start the instance in NOMOUNT mode with the text initialization parameter file."
When I try to connect to idle instance there is an error pops up:
C:\>sqlplus / as sysdba
SQL*Plus: Release 11.1.0.7.0 - Production on Thu May 21 16:28:10 2009
Copyright (c) 1982, 2008, Oracle. All rights reserved.
ERROR:
ORA-12560: TNS:protocol adapter error
I'v checked listener and it is runned. There is no service for database because there is no database yet.
The question is did some one installed data guard configuration using this tutorial? Is there any errors in it? What should I do to finish this installation?

On Windhose for every instance a service must have been created using the oradim command.
Oracle tutorials are usually Unix-centric, as Windhose is an odd man out, so they don't discuss that bit.
'Kindly do the needful' and create the service prior to starting the instance in nomount mode
Hint: oradim is documented and has a help=y clause.
IIRC there is an option in database control (in the maintenance part) which automates everything.
Sybrand Bakker
Senior Oracle DBA
Experts: those who do read documentation

Data Guard logical standby Versus Streams

I'm referring to both Oracle 10g/9i
If a Data Guard logical database uses similar technology to Streams (Log Mining and SQL apply), why can't you stand up a standby database on a different platform, or at least I have found nothing on the subject.
But in 11g Oracle Data Guard (physical standby database) is a solution for same endianness platform migration.
I will appreciate any insight on the subject.

Yes...thats true...both uses same technology...
REDO LOGMINER
SQL------------------------>BLOCK LEVEL CHANGES---------------------------------->SQL
But there are serious implemetation diff..
1) Oracle Data Guard is designed for protecting from data failure and disasters.
Streams is designed for information sharing and distribution but can also provide a very efficient high availability solution.
2) Streams is configured from the bottom up — individual tables, schemas, capture processes, apply processes, queues.
Logical Standby is configured from the top down — start with entire database, then specify only what you don’t want.
As logical standby is top down and changes are capture at remote location (logical standby db) and for that archive log need to be shipped using FAL client/server to remote and to ship the archivelog in Data Guard configuration, all members should be running on same platform.
As said before, Streams is configured from the bottom up, it start with tables--> Schemas--->Database and we can capture changes at local/remote location. If we capture changes locally, target streams db can be on diff platform. But for downstream capture must need same platform as logical standby database needed so that archivelogs can transport from source to downstream db.

Goldengate replicate physical standby database

Friends,
I did not get a answer in data guard place
Could we use oracle golden gate to replicate a data guard physical standby database into a new logical database?
Or we must replicate data guard primary database into a new logical database?
Thanks
newdba

Thanks for your help. In the physical standby database, the log_mode shows archive log. per your statement, we can configure golden gate Extract parameter TRANLOGOPTIONS with the ARCHIVEDLOGONLY option to replicate physical standby database into new customer DB.
But I have other question, As I understand, data guard physical standby database requested the same as primary database.
If you install golden gate in physical standby database host, are there any issue for data guard configuration?
Thanks
newdba

About Data Guard - Physical Standby Database

Similar Messages

Maybe you are looking for