Standby logs in logical standby

I am currently running a logical standby database in an Oracle 10gR2/Linux environment.
The primary and standby databases both seem to be running fine, however I am concerned that there seems to be an excessively large number of standby log files marked as 'CURRENT' - 127 files spanning more then 36 hrs at the time of writing.
According to the alert log of the standby database, more than 35 standby log files were deleted last time a series of files was deleted.
Can anybody suggest why there would be such a large number of standby files marked as 'CURRENT'?? Is it possible to find out why these files are required, and therefore clear any potential blockage??
Thanks

HI eceramm,
Thanks for you reply.
The last 100 line from the logical standby alert log are:
LOGMINER: End mining logfile: /opt/oracle/oradata/UATDR/onlinelog/o1_mf_4_3vpq26xd_.log
Tue May 6 08:08:41 2008
Thread 1 advanced to log sequence 8186
Current log# 1 seq# 8186 mem# 0: /opt/oracle/oradata/UATDR/onlinelog/o1_mf_1_3vpp35lp_.log
Current log# 1 seq# 8186 mem# 1: /opt/oracle/flash_recovery_area/UATDR/onlinelog/o1_mf_1_3vpp36s4_.log
Tue May 6 08:12:35 2008
RFS[4]: Successfully opened standby log 4: '/opt/oracle/oradata/UATDR/onlinelog/o1_mf_4_3vpq26xd_.log'
Tue May 6 08:12:35 2008
RFS LogMiner: Client enabled and ready for notification
Tue May 6 08:12:36 2008
RFS LogMiner: Registered logfile [opt/oracle/arch/standby/UATDR/1_6351_647020607.dbf] to LogMiner session id [1]
Tue May 6 08:12:36 2008
LOGMINER: Begin mining logfile: /opt/oracle/oradata/UATDR/onlinelog/o1_mf_4_3vpq26xd_.log
Tue May 6 08:12:36 2008
LOGMINER: End mining logfile: /opt/oracle/oradata/UATDR/onlinelog/o1_mf_4_3vpq26xd_.log
Tue May 6 08:38:42 2008
Thread 1 advanced to log sequence 8187
Current log# 3 seq# 8187 mem# 0: /opt/oracle/oradata/UATDR/onlinelog/o1_mf_3_3vpp39z0_.log
Current log# 3 seq# 8187 mem# 1: /opt/oracle/flash_recovery_area/UATDR/onlinelog/o1_mf_3_3vpp3bto_.log
Tue May 6 08:42:35 2008
RFS[6]: Successfully opened standby log 4: '/opt/oracle/oradata/UATDR/onlinelog/o1_mf_4_3vpq26xd_.log'
Tue May 6 08:42:35 2008
RFS LogMiner: Client enabled and ready for notification
Tue May 6 08:42:35 2008
RFS LogMiner: Registered logfile [opt/oracle/arch/standby/UATDR/1_6352_647020607.dbf] to LogMiner session id [1]
Tue May 6 08:42:35 2008
LOGMINER: Begin mining logfile: /opt/oracle/oradata/UATDR/onlinelog/o1_mf_4_3vpq26xd_.log
Tue May 6 08:42:35 2008
LOGMINER: End mining logfile: /opt/oracle/oradata/UATDR/onlinelog/o1_mf_4_3vpq26xd_.log
Tue May 6 09:08:42 2008
Thread 1 advanced to log sequence 8188
Current log# 2 seq# 8188 mem# 0: /opt/oracle/oradata/UATDR/onlinelog/o1_mf_2_3vpp37sc_.log
Current log# 2 seq# 8188 mem# 1: /opt/oracle/flash_recovery_area/UATDR/onlinelog/o1_mf_2_3vpp38pk_.log
Tue May 6 09:12:37 2008
RFS[7]: Successfully opened standby log 4: '/opt/oracle/oradata/UATDR/onlinelog/o1_mf_4_3vpq26xd_.log'
Tue May 6 09:12:37 2008
RFS LogMiner: Client enabled and ready for notification
Tue May 6 09:12:37 2008
RFS LogMiner: Registered logfile [opt/oracle/arch/standby/UATDR/1_6353_647020607.dbf] to LogMiner session id [1]
Tue May 6 09:12:37 2008
LOGMINER: Begin mining logfile: /opt/oracle/oradata/UATDR/onlinelog/o1_mf_4_3vpq26xd_.log
Tue May 6 09:12:37 2008
LOGMINER: End mining logfile: /opt/oracle/oradata/UATDR/onlinelog/o1_mf_4_3vpq26xd_.log
Tue May 6 09:38:43 2008
Thread 1 advanced to log sequence 8189
Current log# 1 seq# 8189 mem# 0: /opt/oracle/oradata/UATDR/onlinelog/o1_mf_1_3vpp35lp_.log
Current log# 1 seq# 8189 mem# 1: /opt/oracle/flash_recovery_area/UATDR/onlinelog/o1_mf_1_3vpp36s4_.log
Tue May 6 09:42:35 2008
RFS[4]: Successfully opened standby log 4: '/opt/oracle/oradata/UATDR/onlinelog/o1_mf_4_3vpq26xd_.log'
Tue May 6 09:42:35 2008
RFS LogMiner: Client enabled and ready for notification
Tue May 6 09:42:35 2008
LOGMINER: Begin mining logfile: /opt/oracle/oradata/UATDR/onlinelog/o1_mf_4_3vpq26xd_.log
Tue May 6 09:42:35 2008
RFS LogMiner: Registered logfile [opt/oracle/arch/standby/UATDR/1_6354_647020607.dbf] to LogMiner session id [1]
Tue May 6 09:42:35 2008
LOGMINER: End mining logfile: /opt/oracle/oradata/UATDR/onlinelog/o1_mf_4_3vpq26xd_.log
Tue May 6 10:08:41 2008
Thread 1 advanced to log sequence 8190
Current log# 3 seq# 8190 mem# 0: /opt/oracle/oradata/UATDR/onlinelog/o1_mf_3_3vpp39z0_.log
Current log# 3 seq# 8190 mem# 1: /opt/oracle/flash_recovery_area/UATDR/onlinelog/o1_mf_3_3vpp3bto_.log
Tue May 6 10:12:37 2008
RFS[6]: Successfully opened standby log 4: '/opt/oracle/oradata/UATDR/onlinelog/o1_mf_4_3vpq26xd_.log'
Tue May 6 10:12:37 2008
RFS LogMiner: Client enabled and ready for notification
Tue May 6 10:12:37 2008
RFS LogMiner: Registered logfile [opt/oracle/arch/standby/UATDR/1_6355_647020607.dbf] to LogMiner session id [1]
Tue May 6 10:12:37 2008
LOGMINER: Begin mining logfile: /opt/oracle/oradata/UATDR/onlinelog/o1_mf_4_3vpq26xd_.log
Tue May 6 10:12:37 2008
LOGMINER: End mining logfile: /opt/oracle/oradata/UATDR/onlinelog/o1_mf_4_3vpq26xd_.log
Tue May 6 10:38:43 2008
Thread 1 advanced to log sequence 8191
Current log# 2 seq# 8191 mem# 0: /opt/oracle/oradata/UATDR/onlinelog/o1_mf_2_3vpp37sc_.log
Current log# 2 seq# 8191 mem# 1: /opt/oracle/flash_recovery_area/UATDR/onlinelog/o1_mf_2_3vpp38pk_.log
Tue May 6 10:42:35 2008
RFS[7]: Successfully opened standby log 4: '/opt/oracle/oradata/UATDR/onlinelog/o1_mf_4_3vpq26xd_.log'
Tue May 6 10:42:35 2008
RFS LogMiner: Client enabled and ready for notification
Tue May 6 10:42:35 2008
RFS LogMiner: Registered logfile [opt/oracle/arch/standby/UATDR/1_6356_647020607.dbf] to LogMiner session id [1]
Tue May 6 10:42:35 2008
LOGMINER: Begin mining logfile: /opt/oracle/oradata/UATDR/onlinelog/o1_mf_4_3vpq26xd_.log
Tue May 6 10:42:35 2008
LOGMINER: End mining logfile: /opt/oracle/oradata/UATDR/onlinelog/o1_mf_4_3vpq26xd_.log
Tue May 6 11:08:41 2008
Thread 1 advanced to log sequence 8192
Current log# 1 seq# 8192 mem# 0: /opt/oracle/oradata/UATDR/onlinelog/o1_mf_1_3vpp35lp_.log
Current log# 1 seq# 8192 mem# 1: /opt/oracle/flash_recovery_area/UATDR/onlinelog/o1_mf_1_3vpp36s4_.log
Tue May 6 11:12:36 2008
RFS[4]: Successfully opened standby log 4: '/opt/oracle/oradata/UATDR/onlinelog/o1_mf_4_3vpq26xd_.log'
Tue May 6 11:12:36 2008
RFS LogMiner: Client enabled and ready for notification
Tue May 6 11:12:36 2008
LOGMINER: Begin mining logfile: /opt/oracle/oradata/UATDR/onlinelog/o1_mf_4_3vpq26xd_.log
Tue May 6 11:12:36 2008
RFS LogMiner: Registered logfile [opt/oracle/arch/standby/UATDR/1_6357_647020607.dbf] to LogMiner session id [1]
Tue May 6 11:12:36 2008
LOGMINER: End mining logfile: /opt/oracle/oradata/UATDR/onlinelog/o1_mf_4_3vpq26xd_.log
Thanks for your interest
Gavin

