Oracle9i Data Guard - Filtering for a Logical Standby DB?

Hello All
1) When using Oracle9i data guard with a logical standby database is it possible to "screen" the sql statements that are executed? For example if I don't want any "delete" commands to be replicated on the standby box can I filter them out?.
2) Are there any unlogged transactions that don't get "replicated"? Can I get a list of these commands/transactions?
Any insight would be greatly appreciated
Thanks in advance
...anik

I want to make db_name=boston, not keep it as the same as primary=chicago. Is this valid configuration?NO. DB_NAME must be the same ("chicago") at both sites. The Standby will be using a different DB_UNIQUE_NAME (e.g. "boston") and can be using a different Instance name / SID (e.g. "boston").
can I rename datafiles Yes. The database file names can be changed.
If I don't use primary DB backup. Instead, I copy all datafiles, redo_log files (no control files) to standbyWhat is the difference between the first sentence (a backup of the primary) and the second sentence (a copy of the primary) ? A Copy is a backup.
Are you intending to differentiate between an RMAN Backup and a User-Managed (aka "scripted") backup ?
Normally, for DataGuard, tou can use non-RMAN methods to copy the database but there's no value add in this.
You'd still have to setup DataGuard ! (and I wonder if you'd have complications setting up Active DataGuard).
But remember that you MUST create the Standby controlfile from the Primary and copy it over to your Standby -- particularly as you are planning to use DataGuard. This is not created by 'alter database backup controlfile to trace' , but by 'ALTER DATABASE CREATE STANDBY CONTROLFILE AS 'filename''
Hemant K Chitale

Similar Messages

Oracle data guard configuration for primary and standby db_name

I am working on configuring an active data guard for one primary DB and one standby DB. I have a few questions:
1. Can I use different db_name, db_unique_name and instance_name for primary and standby. For example: primary(db_name, db_unique_name and instance_name)=chicago. When I create standby DB with Rman backup and copy of pfile and control file from primary DB or use Grid control to create standby database. Oracle document or Grid control all keep standby db_name=chicago. Only make standby db_unique_name and instance_name=boston. Due to my application system condition, I want to make db_name=boston, not keep it as the same as primary=chicago. Is this valid configuration?
2. In primary datafiles, application system generate datafile name like this: hr_chicago_01.dbf, fn_chicago_01.dbf. When I move datafiles to standby server, if I plan to use db_name=boston for standby DB, can I rename datafiles as
hr_boston_01.dbf, fn_boston_01.dbf? In this way, datafile name match up with db_name. but I will create standby log group and members on primary and standby identically. If in future switching over, DB will not have problems.
3. If I don't use primary DB backup. Instead, I copy all datafiles, redo_log files (no control files) to standby. Then "alter database backup controlfile to trace" from promary and also " create pfile='/xxx/initSTANDBY.ora' from primary. Then modify init.ora and controlfile. Then run control.sql to bring standby DB up. After that, configure redo log shipping and apply with data guard or SQL. Is this a acceptable way to create physical standby DB?
Please advise your comments. Thanks in advance.

I want to make db_name=boston, not keep it as the same as primary=chicago. Is this valid configuration?NO. DB_NAME must be the same ("chicago") at both sites. The Standby will be using a different DB_UNIQUE_NAME (e.g. "boston") and can be using a different Instance name / SID (e.g. "boston").
can I rename datafiles Yes. The database file names can be changed.
If I don't use primary DB backup. Instead, I copy all datafiles, redo_log files (no control files) to standbyWhat is the difference between the first sentence (a backup of the primary) and the second sentence (a copy of the primary) ? A Copy is a backup.
Are you intending to differentiate between an RMAN Backup and a User-Managed (aka "scripted") backup ?
Normally, for DataGuard, tou can use non-RMAN methods to copy the database but there's no value add in this.
You'd still have to setup DataGuard ! (and I wonder if you'd have complications setting up Active DataGuard).
But remember that you MUST create the Standby controlfile from the Primary and copy it over to your Standby -- particularly as you are planning to use DataGuard. This is not created by 'alter database backup controlfile to trace' , but by 'ALTER DATABASE CREATE STANDBY CONTROLFILE AS 'filename''
Hemant K Chitale

