Logical standby database questions

Hi,
1.Is it possible to encrypt just the logicals standby database? ie primary is not encrypted but when the data comes to logical standby it gets encrypted?
2. Is it possible to replicate only certain schemas to logcial standby?
Please let me know,
Thanks a lot
Sumathy

Hi Sumathy,
1.) Yes this is possible
2.) Yes also possible. However Logical Standby will always gather all information from the primary, and only skip in the apply process.
If you want to lessen your transfer, then you should use other replication mechanism like
- Golden Gate (preferred but does cost money)
- Streams (free, but depricated)
Regards
Sebastian

Similar Messages

MV Logs not getting purged in a Logical Standby Database

We are trying to replicate a few tables in a logical standby database to another database. Both the source ( The Logical Standby) and the target database are in Oracle 11g R1.
The materialized views are refreshed using FAST REFRESH.
The Materialized View Logs created on the source ( the Logical Standby Database) are not getting purged when the MV in the target database is refreshed.
We checked the entries in the following Tables: SYS.SNAP$, SYS.SLOG$, SYS.MLOG$
When a materialized view is created on the target database, a record is not inserted into the SYS.SLOG$ table and it seems like that's why the MV Logs are not getting purged.
Why are we using a Logical Standby Database instead of the Primary ? Because, the load on the Primary Database is too much and the machine doesn't have enough resources to support MV based replication. The CPU usage is 95% all the time. The appplication owner won't allow us to go against the Primary database.
Do we have to do anything different in terms of Configuration/Privileges etc. because we are using a Logical Standby Database as a source ?
Thanks in Advance.

We have a 11g RAC database in solaris OS where there is huge gap in archive log apply.
Thread Last Sequence Received Last Sequence Applied Difference
1 132581 129916 2665
2 108253 106229 2024
3 107452 104975 2477
The MRP0 process seems not to be working also.Almost 7000+ archives lag in standby if compared with primary database.
i suggest you to go with Incremental rollforward backups to make it SYNC, use this below link for step by step procedure.
http://www.oracle-ckpt.com/rman-incremental-backups-to-roll-forward-a-physical-standby-database-2/
Here questions.
1) Whether those archives are transported & just not applied?
2) Is in production do you have archives or backup of archives?
3) What you have found errors in alert log file?
post
SQL> select severity,message,error_code,timestamp from v$dataguard_status where dest_id=2;
4) What errors in primary database alert log file?
Also post
select     ds.dest_id id
,     ad.status
,     ds.database_mode db_mode
,     ad.archiver type
,     ds.recovery_mode
,     ds.protection_mode
,     ds.standby_logfile_count "SRLs"
,     ds.standby_logfile_active active
,     ds.archived_seq#
from     v$archive_dest_status     ds
,     v$archive_dest          ad
where     ds.dest_id = ad.dest_id
and     ad.status != 'INACTIVE'
order by
     ds.dest_id
/Also check errors from standby database.

Materialized View Logs in a logical standby database

I am trying to create materialized views based on a few tables in a logical standby database.
The target database (11g R2) where the MVs will be created is a stand-alone database.
The DB where the base tables reside is a logical standby database (11g R2).
The requirement is to do a "FAST REFRESH" of the Materialized Views.
My questions are :
1. Can I create MV logs in the logical standby DB?
2. If the answer to question no. 1 is "Yes", do I need to do anything different or configure the logical standby DB in a specific manner in order to create MV logs. From what I understand, the objects in the logical standby database are in a locked state. Is that going to be a problem ?
Any other information that might be relevant is greatly appreciated.
Thanks in advance.