Similar Messages

Physical standby database to Logical standby

Can I convert a physical standby database to Logical standby,

Go Through Below link
>>>Can you convert a Logical standby to a Physical Standby?

Skip archive log on logical standby

hi ,
I want to skip archive log from nmber 1150 to 1161 on logical standby dtbs.
I knw , we can skip ddl , dml on logical standby .
How can archive this ??
(oracle 10g entreprise edition )

Hello;
I do not believe this is an option. The closest to this would be "applying modifications to specific tables"
See :
9.4.3 Using DBMS_LOGSTDBY.SKIP to Prevent Changes to Specific Schema Objects
Data Guard Concepts and Administration 10g Release 2 (10.2) B14239-05
While this is not the answer you want the skip Archive would create a Gap and cause many other issues you don't want.
Best Regards
mseberg

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

Logical Standby databases

Hi,
When we say "Logical Standby Databases are logically identical to primary databases although the physical organization and structure of the data can be different." what does it exactly means?
Does it mean that in logical standby tablespace name, schema name, table name, column names etc can be different and still has the same data as primary?
Does it mean that we can exclude indexes and constraints as present in primary?
Only the data should match with primary word by word, value by value?
I am asking this as i have never worked in a logical standby database but i seriously want to know.
Please answer.
Regards,
SID