Data guard difference in primary and standby OS.

Dear All,
We are planning to setup a data guard in our landscape. But my question what are the prerequisites should be consider before getting in to that.
Like my environment -
1. The primary database is running with Red hat Linux 5 - IBM 64 bit and the standby database is Redhat Linux 2.1 IBM 32 bit system.
2. The primary database is running with Red hat Linux 5 - IBM 64 bit with oracle 8.1.7.4 and the standby database is
Linux 2.1 IBM 32 bit system with oracle 10g.
Is the above thing is possible? or we should maintain the same OS / DB combination in the data guard setup.
I am following the below link.
http://download-west.oracle.com/docs/cd/B19306_01/server.102/b14239/standby.htm#i72053
If anyone have thoughts on this please do advice me.
Regards
Vijay

Please explain to us what exactly you want to do with the standby database?
According to note 105047 - Support for Oracle functions in the SAP environment
12. Data Guard
You can use "Physical Standby", but Oracle provides support (not SAP).
You cannot use "Logical Standby"
So in short, no a data guard configuration with Red hat Linux 5 - IBM 64 bit with oracle 8.1.7.4 to Linux 2.1 IBM 32 bit system with oracle 10g is NOT possible.
Regards, Michael

Data guard setup for 2 node RAC primary to 2 node RAC standby

Hi All,
I am going to setup data guard for 2 node RAC primary to 2 node RAC standby on Oracle 10.2.0.4. in AIX5L.
Can you please provide the document on the above setup which is having all the steps (details).
Also, the documents on different scenarios like
1) If one node of standby goes down, how the redo logs will be applied. IS there any problem?
2) If both nodes of standby are failed, how to reciver them?
3) If one node of primary fails, is there any issue?
4) If two nodes of primary fails, is there any issue?
Thanks in advance,
Mahi

Have a look at the following location, you may find some similar documents:
http://www.oracle.com/technology/deploy/availability/htdocs/maa.htm
By
http://www.oraxperts.com

Data Guard configuration for RAC database disappeared from Grid control

Primary Database Environment - Three node cluster
RAC Database 10.2.0.1.0
Linux Red Hat 4.0 2.6.9-22 64bit
ASM 10.2.0.1.0
Management Agent 10.2.0.2.0
Standby Database Environment - one Node database
Oracle Enterprise Edition 10.2.0.1.0 Single standby
Linux Red Hat 4.0 2.6.9-22 64bit
ASM 10.2.0.1.0
Management Agent 10.2.0.2.0
Grid Control 10.2.0.1.0 - Node separate from standby and cluster environments
Oracle 10.1.0.1.0
Grid Control 10.2.0.1.0
Red Hat 4.0 2.6.9-22 32bit
After adding a logical standby database through Grid Control for a RAC database, I noticed sometime later the Data Guard configuration disappeared from Grid Control. Not sure why but it is gone. I did notice that something went wrong with the standby creation but i did not get much feedback from Grid Control. The last thing I did was to view the configuration, see output below.
Initializing
Connected to instance qdcls0427:ELCDV3
Starting alert log monitor...
Updating Data Guard link on database homepage...
Data Protection Settings:
Protection mode : Maximum Performance
Log Transport Mode settings:
ELCDV.qdx.com: ARCH
ELXDV: ARCH
Checking standby redo log files.....OK
Checking Data Guard status
ELCDV.qdx.com : ORA-16809: multiple warnings detected for the database
ELXDV : Creation status unknown
Checking Inconsistent Properties
Checking agent status
ELCDV.qdx.com
qdcls0387.qdx.com ... OK
qdcls0388.qdx.com ... OK
qdcls0427.qdx.com ... OK
ELXDV ... WARNING: No credentials available for target ELXDV
Attempting agent ping ... OK
Switching log file 672.Done
WARNING: Skipping check for applied log on ELXDV : disabled
Processing completed.
Here are the steps followed to add the standby database in Grid Control
Maintenance tab
Setup and Manage Data Guard
Logged in as sys
Add standby database
Create a new logical standby database
Perform a live backup of the primary database
Specify backup directory for staging area
Specify standby database name and Oracle home location
Specify file location staging area on standby node
At the end am presented with a review of the selected options and then the standby database is created
Has any body come across a similar issue?
Thanks,

