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.

Similar Messages

Logical standby versus Streams?

Anybody can explain me difference between logical standby and streams in terms of architecture and functionality?

Both Logical standby and streams share the same underlying architecture. The difference is the requirements u have
1) the Logical standby database is the complete replica of the whole database. while streams enable you to replicate table, schema or the database.
2) The logical standby database can opened in read only mode. ( by the way u can open it in read/write but you have to stop the recovery first and u have flash back database enabled). Streams allow you to open the replicated database read/write mode.
3) The logical standby database allows one way replication. with streams you can implement bi-directional replication as well.
4) Streams are far more customizable than logical data guard.
5) in my opinion streams are much harder to implement, administer and monitor than logical standby database

DATA Guard Logical Standby v.s. Streams Apply (10gR2, rac -- rac )

Greetings -
We currently have a 3 node cluster, doing a 'Schema' capture, with a 2 node cluster serving as the apply side. Both are on 10gR2 (solaris 10)
We have been experiencing apply latency due to large transactions. The way logminer/streams evaluates the arch logs, it converts each updated row into a transaction as part of a transaction set, using 'decode (' statements.
I am under the impression a physical standby will do the same thing. But what about a logical Standby ?
(this from the Oracle Documentation)
[10g Concepts|http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/concepts.htm#SBYDB00010]
...Contains the same logical information as the production database, although the physical organization and structure of the data can be different. 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.
Does anyone know firsthand if SQL APPLY re-issues the original sql, or if it relies on the 'decode' command as well ?
Thanks
The Nets Edge

A Physical standby does not do anything with SQL. It is running media recovery under the covers. A Logical standby uses the Logminer to read the redo, converts it to SQL and Data and applies those transactions to the Logical standby.
The both build logical change records, figure out order, dependencies etc etc and applies the transaction. Both are susceptible to long running transactions on the Primary (source) database.
Streams uses Logminer, Logical Standby use part of the Streams apply so as Mr. Morgan said, they are very similar :^)
If you are having apply performance issues you may want to look at Active data Guard.
Larry

Data Guard Logical Standby DB Questions

Hi,
I am creating Oracle 9i Logical Standby database on AIX 5 on same server ( for
testing only ).
In Data Guard Manual ( PDF file page no : 86 ) it is said that
Step 4 Create a backup copy of the control file for the standby database. On the
primary database, create a backup copy of the control file for the standby database:
SQL> ALTER DATABASE BACKUP CONTROLFILE TO
2> '/disk1/oracle/oradata/payroll/standby/payroll3.ctl';
My Questions regarding this are
1. Does it missing "backup standby controlfile" word ? if not what is the use of
this control file ? Because as per this manual section 4.2.2 step no 1 and 2 I
have stopped the primary database and copied datafiles,logfiles and controlfiles
as specified which are having consistent stage.
2. On primary database I am mirroring 2 controlfiles at two diffrent locations.
On Standby Database I am going to keep same policy. Then on standby database do I have to copy this controlfile to two locations and rename datafiles or I have
to user controlfiles which I have backed up along with datafiles ?
3. Suppose my primary database is "infod" and standby database is "standby".
Then what should be value of log_file_format parameter of standby database ? On
primary db I have defined "infod LOG_ARCHIVE_FORMAT=infod_log%s_%t.arc. Do I have to keep same or change it ? If on standby db I change the value do I
require other parameters to be set ?
regards & thanks
pjp

Q/A1) Its correct you dont need the standby keyword. Not sure abut the reason why but we have created logical standby running in prod using the oracle doc.
Q/A2) Yo can specify any location and name for your controlfiles as it is instance specific and not depending on primary database.
Q/A3) You can set any format for your archlogs on standby side. It doesnt bother the primary db or DG configuration.
Regards,
http://askyogesh.com

Data guard - logical standby in no archive log

We are creating a logical standby for reporting purpose only. I see no reason why it should be in archivelog mode. Would this hamper our current situation?

the solution is already approved , the only thing i could do is wonder if backup is necessary for the logical.
Its not going to be used for any purpose other than reporting.
From what i understand, no archivemode should not affect it. Is this undertanding true

Data Guard Logical Standby Skip Handler bug