HI Daniel,
I appreciate your quick response.
My choice of name may not have been ideal, however changing new to another name - like gav - does not solve the problem.
SYS@UATDR> connect / as sysdba
Connected.
SYS@UATDR>
SYS@UATDR> select name, log_mode, database_role, guard_status, force_logging, flashback_on, db_unique_name
2 from v$database
3 /
NAME LOG_MODE DATABASE_ROLE GUARD_S FOR FLASHBACK_ON DB_UNIQUE_NAME
UATDR ARCHIVELOG LOGICAL STANDBY ALL YES YES UATDR
SYS@UATDR>
SYS@UATDR> create tablespace ts_gav
2 /
Tablespace created.
SYS@UATDR>
SYS@UATDR> create user gav
2 identified by gav
3 default tablespace ts_gav
4 temporary tablespace temp
5 quota unlimited on ts_gav
6 /
User created.
SYS@UATDR>
SYS@UATDR> grant connect, resource to gav
2 /
Grant succeeded.
SYS@UATDR> grant unlimited tablespace, create table, create any table to gav
2 /
Grant succeeded.
SYS@UATDR>
SYS@UATDR> -- show privs given to gav
SYS@UATDR> select * from dba_sys_privs where grantee='GAV'
2 /
GRANTEE PRIVILEGE ADM
GAV CREATE TABLE NO
GAV CREATE ANY TABLE NO
GAV UNLIMITED TABLESPACE NO
SYS@UATDR>
SYS@UATDR> -- create objects in schema
SYS@UATDR> connect gav/gav
Connected.
GAV@UATDR>
GAV@UATDR> -- prove ability to create tables
GAV@UATDR> create table gav
2 (col1 number not null)
3 tablespace ts_gav
4 /
create table gav
ERROR at line 1:
ORA-01031: insufficient privileges
GAV@UATDR>

Logical standby database issue?

Hi,
I created a logical standby database on the same server as primary database.
then I transited the old primary DB to standby DB,
old standby DB to primary DB.
and "alter system switch logfile" in new Primary DB.
execute sql in new standby DB:
SQL> SELECT APPLIED_SCN, NEWEST_SCN FROM DBA_LOGSTDBY_PROGRESS;
APPLIED_SCN NEWEST_SCN
0
question:
the redo logs can not be applied to new standby DB,
How to solve it?
thanks
DB release:9i

Hi,
Can you upload the output of:
sqlplus> show parameter arc
from both instances, or post the init.ora parameters from both. I would like to verify your arc related parameters.
Also, did you check the alert log in the primary and standby for errors?
Thanks,
Idan.

Real-time apply cascaded logical standby database

Hi
I have a primary database orcl
Pysical standby database orcl_std
Cascaded logical standby database orcl_tri which receives archivelogs from orcl_std
Real time apply is enabled both in orcl_std (physical standby) and orcl_tri (logical standby)
When I create a table in primary orcl, I am unable to see it on orcl_tri (Although real time apply is enabled)
However, when I switch log in primary, I can see the new table on orcl_tri.
My question is, why realtime apply is not working in my scenerio ?
orcl_std : ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION USING CURRENT LOGFILE;
orcl_tri: ALTER DATABASE START LOGICAL STANDBY APPLY IMMEDIATE;
Oracle 11.2.0.3.0