Physical standby differs from logical standby:
Physical standby schema matches exactly the source database.
Archived redo logs and FTP'ed directly to the standby database which is always running in "recover" mode. Upon arrival, the archived redo logs are applied directly to the standby database.
Logical standby is different from physical standby:
Logical standby database does not have to match the schema structure of the source database.
Logical standby uses LogMiner techniques to transform the archived redo logs into native DML statements (insert, update, delete). This DML is transported and applied to the standby database.
Logical standby tables can be open for SQL queries (read only), and all other standby tables can be open for updates.
Logical standby database can have additional materialized views and indexes added for faster performance.
Installing Physical standbys offers these benefits:
An identical physical copy of the primary database
Disaster recovery and high availability
High Data protection
Reduction in primary database workload
Performance Faster
Installing Logical standbys offer:
Simultaneous use for reporting, summations and queries
Efficient use of standby hardware resources
Reduction in primary database workload
Some limitations on the use of certain datatypes

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 ?

Time difference between physical and logical standby

Hi,
I have just been tasked on getting some info and setting up dataguard for some users for read-only/reporting purpose.
The 3 questions I am being asked are:
1. What is the time difference in applying changes from primary to physical standby compare to logical standby
2. What is the overhead maintenance of having a standby database?
3.What latency is involved?
I will be glad to have your input on this.
Thanks

Hi,
Physical Standy where its a read only DB.
Logs are applied.
Logical Standy where it can be Read / Write DB and the logs are applied in terms of SQL Statements.
Thanks & Regards,
Pavan Kumar N

Logical Standby recover with RMAN

Hi All,
I have a test environment with Primary DB Server, Physical Standby and Logical Standby.
The Logical Standby DB (cur_log_stdb) is backed up every evening by RMAN and I have a question:
If I recover my Logical Standby DB from backup and switch replication to new Logical Standby DB (new_log_stdb) it will work or not?
My steps e.g.:
1. Make a new server for my new_log_stdb and repair structure of catalogs;
2. Repair listener.ora and tnsnames.ora files from cur_log_stdb to new_log_stdb;
3. Restore DB with RMAN from backup to new_log_stdb;
4. On cur_log_stdb execute "alter database stop logical standby apply";
5. Change a DNS name from cur_log_stdb to new_log_stdb;
6. On new_log_stdb execute "alter database start logical standby apply immediate";
I'm not sure that archivelogs will apply to the new_log_stdb for period since rman backup was created.
But if this plan won't work how can I restore Logical Standby DB from RMAN backup and resume replication from Primary?
Configuration:
Oracle Linux 6.4
Oracle Database 11.2.0.3
Primary and Physical with Data Guard

Hello;
The only way to know for sure is to test it. You are asking somebody you don't know to confirm a recovery test for you. You have to perform the test yourself to be certain.
If your plan does not work you can always rebuild the Standby.
Best Regards
mseberg