Does anyone know of a documented bug concerning the skip handler not skipping a grant on a view in a schema with a SCHEMA_DDL skip handler defined?
Here is my test case.
On Primary:
Create table scott.junk (x number) tablespace users; (created successfully on logical standby)
On logical standby:
exec dbms_logstdby.skip('SCHEMA_DDL','SCOTT','%'null,true,'\'); (created skip handler on all SCOTT objects)
On Primary:
grant select on scott.junk to public; (successfully skipped due to missing object)
On Primary:
create view scott.v_junk as select * from scott.junk; (successfully skipped on logical standby)
On Primary:
grant select on scott.v_junk to public; (received 'ora-00942 table or view does not exist' on logical standby and SQL Apply stopped).
I'm running version 10.2.0.4 but have not applied the recommended patch bundle for logcal standby #7937113.8.
If anyone knows whether this has been documented or not, please let me know. If not, I will submit an SR to get this documented.
Thanks,
Michael Anderson
OCP - Bank of the West

When I look at the syntax for the package
http://www.morganslibrary.org/reference/dbms_logstdby.html
what I see is:
dbms_logstdby.skip(
stmt        IN VARCHAR2,
schema_name IN VARCHAR2 DEFAULT NULL,
object_name IN VARCHAR2 DEFAULT NULL,
proc_name   IN VARCHAR2 DEFAULT NULL,
use_like    IN BOOLEAN DEFAULT TRUE,
esc         IN CHAR1    DEFAULT NULL);So looking at your code:
exec dbms_logstdby.skip('SCHEMA_DDL','SCOTT','%'null,true,'\'); (created skip handler on all SCOTT objects)
'SCHEMA_DDL' is your statement.
'SCOTT' is your schema name.
'%' indicates all objects
and ... shouldn't there be a comma before the NULL?
In the future don't provide values where the default's will suffice. It makes thing's far simpler.

Logical Standby and Streams

Hi,
I am considering different replication scenarios for our future system and have a (maybe stupid:) question. Is it technically possible to create a logical standby database (Data Guard) and than replicate it further using Streams?
Regards,
Tim

Yes , This is possible with logical standby but you need to have mechanisms to take care of role transitioning in case of fail over. See Oracle document http://download.oracle.com/docs/cd/E14072_01/server.112/e10700/whatsnew.htm (Key word search "streams")
Thanks
http://swervedba.wordpress.com/
Edited by: swervedba on May 30, 2011 8:48 PM

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

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!

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

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

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帮我解决问题

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. :)

Why could not Oracle replicates tables which includes Spatial Data to Logical Standby?

Hi all,
Nowadays, i am working on Oracle Logical Standby Databases which includes Spatial Data? But i could not achieve to transport a table with multimedia data (with spatial data types ). But Logical Standby Databases can not support this type of tables? Is this a restriction of modelling Spatial and Geometry in data blocks? And how do i achieve this because i should use this secondary for query-only?
Kind Regards,

Some data types are simply not supported by logical standby replication. Depending on the version, this might or might not include Spatial.
11.2: https://docs.oracle.com/cd/E11882_01/server.112/e41134/data_support.htm#SBYDB4936
12.1: https://docs.oracle.com/database/121/SBYDB/data_support.htm#SBYDB4936
If you need to replicate Spatial data, you need to look at other mechanisms. E.g., physical standby, materialized views, or GoldenGate.

Data Guard phys. standby creation failing in 10g EM?

All,
I'm working on setting up Oracle Data Guard in a test environment at my company. It was suggested to me to go through the GUI to set up a physical standby database and automate the management of my DG setup.
However, the several attempts that I have made result in the process failing during the "Create Standby Database" and the process fails with the following errors:
dgcreate.recoverStby: ALTER DATABASE RECOVER CANCEL
dgcreate.recoverStby: ALTER DATABASE OPEN READ ONLY
SQL Error: ORA-16004: backup database requires recovery
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '/u01/app/oracle/product/10.2.0/db_1/oradata/oratstdg/system01.dbf' (DBD ERROR: OCIStmtExecute)
Can anyone pass along any ideas as to where the issue might be? I would really appreciate it - I need this up and going ASAP. Thanks!
Matt Gordon

Ugonic,
I actually did create a new Physical Standby Database. I did not have an existing database configured as a standby database. In fact, the standby server that I used only had the Oracle binaries installed on it - there was no database on that system.
Additionally, I did not have a saved configuration to use, so I generated completely new files and a new configuration.
I left the screen alone for over an hour before checking the status and seeing these errors in the log - I am wondering if anybody else has encountered this same issue.
On a side note, I've stumbled my way further into this process and now have a functional DG configuration. However, I can only switchover from SQL*Plus - the GUI way fails. When I click on Verify in the GUI I get the following log:
Initializing.
Connected to instance fcoracle1.cdps.cdp:oratest1
Starting alert log monitor...
Updating Data Guard link on database homepage...
WARNING: Database oratest2.cdps.cdp is not discovered.
Data Protection Settings:
Protection mode : Maximum Performance
Log Transport Mode settings:
oratest1.cdps.cdp: ASYNC
oratest2.cdps.cdp: ASYNC
Checking standby redo logs.....OK
Checking Data Guard status
oratest1.cdps.cdp : Normal
oratest2.cdps.cdp : Normal
Checking Inconsistent Properties
Checking agent status
oratest1.cdps.cdp ... WARNING: Undefined subroutine &main::executeSQLPlusSYSDBA called at - line 5.
WARNING: Switchover or failover may not succeed as a result.
oratest2.cdps.cdp ... WARNING: Undefined subroutine &main::executeSQLPlusSYSDBA called at - line 5.
WARNING: Switchover or failover may not succeed as a result.
Switching log file 235.Done
Checking applied log on oratest2.cdps.cdp....OK
Processing completed.
Have you experienced this problem and/or do you have any suggestions to resolve it?
Matt

Data Guard logical standby Versus Streams

Similar Messages

Maybe you are looking for