Hi mseberg,
Thanks for your reply.
There is no load or network issue as I`ve just created these databases for the experiement.
I have the same output from standby and primary databases.
SQL> select bytes/1024/1024 from v$standby_log;
BYTES/1024/1024
             10
             10
             10I can see below output in standby alertlog
Fri Nov 16 08:39:51 2012
ALTER DATABASE START LOGICAL STANDBY APPLY IMMEDIATE
ALTER DATABASE START LOGICAL STANDBY APPLY (orcl)
with optional part
IMMEDIATE
Attempt to start background Logical Standby process
Fri Nov 16 08:39:51 2012
LSP0 started with pid=37, OS id=16141
Completed: ALTER DATABASE START LOGICAL STANDBY APPLY IMMEDIATE
LOGMINER: Parameters summary for session# = 1
LOGMINER: Number of processes = 3, Transaction Chunk Size = 201
LOGMINER: Memory Size = 30M, Checkpoint interval = 150M
LOGMINER: SpillScn 1953318, ResetLogScn 995548
LOGMINER: summary for session# = 1
LOGMINER: StartScn: 0 (0x0000.00000000)
LOGMINER: EndScn: 0 (0x0000.00000000)
LOGMINER: HighConsumedScn: 1955287 (0x0000.001dd5d7)
LOGMINER: session_flag: 0x1
LOGMINER: Read buffers: 16
Fri Nov 16 08:39:55 2012
LOGMINER: session#=1 (Logical_Standby$), reader MS00 pid=30 OS id=16145 sid=49 started
Fri Nov 16 08:39:55 2012
LOGMINER: session#=1 (Logical_Standby$), builder MS01 pid=39 OS id=16149 sid=44 started
Fri Nov 16 08:39:55 2012
LOGMINER: session#=1 (Logical_Standby$), preparer MS02 pid=40 OS id=16153 sid=50 started
LOGMINER: Turning ON Log Auto Delete
LOGMINER: Begin mining logfile during commit scan for session 1 thread 1 sequence 202, +DATA/orcl_std/archivelog/2012_11_15/thread_1_seq_202.349.799450179
LOGMINER: End mining logfiles during commit scan for session 1
LOGMINER: Turning ON Log Auto Delete
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 202, +DATA/orcl_std/archivelog/2012_11_15/thread_1_seq_202.349.799450179
LOGMINER: End   mining logfile for session 1 thread 1 sequence 202, +DATA/orcl_std/archivelog/2012_11_15/thread_1_seq_202.349.799450179
Fri Nov 16 08:40:04 2012
LOGSTDBY Analyzer process AS00 started with server id=0 pid=41 OS id=16162
Fri Nov 16 08:40:05 2012
LOGSTDBY Apply process AS03 started with server id=3 pid=45 OS id=16175
Fri Nov 16 08:40:05 2012
LOGSTDBY Apply process AS04 started with server id=4 pid=46 OS id=16179
Fri Nov 16 08:40:05 2012
LOGSTDBY Apply process AS01 started with server id=1 pid=42 OS id=16167
Fri Nov 16 08:40:05 2012
LOGSTDBY Apply process AS05 started with server id=5 pid=47 OS id=16183
Fri Nov 16 08:40:05 2012
LOGSTDBY Apply process AS02 started with server id=2 pid=44 OS id=16171Do you think real-time apply wasnt setup properly ?

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

Logical standby database keeps displaying ORA-16768

I have a logical standby database setup on a remote host to accept cascaded logs from a physical standby. Everything was working fine until yesterday when I get the above error and log apply services stopped. When I go into Grid Control to Data Guard I see the error and it displays the failed SQL statement which is a create index statement. I have the option of clicking the SKIP button. When I click SKIP it appears to have processed it as the error goes away but then a few minutes later the error comes back, log apply stops and the failed SQL statement is the same create index statement. I guess the Skip doesn't mean Skip, it means Retry... My question is how do I get past this? Logs have been piling up.

Hi,
Ok I applied :
SQL> ALTER DATABASE STOP LOGICAL STANDBY APPLY;
Database altered.
SQL> alter database start logical standby apply immediate;
Database altered.
SQL>
And now I received this :
ORA-16825: Fast-Start Failover and other errors or warnings detected for the database
Cause: The broker has detected multiple errors or warnings for the database. At least one of the detected errors or warnings may prevent a Fast-Start Failover from occurring.
Action: Check the StatusReport monitorable property of the database specified.
What does it mean to check the status report.....
I found this about monitorable status report !!
DGMGRL> show database 'M3RPT' 'StatusReport';
STATUS REPORT
INSTANCE_NAME SEVERITY ERROR_TEXT
* WARNING ORA-16821: logical standby database dictionary not yet loaded
DGMGRL>
What can I do ?
Thanks a lot
oldschool
Edited by: oldschool on Jun 4, 2009 2:37 AM

Create table on Logical Standby Database

Dear DBAs,
here is my situation;
1. My primary database (where the tables' owner is "ICC" having a DBA) is used for insert/update transactions.
2. The logical stdby DB (dataguard structure with MAX availability) is used to generate reports, after updating some tables owned by the same user "ICC". note that these tables are excluded from the replication.
3. The developers might need to create this kind of tables to generate another kind of reports.
The issue is that when the standby apply is enabled or disabled, the user ICC is not able to create a new table, it gives ORA-01031: insufficient privileges. note that it's not practical to ask the DBA to disable the "APPLY" at any table creation.
Do you have an idea about how to resolve.
My database is 10gR2 path.10.2.0.4.0 on Windows 2003
Thank you in advance

If you stop applying log on the logical standby you can easily create a table over there. See oracle docs. The following list shows >how to re-create a table and restart SQL Apply on that table:
>
Stop SQL Apply:
SQL> ALTER DATABASE STOP LOGICAL STANDBY APPLY;
Ensure no operations are being skipped for the table in question by querying the DBA_LOGSTDBY_SKIP view:
SQL> SELECT * FROM DBA_LOGSTDBY_SKIP;
ERROR STATEMENT_OPT OWNER NAME PROC
N SCHEMA_DDL HR EMPLOYEES
N DML HR EMPLOYEES
N SCHEMA_DDL OE TEST_ORDER
N DML OE TEST_ORDER
Because you already have skip rules associated with the table that you want to re-create on the logical standby >database, you must first delete those rules. You can accomplish that by calling the DBMS_LOGSTDBY.UNSKIP >procedure. For example:
SQL> EXECUTE DBMS_LOGSTDBY.UNSKIP(stmt => 'DML', -
schema_name => 'HR', - object_name => 'EMPLOYEES');SQL> EXECUTE DBMS_LOGSTDBY.UNSKIP(stmt >=> 'SCHEMA_DDL', -
schema_name => 'HR', - object_name => 'EMPLOYEES');
Re-create the table HR.EMPLOYEES with all its data in the logical standby database by using the >DBMS_LOGSTDBY.INSTANTIATE_TABLE procedure. For example:
SQL> EXECUTE DBMS_LOGSTDBY.INSTANTIATE_TABLE(shema_name => 'HR', -
object-_name => 'EMPLOYEES', -
dblink => 'BOSTON');
Start SQL Apply:
SQL> ALTER DATABASE START LOGICAL STANDBY APPLY IMMEDIATE;Regards.

Physical Standby database Vs. Logical Standby database

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

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

Will logical standby database be replaced by physical standby database?

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

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

Creating standby or logical standby database manually?

Hi,
I have to create 4 logical standby databases on a Linux Red Hat 64-bits server.
The primary databases reside on another Linux Red Hat 64-bits server.
The oracle database version is 10.2.0.3.
The question is as follows:
Should I create the logical standby databases manually or should I do it with the Oracle EM Grid Control?
I have read that the creation of standby databases with the Grid Control is very straightforward, but I really want to read of some of your experiences.
I have read that there are some problems in Grid Control with the test of Failover and Switchover.
Please advice.

Hi,
It all depends.
I assume you don't backup your database to tape using RMAN.
Do you backup your database to disk using RMAN?
You would need to set up NFS links from your standby server to the primary server.
For this purpose, in 9i, I made sure my disk backup ended up in <directory>/backup/<nodename>, so I could easily set up a NFS link.
If you do it manually, you need to have made a full database RMAN backup first.
Probably Grid Control is taking care of this for you.
I have done it once using database control in 10g. It is really simple, and you just have to click a few buttons and sit back.
Doing it manually is slightly more work: you need to make sure parameters are correct and you need to write a (generic) script of less than 10 lines.
You probably do have more control over it, though RMAN's duplicate database command is robust and can be restarted easily.
I can't answer your last remark.
Hth
Sybrand Bakker
Senior Oracle DBA

Prerequisite of Logical standby database ????

Hi,
We have Oracle 10g database with two physical standby databases on windows 2003 server 64 bit. we was thinking of shifting physical standby database into logical standby database.
We also look at the oracle documentation, as the link below. As we also found tables without unique logical identifier in the primary database.
http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/create_ls.htm#i76646
1 SELECT OWNER, TABLE_NAME FROM DBA_LOGSTDBY_NOT_UNIQUE
2 WHERE (OWNER, TABLE_NAME) NOT IN
3 (SELECT DISTINCT OWNER, TABLE_NAME FROM DBA_LOGSTDBY_UNSUPPORTED)
4* AND BAD_COLUMN='Y'
SQL> /
OWNER TABLE_NAME
TSMSYS SRS$
ICONNECT SYS_EXPORT_SCHEMA_01
KBC SYSTEM
KBC PLAN_TABLE
KBC AUDIT_SYSTEM
KBC SYS_EXPORT_SCHEMA_01
KASB_FIN PLAN_TABLE
ICONNECT PLAN_TABLE
UMAS PLAN_TABLE
The question is after we have found the tables without unique logical identifier in the primary database,
*1. Step 1: What to do with these tables. How to add unique logical identifier for theses table in the primary database.*
*2. Step 2: Add a disabled primary-key RELY constraint.* , Do we have to enable rely constraint to all tables in all schemas ???
Thanks in advanced.

1. Step 1: What to do with these tables. How to add unique logical identifier for theses table in the primary database.add a primary key on those tables
2. Step 2: Add a disabled primary-key RELY constraint. , Do we have to enable rely constraint to all tables in all schemas ???Document says this is for the ones returned from the query. If you are sure that uniqueness is controlled by your application on thise tables than you can add this type of constraint.
As you see most of them are plan tables for individual users. if you dont need tje, you can skip transactions for those objects by DBMS_LOGSTDBY.SKIP
hope it helps
Coskan Gundogar
http://coskan.wordpress.com

Restore/recover after failover to a Logical Standby database

I have a question about how to recover or restore back to my original environment after I failover to my Logical Standby database.
My setup is as follows: Oracle version 11.2.0.3, Non-RAC.
1. A Primary database at one location.
2. A Physical Standby database at a second location.
3. A Logical Standby database at a third location.
All three databases have Flashback Database on
All three databases are configured thru the Data Guard Broker.
All three databases has a Fast Recovery Area.
Suppose I loose my primary database (1) and my Physical Standby database (3) so I Failover to my only remaining database, the Logical Standby database (2).
What type of Databases are let after the this failover?
What are my recover/restore/Instantiate options?
The Data Guard Concepts book on 13.2.2 says how to bring the old Primary in to the Data Guard Configuration as a new Logical Standby database.
How do I get back to the original configuration above, a primary, a Physical, and a Logical Standby without having to re-create some databases?
Will Flashback database thru the Broker or Cloud Control/Grid Control rewind my databases?

Suppose I loose my primary database (1) and my Physical Standby database (3) so I Failover to my only remaining database, the Logical Standby database (2).
What type of Databases are let after the this failover?
What are my recover/restore/Instantiate options? Then forget about your current primary database, its out of network.
AFAIK
Now you will have only Physical standby & logical standby. Now you will perform failover only current standby to primary database.
So now you will have only one primary database with new incarnation, so you have to recreate a new standby database again.
The Data Guard Concepts book on 13.2.2 says how to bring the old Primary in to the Data Guard Configuration as a new Logical Standby database.
How do I get back to the original configuration above, a primary, a Physical, and a Logical Standby without having to re-create some databases?
Will Flashback database thru the Broker or Cloud Control/Grid Control rewind my databases?Check this. But not much aware of Clound control and all. Sorry for that. ;-) I'm sure Uwe/Mseberg can answer this ;-)
http://www.idevelopment.info/data/Oracle/DBA_tips/Data_Guard/DG_49.shtml#Flashing%20Back%20a%20Failed%20Primary%20Database%20into%20a%20Logical%20Standby%20Database

Asynchronous CDC on a Logical Standby database (10gR2)

Hi,
Question:
Is it possible to setup Asynchronous CDC on a Logical Standby database (10gR2)?
Background:
In our Oracle Data Warehouse environment where we need to provide up-to-the-second "operational" reporting against a Logical Standby database (10gR2 Data Guard) as the production application database owners do not permit direct reporting against the Primary database (10gR2); we also have a Data Warehouse database (10gR2) that requires more sophisticated/summary reporting which is updated at less regular intervals from the Logical Standby database.
The complication is that although the Logical Standby database will serve the purpose of a 'syncronized' version of the Primary database by giving us a current-state view of the data, we require more detailed change data capture on certain tables to audit change history between the points we extract data for the Data Warehouse.
The DBAs do not want to set-up Asynchronous CDC on the Primary database, so is it possible to setup Asynchronous CDC on a Logical Standby database?
Anyone done it before?
Any issues?
Any alternatives?
Any help would be much appreciated.
Thanks

As far as I know it is but it would be easier, and more robust, to just create a second logical standby and feed them both from the primary.
Logical Data Guard and Streams are essentially just two implementations of the same technology written by the same team of developers.

Asynchronous CDC on a Logical Standby Database

Hi,
Question:
Is it possible to setup Asynchronous CDC on a Logical Standby database (10gR2)?
Background:
In our Oracle Data Warehouse environment where we need to provide up-to-the-second "operational" reporting against a Logical Standby database (10gR2 Data Guard) as the production application database owners do not permit direct reporting against the Primary database (10gR2); we also have a Data Warehouse database (10gR2) that requires more sophisticated/summary reporting which is updated at less regular intervals from the Logical Standby database.
The complication is that although the Logical Standby database will serve the purpose of a 'syncronized' version of the Primary database by giving us a current-state view of the data, we require more detailed change data capture on certain tables to audit change history between the points we extract data for the Data Warehouse.
The DBAs do not want to set-up Asynchronous CDC on the Primary database, so is it possible to setup Asynchronous CDC on a Logical Standby database?
Anyone done it before?
Any issues?
Any alternatives?
Any help would be much appreciated.
Thanks
Tim

Autolog CDC could be one possible solution. It uses a feature of the downstream capture.
See details from the following link
http://search.oracle.com/search/search?default=true&keyword=change+data+capture&start=1&nodeid=&fid=&showSimilarDoc=true&group=Oracle+Technology+Network

Logical standby database questions

Similar Messages

Maybe you are looking for