Configuration of the Physical & Logical standby servers on the same machine

I've encoutered a problem to connect to one of the standby servers .
I created a DataGuard in 10.2. Primary on 1 machine, 1 physical standby and 1 logical standby on another machine (both phy and logical in same machine)
I first created a primary then a physical standby. I've got no problem at all.
But when I created a logical standby server on the same machine with the physical then I could not connect to both phy and logical . I can connect to either one of them.
According to DataGuard setup, the db_name must be the same in primary and all standby servers. This is fine when each of the primary or the standby installed in a separate machine.
The db_name of the physical = rolex
The db_name of the logical = rolex
When we have more than one instance in the same machine, we just set the ORACLE_SID = db_name ( or instance), then connect to it.
If I connect to the physical, then I try to connect to the logical, it goes to the physical or vice versus.
Does anyone have the solution ?
QN

DB_UNIQUE_NAME parameter will be the seperator.
give DB_UNIQUE_NAME parameters different names and set ORACLE_SID with DB_UNIQUE_NAME name you gave
DB_NAME is the primary instances database name DB_UNIQUE_NAME is given for standby instances database name

How to Create Primary DB and Physical/Logical Standby DB on the same host?

Now I encounter a issue. I want to create one Primary DB and one Physical standby DB and one Logical standby DB on the same host.
Create this env on the same host aims to test whether we can using EM Patching DP to apply patches on Primary/Physical/Logical DB successfully.
I try to setup this env but fails. I want to know more related issues about create Primary DB /Physical DB/Logical DB on the same host and how to configure between them.
Below steps is my try:
1. Create Primary DB on the /scratch/primary_db
2. Create Physical Db software only on the /scratch/physical_db
3. Create Logical Db software only on the /scratch/logical_db
4. Using EM Wizard to create physical standby database and logical standby database, and these two targets can show up on the "All Targets" Page.
5. But when using EM Patching DP, it fails and the reason is the listener of physical and logical db cannot configured well.
Issues:
So I want to know about how to configure physical db and logical db's listener using EM or manually?
If the listener name of Primary Db is LISTENER and the port is 1521,and the listener.ora is under the /scratch/primary_db/network/admin directory, then how to config physical db and logical db's listener's name and port?

Hi,
As this a test case then you need to create two more listener for each Oracle Home (/scratch/physical_db & /scratch/logical_db) make sure that they have different names and ports.
Then add the new listeners manually using GC?
Try it and let me know
Regards
Amin

Problem while mining archivelog in Logical Standby Database

I have configure Data Guard with one Primary database, one physical standby and one logical standby database; redo are applied correcly on the physical standby database but on the logical standby database when logminer begin mining logfile it encounter this errors :
ORA-00600 internal error code, arguments : [kpotcgah-7],[64],[X4],[],[],[],[],[]
ORA-12801 error signaled in parallel query server P003
ORA-07445
ORA-12805 parallel query server died unexpectedly

Unfortunately ORA-00600 errors are beyond the scope ot this forum, as they require tools and source code available only at Oracle Support. The only directions you most probably will get here is to issue a Service Request. Oracle support will, among other things, ask you if you are at the latest available patch for your platform.
Good luck.

Status of Logical Standby In case of Failover to Physical Standby

I am using oracle 9.2.0.8 database . I have one logical and one physical standby database in place. If I perform failover to my physical standby, will my logical standby still continue to work with new primary database?

Thank you for your kind reply.
I performed failover to my physical standby and now archives are going on my logical standby from new primary but changes are not getting applied on my logical standby database.
when i tried to register the logical logfile from new primary on my logical standby i am getting following error.
SQL> ALTER DATABASE REGISTER LOGICAL LOGFILE 'E:\orcl1\stdb\archives\TESTDBT001S00001.ARC';
ALTER DATABASE REGISTER LOGICAL LOGFILE 'E:\orcl1\stdb\archives\TESTDBT001S00001.ARC'
ERROR at line 1:
ORA-01287: file is from a different database incarnation

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

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

Second logical standby

Hello,
i've this architecture: 1 production database, 1 physical standby, and 2 logical standby. One of the logical standby must now be rebuild, and my question is: i have already play the DBMS_LOGSTDBY.BUILD procedure for the old logical standby that i have to rebuild, do i have to replay this procedure in my rebuild script?
Thanks for suggestion

In the new script most of the primary related issues you can avoid as they are set during the first logical standby creation.

Standby logs in logical standby

Similar Messages

Maybe you are looking for