Any resolution on this?
I just created a Logical Standby database and I'm getting the same warning (WARNING: No credentials available for target ...) when I do a 'Verify Configuration' from the Data Guard page.
Everything else seems to be working fine. Logs are being applied, etc.
I can't figure out what credentials its looking for.

DR for a logical standby

Friends,
Oracle version 10.2.0.4:
On the primary site, we have one non-rac primary database P1. We will create a logical standby (L1) on primary site to be used for reporting. This logical standby L1 will have its own additional indexes and materialized views.
On the Disaster recovery site, which is at a remote location, a physical standby P2 will protect the primary database P1. What should be done such that the logical database L2 on the disaster recovery site remains in sync with L1? Also, if we were to lose the primary site, what should be done such that L2 gets fed by P2 after P2 takes over as primary?
Is such a configuration possible?
thanks for any thoughts.

Hi,
If you setup a physical standby L2, which will be sync with L1 this will be a cascaded configuration.
P1 --> L1 (logical) --> L2 (physical)
But this configuration is not supported. (It used to be, but not now... ) From my blog post about cascade standby databases: (http://emrebaransel.blogspot.com/2010/08/dataguard-cascade-standby-database.html)
The Layer1 standby database cannot be a logical standby where Layer2 can be. (Oracle mentions about Layer1 logical standby configuration on 10gR2 doc, and indicates that a Layer1 logical standby will generate and transmit redo information which won’t be identical with the one between primary and Layer1 standby. As a result "Layer2 physical standby databases created from a logical standby database will be a block-for-block copy of the logical standby database and a logical copy of the original primary database.”
But it is indicated that information in Metalink bulletin 409013.1 replaces Appendix E Cascaded Destinations, of Oracle Data Guard Concepts and Administration 10g Release 2 document. Metalink bulletin 409013.1 and 11gR1 doc says that “A logical standby database cannot forward redo to another standby database” and specifies that Layer1 logical standby configuration is not supported.
A logical standby database cannot forward redo to another standby database
At the end, this means you're not able to keep a copy of L1 logical standby.
But you can have this:
P1 --> P2 (physical) --> L2 (logical)
L2 will be sync with primary (P1). In a case of disaster it will still be sync with new primary (P2). But you need to maintain its own additional indexes and materialized views.

Database Guard enabled error in Logical standby database

Hi All,
In my logical standby db i have a schema REP which is not present in Primary database, but even then i am getting ora-16224 Database Guard enabled error when ever i try DDL and DML operation on REP schema objects in Logical standby db.
even when i compile sys object i am getting the same error. when i set database data guard status to NONE, i don't get error, but my requirement is to keep database data guard status in STANDBY
My database version is 11.2.0.3.0.
Please help in resolving this error.
Thanks,
Mukesh

>In my logical standby db i have a schema REP which is not present in Primary database,
not possible

Best Way to setup a disaster Recovery site for a logical standby database

I have a logical standby DB (L1DB) as a reporting db on the same machine as the primary (P1DB). We are planning on building a disaster recovery site with similar hardware and potentially have disk mirroring of atleast the redo log files.
The DR site can hold an additional physical standby (S1DB) for the primary (P1DB). I am trying to understand what would be the best way to setup the Disaster Recovery site for the L1DB logical stdby. Ideally, when the disaster happens, and I no longer have P1DB and L1DB, I should be able to switch to S1DB as the new primary. But how do I setup to have a L2DB that takes the place of L1DB and has its contents and can be setup as a logical standby of S1DB?

If you already setup one logical standby, then you know how it works, so not sure what question you are asking ?
Personally I would setup L2DB as a standby of the original primary P1DB. Having downstream standby databases complicates things, and adds additional lag between primary transaction time and L2DB apply.

Data file time stamp on Logical Standby

Dear All,
My Logical Standby Database that is Oracle 10gR2 on Wondows 2003 Server is fully synced with the production database.
If i query number of records on Logical Standby they are the same as on production.
And when i query applied_time from dba_logstby_progress view, there is hardly a difference of second since I have configured real time apply.
BUT the date and time stamp of my data files and index files on Logical Standby is more than 12 days old.
I am confused, why this its like this. Is there any workout to fix that? Is it normal? or what?
Kindly help.
Regards, Imran

misterimran wrote:
Dear All,
My Logical Standby Database that is Oracle 10gR2 on Wondows 2003 Server is fully synced with the production database.
If i query number of records on Logical Standby they are the same as on production.
And when i query applied_time from dba_logstby_progress view, there is hardly a difference of second since I have configured real time apply.
BUT the date and time stamp of my data files and index files on Logical Standby is more than 12 days old.
I am confused, why this its like this. Is there any workout to fix that? Is it normal? or what?
Kindly help.
Regards, Imran
Is there any workout to fix that?
Who said it is something to "fix"?

Data Guard Archive Latency with Physical Standby

I'm trying to get a latency number that tells me how long it took ARCH to move an archive file from the Primary instance to the physical standby instance and "apply it". I see lots of numbers but I can't make heads or tails of them. Does a metric such as this exist in a log file, a V$ view, or can it possibly be calculated or extrapolated?
Thanks
Steve ([email protected])

This is how calculated the same in a test env.
1. stop standby listener
2. shutdown standby
3. perform a data load (import)
4. start the standby listener. This will cause arch files to be shipped to the standby. Monitor the files being shipped and time it
5. start the standby db in recovery mode
6. repeatedly execute the following query while timing the log apply services:
SELECT SEQUENCE#,APPLIED FROM V$ARCHIVED_LOG ORDER BY SEQUENCE#;

Can I use data guard to create a RAC standby database for a non RAC primary

Hi,
we need to RAC our production database but the normal methods will mean a long outage. It is possible to create a standby as a single node RAC database and when ready do a graceful failover to the standby database and open it for business. The next step would be to create another RAC node from this on the original server.
servers are already cluster aware, using ASM etc
Oracle 10.2

Yes, you will be able to setup RAC stnadby for a non-RAC Primary. For primary it just needs a available destination for redo shipping it doesn't matter whether it's RAC enabled or not. And ofcourse you are using 10.2 anyway only one node will be running MRP and that is too in standby mount mode.
However since you have are using You may follow below sequence.
1. Setup a new standby as RAC enabled.
2. Perform a switchover.
3. Shutdown the Old primary (which is standby now).
4. Install CRS and RDBMS on the old primary and it's new node.
5. Modify the cluster_database=TRUE and cluster_database_instances=<required number of instances>.
With above modification mount the standby database in standby mode and start MRP.
6. Introduce the database and instances to the OCR using SRVCTL add command.
7. Once you your database is synchronized with Primary do a switchover.
9. Now you can repeat step 3 to 6 on the other site too. <- if you need your secondary site to be RAC enabled too
10. Finally both the sites should be RAC enabled.
Hope this is helpful!!!
Thanks,
Asif Haliyal

Data Guard - Steps to install Physical standby database in an RHEL 5.6 x86

HI Team,
I need to install Physical standby database in a OS installed from factory with most basic packages. Please find the info in detail
Standby Server :
Database Version : 10g Release 2
Operating System : Red Hat Enterprise Linux Server release 5.6 (Tikanga) , RHEL 5.6 x86_64
swartis.dc$ free -m
total used free shared buffers cached
Mem: 34158 33847 311 0 558 28367
-/+ buffers/cache: 4921 29237
Swap: 10001 63 9937
- Things i need to validate in the PROD server. Eg : Are the prod db version & standby db version should be the same, Do the OS need to be same ............ETC
- Basic Linux rpm required for standby server & any other pre-requisites required at standby server
- Verify connectivity speed btw servers to decide log file size
- Please give me more detailed steps , where i need to start the steps in installation of Physical standby database.
Thanks in advance.
-- Rakesh
Edited by: Rakesh on Jan 10, 2012 8:23 AM

Hello again;
Sorry for the Delay.
To this question "Do i need to install 10.2.0.2.0 ORACLE_HOME & on top of it apply 10.2.0.3.0 patchset.?"
Yes.
All my Oracle 10 installs started with 10.2.0.1 and then I patched up from there. If I remember correctly 10.2.0.1 may bark on Red Hat 5.
You can work around this by reviewing this file :
/etc/redhat-releaseSave whatever is in there somewhere and replace it with :
redhat-3After the install put back what was there and get rid of the "redhat-3".
I extra RPM's I used were :
rpm -ivh kernel-headers-2.6.18-164.el5.x86_64.rpm
rpm -ivh compat-libstdc++-33* libaio-devel*.x86_64.rpm
rpm -ivh elfutils-libelf-devel*.x86_64.rpm glibc-devel-2* gcc-4*.x86_64.rpm gcc-c++-4*.x86_64.rpm libstdc++-devel-4*.x86_64.rpm glibc-headers*.x86_64.rpm libgomp*.x86_64.rpm
rpm -ivh compat-libstdc++-33* libaio-devel*.x86_64.rpm
rpm -ivh sysstat*I searched my Red Hat Disks before hand and ran the RPM commands as shown. Adjust as needed.
To verify that the required packages have been installed on your system, run the following command :
pm -q --queryformat "%{NAME}-%{VERSION}-%{RELEASE} (%{ARCH})\n" binutils \
compat-libstdc++-33 elfutils-libelf elfutils-libelf-devel gcc gcc-c++ glibc \
glibc-common glibc-devel-2.5 libaio libaio-devel libgcc libstdc++ libstdc++-devel \
make sysstatThis document is for Oracle 11, but the OS part should be the same.
http://www.visi.com/~mseberg/installing_oracle_11g_r2_64.html
Currently I have 3 servers running both Oracle 10 and 11 ( In different homes ) using this OS.
I have used Oracle 11 document with Oracle 10 also : ( Better once you are setup and a great standby recovery document )
http://www.visi.com/~mseberg/duprman2.html
Best Regards
mseberg

Logical Standby Creation Problems "Create STatus Unknown"

We are using Grid Control 10.2.0.3 on Oracle 10.2..0.3 databases, Windows 2003 sp2 machines.
We have a primary and fsfo physical standby working properly. We went to create a logical standby on a separate server and had problems. it turned out that the listener on the server was not discovered on the target. we fixed that problem and finished the creation of the logical standby and it seems to be functioning properly now.
However, the status on the data guard page for the logical standby shows Create Status Unknown and we are unable to proceed on to create an additional standby database for other purposes. We have tried removing the logical standby target and re-discovering it but status still shows Create Status Unknown.
Is there any way to clear this status without having to drop the logical standby and completely recreate it.

The status on the agent shows it uploading successfully.
We resolved the issue by removing the logical standby from the configuration and selecting to retain the log apply. We then re-added the standby selecting to manage an existing standby database and the status went to normal.

Sql Developer and Data Guard enabled instance

I have version 1.1.2.25 SQL Developer and when I try to connect to Oracle 10gR2 instance which is data guard enabled and its logical standby it spits few message, and then connects, but data is not visible from any table.
Is there any way to see data and other code while in logical standby instance which only in read only mode?
Thanks.

This problem came when I tried to connect to Oracle
instance which is a logical standby in data guard
setup. Eventually connection is made and then you can
not see any object.
In logical standby database its suppose to be read
only and should be available for query.
In TOAD you can see every thing and when you want to
make any change ,it spits an error and wouldn't allow
you to make any change.
My question was, why SQL Developer is not showing the
objects in the list and its contains.Perhaps we could help you if you told us what the error was.

Logical Standby Data Consistency issues

Hi all,
We have been running a logical standby instance for about three weeks now. Both our primary and logical are 11g (11.1.0.7) databases running on Sun Solaris.
We have off-loaded our Discoverer reporting to the logical standby.
About three days ago, we started getting the following error message (initially for three tables, but from this morning on a whole lot more)
ORA-26787: The row with key (<coulmn>) = (<value>) does not exist in table <schema>.<table>
This error implies that we have data consistency issues between our primary and logical standby databases, but we find that hard to believe
because the "data guard" status is set to "standby", implying that schemas' being replicated by data guard are not available for user modification.
any assistance in this regard would be greatly appreciated.
thanks
Mel

It is a bug : Bug 10302680 . Apply the corresponding Patch 10302680 to your standby db.

Oracle9i Data Guard - Filtering for a Logical Standby DB?

Similar Messages

Maybe you are looking for